Settings and activity
7 results found
-
1 vote
Japs van der Zandt
shared this idea
·
-
29 votes
Japs van der Zandt
supported this idea
·
-
1 vote
Japs van der Zandt
supported this idea
·
-
4 votes
Japs van der Zandt
supported this idea
·
-
3 votes
An error occurred while saving the comment
Japs van der Zandt
supported this idea
·
-
1 vote
An error occurred while saving the comment
Japs van der Zandt
commented
Correct me if I'm wrong, but I believe this is not a problem on Mailjet's end.
When a receiving server forwards the message to an external recipient, they have 2 options to ensure they are not spoofing the Mailjet email. They should either rewrite the message to conform with DMARC. Or perform an ARC seal themselves.If the message is transferred internally, according to RFC5322/RFC7489 the responsibility to ensure this does not break authentication falls on the forwarding server.
-
6 votes
Japs van der Zandt
supported this idea
·
This should be a no brainer. Either implement best-practice 2 (or 3) keys so rotation is easy and painless. Or hold all email until propagation is complete, as RFC 6376 section 5.2 states.