1 - debian bug #377135/freeaddrinfo()?
2 - log/print warning if fetchmail uses TLS without configuration,
3 to avoid users being surprised (see Debian Bug#294547).
4 - allow full user@domain mappings in multidrop matching
5 (is this perhaps a 6.4.0 issue?) see Andrew Longland-Meech's
6 multidrop problems on fetchmail-users
7 - Patterson: --logfile w/ ~/blah confuses fetchmail;
8 see thread [fetchmail-users] option -v not working...
9 - Uli Zappe: [fetchmail-users] [BUG] fetchmail daemon does not resume
10 fetching after a network outage (has probable analysis)
11 - check recent list mail
12 - check Debian BTS and other bug trackers
13 - better logging (log all headers)
14 - check strict envelope N Received parsing, mail from Admin Att on
16 - document Received: parsing expectations
17 - revise FAQ, continue in section T.
18 - 6.3.4-pending-deletes.patch
19 - Add info whether Keywords are global, server or user keywords
20 - merge BerliOS IMAP AUTHENTICATE EXTERNAL patch