L A Walsh wrote:
Seems like when the email is resent from suse, suse should add it's own SPF --
That's not how it works though. It cnanot be "added" as part of processing. suse.com does publish an SPF record, but opensuse.org does not, for good reason. (it would play havoc with our member email addresses).
but enforcing the SPF rules against forwarding servers (whether internal to an email list or internal to a receiving ISP) seems wrong --
Yes, and many ISPs do whitelist mailing list servers.
like SPF was never intended to be compared against 'in-transit' hosts -- only the source of the original message, no?
Yup.
Certainly with SPF, it should only be enforced against the original sender.
BTW, where does DKIM fit into all this?
It is a method to detect forged email addresses. With DKIM, you sign your outgoing emails with your domain key. Receivers can verify the signature with a simple DNS lookup. -- Per Jessen, Zürich (8.2°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org