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