1 Note that there is a separate todo.html with different content than this.
4 - Debian Bug #475239, MIME decoder may break up words (need to quote results)
5 - Replace sscanf/fscanf by functions that do range checking (strtol/strtoul) :-/
6 See http://sourceware.org/bugzilla/show_bug.cgi?id=6453
9 - allow \Deleted without \Seen, rf.
10 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466299
11 - document IMAP4 ACL requirements
12 - log configured server name on certificate mismatch (perhaps pay
13 attention to via entries and stuff like that)
14 - BerliOS Bug #11576, thread on fetchmail users "Invalid SSL certificate" by
15 Philip Susi, SSL negotiation does not use ERR_error_string(3ssl) to report
16 errors in a readable way, we just report socket errors with no good reason.
17 - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432618
18 * write a table of combinations of TLS/SSL options
19 - add To: header to warning mails (authfail for instance)
20 - Fix TOCTOU race around prc_filecheck*
21 - Read CAPABILITY from greeting if present, saves one round trip.
24 - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471176
25 => fetchmail: support utf-8 encoding in log file
26 Revisit http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400719
27 => syslog messages are localised
28 http://lists.debian.org/debian-devel/2006/11/msg01068.html
29 - Get rid of peeking in socket.c? MSG_PEEK seems non-portable.
32 - find a solution for the "invalid header" discards message problem
33 (escape headers and stuff reminder into body)
34 - add Message-ID: header and other SHOULD headers to warning mails?
35 - report multiline SMTP errors properly (sample in private mail from
36 Earl Chew, 2007-07-30T02:28), Debian Bug #529899
37 => requires reworking SMTP_ok to actually not only read the last line
38 of multiline replies, but buffer.
39 - revise ticker, and add something like .........20%.... ... 100%
43 - Convert POP3 UIDs to X-UIDL?
44 - fetch IMAP message in one go (fetchmail-devel by Adam Simpkins
45 <simpkins@cisco.com> around Nov 2nd)?
48 - use PS_PROTOCOL for pre-/post-connect command failures - 6.3 uses
49 PS_SYNTAX, and that's not necessarily the case. At least if the
50 command terminates with a signal, we should report PS_PROTOCOL.
51 - revisit maximum allowed rcfile permissions, fix inconsistency
52 (silently allowing g+x).
53 - make UID code more efficient, parsing is O(n^2), should be no worse
55 - help systematic debugging
56 - by making logging more strict (Postfix's msg_* as example??)
57 - by adding a --loggingtest or something that emits
58 a set of test log messages at various severity levels, in order to
59 make sure people get complete logs.
60 - by adding messages where fetchmail stuffed its output.
61 - Debian Bug #454291 fetchmail --quit: should check, that pid file
62 really contains pid of fetchmail process (Dmitry Nezhevenko)
64 - feature to skip first N or all messages upon first download
65 - download only messages whose headers match a filter (by Toby, Usenet
66 Nov 2007 de.comm.software.mailserver
67 Message-ID: <1195033726.123704.296060@k79g2000hse.googlegroups.com>)
68 - feature request by Daniel Goering <g_daniel@gmx.net> on
69 fetchmail-devel 2007-11-15: populate .fetchids from current messages.
70 (it'll probably be useful to limit this to "all but the 10 latest" or
71 "all before date this-and-that")
72 - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374514
73 "Deleting fetchids file" vs. POP3 - probably unneeded if we use IMAP UIDs.
74 - change SSL/TLS UI incompatibly, making it easier to use
75 - allow selection of SSL/TLS Ciphers
76 - perhaps switch to libgsasl and libgnutls (which doesn't talk SSLv2)
77 - make the SSL default v3 (rather than v23).
78 - put more hints to the FAQ (should we call it FGA?) as first support place
79 - make sure we print socket error messages such as connection reset by
80 peer to hint users the problem is not in fetchmail
81 - require envelope option for multidrop ; if not found in header, defer message?
82 - > b) When the envelope header is specified, but it isn't found, a
83 > warning is logged and the mail is forwarded to the postmaster
84 > ("WARNING: Envelope header $HEADER found, cannot identify the
85 > recipient. Forwarding to the postmaster")
86 Rob MacGregor 2007-03-16 Patch to the man page, fetchmail-devel@
87 - integrate Isaac Wilcox's test rig
88 - look at Tony Earnshaw's .spec file
89 - look at Gentoo patches
90 - remove dead replacement functions: strdup (Andreas Krennmair), ...
91 - more SMTP/LMTP error detail on message rejections even outside verbose mode.
92 Ian D. Allen, fetchmail-users. Two messages with examples.
93 What goes here? fetchmailrc location, server, port, user, folder, anything else?
94 - see if "AUTH SSH" can be made to work for POP3
95 - revisit BerliOS patches
96 - check recent list mail
97 - check Debian BTS and other bug trackers
98 - better logging (log all headers, log forward destination + method)
99 - check strict envelope N Received parsing,
100 see mail from Admin Att on fetchmail-users
101 - 6.3.4-pending-deletes.patch
102 - fetchmail -s with running daemon complains rather than silently
104 - send warning message when connection fails?
105 - when logging to syslog, disable locale?
106 - check FAQ O5 - do we really prefer From: over envelope?!?
107 - add code to allow safe authentication schemes if TLS fails
108 - make APOP an authenticator, integrate with regular auto authentication
109 but stuff it at the end
110 - allow forcing RETR (RETR vs. TOP, fetchmail-users, drbob 2008-01-11)
112 - make logfile more useful (redirect not only in daemon mode)
113 - for virtual mapping, we don't currently support local user aliases or
114 regexp matching with replacement. This would be useful for hosting
115 several virtual domains in one multidrop mailbox, as in
122 some@one.example maps to bob-one-some@serverdomain
123 another@two.example maps to bob-two-example@serverdomain
125 we can strip the bob-*, but but we don't support domain catchalls
126 here, and we cannot currently delegate or rewrite the remaining
127 one-* or two-* users in a useful way. All local parts of the upstream
128 domains must be known and mapped in the configuration file.
129 (See fetchmail-users, Michelle Konzack, 2009-05-03, "4 multidrop but one
130 destination server" and followup)
132 This probably entails some form of extended user mapping inside
133 fetchmail, for map_name() in transact.c, and possibly
134 find_server_names() ibidem.
137 - Add info whether Keywords are global, server or user keywords
138 - consolidate multidrop documentation