Note that there is a separate TODO.txt document of +different content than this.
+I try to respond to urgent bug reports in a timely way. But fetchmail is now pretty mature and I have many other projects, so I don't personally chase obscure or marginal problems. Help with any @@ -24,10 +27,6 @@ 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.
@@ -37,19 +36,12 @@ that everyone can alter. 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 @@ -57,8 +49,6 @@ reports.
SSL validation prints CommonName mismatch more than once.
-Alan Munday suggests message change MULTIDROP without ENVELOPE:
fetchmail: warning: MULTIDROP configuration for pop.example.org requires the envelope option to be set! @@ -79,8 +69,6 @@ for bounce messages."In the SSL support, add authentication of Certifying Authority (Is this a Certifying Authority we recognize?).
-Debian wishlist item 181157: ssl key learning for self-signed certificates.
-Laszlo Vecsey writes: "I believe qmail uses a technique of writing temporary files to nfs, and then moving them into place to ensure that they're written. Actually a hardlink is made to the