#1454: mailman: Mass bouncing of yahoo user subscriptions
---------------------------+------------------------------------------------
Reporter: neteler | Owner: sac@…
Type: defect | Status: new
Priority: critical | Milestone:
Component: Systems Admin | Keywords: mailman, postfix
---------------------------+------------------------------------------------
Just got tons of notifications that our yahoo subscribers are blocked:
{{{
<xxxxxxxx@yahoo.com>: host mta6.am0.yahoodns.net[98.138.112.33] said: 554
5.7.9 Message not accepted for policy reasons. See
http://postmaster.yahoo.com/errors/postmaster-28.html (in reply to end
of
DATA command)
}}}
Looks like Google is fighting Yahoo is fighting Google?
This will affect Yahoo users in *all* OSGeo mailing lists.
Additionally, I see
{{{
<xxxxxx@hotmail.com>: host mx1.hotmail.com[65.55.92.136] said: 550 5.7.0
(SNT004-MC1F43) Unfortunately, messages from (140.211.15.134) on
behalf of
(yahoo.com) could not be delivered due to domain owner policy
restrictions.
(in reply to end of DATA command)
<xxxxxx@rocketmail.com>: host mta7.am0.yahoodns.net[98.138.112.38] said:
554
5.7.9 Message not accepted for policy reasons. See
http://postmaster.yahoo.com/errors/postmaster-28.html (in reply to end
of
DATA command)
[... many more ...]
}}}
Not sure what's next.
--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/1454>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1454: mailman: Mass bouncing of yahoo user subscriptions
---------------------------+------------------------------------------------
Reporter: neteler | Owner: sac@…
Type: defect | Status: new
Priority: critical | Milestone:
Component: Systems Admin | Keywords: mailman, postfix
---------------------------+------------------------------------------------
Comment(by wildintellect):
Quote from that page "For mailing lists, also known as "listservs," you
should change your sending behavior by adding the mailing lists’ address
to the "From:" line, rather than the sender’s address. Also, enter the
actual user/sender address into the "Reply-To:" line."
This is similar in issue to our previous unresolved tangle with Hotmail.
https://trac.osgeo.org/osgeo/ticket/1242
I'm having trouble tracking down the email thread on that. It seemed to me
there were several security measure that we could add to our mail server
that would make it more trusted.
--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/1454#comment:1>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1454: mailman: Mass bouncing of yahoo user subscriptions
---------------------------+------------------------------------------------
Reporter: neteler | Owner: sac@…
Type: defect | Status: new
Priority: critical | Milestone:
Component: Systems Admin | Keywords: mailman, postfix
---------------------------+------------------------------------------------
Comment(by wildintellect):
Here's the info about creating an SPF record and the thread that related
to hotmail:
http://lists.osgeo.org/pipermail/sac/2013-September/004612.html
--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/1454#comment:2>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1454: mailman: Mass bouncing of yahoo user subscriptions
---------------------------+------------------------------------------------
Reporter: neteler | Owner: sac@…
Type: defect | Status: new
Priority: critical | Milestone:
Component: Systems Admin | Keywords: mailman, postfix
---------------------------+------------------------------------------------
Comment(by neteler):
Replying to [comment:1 wildintellect]:
> Quote from that page "For mailing lists, also known as "listservs," you
should change your sending behavior by adding the mailing lists’ address
to the "From:" line, rather than the sender’s address. Also, enter the
actual user/sender address into the "Reply-To:" line."
How would that be done with mailman?
Also remember: http://www.unicom.com/pw/reply-to-harmful.html
Or is it compliant?
--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/1454#comment:3>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1454: mailman: Mass bouncing of yahoo user subscriptions
---------------------------+------------------------------------------------
Reporter: neteler | Owner: sac@…
Type: defect | Status: new
Priority: blocker | Milestone:
Component: Systems Admin | Keywords: mailman, postfix
---------------------------+------------------------------------------------
Changes (by neteler):
* priority: critical => blocker
Comment:
Does any SAC member know how to solve it? More Yahoo users get
automatically unsubscribed...
--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/1454#comment:4>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1454: mailman: Mass bouncing of yahoo user subscriptions
---------------------------+------------------------------------------------
Reporter: neteler | Owner: sac@…
Type: defect | Status: new
Priority: blocker | Milestone:
Component: Systems Admin | Keywords: mailman, postfix
---------------------------+------------------------------------------------
Comment(by wildintellect):
My best guess is to start by ensuring we have an SFP record.
https://www.howtoforge.com/postfix_spf
Then look into re-arranging so that the original sender stays the sender
and the list email is in the reply-to-list spot.
--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/1454#comment:5>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
On Jan 25, 2015, at 2:38 PM, "OSGeo" <trac_osgeo@osgeo.org> wrote:
#1454: mailman: Mass bouncing of yahoo user subscriptions
---------------------------+------------------------------------------------
Reporter: neteler | Owner: sac@…
Type: defect | Status: new
Priority: blocker | Milestone:
Component: Systems Admin | Keywords: mailman, postfix
---------------------------+------------------------------------------------
Comment(by wildintellect):
My best guess is to start by ensuring we have an SFP record.
https://www.howtoforge.com/postfix_spf
Then look into re-arranging so that the original sender stays the sender
and the list email is in the reply-to-list spot.
Sounds like a reasonable start
more info @
https://help.yahoo.com/kb/mail/SLN24016.html
http://yahoomail.tumblr.com/post/82426900353/yahoo-dmarc-policy-change-what-should-senders
http://dmarc.org/
#1454: mailman: Mass bouncing of yahoo user subscriptions
---------------------------+------------------------------------------------
Reporter: neteler | Owner: sac@…
Type: defect | Status: new
Priority: blocker | Milestone:
Component: Systems Admin | Keywords: mailman, postfix
---------------------------+------------------------------------------------
Comment(by martin):
I'll try to create an SFP record - I never did that before ....
Martin.
--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/1454#comment:6>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1454: mailman: Mass bouncing of yahoo user subscriptions
---------------------------+------------------------------------------------
Reporter: neteler | Owner: sac@…
Type: defect | Status: new
Priority: blocker | Milestone:
Component: Systems Admin | Keywords: mailman, postfix
---------------------------+------------------------------------------------
Comment(by martin):
SPF records are now available in DNS, try:[[BR]]
{{{
#~> host -t spf osgeo.org
}}}
or[[BR]]
{{{
#~> host -t txt osgeo.org
}}}
.... and let's see what the outcome is.
--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/1454#comment:7>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1454: mailman: Mass bouncing of yahoo user subscriptions
---------------------------+------------------------------------------------
Reporter: neteler | Owner: sac@…
Type: defect | Status: new
Priority: blocker | Milestone:
Component: Systems Admin | Keywords: mailman, postfix
---------------------------+------------------------------------------------
Comment(by neteler):
FYI - Recently mailman 2.1.19 has been released which has some important
fixes to deal with DMARC policies and more.
https://mail.python.org/pipermail/mailman-
announce/2015-February/000202.html
I found that through this RHEL ticket (only the report there is
interesting):
"Yahoo.com and AOL DMARC reject policies cripples Mailman-2.1.12 - update
to newer release"
https://bugzilla.redhat.com/show_bug.cgi?id=1095359
--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/1454#comment:8>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1454: mailman: Mass bouncing of yahoo user subscriptions
------------------------------+--------------------
Reporter: neteler | Owner: sac@…
Type: defect | Status: new
Priority: blocker | Milestone:
Component: Systems Admin | Resolution:
Keywords: mailman, postfix |
------------------------------+--------------------
Comment (by neteler):
My OSGeo mailman monitor reports again mass bouncing today due to
rejection of our mailman delivery:
{{{
# excerpt from a LONG list... list reducted to show affected providers:
<xxx@live.com>: host mx1.hotmail.com[207.46.8.167] said: 550 5.7.0
(BAY004-MC5F8) Unfortunately, messages from (140.211.15.134) on behalf
of
(yahoo.com) could not be delivered due to domain owner policy
restrictions.
(in reply to end of DATA command)
<xxx@outlook.com>: host mx3.hotmail.com[65.54.188.72] said: 550 5.7.0
(BAY004-MC1F42) Unfortunately, messages from (140.211.15.134) on
behalf of
(yahoo.com) could not be delivered due to domain owner policy
restrictions.
(in reply to end of DATA command)
<xxx@rocketmail.com>: host mta5.am0.yahoodns.net[98.138.112.38] said: 554
5.7.9 Message not accepted for policy reasons. See
http://postmaster.yahoo.com/errors/postmaster-28.html (in reply to end
of
DATA command)
<xxx@hotmail.com>: host mx3.hotmail.com[134.170.2.199] said: 550 5.7.0
(BLU004-MC1F14) Unfortunately, messages from (140.211.15.134) on
behalf of
(yahoo.com) could not be delivered due to domain owner policy
restrictions.
(in reply to end of DATA command)
<xxxx@yahoo.com>: host mta5.am0.yahoodns.net[98.138.112.33] said: 554
5.7.9
Message not accepted for policy reasons. See
http://postmaster.yahoo.com/errors/postmaster-28.html (in reply to end
of
DATA command)
}}}
See above comment for mailman 2.1.19 with improvements with regards to
this unfortunate situation.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1454#comment:9>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1454: mailman: Mass bouncing of yahoo + hotmail + outlook + live + rocketmail
user subscriptions
------------------------------+--------------------
Reporter: neteler | Owner: sac@…
Type: defect | Status: new
Priority: blocker | Milestone:
Component: Systems Admin | Resolution:
Keywords: mailman, postfix |
------------------------------+--------------------
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1454#comment:10>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1454: mailman: Mass bouncing of yahoo + hotmail + outlook + live + rocketmail
user subscriptions
------------------------------+--------------------
Reporter: neteler | Owner: sac@…
Type: defect | Status: new
Priority: blocker | Milestone:
Component: Systems Admin | Resolution:
Keywords: mailman, postfix |
------------------------------+--------------------
Comment (by neteler):
Replying to [comment:8 neteler]:
> FYI - Recently mailman 2.1.19 has been released which has some important
fixes to deal with DMARC policies and more.
>
> https://mail.python.org/pipermail/mailman-
announce/2015-February/000202.html
>
> I found that through this RHEL ticket (only the report there is
interesting):
>
> "Yahoo.com and AOL DMARC reject policies cripples Mailman-2.1.12 -
update to newer release"
> https://bugzilla.redhat.com/show_bug.cgi?id=1095359
At time (after migration to osgeo6) we use mailman 2.1.18.
The current stable GNU Mailman version are 2.1.20 released on 31-Mar-2015.
and 3.0.0 released on 28-Apr-2015.
To get at least mailman 2.1.19 would be great to address this ticket.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1454#comment:11>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1454: mailman: Mass bouncing of yahoo + hotmail + outlook + live + rocketmail
user subscriptions
------------------------------+--------------------
Reporter: neteler | Owner: sac@…
Type: defect | Status: new
Priority: blocker | Milestone:
Component: Systems Admin | Resolution:
Keywords: mailman, postfix |
------------------------------+--------------------
Comment (by neteler):
Replying to [comment:11 neteler]:
> Replying to [comment:8 neteler]:
> > FYI - Recently mailman 2.1.19 has been released which has some
important fixes to deal with DMARC policies and more.
> >
> > https://mail.python.org/pipermail/mailman-
announce/2015-February/000202.html
> >
> > I found that through this RHEL ticket (only the report there is
interesting):
> >
> > "Yahoo.com and AOL DMARC reject policies cripples Mailman-2.1.12 -
update to newer release"
> > https://bugzilla.redhat.com/show_bug.cgi?id=1095359
>
> At time (after migration to osgeo6) we use mailman 2.1.18.
>
> The current stable GNU Mailman version are 2.1.20 released on
31-Mar-2015. and 3.0.0 released on 28-Apr-2015.
>
> To get at least mailman 2.1.19 would be great to address this ticket.
For the record: The installation got updated by accident to 2.1.20 
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1454#comment:12>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1454: mailman: Mass bouncing of yahoo + hotmail + outlook + live + rocketmail
user subscriptions
------------------------------+---------------------
Reporter: neteler | Owner: sac@…
Type: defect | Status: closed
Priority: blocker | Milestone:
Component: Systems Admin | Resolution: fixed
Keywords: mailman, postfix |
------------------------------+---------------------
Changes (by neteler):
* status: new => closed
* resolution: => fixed
Comment:
The new mailman version seems to help. Closing.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1454#comment:13>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.