Feature Request - Fail SPF record validation on too many SPF lookups

5 Commentaires

  • Henrik Schack

    Tools already exist for such tasks, here is the one I always use: 
    https://dmarcian.com/spf-survey/

    0
  • Kay

    Henrik, maybe there is a little bit of confusion. There are tools out there, but that goes for the default SPF check as well.

    It's about the meaning of validation and information. Zendesk right now validates a record as valid, even though it's should be invalid.

    The underlying problem i.m.o. right now is in organizations, it's nobodies responsibility, even though it should be someones responsibility. And comes to light when there are issues with it. With a relatively simple fix, Zendesk can protect accounts from this behavior. This can easily be fixed with this check.

    0
  • Henrik Schack

    Yes and no.

    Example:

    You configure Zendesk and everything reports OK.

    2 weeks later someone from marketing has something added to the SPF record (new email tool)

    You then get an error from Zendesk, how would that make sense?

    This is a task for the person managing DNS, always always always test things.

    0
  • Henrik Schack

    But soon, when Zendesk begins to use Amazon SES for email delivery, this issue will be history, you will no longer have anything Zendesk related in the SPF record at the root of your domain.

     

    0
  • Kay
    Example:
    You configure Zendesk and everything reports OK.
    2 weeks later someone from marketing has something added to the SPF record (new email tool)
    You then get an error from Zendesk, how would that make sense?

    It makes sense, if I don't get that notification it means messages might not be delivered.

    This is a task for the person managing DNS, always always always test things.

    We agree on what it should be. Experience learns us, that this is not always the case. And thus I want to be ahead of any kind of changes made that might impact 'our' system.

    I am not sure, maybe the reason I am asking for it, is seeing that the person responsible for DNS is not the same person responsible for Zendesk. However making a change in the first, highly effects the second.

    0

Veuillez vous connecter pour laisser un commentaire.

Réalisé par Zendesk