<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Wolfgang S. Rupprecht wrote:
<blockquote cite="mid:87odik945w.fsf@arbol.wsrcc.com" type="cite">
<pre wrap="">Marco Barreno <a class="moz-txt-link-rfc2396E" href="mailto:barreno@cs.berkeley.edu"><barreno@cs.berkeley.edu></a>
writes:
</pre>
<blockquote type="cite">
<pre wrap="">Can someone with admin access to the list machine send me the SMTP
logs for one of the duplicated messages? I'm working in the Gmail
group at Google for the summer and I can have someone try to diagnose
the problem from this end. The full SMTP logs would be helpful.
</pre>
</blockquote>
<pre wrap=""><!---->
I don't have access there, but I can fill in part of the puzzle.
At least one of the opemoko machines at 88.198.124.203 opens an smtp
connection back to the sending domain to verify the sender address of
any incoming message. The smtp-back machine has messed up DNS. The
claimed rDNS for that IP is "openmoko.org" but the forward DNS check
for that "openmoko.org" doesn't list 88.198.124.203 as a valid
address. If the sending machine is checking for spammers claiming a
bunk DNS name will reject 88.198.124.203's SMTP verify. The opemmoko
machine will then interpret that failed smtp verify attempt as the
verified address not existing and will decline the initial incoming
transfer.
In short, folks really need to check the forward and backward DNS and
make sure it is consistent, especially if that machine tries open an
outgoing SMTP connection (such as the attempted verification).
Jul 9 12:48:17 arbol postfix/smtp[26802]: 29AF91C98001: to=<a class="moz-txt-link-rfc2396E" href="mailto:xxx@openmoko.com"><xxx@openmoko.com></a>, relay=sita.openmoko.org[88.198.124.203]:25, delay=6.2, delays=0.18/0.04/5.4/0.64, dsn=4.0.0, status=deferred (host sita.openmoko.org[88.198.124.203] said: 451 Could not complete sender verify callout (in reply to RCPT TO command))
Jul 9 12:55:35 arbol postfix/smtpd[26864]: warning: 88.198.124.203: address not listed for hostname openmoko.org
Jul 9 12:55:35 arbol postfix/smtpd[26864]: connect from unknown[88.198.124.203]
Jul 9 12:55:36 arbol postfix/smtpd[26864]: NOQUEUE: reject: RCPT from unknown[88.198.124.203]: 554 5.7.1 Client host rejected: cannot find your hostname, [88.198.124.203]; from=<> to=<a class="moz-txt-link-rfc2396E" href="mailto:xxx@wsrcc.com"><xxx@wsrcc.com></a> proto=SMTP helo=<sita.openmoko.org>
Jul 9 12:55:36 arbol postfix/smtpd[26864]: disconnect from unknown[88.198.124.203]
Jul 9 12:55:38 arbol postfix/smtp[26863]: 29AF91C98001: to=<a class="moz-txt-link-rfc2396E" href="mailto:xxx@openmoko.com"><xxx@openmoko.com></a>, relay=sita.openmoko.org[88.198.124.203]:25, delay=447, delays=441/0.05/1.2/4.3, dsn=5.0.0, status=bounced (host sita.openmoko.org[88.198.124.203] said: 550-Verification failed for <a class="moz-txt-link-rfc2396E" href="mailto:xxx@wsrcc.com"><xxx@wsrcc.com></a> 550-Called: 64.142.50.224 550-Sent: RCPT TO:<a class="moz-txt-link-rfc2396E" href="mailto:xxx@wsrcc.com"><xxx@wsrcc.com></a> 550-Response: 554 5.7.1 Client host rejected: cannot find your hostname, [88.198.124.203] 550 Sender verify failed (in reply to RCPT TO command))
-wolfgang
</pre>
</blockquote>
That wouldn't cause duplicates.<br>
<br>
You got a 550 error which means delivery was not attempted.<br>
<br>
I'll repeat again because a lot of people are coming up with some
kinda wild answers.<br>
<br>
Google mail was causing dupes within google mail -before- it talks to
any server outside of google mail. I posted the smtp logs of a
message from one dupe chain that revealed this. I compared it with
two other dupe chains and they both showed the same internal problem.<br>
<br>
Regardless it appears to have been fixed as google emails are no
longer making dupe chains.<br>
<br>
-david<br>
</body>
</html>