Well, if I did everything right, the people on yahoo, comcast, and sbcglobal who weren't getting messages from this mailing list because of those ISPs' DMARC filtering should now be getting messages once again. - Brian
On Tue, 4 Aug 2015, Brian Kantor wrote:
Well, if I did everything right, the people on yahoo, comcast, and sbcglobal who weren't getting messages from this mailing list because of those ISPs' DMARC filtering should now be getting messages once again.
+ AOL
Antonio Querubin e-mail: tony@lavanauts.org xmpp: antonioquerubin@gmail.com
On Tue, Aug 4, 2015 at 12:21 PM, Antonio Querubin tony@lavanauts.org wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Tue, 4 Aug 2015, Brian Kantor wrote:
Well, if I did everything right, the people on yahoo, comcast, and sbcglobal who weren't getting messages from this mailing list because of those ISPs' DMARC filtering should now be getting messages once again.
- AOL
I'm still seeing AOL mail from @aol.com (not munged), resulting in it getting dropped into spam. Maybe these users should be prohibited from posting or simply unsubscribed.
Tom KD7LXL
On Tue, Aug 04, 2015 at 12:38:03PM -0700, Tom Hayward wrote:
I'm still seeing AOL mail from @aol.com (not munged), resulting in it getting dropped into spam. Maybe these users should be prohibited from posting or simply unsubscribed.
As I understand it, it will only munge addresses when delivering to a host that specifies via the DNS that it does DMARC. I presume your host does not do so, so you would not see headers being munged. - Brian
On Tue, Aug 4, 2015 at 12:43 PM, Brian Kantor Brian@ucsd.edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Tue, Aug 04, 2015 at 12:38:03PM -0700, Tom Hayward wrote:
I'm still seeing AOL mail from @aol.com (not munged), resulting in it getting dropped into spam. Maybe these users should be prohibited from posting or simply unsubscribed.
As I understand it, it will only munge addresses when delivering to a host that specifies via the DNS that it does DMARC. I presume your host does not do so, so you would not see headers being munged.
Correct, my host does not specify DMARC on its messages. However, it honors DMARC rules from other hosts by moving unauthenticated messages to the spam folder. This means messages from aol.com via ampr.org get moved to spam, as requested by aol.com. My suggestion is to restrict posting to this mailing list to only hosts that allow their messages to be forwarded.
Tom KD7LXL
-
Antonio Querubin -
Brian Kantor -
Tom Hayward