Re: Duplicate message troubleshooting
El jue, 16-08-2007 a las 20:46 +0200, Daniel Mewes escribió: > On Thu, 2007-08-16 at 20:25 +0200, Santiago Crespo wrote: > > Nobody has reported this yet: > > > > http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=Site+Infrastructure&component=Lists&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= > > > > Look at this bug: > http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=710 Correct, I saw it, but thought that it isn't related. -- Santiago Crespo signature.asc Description: Esta parte del mensaje está firmada digitalmente ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Duplicate message troubleshooting
On Thu, 2007-08-16 at 20:25 +0200, Santiago Crespo wrote: > Nobody has reported this yet: > > http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=Site+Infrastructure&component=Lists&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= > Look at this bug: http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=710 -- Daniel Mewes ([EMAIL PROTECTED]) Phone: 0800 DAMEWES (3263937; from inside Germany, I call back) Mobile: +49 (0) 160 8577603 Pager: [EMAIL PROTECTED] ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Duplicate message troubleshooting
Good idea. I'll do that later today if I don't get a direct response from an admin. Marco On Thu, Aug 16, 2007 at 08:25:42PM +0200, thus spake Santiago Crespo: > Hi Marco, > > I think that the best way to solve this is opening a bug in the > bugzilla.openmoko.org system, select "Site Infraestructure" and then "Lists": > > http://bugzilla.openmoko.org/cgi-bin/bugzilla/enter_bug.cgi?product=Site%20Infrastructure > > Nobody has reported this yet: > > http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=Site+Infrastructure&component=Lists&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= > > Thanks! > > > > El mar, 24-07-2007 a las 13:14 -0700, Marco Barreno escribi??: > > Messages to the list are being duplicated again. Some of the messages > > are from Gmail, but not all (e.g. some are from kostyrka.org and > > cnlohr.com). I can try to help debug the problem from the Gmail end > > if an admin on the list machine can send me verbose SMTP logs; please > > see below for details. Harald or Sean, can one of you send detailed > > logs? Anyone else? > > > > Some Gmail message IDs with duplicated messages today: > > [EMAIL PROTECTED] > > [EMAIL PROTECTED] > > [EMAIL PROTECTED] > > > > Thanks, > > Marco > > > > > > - Forwarded message from Marco Barreno <[EMAIL PROTECTED]> - > > > > From: Marco Barreno <[EMAIL PROTECTED]> > > Date: Fri, 13 Jul 2007 14:36:57 -0700 > > To: "Wolfgang S. Rupprecht" <[EMAIL PROTECTED]> > > Cc: community@lists.openmoko.org > > Subject: Re: gmail.com problems and this list > > > > Hi everyone, > > > > > > Short version: > > > > It seems the duplicated messages are not just a Gmail problem: mails > > are also being duplicated from starband.net and possibly others as > > well, so it seems the problem is likely something on the openmoko side > > that only happens to cause duplicates with some sending domains and > > not others. I'ts also not consistent; some messages from Gmail and > > starband.net are duplicated while others aren't. > > > > I've checked with the Gmail team, and the duplicated messages from > > Gmail are happening because Gmail doesn't receive the SMTP OK from the > > openmoko list server, so it retransmits because it thinks the messages > > don't get delivered. To debug further, an admin on the list machine > > needs to enable verbose SMTP logging if it's not already enabled and > > provide information about if/when the OK is sent. Here are some > > example message IDs for which the logs would be useful: > > [EMAIL PROTECTED] > > [EMAIL PROTECTED] > > [EMAIL PROTECTED] > > If verbose logging isn't already enabled, however, enabling it and > > then sending logs for any future duplicated messages would work too. > > > > > > Detailed version: > > > > On Mon, Jul 09, 2007 at 11:14:03PM -0700, thus spake Wolfgang S. Rupprecht: > > > 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. > > > > Even ignoring the messed-up DNS for the moment, doing an SMTP callback > > is not a good way to check existence of an email account. For one > > thing, whenever a spammer spoofs a From address in an innocent domain, > > that domain can get bombarded with callbacks. For another thing, > > spammers sometimes use RCPT commands themselves to check existence of > > email addresses, so ISPs are likely to consider many such requests to > > be abusive behavior. In the case of a large ISP (such as Gmail), if a > > lot of email is sent to a destination that does callbacks, the > > frequency of callbacks can trigger abuse prevention measures. See > > http://en.wikipedia.org/wiki/Callback_verification for more drawbacks. > > (In particular, note: "If a server receives a lot of spam, it will do > > a lot of callbacks and if those addresses are invalid, the server will > > look very similar to a spam
Re: Duplicate message troubleshooting
Hi Marco, I think that the best way to solve this is opening a bug in the bugzilla.openmoko.org system, select "Site Infraestructure" and then "Lists": http://bugzilla.openmoko.org/cgi-bin/bugzilla/enter_bug.cgi?product=Site%20Infrastructure Nobody has reported this yet: http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=Site+Infrastructure&component=Lists&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Thanks! El mar, 24-07-2007 a las 13:14 -0700, Marco Barreno escribió: > Messages to the list are being duplicated again. Some of the messages > are from Gmail, but not all (e.g. some are from kostyrka.org and > cnlohr.com). I can try to help debug the problem from the Gmail end > if an admin on the list machine can send me verbose SMTP logs; please > see below for details. Harald or Sean, can one of you send detailed > logs? Anyone else? > > Some Gmail message IDs with duplicated messages today: > [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > Thanks, > Marco > > > - Forwarded message from Marco Barreno <[EMAIL PROTECTED]> - > > From: Marco Barreno <[EMAIL PROTECTED]> > Date: Fri, 13 Jul 2007 14:36:57 -0700 > To: "Wolfgang S. Rupprecht" <[EMAIL PROTECTED]> > Cc: community@lists.openmoko.org > Subject: Re: gmail.com problems and this list > > Hi everyone, > > > Short version: > > It seems the duplicated messages are not just a Gmail problem: mails > are also being duplicated from starband.net and possibly others as > well, so it seems the problem is likely something on the openmoko side > that only happens to cause duplicates with some sending domains and > not others. I'ts also not consistent; some messages from Gmail and > starband.net are duplicated while others aren't. > > I've checked with the Gmail team, and the duplicated messages from > Gmail are happening because Gmail doesn't receive the SMTP OK from the > openmoko list server, so it retransmits because it thinks the messages > don't get delivered. To debug further, an admin on the list machine > needs to enable verbose SMTP logging if it's not already enabled and > provide information about if/when the OK is sent. Here are some > example message IDs for which the logs would be useful: > [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED] > If verbose logging isn't already enabled, however, enabling it and > then sending logs for any future duplicated messages would work too. > > > Detailed version: > > On Mon, Jul 09, 2007 at 11:14:03PM -0700, thus spake Wolfgang S. Rupprecht: > > 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. > > Even ignoring the messed-up DNS for the moment, doing an SMTP callback > is not a good way to check existence of an email account. For one > thing, whenever a spammer spoofs a From address in an innocent domain, > that domain can get bombarded with callbacks. For another thing, > spammers sometimes use RCPT commands themselves to check existence of > email addresses, so ISPs are likely to consider many such requests to > be abusive behavior. In the case of a large ISP (such as Gmail), if a > lot of email is sent to a destination that does callbacks, the > frequency of callbacks can trigger abuse prevention measures. See > http://en.wikipedia.org/wiki/Callback_verification for more drawbacks. > (In particular, note: "If a server receives a lot of spam, it will do > a lot of callbacks and if those addresses are invalid, the server will > look very similar to a spammer who is doing a dictionary attack to > harvest addresses. This in turn might get the server blacklisted > elsewhere.") > > For these reasons, Gmail strongly recommends avoiding callbacks and > instead checking SPF records (Sender Policy Framework, provided via > DNS) to verify that the mail is indeed coming from Google (i.e. the > SMTP connectio
Re: Duplicate message troubleshooting
Nicolas Bougues wrote: > > Here is the kind of things my SMTP relay logs while talking to openmoko's > list > server : > > Jul 24 18:46:21 cassis postfix/smtp[9586]: 7E28BE0BA0: > to=, > relay=sita.openmoko.org[88.198.124.203]:25, delay=12360, > delays=12279/0.16/0.15/80, dsn=4.4.2, status=deferred ( > conversation with sita.openmoko.org[88.198.124.203] timed out while sending > end of data -- message may be sent more than once) > > There is a fair amount of those messages concerning openmoko, and just one or > two regarding other destinations (out of 25000+ mails relayed yesterday). > > I only posted once or twice to the list before, and no such behavior was > encountered. > > Unfortunatly, I don't have further SMTP traces. > > Could there be some connectivity problem, maybe firewall related, on > openmoko's side ? The problem is their SMTP server is taking its own sweet time recognizing the end-of-message sequence, so peer MUAs are starting to timeout instead. Here is a manual session: [EMAIL PROTECTED] ~ $ telnet sita.openmoko.org smtp Trying 88.198.124.203... Connected to sita.openmoko.org. Escape character is '^]'. 220 sita.openmoko.org ESMTP Exim 4.50 Wed, 25 Jul 2007 10:37:31 +0200 EHLO taupro.com 250-sita.openmoko.org Hello adsl-68-95-135-33.dsl.rcsntx.swbell.net [68.95.135.33] 250-SIZE 52428800 250-PIPELINING 250 HELP RCPT: [EMAIL PROTECTED] 500 unrecognized command MAIL FORM 500 unrecognized command MAIL FROM:<[EMAIL PROTECTED]> 250 OK RCPT TO:<[EMAIL PROTECTED]> 550 unknown user RCPT TO: 250 Accepted DATA 354 Enter message, ending with "." on a line by itself Date: 25 Jul 2007 03:34:00 From: [EMAIL PROTECTED] To: community@lists.openmoko.org Subject: Diagnostic Message This is a probe message to diagnose the SMTP problems. Please ignore. . (very long idle interval of 5 minutes or so) 250 OK id=1IDcPE-0002wr-QA It may be running off to validate the sender domain name to prevent spam, but is taking too long I think - perhaps an inefficient DNS arrangement. There are issues with their DNS, as this validator shows: http://www.dnsstuff.com/tools/dnsreport.ch?domain=openmoko.org with the biggest problem being stealth NS records with leakage, which can wreak havoc with timeouts. And yes, I copied the -owner of the community list. -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Duplicate message troubleshooting
On Wednesday 25 July 2007 00:47:02 Marco Barreno wrote: > On Tue, Jul 24, 2007 at 10:42:01PM +0200, thus spake Andreas Kostyrka: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Ok, putting on my Postmaster hat, could you please provide Message Ids > > and headers for messages from heaven.kostyrka.org that were sent > > duplicate? Please use private mail. > > > > Andreas > > I must apologize--I got some notes mixed up and listed the wrong > domain. Actually I don't have a record of emails being duplicated > from kostyrka.org. I have seen duplicate messages from cnlohr.com > (Message ID [EMAIL PROTECTED]) and axialys.net (Message ID > [EMAIL PROTECTED]), however. > Here is the kind of things my SMTP relay logs while talking to openmoko's list server : Jul 24 18:46:21 cassis postfix/smtp[9586]: 7E28BE0BA0: to=, relay=sita.openmoko.org[88.198.124.203]:25, delay=12360, delays=12279/0.16/0.15/80, dsn=4.4.2, status=deferred ( conversation with sita.openmoko.org[88.198.124.203] timed out while sending end of data -- message may be sent more than once) There is a fair amount of those messages concerning openmoko, and just one or two regarding other destinations (out of 25000+ mails relayed yesterday). I only posted once or twice to the list before, and no such behavior was encountered. Unfortunatly, I don't have further SMTP traces. Could there be some connectivity problem, maybe firewall related, on openmoko's side ? -- Nicolas Bougues Axialys Interactive ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Duplicate message troubleshooting
Marco Barreno wrote: Messages to the list are being duplicated again. Some of the messages are from Gmail, but not all (e.g. some are from kostyrka.org and cnlohr.com). And my last message to the list (<[EMAIL PROTECTED]>) has been duplicated thrice so far, even though I'm neither sending nor receiving that message through gmail. -myk ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Duplicate message troubleshooting
Joe Pfeiffer writes: >Marco Barreno writes: >>On Tue, Jul 24, 2007 at 10:42:01PM +0200, thus spake Andreas Kostyrka: >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> Ok, putting on my Postmaster hat, could you please provide Message Ids >>> and headers for messages from heaven.kostyrka.org that were sent >>> duplicate? Please use private mail. > >Not from that domain, but I've now seen message-ID > >[EMAIL PROTECTED] > >(from inside openmoko.com, mind you!) twice. Now four times, unless I missed it once. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Duplicate message troubleshooting
Marco Barreno writes: >On Tue, Jul 24, 2007 at 10:42:01PM +0200, thus spake Andreas Kostyrka: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Ok, putting on my Postmaster hat, could you please provide Message Ids >> and headers for messages from heaven.kostyrka.org that were sent >> duplicate? Please use private mail. Not from that domain, but I've now seen message-ID [EMAIL PROTECTED] (from inside openmoko.com, mind you!) twice. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Duplicate message troubleshooting
On Tue, Jul 24, 2007 at 10:42:01PM +0200, thus spake Andreas Kostyrka: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Ok, putting on my Postmaster hat, could you please provide Message Ids > and headers for messages from heaven.kostyrka.org that were sent > duplicate? Please use private mail. > > Andreas I must apologize--I got some notes mixed up and listed the wrong domain. Actually I don't have a record of emails being duplicated from kostyrka.org. I have seen duplicate messages from cnlohr.com (Message ID [EMAIL PROTECTED]) and axialys.net (Message ID [EMAIL PROTECTED]), however. Again, sorry for my confusion. Marco ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Duplicate message troubleshooting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ok, putting on my Postmaster hat, could you please provide Message Ids and headers for messages from heaven.kostyrka.org that were sent duplicate? Please use private mail. Andreas Marco Barreno wrote: > Messages to the list are being duplicated again. Some of the messages > are from Gmail, but not all (e.g. some are from kostyrka.org and > cnlohr.com). I can try to help debug the problem from the Gmail end > if an admin on the list machine can send me verbose SMTP logs; please > see below for details. Harald or Sean, can one of you send detailed > logs? Anyone else? > > Some Gmail message IDs with duplicated messages today: > [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > Thanks, > Marco > > > - Forwarded message from Marco Barreno <[EMAIL PROTECTED]> - > > From: Marco Barreno <[EMAIL PROTECTED]> > Date: Fri, 13 Jul 2007 14:36:57 -0700 > To: "Wolfgang S. Rupprecht" <[EMAIL PROTECTED]> > Cc: community@lists.openmoko.org > Subject: Re: gmail.com problems and this list > > Hi everyone, > > > Short version: > > It seems the duplicated messages are not just a Gmail problem: mails > are also being duplicated from starband.net and possibly others as > well, so it seems the problem is likely something on the openmoko side > that only happens to cause duplicates with some sending domains and > not others. I'ts also not consistent; some messages from Gmail and > starband.net are duplicated while others aren't. > > I've checked with the Gmail team, and the duplicated messages from > Gmail are happening because Gmail doesn't receive the SMTP OK from the > openmoko list server, so it retransmits because it thinks the messages > don't get delivered. To debug further, an admin on the list machine > needs to enable verbose SMTP logging if it's not already enabled and > provide information about if/when the OK is sent. Here are some > example message IDs for which the logs would be useful: > [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED] > If verbose logging isn't already enabled, however, enabling it and > then sending logs for any future duplicated messages would work too. > > > Detailed version: > > On Mon, Jul 09, 2007 at 11:14:03PM -0700, thus spake Wolfgang S. Rupprecht: >> 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. > > Even ignoring the messed-up DNS for the moment, doing an SMTP callback > is not a good way to check existence of an email account. For one > thing, whenever a spammer spoofs a From address in an innocent domain, > that domain can get bombarded with callbacks. For another thing, > spammers sometimes use RCPT commands themselves to check existence of > email addresses, so ISPs are likely to consider many such requests to > be abusive behavior. In the case of a large ISP (such as Gmail), if a > lot of email is sent to a destination that does callbacks, the > frequency of callbacks can trigger abuse prevention measures. See > http://en.wikipedia.org/wiki/Callback_verification for more drawbacks. > (In particular, note: "If a server receives a lot of spam, it will do > a lot of callbacks and if those addresses are invalid, the server will > look very similar to a spammer who is doing a dictionary attack to > harvest addresses. This in turn might get the server blacklisted > elsewhere.") > > For these reasons, Gmail strongly recommends avoiding callbacks and > instead checking SPF records (Sender Policy Framework, provided via > DNS) to verify that the mail is indeed coming from Google (i.e. the > SMTP connection is coming from an IP authorized to send email on > behalf of Google). > > However, in this case it does not seem that the problem was caused by > the callbacks. The openmoko server accepted the mail (which it > wouldn't do if the callback failed to verify the sender) and the DATA > command was sent, but Gmail never received the next SMTP OK > acknowledgment before timing out. So one of four things was > happening: > > 1) openmoko never sent the OK -- problem on openmoko end > 2) openmoko waited too long before sending the OK and SMTP timed out > -- seems to indicate problem on the openmoko end > 3) the OK was lost in transit -- network difficulties, neither side > at fault > 4) the OK was received by Gmail -- problem at the Gmail end > > Since at least one other domain i
