<html><head></head><body>You appear to have forgotten to carbon Jared, so I have added him in, Jeremy, but I agree with your appraisal of the situation, and there is in fact little that can be done about it except to remove the offending addresses from the list.<br>
<br>
Thanks for letting us know, Erin. If you can add the remainder of the addresses from which you have gotten this sort of Bounce ...<br><br><div class="gmail_quote">On September 12, 2016 3:01:30 AM EDT, Jeremy Chadwick <jdc@koitsu.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">(Moved to outages-discussion, CC'ing Jared -- request for you is at the<br />end of the email)<br /><br />I disagree with the assertion that mailman on <a href="http://outages.org">outages.org</a> is<br />misconfigured.<br /><br />The <a href="http://outages.org">outages.org</a> subscriber reamea.chey@azcom.net.kh appears to be<br />indirectly triggering this problem. **I** did not see it, so it may<br />have been a transient issue, but hard to say. So let's review the SMTP<br />conversation history since bounces are nice enough to include it.<br />Working from the bottom up:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> Received: from <a href="http://puck.nether.net">puck.nether.net</a> (<a href="http://puck.nether.net">puck.nether.net</a> [<a href="http://204.42.254.5">204.42.254.5</a>]) by<br /> <a href="http://mx04.online.com.kh">mx04.online.com.kh</a> (Postfix) with
ESMTP id 3BD2537F2B for<br /> <reamea.chey@azcom.net.kh>; Sun, 11 Sep 2016 01:23:55 +0700 (ICT)<br /></blockquote><br /><a href="http://puck.nether.net">puck.nether.net</a> (where <a href="http://outages.org">outages.org</a> is hosted) contacts<br /><a href="http://mx04.online.com.kh">mx04.online.com.kh</a> (an MX record for <a href="http://azcom.net.kh">azcom.net.kh</a>).<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> Received: from <a href="http://mx04.online.com.kh">mx04.online.com.kh</a> (<a href="http://mx04.online.com.kh">mx04.online.com.kh</a> [<a href="http://203.189.128.14">203.189.128.14</a>]) by<br /> <a href="http://mx04.online.com.kh">mx04.online.com.kh</a> (Postfix) with SMTP id BF29C1E7862 for<br /> <reamea.chey@online.com.kh>; Sun, 11 Sep 2016 01:23:55 +0700 (ICT)<br /></blockquote><br />That server then re-writes the delivery address into<br
/>reamea.chey@online.com.kh (no idea why) before punting the mail to<br />something called "red" (a Microsoft Exchange server from the look of<br />it), which may in fact be the machine itself but with a private address<br />interface (<a href="http://192.168.1.170">192.168.1.170</a>) or possibly transparent SMTP forwarding of<br />some kind:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> Received: from red (<a href="http://192.168.1.170">192.168.1.170</a>) by <a href="http://red.cogetel.com.kh">red.cogetel.com.kh</a> (<a href="http://192.168.1.170">192.168.1.170</a>) with<br /> Microsoft SMTP Server id <a href="http://14.3.181.6">14.3.181.6</a>; Sun, 11 Sep 2016 01:21:02 +0700<br /></blockquote><br />The same server then attempts to punt the mail to <a href="http://192.168.1.172">192.168.1.172</a> (another<br />machine claiming to be the same thing, "red"):<br /><br /><blockquote class="gmail_quote"
style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> Received: from <a href="http://RED.cogetel.com.kh">RED.cogetel.com.kh</a> (<a href="http://192.168.1.170">192.168.1.170</a>) by <a href="http://red.cogetel.com.kh">red.cogetel.com.kh</a><br /> (<a href="http://192.168.1.172">192.168.1.172</a>) with Microsoft SMTP Server (TLS) id <a href="http://14.3.181.6">14.3.181.6</a>; Sun, 11 Sep<br /> 2016 01:21:02 +0700<br /></blockquote><br />This infinitely continues until the "hop count" (think traceroute but<br />with SMTP history), indicating a kind of SMTP redirection loop (i.e.<br /><a href="http://192.168.1.172">192.168.1.172</a> is rejecting what <a href="http://192.168.1.170">192.168.1.170</a> is trying to do, but it<br />keeps trying because that's how it's configured). What's interesting<br />is that the redelivery attempts for this go on for over a day.<br /><br />So why did _you_ get a copy of this?<br /><br />When you replied to my Email,
you (appropriately) sent a copy to me via<br />the To: line (which I got), and also CC'd outages@outages.org (which<br />then sends a copy out each subscriber). When certain kinds of bounces<br />happen, they end up going back to the original person who sent the mail.<br />They're SUPPOSED to go to the MAIL FROM address (which is<br />outages-bounces@outages.org I assure you (I checked)), but some software<br />has been known to key off of the From: line instead (this is<br />particularly common when seeing "magic things" that appear in the SMTP<br />path that don't make clear indication of what's going on in Received:<br />headers, or because there is a kind of forwarding happening where the<br />original MAIL FROM is lost). Some details are on Wikipedia:<br /><br /><a href="https://en.wikipedia.org/wiki/Bounce_address">https://en.wikipedia.org/wiki/Bounce_address</a><br /><br /><a href="http://mxtoolbox.com">mxtoolbox.com</a> also has a "header analyser" tool that can parse
Received:<br />lines and make them a bit more clear. Here's a link to the tool, and<br />the analysis in question:<br /><br /><a href="http://mxtoolbox.com/EmailHeaders.aspx">http://mxtoolbox.com/EmailHeaders.aspx</a><br /><a href="http://mxtoolbox.com/Public/Tools/EmailHeaders.aspx?huid=cea3b136-d1a3-43ea-af3a-439a5710aaaa">http://mxtoolbox.com/Public/Tools/EmailHeaders.aspx?huid=cea3b136-d1a3-43ea-af3a-439a5710aaaa</a><br /><br />Jared -- maybe you could remove reamea.chey@azcom.net.kh for the time<br />being, or send them an Email directly telling them of the issue (to<br />forward to whatever mail services provider they use)?<br /></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>