4 Aug
2015
4 Aug
'15
10:56 a.m.
It appears that comcast and yahoo have implemented DMARC mail filtering
around the first of the month.
This breaks mailing lists such as 44net.
As a result, about a dozen people have had their mail from this list
bouncing and they've been unsubscribed from the list as a result.
This message won't reach them, but if you happen to hear from a former
participant in this list who is wondering what happened, you might let
them know that their ISP has broken mail filtering software in place
that is blocking their participation.
- Brian
4 Aug
4 Aug
12:45 p.m.
On Tue, 4 Aug 2015, Brian Kantor wrote:
It appears that comcast and yahoo have implemented
DMARC mail filtering
around the first of the month.
This breaks mailing lists such as 44net.
The Redhat/CentOS mailman RPM was recently updated to handle DMARC
filtered domains.
Antonio Querubin
e-mail: tony(a)lavanauts.org
xmpp: antonioquerubin(a)gmail.com
1:01 p.m.
On Tue, 4 Aug 2015, Antonio Querubin wrote:
Ugh, disregard. I just noticed it's running under FreeBSD.
The most recent ports version is 2.1.20 which does have DMARC support.
Antonio Querubin
e-mail: tony(a)lavanauts.org
xmpp: antonioquerubin(a)gmail.com
It appears
that comcast and yahoo have implemented DMARC mail filtering
around the first of the month.
This breaks mailing lists such as 44net.
The Redhat/CentOS mailman RPM was recently updated to handle DMARC filtered
domains.
1:15 p.m.
On Tue, Aug 04, 2015 at 07:01:17AM -1000, Antonio Querubin wrote:
Ugh, disregard. I just noticed it's running under
FreeBSD.
The most recent ports version is 2.1.20 which does have DMARC support.
Thanks. We're currently running 2.1.14 which doesn't; I'll look into
updating it. Unfortunately, the fix involves changing the way that
message addresses are formatted which could cause some problems.
- Brian
1:57 p.m.
On Tue, 4 Aug 2015, Brian Kantor wrote:
Thanks. We're currently running 2.1.14 which
doesn't; I'll look into
updating it. Unfortunately, the fix involves changing the way that
message addresses are formatted which could cause some problems.
That's correct. The munge-from option adjusts the from address to be the
list-address and moves the sender address into the reply-to address only
for the DMARC-specific recipient. If the recipient's domain doesn't
specify a DMARC policy, the from-address is not touched.
This does add a small amount of DNS lookup overhead for each recipient.
Antonio Querubin
e-mail: tony(a)lavanauts.org
xmpp: antonioquerubin(a)gmail.com
3745
days inactive
3745
days old
4 comments
2 participants
participants (2)
-
Antonio Querubin -
Brian Kantor