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