Update.

[~andy/fetchmail] / TODO.txt

diff --git a/TODO.txt b/TODO.txt
index b0341b9f54f1f54e26b8c0b7cb54c60f5599b5c5..87479a3bfa8342e607de817ee64762d77b1294e6 100644 (file)
--- a/TODO.txt
+++ b/TODO.txt
@@ -1,17 +1,35 @@
-- allow full user@domain mappings in multidrop matching
-  (is this perhaps a 6.4.0 issue?) see Andrew Longland-Meech's
-  multidrop problems on fetchmail-users
-- Patterson: --logfile w/ ~/blah confuses fetchmail;
-  see thread [fetchmail-users] option -v not working...
-- Uli Zappe: [fetchmail-users] [BUG] fetchmail daemon does not resume
-  fetching after a network outage (has probable analysis)
+6.4:
+- disable SOCKS by default? Add hooks to do that?
+- > b) When the envelope header is specified, but it isn't found, a
+  > warning is logged and the mail is forwarded to the postmaster
+  > ("WARNING: Envelope header $HEADER found, cannot identify the
+  > recipient.  Forwarding to the postmaster")
+  Rob MacGregor 2007-03-16 Patch to the man page, fetchmail-devel@
+- integrate Isaac Wilcox's test rig
+- look at Tony Earnshaw's .spec file
+- look at Gentoo patches
+- remove dead replacement functions: strdup (Andreas Krennmair), ...
+- more SMTP/LMTP error detail on message rejections even outside verbose mode.
+  Ian D. Allen, fetchmail-users. Two messages with examples.
+  What goes here? fetchmailrc location, server, port, user, folder, anything else?
+- see if "AUTH SSH" can be made to work for POP3
+- revisit BerliOS patches
 - check recent list mail
 - check Debian BTS and other bug trackers
-- better logging (log all headers)
-- check strict envelope N Received parsing, mail from Admin Att on
-  fetchmail-users
-- document Received: parsing expectations
-- revise FAQ, continue in section T.
+- better logging (log all headers, log forward destination + method)
+- check strict envelope N Received parsing,
+  see mail from Admin Att on fetchmail-users
 - 6.3.4-pending-deletes.patch
+- fetchmail -s with running daemon complains rather than silently
+  restarting daemon
+- send warning message when connection fails?
+- when logging to syslog, disable locale?
+- check FAQ O5 - do we really prefer From: over envelope?!?
+- add code to allow safe authentication schemes if TLS fails
+- make APOP an authenticator, integrate with regular auto authentication
+  but stuff it at the end
+- use SASL?
+
+DOCUMENTATION:
 - Add info whether Keywords are global, server or user keywords
-- merge BerliOS IMAP AUTHENTICATE EXTERNAL patch
+- consolidate multidrop documentation