1 Note that there is a separate todo.html with different content than this.
4 - audit if there are further untrusted data report_*() calls.
5 - Debian Bug #475239, MIME decoder may break up words (need to quote results)
6 - put bare IP addresses in brackets for SMTP (check if there are RFC
7 1123/5321/5322 differences)
8 - Debian Bug #531589: fetchmail ignores SIGUSR1 in idle mode.
9 seems non-trivial to fix: in imap_idle(), we wait for untagged
10 responses, and may be deep in SSL_peek -- and that restarts the
11 underlying blocking read() from the socket, so we never break out of
12 the SSL_peek() with SIGUSR1.
13 - Fix further occurrences of SMTP reply code handling:
14 - for proper smtp_reponse caching of multiline codes (there are some)
15 - for stomping over control characters.
16 - check if smtpname and smtpaddress in particular work as advertised,
17 thread "Fetchmail with Postfix virtual users" around 2009-09-23 on
18 fetchmail-users@, by Joost Roeleveld and Gerard Seibert.
19 - virtual domain DOCUMENTATION (rewriting @example.com to
20 @virtual.example.com possible? Joost Roeleveld, thread "Fetchmail with
21 Postfix virtual users" around 2009-09-23 on fetchmail-users@).
24 - add repoll for all kinds of auth failures
25 (requires framework to track which auth failed in auto mode)
26 - SockOpen sometimes exits with errno == 0, confusing users (found with
27 Google RealTime on Twitter)
28 - make sure the man page completely lists all options (f. i. sslcertpath) in
30 - allow \Deleted without \Seen, rf.
31 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466299
32 - document IMAP4 ACL requirements
33 - CRYPTO: log configured server name on certificate mismatch (perhaps pay
34 attention to via entries and stuff like that)
35 - CRYPTO: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432618
36 * write a table of combinations of TLS/SSL options
37 - add To: header to warning mails (authfail for instance)
38 - Fix TOCTOU race around prc_filecheck*
39 - Read CAPABILITY from greeting if present, saves one round trip.
40 - Check if LAST argument is properly validated against message count.
41 - add Message-ID: header and other SHOULD headers to warning mails?
42 - report actual SMTP error with "SMTP listener refused delivery", sugg.
43 Richard Brooksby, fetchmail-users 2010-04-06.
46 - find a better replacement for sscanf parsing - we don't usually
47 detect errors in format strings such as "* %d FETCH " because we don't
48 check if the FETCH is (a) present, (b) consumed.
49 - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471176
50 => fetchmail: support utf-8 encoding in log file
51 Revisit http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400719
52 => syslog messages are localised
53 http://lists.debian.org/debian-devel/2006/11/msg01068.html
54 - when logging to syslog, disable locale?
55 - Get rid of peeking in socket.c? MSG_PEEK seems non-portable.
56 - revise ticker, and add something like .........20%.... ... 100%
60 - Convert POP3 UIDs to X-UIDL?
61 - fetch IMAP message in one go (fetchmail-devel by Adam Simpkins
62 <simpkins@cisco.com> around Nov 2nd)?
65 - Properly free host/user entries (through C++ class instantiation and destructors...)
66 - Remove stupid options, such as spambounce, or deferred bounces for anything
68 - Do not ever guess envelope from content headers such as To:/Cc:/Resent-To: or
70 - Replace sscanf/fscanf by functions that do range checking
71 (strtol/strtoul), and make arguments unsigned long.
73 - use PS_PROTOCOL for pre-/post-connect command failures - 6.3 uses
74 PS_SYNTAX, and that's not necessarily the case. At least if the
75 command terminates with a signal, we should report PS_PROTOCOL.
76 - revisit maximum allowed rcfile permissions, fix inconsistency
77 (silently allowing g+x).
78 - make UID code more efficient, parsing is O(n^2), should be no worse
79 than O(n log n), lookup is O(n), should be O(log n).
80 * Idea for C: use <search.h> tfind/tsearch. Need to split idlist up
81 so it only keeps the ids, and use an array to track status.
82 - help systematic debugging
83 - by making logging more strict (Postfix's msg_* as example??)
84 - by adding a --loggingtest or something that emits
85 a set of test log messages at various severity levels, in order to
86 make sure people get complete logs.
87 - by adding messages where fetchmail stuffed its output.
88 - Debian Bug #454291 fetchmail --quit: should check, that pid file
89 really contains pid of fetchmail process (Dmitry Nezhevenko)
91 - feature to skip first N or all messages upon first download, or fetch
93 - download only messages whose headers match a filter (by Toby, Usenet
94 Nov 2007 de.comm.software.mailserver
95 Message-ID: <1195033726.123704.296060@k79g2000hse.googlegroups.com>)
96 - feature request by Daniel Goering <g_daniel@gmx.net> on
97 fetchmail-devel 2007-11-15: populate .fetchids from current messages.
98 (it'll probably be useful to limit this to "all but the 10 latest" or
99 "all before date this-and-that")
100 - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374514
101 "Deleting fetchids file" vs. POP3 - probably unneeded if we use IMAP UIDs.
102 - CRYPTO: change SSL/TLS UI incompatibly, making it easier to use
103 - CRYPTO: allow selection of SSL/TLS Ciphers
104 - CRYPTO: perhaps switch to libgsasl and libgnutls (which doesn't talk SSLv2,
105 but we should abandon that anyways).
106 - CRYPTO: perhaps port to NSS? Check license and features and required procedure
107 changes. - Redhat Bugs #333741 (crypto consolidation), #346891 (port fetchmail to NSS)
108 - CRYPTO: make the SSL default v3 (rather than v23).
109 - CRYPTO: remove sslfingerprint? too easily abused (see NEWS)
110 - CRYPTO: force sslcertck
111 - CRYPTO: by default forbid cleartext or other compromising password
112 schemes over insecure connections?
113 - put more hints to the FAQ (should we call it FGA?) as first support place
114 - make sure we print socket error messages such as connection reset by
115 peer to hint users the problem is not in fetchmail
116 - require envelope option for multidrop ; if not found in header, defer message?
117 - > b) When the envelope header is specified, but it isn't found, a
118 > warning is logged and the mail is forwarded to the postmaster
119 > ("WARNING: Envelope header $HEADER found, cannot identify the
120 > recipient. Forwarding to the postmaster")
121 Rob MacGregor 2007-03-16 Patch to the man page, fetchmail-devel@
122 - integrate Isaac Wilcox's test rig
123 - look at Tony Earnshaw's .spec file
124 - look at Gentoo patches
125 - remove dead replacement functions: strdup (Andreas Krennmair), ...
126 - more SMTP/LMTP error detail on message rejections even outside verbose mode.
127 Ian D. Allen, fetchmail-users. Two messages with examples.
128 What goes here? fetchmailrc location, server, port, user, folder, anything else?
129 - see if "AUTH SSH" can be made to work for POP3
130 - revisit BerliOS patches
131 - check recent list mail
132 - check Debian BTS and other bug trackers
133 - better logging (log all headers, log forward destination + method)
134 - check strict envelope N Received parsing,
135 see mail from Admin Att on fetchmail-users
136 - 6.3.4-pending-deletes.patch
137 - fetchmail -s with running daemon complains rather than silently
139 - send warning message when connection fails?
140 - check FAQ O5 - do we really prefer From: over envelope?!?
141 - add code to allow safe authentication schemes if TLS fails
142 - make APOP an authenticator, integrate with regular auto authentication
143 but stuff it at the end
144 - allow forcing RETR (RETR vs. TOP, fetchmail-users, drbob 2008-01-11)
146 - make logfile more useful (redirect not only in daemon mode)
147 - close/reopen logfile on certain signals (for newsyslog/logrotate
149 - for virtual mapping, we don't currently support local user aliases or
150 regexp matching with replacement. This would be useful for hosting
151 several virtual domains in one multidrop mailbox, as in
158 some@one.example maps to bob-one-some@serverdomain
159 another@two.example maps to bob-two-example@serverdomain
161 we can strip the bob-*, but but we don't support domain catchalls
162 here, and we cannot currently delegate or rewrite the remaining
163 one-* or two-* users in a useful way. All local parts of the upstream
164 domains must be known and mapped in the configuration file.
165 (See fetchmail-users, Michelle Konzack, 2009-05-03, "4 multidrop but one
166 destination server" and followup)
168 This probably entails some form of extended user mapping inside
169 fetchmail, for map_name() in transact.c, and possibly
170 find_server_names() ibidem.
171 - more verbose diagnostics, what, why, how, ... (what does fetchmail do, what
172 does it expect, what does it get instead, what does that mean, how can the
173 user fix it; references to the manual)
177 - Add info whether Keywords are global, server or user keywords
178 - consolidate multidrop documentation
179 - HOWTO (on configuration, and on SSL in particular)