<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
A lot of those places block e-mails for stupid reasons.<br>
For this one, all that is needed is to just sent an e-mail to <a
href="mailto:postmaster@proxad.net">postmaster@proxad.net</a>
asking for it to be unblocked.<br>
<br>
Getting a bounced e-mail will help explain the the reason that they
are bouncing it.<br>
<br>
I will send them an e-mail.<br>
<br>
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.<br>
<br>
Wayne Sallee<br>
<a class="moz-txt-link-abbreviated" href="mailto:Wayne@WayneSallee.com">Wayne@WayneSallee.com</a><br>
<br>
<br>
<br>
On 03/24/2016 01:32 PM, Jean-Claude Vanier wrote:
<blockquote
cite="mid:CAFXDyrK7JBj8DKuSG3S1Dhc_D9ypnAaYH_25jUett6iGOupD+g@mail.gmail.com"
type="cite">
<pre wrap="">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):
</pre>
<blockquote type="cite">
<pre wrap="">Final-Recipient: rfc822; <a class="moz-txt-link-abbreviated" href="mailto:xxxxxxxx@free.fr">xxxxxxxx@free.fr</a>
Original-Recipient: <a class="moz-txt-link-abbreviated" href="mailto:rfc822;xxxxxxxx@free.fr">rfc822;xxxxxxxx@free.fr</a>
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 <a class="moz-txt-link-freetext" href="http://postmaster.free.fr/">http://postmaster.free.fr/</a>"""
</pre>
</blockquote>
<pre wrap="">
>From <a class="moz-txt-link-freetext" href="http://postmaster.free.fr/:">http://postmaster.free.fr/:</a>
</pre>
<blockquote type="cite">
<pre wrap="">Is my IP blocked ?
IP 23.83.215.13 is blacklisted for 86265s (too many errors (unexisting recipients, broken connections), testing)
</pre>
</blockquote>
<pre wrap="">
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:
</pre>
<blockquote type="cite">
<pre wrap="">Final-Recipient: rfc822; <a class="moz-txt-link-abbreviated" href="mailto:xxxxx@compuserve.com">xxxxx@compuserve.com</a> (or <a class="moz-txt-link-abbreviated" href="mailto:xxxxx@aol.com">xxxxx@aol.com</a>)
Original-Recipient: <a class="moz-txt-link-abbreviated" href="mailto:rfc822;xxxxx@compuserve.com">rfc822;xxxxx@compuserve.com</a> (or <a class="moz-txt-link-abbreviated" href="mailto:xxxxx@aol.com">xxxxx@aol.com</a>)
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
<a class="moz-txt-link-freetext" href="http://postmaster-blog.aol.com/2014/04/22/aol-mail-updates-dmarc-policy-to-reject/">http://postmaster-blog.aol.com/2014/04/22/aol-mail-updates-dmarc-policy-to-reject/</a>"""
</pre>
</blockquote>
<pre wrap="">
They suggest:
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">
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
<a class="moz-txt-link-abbreviated" href="mailto:OM-Infra@ml.openmandriva.org">OM-Infra@ml.openmandriva.org</a>
<a class="moz-txt-link-freetext" href="http://ml.openmandriva.org/mailman/listinfo/om-infra_ml.openmandriva.org">http://ml.openmandriva.org/mailman/listinfo/om-infra_ml.openmandriva.org</a>
</pre>
</blockquote>
</body>
</html>