This 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).
Not true. While -some- email servers use the envelope-From in SPF validation, -all- Exchange servers (most enterprise and business servers including Office 365) use the actual from address as well since this is a common form of spoofing.
Those 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.
"Those servers", again, are -all- Microsoft Exchange servers blocking domain origin.? I have tested and, again like SPF, Exchange blocks both envelope-From and header-From since that, again, is a common method of spoofing.? I realize you don't like or have experience with Microsoft Exchange or its common deployment (it also does not directly implement DMARC), but it is the most used enterprise and business mail server.? As I indicated before, to deny this fact is to tell millions of potential users of groups.io "we don't want you".
Groups.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.
Yes it is, I have experienced it directly, reported it here (where is the only place I am aware of reporting these issues), and have been met with statements like this that ignore a large set of users who may not know why they are being blocked.? I am savvy enough to recognize what is going on, why it is happening, and to report what the root cause is.? That is what I have done with this post.
As 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".
Like you, I have a day job which does not include debugging other people's products.? No, I had not "figured out" "beta is just a group".? I guess maybe this should all be reported over there since no action has occurred on this group other than your statements that it is a non-issue.? BTW, Yahoo has always supported having groups show the From as being the group, not the user so it would pass server tests that the from is not improperly originating from a non-domain-owned mail server.? I also make this statement based on experience with Y! groups.
I guess I need to open this over on the beta group.? Thank you for letting me know where to go with this issue.
