2 - mark fetchmail -vvv in the FAQ
3 - find a solution for the "invalid header" discards message problem
4 (escape headers and stuff reminder into body)
5 - https://bugzilla.novell.com/show_bug.cgi?id=247233
6 (same as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421446)
7 might be our fallback of setting sslproto to ""? But what triggers it?
10 - make the SSL default v3 (rather than v23).
11 - put more hints to the FAQ (should we call it FGA?) as first support place
12 - make sure we print socket error messages such as connection reset by
13 peer to hint users the problem is not in fetchmail
14 - > b) When the envelope header is specified, but it isn't found, a
15 > warning is logged and the mail is forwarded to the postmaster
16 > ("WARNING: Envelope header $HEADER found, cannot identify the
17 > recipient. Forwarding to the postmaster")
18 Rob MacGregor 2007-03-16 Patch to the man page, fetchmail-devel@
19 - integrate Isaac Wilcox's test rig
20 - look at Tony Earnshaw's .spec file
21 - look at Gentoo patches
22 - remove dead replacement functions: strdup (Andreas Krennmair), ...
23 - more SMTP/LMTP error detail on message rejections even outside verbose mode.
24 Ian D. Allen, fetchmail-users. Two messages with examples.
25 What goes here? fetchmailrc location, server, port, user, folder, anything else?
26 - see if "AUTH SSH" can be made to work for POP3
27 - revisit BerliOS patches
28 - check recent list mail
29 - check Debian BTS and other bug trackers
30 - better logging (log all headers, log forward destination + method)
31 - check strict envelope N Received parsing,
32 see mail from Admin Att on fetchmail-users
33 - 6.3.4-pending-deletes.patch
34 - fetchmail -s with running daemon complains rather than silently
36 - send warning message when connection fails?
37 - when logging to syslog, disable locale?
38 - check FAQ O5 - do we really prefer From: over envelope?!?
39 - add code to allow safe authentication schemes if TLS fails
40 - make APOP an authenticator, integrate with regular auto authentication
41 but stuff it at the end
45 - Add info whether Keywords are global, server or user keywords
46 - consolidate multidrop documentation