|
From: Gary S. <ga...@ga...> - 2004-07-23 12:13:58
|
Hi, This is a problem which is on going on the fetchmail-friends list at ccil.org. I thought I would post it here as well in case people have migrated. Any help will would mich appreciated. +++++++++++++ I have a dial up connection and I am using latest fetchmail (6.2.5) to get the mail from a POP3 mailbox and I am using postfix (V1.1.11) as the local SMTP server and all this is running on RedHat 9.0. In general my email is getting through but I do get the following errors in my mail logs. Jul 18 13:25:51 exodus postfix/smtpd[25020]: warning: Illegal address syntax from unknown[127.0.0.1] in MAIL command: <col...@li...: (qmail 21055 invoked from network); 18 Jul 2004 07:09:56 -0000> It is about a message which I am expecting... I am guessing the error is occuring when fetchmail talks to postfix to submit the message for local delivery. Looking at the "illegal address" it is clear that the Received line is mixed in with the address. I have now traced one of my problem messages with fetchmail -v -v and this is what I get fetchmail: POP3> LIST 7 fetchmail: POP3< +OK 7 8568 fetchmail: POP3> TOP 7 99999999 fetchmail: POP3< +OK headers follow. reading message gar...@ma...:7 of 8 (8568 octets) About to rewrite Return-Path: <c615952fff0eb8febd27fbc7b1dd4792bdeb77a3023419e0f4063f69cReceived: (qmail 22262 invoked from network); 23 Jul 2004 04:01:03 -0000 Rewritten version is Return-Path: <c615952fff0eb8febd27fbc7b1dd4792bdeb77a3023419e0f4063f69cReceived: (qmail 22262 invoked from network); 23 Jul 2004 04:01:03 -0000 About to rewrite Reply-To: c61...@eb... Rewritten version is Reply-To: c61...@eb... About to rewrite From: "BBC daily email" <dai...@bb...> Rewritten version is From: "BBC daily email" <dai...@bb...> About to rewrite To: ga...@ga... Rewritten version is To: ga...@ga... fetchmail: forwarding to localhost fetchmail: SMTP> MAIL FROM:<c615952fff0eb8febd27fbc7b1dd4792bdeb77a3023419e0f4063f69cReceived: (qmail 22262 invoked from network); 23 Jul 2004 04:01:03 -00...@ma...> BODY=8BITMIME SIZE=8568 fetchmail: SMTP< 501 Bad address syntax fetchmail: SMTP error: 501 Bad address syntax fetchmail: SMTP< 220 exodus.aca-vulcan.ro ESMTP Postfix fetchmail: SMTP> HELO localhost fetchmail: SMTP< 250 exodus.aca-vulcan.ro fetchmail: SMTP> MAIL FROM:<FETCHMAIL-DAEMON@exodus> fetchmail: SMTP< 250 Ok fetchmail: SMTP> RCPT TO:<c615952fff0eb8febd27fbc7b1dd4792bdeb77a3023419e0f4063f69cReceived: (qmail 22262 invoked from network); 23 Jul 2004 04:01:03 -0000> fetchmail: SMTP< 501 Bad address syntax fetchmail: SMTP> QUIT fetchmail: SMTP< 221 Bye fetchmail: SMTP> RSET fetchmail: SMTP< 250 Ok ...... flushed fetchmail: POP3> DELE 7 fetchmail: POP3< +OK Deleted. Clearly the address which fetchmail is submitting to the SMTP server in the MAIL FROM command is broken. Of course the question is what was the origial like. The problem is that I don't know as the message has now been deleted. Before this I removed the antispam option from my fetchmailrc file. However the email is still being deleted even though it was not delivered or non-delivered. Is that behaviour correct? Any more clues? Thanks, Gary -- Gary Sims (ga...@ga...) Vulcan, Brasov, Romania |
|
From: Graham W. <bo...@de...> - 2004-07-24 08:41:44
|
On Fri, Jul 23, 2004 at 01:13:24PM +0300, Gary Sims wrote: > Hi, Hello. > Clearly the address which fetchmail is submitting to the SMTP server in the > MAIL FROM command is broken. Of course the question is what was the origial > like. The problem is that I don't know as the message has now been deleted. Without the original message, it will be kind of difficult to determine where the problem is. Is the original message at fault, or is fetchmail mangling something somehow? > Before this I removed the antispam option from my fetchmailrc file. However > the email is still being deleted even though it was not delivered or > non-delivered. Is that behaviour correct? I don't think so. It seems like the SMTP server gave a 501 response, in which case I would expect fetchmail to bounce the message. Maybe it tried? -- gram |
|
From: Gary S. <ga...@ga...> - 2004-07-24 10:23:15
|
Hi everyone, OK, I have now seen that this isn't a fetchmail problem. I added the KEEP option to my fetchmailrc and I used telnet to talk to my ISP's POP3 server. The Return-Path is broken when it is sent from my ISP. Interesting enough I also signed up to this BBC message on a web mail account and it arrives there OK without any corruption, so the problem is definatley with my ISP. Thanks (everyone) for all your help. Gary -- Gary Sims (ga...@ga...) Vulcan, Brasov, Romania |
|
From: Rob F. <rf...@fu...> - 2004-07-24 16:59:10
|
Gary Sims wrote: > OK, I have now seen that this isn't a fetchmail problem. I added the > KEEP option to my fetchmailrc and I used telnet to talk to my ISP's POP3 > server. The Return-Path is broken when it is sent from my ISP. > Interesting enough I also signed up to this BBC message on a web mail > account and it arrives there OK without any corruption, so the problem > is definatley with my ISP. I'm curious about what the broken Return-Path header looks like. It would be nice if we could do something besides drop the message on the floor. -- ==============================| "A microscope locked in on one point Rob Funk <rf...@fu...> |Never sees what kind of room that it's in" http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind" |
|
From: Rob <rob...@ho...> - 2004-07-24 23:26:44
|
> -----Original Message----- > From: fet...@be... > [mailto:fet...@be...] On Behalf Of Rob Funk > > I'm curious about what the broken Return-Path header looks > like. It would > be nice if we could do something besides drop the message on > the floor. Details are on the other list's archive, where this problem has had more discussion :) From memory there were 2 I saw, one that was concatenated with the Received header, another that seemed to be missing the closing >. What I, personally, would like is that any "broken" message (missing the header line separator, addresses with invalid format etc), could optionally be forwarded as a plain text attachment to the postamster address. That way those who want to receive everything can, and those who're happy to lose it on the assumption is spam/virus/whatever related can drop it. PLEASE - keep list traffic on the list. Email sent directly to me may be ignored utterly. -- Rob | What part of "no" was it you didn't understand? |