*8085* Add SPF enhancements ##ulsdevteam/add-spf-enhancements##

[ctgraham]

Backport http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=8085 to dev-2_4. Also includes a new config variable to force a default envelope sender in the case of a multi-host install where the from address is not necessarily hosted on the same server.

[asmecher]

Thanks, Clinton, I've reviewed this and it looks good. Would you mind rebasing so that I can merge directly? The lib/pkp submodule hash is out of date.

[bozana]

Have I understood it correctly, that the 3. solution for SPF problem i.e. noreply e-mail address is the same as the default_envelope_sender? If so, I am wondering if there should be maybe another variable for this noreply e-mail address -- shouldn't the envelope sender be the address that receives the bounce messages or errors and noreply a really noreply address? -- It is good to get/see the bounce messages and errors but the noreply address could be used in several applications for the same purpose and one could assume that these e-mails are not considered/read?

[ctgraham]

Yes, the intent of this force_default_envelope_sender setting is to make sure all messages originate from the default envelope sender for SPF purposes. We had a journal which was in crisis mode because of non-delivered emails, and this was the closest extension of Alec's changes in bug 8085, so it was a quick fix. It works well if you can create a noreply address and attach your nondeliverable processing to that address.

For example:
Host: myjournal.org
default_envelope_sender: noreply@myjournal.org (forwarded to ojs@my.edu in postfix)
Site Principal Contact: ojs@my.edu
Journal Contact: editor@yahoo.com

[bozana]

Thanks Clinton! I think it will work well -- I was worried how it would work if the noreply@myinstitution.org is also used by other hosting groups/applications (e.g. OJS, Blogs, Wikis, CMS, ...) that don't necessarily have to know each other issues. But I think one could always get separate e-mail addresses, e.g. ojs-noreply@myinstitution.org cms-noreply@myinstitution.org ... :-)