[Bug 246829] New: fetchmail lost some mail
https://bugzilla.novell.com/show_bug.cgi?id=246829 Summary: fetchmail lost some mail Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jnelson-suse@jamponi.net QAContact: qa@suse.de I thought fetchmail tried hard not to lose mail? It lost the mail in this case. :-( Mon Feb 19 18:06:51 2007 1 message for AAA at BBBB (29460 octets). Mon Feb 19 18:06:52 2007 fetchmail: SMTP error: 530 5.7.0 Must issue a STARTTLS command first Mon Feb 19 18:06:52 2007 reading message AAA@BBBB:1 of 1 (29460 octets) flushed The 530 error clearly indicates failure but fetchmail flushed it anyway! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246829 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |sbrabec@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246829 meissner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |security-team@suse.de, matthias.andree@gmx.de Severity|Normal |Critical ------- Comment #1 from meissner@novell.com 2007-02-20 07:18 MST ------- is this with our current fetchmail online update installed? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246829 ------- Comment #2 from matthias.andree@gmx.de 2007-02-20 07:31 MST ------- Please show your configuration. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246829 ------- Comment #3 from matthias.andree@gmx.de 2007-02-20 07:31 MST ------- And of course, remember to mask out passwords. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246829 ------- Comment #4 from jnelson-suse@jamponi.net 2007-02-20 07:53 MST ------- This is with the previous version of the update installed, but the update only addresses MDA delivery not local smtp delivery, correct? Normallly I also have this: mda "/usr/bin/maildrop" as well but fetchmail kept barfing on a particular message (I have no idea why, both the previous and current versions) and I switched it briefly to localhost delivery, which is set to require STARTTLS. Essentially, I was working around the issue the update was there to fix (but it didn't fix it entirely for me). I wish I could have kept the message, it would have been handy for debugging. IN ANY CASE, No offense intended, but why would having my configuration help diagnose what would appear to be an easily reproduceable error (fetchmail doesn't catch 530 errors and doesn't treat them accordingly, it would appear). NOTE: The updated fetchmail behaves identically. The only difference between the new and old fetchmail is the addition of a noisy, annoying message. Furthermore, fetchmail appears to totally ignore the configuration option "sslproto ssl3" (not present below but tried). Tue Feb 20 08:49:08 2007 Invalid SSL protocol '' specified, using default (SSLv23). Tue Feb 20 08:49:08 2007 1 message for AAA at BBBB (3500 octets). Tue Feb 20 08:49:11 2007 fetchmail: SMTP error: 530 5.7.0 Must issue a STARTTLS command first Tue Feb 20 08:49:11 2007 reading message AAA@BBBB:1 of 1 (3500 octets) flushed Configuration between '=======' ============================ set postmaster "jnelson@jamponi.net" set no bouncemail set no spambounce set no showdots set properties "" set no syslog #set daemon 60 set invisible defaults no dns timeout 15 no rewrite fetchall smtphost localhost poll BBBB with proto POP3 user 'AAAA' there with password 'PASSWORD' is 'jnelson' here ssl sslfingerprint '90:08:65:4D:4C:D4:B8:E2:CB:0F:88:4B:67:94:54:5D' ============================ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246829 ------- Comment #5 from matthias.andree@gmx.de 2007-02-20 08:36 MST ------- Re comment #1: Which SMTP command caused the "530 5.7.0 Must issue a STARTTLS command first"? HELO, EHLO, FROM, RCPT? Is this - perhaps with a test message - reproducible with "fetchmail -vvv"? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246829
jnelson-suse@jamponi.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- Comment #6 from jnelson-suse@jamponi.net 2007-02-20 19:51 MST -------
Tue Feb 20 20:49:23 2007 fetchmail: SMTP< 220 turnip.jamponi.pvt ESMTP Postfix
Tue Feb 20 20:49:23 2007 fetchmail: SMTP> EHLO SOME_HOST
Tue Feb 20 20:49:23 2007 fetchmail: SMTP< 250-turnip.jamponi.pvt
Tue Feb 20 20:49:23 2007 fetchmail: SMTP< 250-PIPELINING
Tue Feb 20 20:49:23 2007 fetchmail: SMTP< 250-SIZE 10240000
Tue Feb 20 20:49:23 2007 fetchmail: SMTP< 250-VRFY
Tue Feb 20 20:49:23 2007 fetchmail: SMTP< 250-ETRN
Tue Feb 20 20:49:23 2007 fetchmail: SMTP< 250-STARTTLS
Tue Feb 20 20:49:23 2007 fetchmail: SMTP< 250-ENHANCEDSTATUSCODES
Tue Feb 20 20:49:23 2007 fetchmail: SMTP< 250-8BITMIME
Tue Feb 20 20:49:23 2007 fetchmail: SMTP< 250 DSN
Tue Feb 20 20:49:23 2007 fetchmail: forwarding to localhost
Tue Feb 20 20:49:23 2007 fetchmail: SMTP> MAIL FROM:
https://bugzilla.novell.com/show_bug.cgi?id=246829 ------- Comment #7 from matthias.andree@gmx.de 2007-02-21 01:38 MST ------- Looks like correct behavior to me. fetchmail gets a permanent error back to the sender address, so it is pointless to ever retry the message; given the fetchall keyword, the only reasonable reaction is to flush the message else fetchmail would end up trying a message again and again and again that it can never deliver. Fetchmail cannot derive from the SMTP dialog that there is a local configuration issue, but must assume that your Postfix doesn't like the sender's address. I wonder if Postfix's returning a 530 code is the right thing to see here (should be some 400 series code instead, because it's not the sender address at fault, but the history of the SMTP session), and Postfix's refusal of the RSET command is outright scary. Are there any pertinent Postfix patches in openSUSE or should we take this upstream to Wietse Venema? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246829 ------- Comment #8 from jnelson-suse@jamponi.net 2007-02-21 06:25 MST ------- (In reply to comment #7)
Looks like correct behavior to me. fetchmail gets a permanent error back to the sender address, so it is pointless to ever retry the message; given the fetchall keyword, the only reasonable reaction is to flush the message else fetchmail would end up trying a message again and again and again that it can never deliver.
It's absolutely INCORRECT behavior. For ANY REASON, fetchmail should not delete a message until it is successfully delivered. That's how fetchmail has behaved (except for bugs) for years, that's what the docs and manpage indicate, and that's what people expect. As for the fetchall keyword, that has nothing to do with deleting messages, only whether or not fetchmail will retrieve *all* messages or only ones it thinks it hasn't seen yet (used in conjunction with the 'keep' and 'uidl' directives). Fetchmail *should* try again and again.
Fetchmail cannot derive from the SMTP dialog that there is a local configuration issue, but must assume that your Postfix doesn't like the sender's address.
I wonder if Postfix's returning a 530 code is the right thing to see here (should be some 400 series code instead, because it's not the sender address at fault, but the history of the SMTP session), and Postfix's refusal of the RSET command is outright scary.
Are there any pertinent Postfix patches in openSUSE or should we take this upstream to Wietse Venema?
I don't know whether postfix should return a 4xx or 5xx error but it's not relevant - fetchmail should not delete the message and continue. That's a bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
From personal negative experience I agree with Jon. Even if postfix returns some error it would be incredibly nice from fetchmail to not throw away mails but try whatever it can to save it instead. In my case it was an accidental misconfiguration of postfix. As consequence to avoid losing mail due to fraglie
https://bugzilla.novell.com/show_bug.cgi?id=246829 ------- Comment #9 from lnussel@novell.com 2007-02-22 02:25 MST ------- postfix configurations I use procmail as mda directly which is probably even worse :) That's something Matthias has to consider as upstream author, I don't think we can nor should do anything about it in the SUSE packages. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246829 ------- Comment #10 from sbrabec@novell.com 2007-02-22 02:52 MST ------- .. For example save mail to ~/lost.mail or so and create critical syslog message to warn admin. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246829 ------- Comment #11 from matthias.andree@gmx.de 2007-02-23 02:50 MST ------- Without having actually checked code, I doubt that fetchmail's behavior has changed since 6.2.X. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246829 ------- Comment #12 from jnelson-suse@jamponi.net 2007-02-23 09:35 MST ------- A quote from the "Fetchmail FAQ": Fetchmail only sends a delete mail request to the server when either (a) it gets a positive delivery acknowledgment from the SMTP listener, or (b) it gets one of the spam-filter errors (see the description of the antispam> option) from the listener. No interrupt can cause it to lose mail. --- I'm not using the antispam directive. From the fetchmail manpage: f you don’t specify ’-k’, then fetchmail will automatically delete messages after successful delivery. From the fetchmail manpage: The protocols fetchmail uses to talk to mailservers are next to bulletproof In normal operation forwarding to port 25, no message is ever deleted (or even marked for deletion) on the host until the SMTP listener on the client side has acknowledged to fetchmail that the message has been either accepted for delivery or rejected due to a spam block. From the manpage: Return codes which fetchmail treats as antispam responses and discards the message can be set with the ’antispam’ option. This is one of the only three circumstance under which fetchmail ever discards mail (the others are the 552 and 553 errors described below, and the suppression of multidropped messages with a message-ID already seen). and By default, the list of antispam responses is empty. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246829 ------- Comment #13 from matthias.andree@gmx.de 2007-02-24 02:58 MST ------- I see that behavior does not match documentation, but fetchmail 6.2 behaves the same way, so this is a long-standing bug and changes to behavior of fetchmail 6.3.X are undesirable to be made upstream unless they fix a security issue or a recently introduced regression. I'd suggest to resolve this as "LATER" or "REMIND". The reporter has not only misconfigured his SMTP listener that doesn't accept messages for relay from 127.0.0.1, but also suppressed bounces and does not detail on the actual problem, namely messages getting stuck with --mda. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246829 ------- Comment #14 from jnelson-suse@jamponi.net 2007-02-24 16:10 MST ------- The mda problem is a separate concern. However, I'll note that fetchmail won't delete messages until the mda returns 0, which is very different than the behavior seen with delivery via smtp. The MTA is *not* misconfigured -- it works fine and delivers MANY messages a day from localhost as well as others -- it just doesn't accept delivery without STARTTLS. I am suppressing bounces because I don't want *bounces*, I want fetchmail to either deliver the message and delete from the server or fail but retain the message. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246829
Petr Cerny
https://bugzilla.novell.com/show_bug.cgi?id=246829#c15
Petr Cerny
https://bugzilla.novell.com/show_bug.cgi?id=246829#c16
Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=246829#c17
Petr Cerny
https://bugzilla.novell.com/show_bug.cgi?id=246829
User matthias.andree@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=246829#c18
Matthias Andree
https://bugzilla.novell.com/show_bug.cgi?id=246829
User pcerny@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=246829#c19
Petr Cerny
https://bugzilla.novell.com/show_bug.cgi?id=246829
User pcerny@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=246829#c20
--- Comment #20 from Petr Cerny
https://bugzilla.novell.com/show_bug.cgi?id=246829
User pcerny@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=246829#c21
Petr Cerny
participants (1)
-
bugzilla_noreply@novell.com