3 ms·
I've added a new acronym to my personal mail servers over the weekend: SRS (fixes SPF when doing basic forwarding to another email address, e.g.: to gmail). An
by emilburzo 10y ago
I've added a new acronym to my personal mail servers over the weekend: SRS (fixes SPF when doing basic forwarding to another email address, e.g.: to gmail).
And now I'm not even sure that was a correct move, since Gmail explicitly states[1] that you shouldn't change the envelope sender (which SRS does).
[1] - https://support.google.com/mail/answer/175365?hl=en https://support.google.com/mail/answer/175365?hl=en
- walrus01 10y agoAnything that breaks DKIM so the signature coming from your SMTPd is no longer valid, not matching the public key published in your DNS records, will make your mail MUCH more likely to be flagged as spam.
- emilburzo 10y agoSRS[1] doesn't break DKIM, because the sender rewrite happens on my server, before DKIM. That's the thing, in theory I went from: spf: fail dkim: pass for forwarded mails, before SRS, to: spf: pass dkim: pass so it should be better, right? But as I said, they explicitly mention NOT changing the envelope sender (maybe they have an exception for SRS cases, but it's not documented anywhere). Oh yeah, and now I'm also responsible for any real spam forwarded to Gmail, since the From is @mydomain. [1] - http://www.openspf.org/SRS http://www.openspf.org/SRS