Mailscanner, forwarding and SPF - the answer is SRS
daniel at brunt.ca
Thu Mar 2 22:34:14 UTC 2017
I found an answer to the SPF issue on forwarded emails - SRS. I found the setting at Barracuda in advanced settings. This rewrites the sender envelope info such that the next hop will accept it as it appears to be (in my case) from barracudanetworks.com and GoDaddy is now happy. (envelope-sender <srs0=by7r=2l=<my_domain>.ca=daniel at srs.ess.barracudanetworks.com>)
Now what you need is a way to implement SRS in EFA. Note: PostSRSd is not currently part of EFA - that's not to say it cannot be added! See https://github.com/roehling/postsrsd
Also see http://www.openspf.org/SRS
> Date: Fri, 24 Feb 2017 18:47:42 +0000
> From: Daniel Brunt <daniel at brunt.ca>
> To: "mailscanner at lists.mailscanner.info"
> <mailscanner at lists.mailscanner.info>
> Subject: RE: Mailscanner, forwarding and SPF
> <YTXPR01MB05442D7C69F0E19F3A02E8A8A2520 at YTXPR01MB0544.CANPRD01.PROD.OUTLOOK.COM>
> Content-Type: text/plain; charset="us-ascii"
> Hi Don,
> My g/f had similar issue using GoDaddy for her e-mail. I was filtering her e-mail via Barracuda (formerly MailFoundry). I was asked to troubleshoot NDRs.
> Turns out, GoDaddy had implemented SPF checking and was rejecting emails forwarded from Barracuda where the domain had a SPF record.
> No way around this since GoDaddy was unwilling to whitelist Barracuda mail servers from the SPF check; and their whitelisting mechanism is post-SPF check.
> I had to turn off the Barracuda email filtering for her. She was not happy. She started receiving a *lot* more SPAM as a result.
More information about the MailScanner