[om-infra] MLs: some users automatically unsubscribed
Jean-Claude Vanier
jclvanier at gmail.com
Thu Mar 24 13:32:58 EDT 2016
Hi,
our new ML manager, mailman, seems to run better than the preceding
one but there remains some annoying issues.
* free.fr: users whose email address is hosted at free.fr doesn't
receive the om-cooker messages because of the IP address of the sender
(mailman):
>Final-Recipient: rfc822; xxxxxxxx at free.fr
>Original-Recipient: rfc822;xxxxxxxx at free.fr
>Action: failed
>Status: 4.0.0
>Remote-MTA: dns; mx1.free.fr
>Diagnostic-Code: smtp; 451 too many errors from your ip (23.83.215.13), please
> visit http://postmaster.free.fr/"""
>From http://postmaster.free.fr/:
>Is my IP blocked ?
>IP 23.83.215.13 is blacklisted for 86265s (too many errors (unexisting recipients, broken connections), testing)
So, probably, the smtp server is used by misconfigured email services.
We cannot manage such issues.
* aol.com + compuserve.com: users using those email providers are in
fact only 2: maik and itchka. The issue is:
>Final-Recipient: rfc822; xxxxx at compuserve.com (or xxxxx at aol.com)
>Original-Recipient: rfc822;xxxxx at compuserve.com (or xxxxx at aol.com)
>Action: failed
>Status: 5.2.1
>Remote-MTA: dns; mailin-02.mx.aol.com
>Diagnostic-Code: smtp; 521 5.2.1 : (DMARC:AOL) This message failed DMARC
> Evaluation for an AOL Domain. For more information please visit
> http://postmaster-blog.aol.com/2014/04/22/aol-mail-updates-dmarc-policy-to-reject/"""
They suggest:
>For mailing lists we recommend configuring reply behavior to fill the From line with the mailing list's address
>rather than the sender's and put the actual user / sender address into the Reply-To: line.
>Please also note that current "auto unsubscribe" logic based upon bounces might be too rigid until this change has been in place for a while.
I'm not sure if this change, if possible, is what we want.
So, which solution do we have?
1) we continue as this
--> obviously, this is not very comfortable
Maybe, anurag can talk to the provider to see if something can be done
on server side.
2) we build our own mailman in one of the oma's server or one member server
--> yet another (not so simple) service to manage, therefore someone
available to do it
But this would be the situation in which we would have the best control
3) we switch the lists to discourse
--> users will have to set their password again
--> easy for small lists like workshop, QA
--> might disturb a lot of cooker people
Any other idea?
More information about the OM-Infra
mailing list