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