From: Eddie <st...@at...> - 2007-01-25 20:40:07
|
I've been running some tests, for about 3 days now, using fetchmail, in daemon mode, to pull my mail down from a POP server every 10 minutes, and then pass it off to procmail. As far as I can make out, reading the man pages, I am running in singledrop-mode. This appears to work fine, except on one or two e-mails, I got the following error: Jan 24 11:51:22 The-Tardis fetchmail[22142]: awakened at Wed 24 Jan 2007 11:51:22 AM PST Jan 24 11:51:23 The-Tardis fetchmail[22142]: 2 messages for xxxxxxxx at pop5.xxxxxxxx.net (3345 octets). Jan 24 11:51:23 The-Tardis fetchmail[22142]: reading message xxx...@po...:1 of 2 (2187 octets) Jan 24 11:51:23 The-Tardis sm-mta[22324]: l0OJpNXo022324: ruleset=check_mail, arg1=<ke...@la...""chantelfisher" ame...@sh...">, relay=localhost [127.0.0.1], reject=553 5.1.8 <ke...@la...""chantelfisher" ame...@sh...">... Domain of sender address ke...@la...chantelfisher ame...@sh... does not exist Jan 24 11:51:23 The-Tardis fetchmail[22142]: SMTP error: 553 5.1.8 <ke...@la...""chantelfisher" ame...@sh...">... Domain of sender address ke...@la...chantelfisher ame...@sh... does not exist Jan 24 11:51:23 The-Tardis sm-mta[22324]: l0OJpNXo022324: from=<ke...@la...""chantelfisher" ame...@sh...">, size=2187, class=0, nrcpts=0, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1] Jan 24 11:51:23 The-Tardis fetchmail[22142]: flushed Jan 24 11:51:23 The-Tardis fetchmail[22142]: reading message xxx...@po...:2 of 2 (1158 octets) Jan 24 11:51:24 The-Tardis sm-mta[22324]: l0OJpNXp022324: from=<To...@li...>, size=1309, class=0, nrcpts=1, msgid=<200...@Th...>, bodytype=7BIT, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1] Jan 24 11:51:24 The-Tardis fetchmail[22142]: flushed Jan 24 11:51:24 The-Tardis fetchmail[22142]: sleeping at Wed 24 Jan 2007 11:51:24 AM PST Jan 24 11:51:42 The-Tardis sm-mta[22325]: l0OJpNXp022324: to=<eddie@localhost>, delay=00:00:19, xdelay=00:00:18, mailer=local, pri=31584, dsn=2.0.0, stat=Sent In this snippet, 2 messages were retrieved from the server. For the first one, it looks like sendmail tried to deliver the mail, and failed, instead of putting it into the mailbox for eddie. The 2nd message was hadled correctly, in the same way every other message has been. Here's the .fetchmailrc contents: set daemon 600 set syslog poll pop5.xxxxxxxx.net proto pop3 user "xxxxxxxx" pass xxxxxxxx The user in .fetchmailrc is *not* the same as the user, eddie, that runs this process. So, why, if I'm running in singledrop-mode was that one message treated as if I am running multidrop-mode, and should I be concerned about this. Incoming port 25 is blocked by my firewall, so not "outside" smtp servers can talk to my sendmail. Cheers. |
From: Rob M. <rob...@gm...> - 2007-01-25 21:29:34
|
On 1/25/07, Eddie <st...@at...> wrote: > I've been running some tests, for about 3 days now, using fetchmail, in daemon > mode, to pull my mail down from a POP server every 10 minutes, and then pass > it off to procmail. As far as I can make out, reading the man pages, I am > running in singledrop-mode. This appears to work fine, except on one or two > e-mails, I got the following error: > > Jan 24 11:51:23 The-Tardis sm-mta[22324]: l0OJpNXo022324: ruleset=check_mail, > arg1=<ke...@la...""chantelfisher" ame...@sh...">, > relay=localhost [127.0.0.1], reject=553 5.1.8 > <ke...@la...""chantelfisher" ame...@sh...">... Domain of sender > address ke...@la...chantelfisher ame...@sh... does not exist Sendmail generates a permanent failure as the sender's address doesn't resolve. > Jan 24 11:51:23 The-Tardis fetchmail[22142]: SMTP error: 553 5.1.8 > <ke...@la...""chantelfisher" ame...@sh...">... Domain of sender > address ke...@la...chantelfisher ame...@sh... does not exist > Jan 24 11:51:23 The-Tardis sm-mta[22324]: l0OJpNXo022324: > from=<ke...@la...""chantelfisher" ame...@sh...">, size=2187, > class=0, nrcpts=0, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1] > Jan 24 11:51:23 The-Tardis fetchmail[22142]: flushed Fetchmail drops it on the floor, as per the man page (see SMTP/ESMTP ERROR HANDLING). > In this snippet, 2 messages were retrieved from the server. For the first > one, it looks like sendmail tried to deliver the mail, and failed, instead of > putting it into the mailbox for eddie. I fail to see the problem. Sendmail is doing what you've told it to - rejecting emails with a sender domain that doesn't resolve. Fetchmail is doing what it's supposed to - dropping emails that the SMTP server rejects with an error code of 553. -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche |
From: Eddie <st...@at...> - 2007-01-25 21:55:58
|
On Thursday 25 January 2007 12:28, Rob MacGregor wrote: > On 1/25/07, Eddie <st...@at...> wrote: > > I've been running some tests, for about 3 days now, using fetchmail, in > > daemon mode, to pull my mail down from a POP server every 10 minutes, and > > then pass it off to procmail. As far as I can make out, reading the man > > pages, I am running in singledrop-mode. This appears to work fine, > > except on one or two e-mails, I got the following error: > > > > Jan 24 11:51:23 The-Tardis sm-mta[22324]: l0OJpNXo022324: > > ruleset=check_mail, arg1=<ke...@la...""chantelfisher" > > ame...@sh...">, > > relay=localhost [127.0.0.1], reject=553 5.1.8 > > <ke...@la...""chantelfisher" ame...@sh...">... Domain of > > sender address ke...@la...chantelfisher ame...@sh... does > > not exist > > Sendmail generates a permanent failure as the sender's address doesn't > resolve. > > > Jan 24 11:51:23 The-Tardis fetchmail[22142]: SMTP error: 553 5.1.8 > > <ke...@la...""chantelfisher" ame...@sh...">... Domain of > > sender address ke...@la...chantelfisher ame...@sh... does > > not exist Jan 24 11:51:23 The-Tardis sm-mta[22324]: l0OJpNXo022324: > > from=<ke...@la...""chantelfisher" ame...@sh...">, > > size=2187, class=0, nrcpts=0, proto=ESMTP, daemon=MTA, relay=localhost > > [127.0.0.1] Jan 24 11:51:23 The-Tardis fetchmail[22142]: flushed > > Fetchmail drops it on the floor, as per the man page (see SMTP/ESMTP > ERROR HANDLING). > > > In this snippet, 2 messages were retrieved from the server. For the > > first one, it looks like sendmail tried to deliver the mail, and failed, > > instead of putting it into the mailbox for eddie. > > I fail to see the problem. Sendmail is doing what you've told it to - > rejecting emails with a sender domain that doesn't resolve. Fetchmail > is doing what it's supposed to - dropping emails that the SMTP server > rejects with an error code of 553. OK, I guess it was my misunderstanding of exactly how sendmail works. :-( I'd assumed that fetchmail would direct all mail, regardless, to my inbox, which I now realise it is. What I didn't know, was that even though sendmail *is* trying to deliver it locally, it still validates the sender domain. So, it was a validation that failed, not an attempt at sending that failed. Thanks for the explanation. -- Cheers |
From: Rob M. <rob...@gm...> - 2007-01-25 22:47:41
|
On 1/25/07, Eddie <st...@at...> wrote: > > OK, I guess it was my misunderstanding of exactly how sendmail works. :-( > > I'd assumed that fetchmail would direct all mail, regardless, to my inbox, > which I now realise it is. Fetchmail directs all email to your SMTP server, not your inbox (to be picky). > What I didn't know, was that even though sendmail > *is* trying to deliver it locally, it still validates the sender domain. So, > it was a validation that failed, not an attempt at sending that failed. You can disable that check (see cf/README - accept_unresolvable_domains), however given that almost all mail with an unresolvable sender domain is spam, you're not likely to benefit from it. -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche |