On 8/13/2015 4:57 AM, Uwe Schindler wrote: > This seems to be a problem @ the ASF. > > I checked the mail server, the mail was only delivered *once* to ASF. I we > arrive those mail any longer I will contact infra! > > serv1:~# grep '730516776.47.1439413674893.JavaMail.jenkins@serv1' > /var/log/exim4/mainlog.1 | wc -l > 1 > > From log: > 2015-08-12 21:07:54 1ZPdFa-0006Ix-Ss <= [email protected] > H=localhost.localdomain (serv1) [127.0.0.1] P=esmtp S=103656 > id=730516776.47.1439413674893.JavaMail.jenkins@serv1 > 2015-08-12 21:08:03 1ZPdFa-0006Ix-Ss => [email protected] R=dnslookup > T=remote_smtp H=mx1-us-west.apache.org [54.191.145.13] > X=TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128 DN="C=US,ST=Maryland,L=Forest > Hill,O=The Apache Software Foundation,OU=Infrastructure,CN=*.apache.org" > C="250 2.0.0 Ok: queued as 776CA32C07" > 2015-08-12 21:08:03 1ZPdFa-0006Ix-Ss Completed > > From the mail headers, it looks like this mail loops around, just count the > "Received: " headers!
There was a message yesterday on the main infra list about changes to how ASF mail is routed internally. The message implied that the change was for ASF committers sending outbound email, but the described routing pipeline sounds similar to the semi-circular loop that I can see in the received headers you mentioned above, so there's probably unintended consequences from their change. There are no public archives of the infra list, and the web page for the infra lists says *not* to forward messages to public lists. I'm not even sure how to summarize what the message says for public consumption without quoting from it, so this vague reference is what I feel comfortable sharing. ;) Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
