Pete,
Sorry for the delayed response. My day job has kept me busier than normal lately and I've neglected a backlog of messages. That is correct regarding SPFs and that is why a server doing SPFThis is incorrect -- Groups.io's messages pass SPF. That's because SPF tests the envelope-From, not the header-From. During the handshake between Groups.io's server and the receiving email service Groups.io's server correctly presents its own domain during the SMTP transaction (envelope-From). My example has nothing to do with DMARC but shows how "spoofing" thatHistorically leaving the header-From address unmodified was typical email list behavior. Now many do replace the header From, but not all. Yahoo Groups didn't make this change until the advent of DMARC, which was a "forcing function" for many lists. It was not until DMARC introduced the requirement that the header-From be /aligned/ with the envelope-From that many email lists began experiencing deliverability problems, and changed their handling of the From: header field. There are servers that do not use DMARC records but still block emailThose servers really should be using the envelope-From, not the header-From for blocking purposes, matching the implementation of SPF. At worst, an internal header-From domain arriving from outside should be a demerit in the server's spam filter. Worse, this is not explained anywhere in groups.io information on whatGroups.io's practice does not cause bouncing, nor is it causing a problems for Groups.io's users. Mark is very sensitive to deliverability issues and if it were a problem he'd be on it. You indicated getting this option in "beta". How do I do that and howAs you may have figured out in the mean time, beta is just a group; there is no separate beta test platform. Anyone can join the group and post there. It serves as Groups.io's official "suggestion board". Shal -- Help: /static/help More Help: /g/GroupManagersForum/wiki Even More Help: Search button at the top of Messages list |