From 9e69418a4b0a995f8bd371639acebc08cdeb7166 Mon Sep 17 00:00:00 2001
From: Matthias Andree I try to respond to urgent bug reports in a timely way. But
@@ -31,6 +22,51 @@ fetchmail is now pretty mature and I have many other projects, so I
don't personally chase obscure or marginal problems. Help with any
of these will be cheerfully accepted. SSL trust model violation: (Brian Candler)
+http://lists.ccil.org/pipermail/fetchmail-friends/2004-April/008516.html Let IMAP code use UID and UIDVALIDITY rather than relying on flags
+that everyone can alter. POP3 hang when polling mail with NUL char that is rejected (David
+Greaves) https://lists.berlios.de/pipermail/fetchmail-devel/2004-October/000154.html Remove spaces after MAIL FROM: or RCPT TO: et al. in BSMTP output
+(sink.c) It has been reported that multidrop name matching fails when the
+name to be matched contains a Latin-1 umlaut. Dollars to doughnuts
+this is some kind of character sign-extension problem. Trouble is,
+it's very likely in the BIND libraries. Someone should go in with a
+debugger and check this. Move everything to using service strings rather that port
+numbers, so we can get rid of ENABLE_INET6 everywhere but in
+SockOpen (this will get rid of the kluge in rcfile_y.y). The
+Debian bug-tracking page for fetchmail lists other bug
+reports. SSL validation prints CommonName mismatch more than once. Alan Munday suggests message change MULTIDROP without ENVELOPE: Feature request from "Ralf G. R. Bergs" <rabe@RWTH-Aachen.DE> "When
fetchmail downloads mail and Exim+SpamAssassin detecs an incoming
message as spam, fetchmail tries to bounce it. Unfortunately it uses
@@ -40,18 +76,6 @@ and fetchmail picks the internal name of my host.) So I'd like to have
a config statement that allows me to explicitly set a senderaddress
for bounce messages." POP3 can't presently distinguish a wedged or down server from an
-authentication failure. Possible fix: after issuing a PASS command.
-wait 300 (xx) seconds for a "-ERR" or a "+OK" . If nothing comes
-back, retry at the next poll event and generate no errors. If we
-get an -ERR then log an authentication failure. It has been reported that multidrop name matching fails when the
-name to be matched contains a Latin-1 umlaut. Dollars to doughnuts
-this is some kind of character sign-extension problem. Trouble is,
-it's very likely in the BIND libraries. Someone should go in with a
-debugger and check this. In the SSL support, add authentication of Certifying Authority
(Is this a Certifying Authority we recognize?).
-
-
-
-
-Back to Eric's Home Page
-Up to Site Map
-$Date: 2004/01/13 03:21:41 $
-
Fetchmail Bugs and To-Do Items
Serious
+
+Normal
+
+Cosmetic
+
+
+fetchmail: warning: MULTIDROP configuration for pop.example.org requires the envelope option to be set!
+fetchmail: warning: Check ENVELOPE option if fetchmail sends all mail to postmaster!
+
+
+Feature requests/Wishlist items
+
Move everything to using service strings rather that port -numbers, so we can get rid of ENABLE_INET6 everywhere but in -SockOpen (this will get rid of the kluge in rcfile_y.y).
- -John Summerfield suggests that specifying a localname containing -@ ought to be treated as an smtpname option, with the domain part -removed for other purposes such as local-address matching.
-Maybe refuse multidrop configuration unless "envelope" is _explicitly_ configured (and tell the user he needs to configure the envelope -option) and change the envelope default to nil. This would +option) and change the envelope default to nil. This would prevent a significant class of shoot-self-in-foot problems.
Given the above change, perhaps treat a delivery as "temporarily @@ -94,7 +110,7 @@ could be alleviated by pipelining the list commands, which needs either asynchronous reading while sending the commands, or knowing the send buffer, to avoid deadlocks. Unfortunately, I don't have the time to delve deeper into the code and look around.
- +Note that such a pipelining function would be of universal use, so it should not be in pop3.c or something. I'd think the best approach is to call a "sender" function with the command and a callback, and the sender @@ -105,23 +121,12 @@ callback function for each reply received.
requirements. - -The -Debian bug-tracking page for fetchmail lists other bug -reports.
-Back to Eric's Home Page | -Up to Site Map | -$Date: 2004/01/13 03:21:41 $ | -