[om-infra] MLs: some users automatically unsubscribed

Wayne Sallee Wayne at WayneSallee.com
Fri Mar 25 11:57:59 EDT 2016


Looks like for this situation the host needs to be contacted.

In all the years in my expreiences, I've never had to contact the host. I have always been able to take care of it 
individualy, but judging by the postmaster's quick responce, looks like the host will need to be contacted.

Wayne Sallee
Wayne at WayneSallee.com

> The problem is that they filter at ip level, not sender level. I guess we will not weight enough to convince them to 
> change their policy ...
>
> Le 25 mars 2016 16:14, "Wayne Sallee" <Wayne at waynesallee.com <mailto:Wayne at waynesallee.com>> a écrit :
>
>     __
>     A lot of those places block e-mails for stupid reasons.
>     For this one, all that is needed is to just sent an e-mail to postmaster at proxad.net <mailto:postmaster at proxad.net>
>     asking for it to be unblocked.
>
>     Getting a bounced e-mail will help explain the the reason that they are bouncing it.
>
>     I will send them an e-mail.
>
>     I have to do this from time to time with my e-mail server that is hosted by my web host. I don't contact my web
>     host. I just send the e-mail to have it unblocked.
>
>     Wayne Sallee
>     Wayne at WayneSallee.com <mailto:Wayne at WayneSallee.com>
>
>
>
>     On 03/24/2016 01:32 PM, Jean-Claude Vanier wrote:
>>     Hi,
>>     our new ML manager, mailman, seems to run better than the preceding
>>     one but there remains some annoying issues.
>>
>>     *free.fr  <http://free.fr>: users whose email address is hosted atfree.fr  <http://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  <mailto:xxxxxxxx at free.fr>
>>>     Original-Recipient:rfc822;xxxxxxxx at free.fr  <mailto:rfc822;xxxxxxxx at free.fr>
>>>     Action: failed
>>>     Status: 4.0.0
>>>     Remote-MTA: dns;mx1.free.fr  <http://mx1.free.fr>
>>>     Diagnostic-Code: smtp; 451 too many errors from your ip (23.83.215.13), please
>>>         visithttp://postmaster.free.fr/"""
>>     >Fromhttp://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  <http://aol.com>  +compuserve.com  <http://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  <mailto:xxxxx at compuserve.com>  (orxxxxx at aol.com  <mailto:xxxxx at aol.com>)
>>>     Original-Recipient:rfc822;xxxxx at compuserve.com  <mailto:rfc822;xxxxx at compuserve.com>  (orxxxxx at aol.com  <mailto:xxxxx at aol.com>)
>>>     Action: failed
>>>     Status: 5.2.1
>>>     Remote-MTA: dns;mailin-02.mx.aol.com  <http://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?
>>
>>     _______________________________________________
>>     OM-Infra mailing list
>>     OM-Infra at ml.openmandriva.org  <mailto:OM-Infra at ml.openmandriva.org>
>>     http://ml.openmandriva.org/mailman/listinfo/om-infra_ml.openmandriva.org
>>
>
>     _______________________________________________
>     OM-Infra mailing list
>     OM-Infra at ml.openmandriva.org <mailto:OM-Infra at ml.openmandriva.org>
>     http://ml.openmandriva.org/mailman/listinfo/om-infra_ml.openmandriva.org
>
>
> _______________________________________________
> OM-Infra mailing list
> OM-Infra at ml.openmandriva.org
> http://ml.openmandriva.org/mailman/listinfo/om-infra_ml.openmandriva.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.openmandriva.org/mailman/private/om-infra_ml.openmandriva.org/attachments/20160325/7f9a1be4/attachment-0001.html>


More information about the OM-Infra mailing list