gmail.com problems and this list
david at blue-labs.org
Tue Jul 10 15:18:18 CEST 2007
Wolfgang S. Rupprecht wrote:
> Marco Barreno <barreno at cs.berkeley.edu>
>> 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.
> I don't have access there, but I can fill in part of the puzzle.
> At least one of the opemoko machines at 126.96.36.199 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 188.8.131.52 as a valid
> address. If the sending machine is checking for spammers claiming a
> bunk DNS name will reject 184.108.40.206'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
> 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: 29AF91C98001: to=<xxx at openmoko.com>, relay=sita.openmoko.org[220.127.116.11]:25, delay=6.2, delays=0.18/0.04/5.4/0.64, dsn=4.0.0, status=deferred (host sita.openmoko.org[18.104.22.168] said: 451 Could not complete sender verify callout (in reply to RCPT TO command))
> Jul 9 12:55:35 arbol postfix/smtpd: warning: 22.214.171.124: address not listed for hostname openmoko.org
> Jul 9 12:55:35 arbol postfix/smtpd: connect from unknown[126.96.36.199]
> Jul 9 12:55:36 arbol postfix/smtpd: NOQUEUE: reject: RCPT from unknown[188.8.131.52]: 554 5.7.1 Client host rejected: cannot find your hostname, [184.108.40.206]; from=<> to=<xxx at wsrcc.com> proto=SMTP helo=<sita.openmoko.org>
> Jul 9 12:55:36 arbol postfix/smtpd: disconnect from unknown[220.127.116.11]
> Jul 9 12:55:38 arbol postfix/smtp: 29AF91C98001: to=<xxx at openmoko.com>, relay=sita.openmoko.org[18.104.22.168]:25, delay=447, delays=441/0.05/1.2/4.3, dsn=5.0.0, status=bounced (host sita.openmoko.org[22.214.171.124] said: 550-Verification failed for <xxx at wsrcc.com> 550-Called: 126.96.36.199 550-Sent: RCPT TO:<xxx at wsrcc.com> 550-Response: 554 5.7.1 Client host rejected: cannot find your hostname, [188.8.131.52] 550 Sender verify failed (in reply to RCPT TO command))
That wouldn't cause duplicates.
You got a 550 error which means delivery was not attempted.
I'll repeat again because a lot of people are coming up with some kinda
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.
Regardless it appears to have been fixed as google emails are no longer
making dupe chains.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the community