1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
|
soon:
- BerliOS Bug #11576, thread on fetchmail users "Invalid SSL certificate" by
Philip Susi, SSL negotiation does not use ERR_error_string(3ssl) to report
errors in a readable way, we just report socket errors with no good reason.
- find a solution for the "invalid header" discards message problem
(escape headers and stuff reminder into body)
- https://bugzilla.novell.com/show_bug.cgi?id=246829 - fetchmail lost some mail
(5XX error code in contradiction with manual?)
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432618
* write a table of combinations of TLS/SSL options
- add To: header to warning mails (authfail for instance)
- add Message-ID: header and other SHOULD headers to warning mails?
- BerliOS Bug #11797, imap_mark_seen doesn't consider expunged messages
- BerliOS Bug #10972, Fetchmail refetches big messages repeatedly (SMTP listener
issue)
- report multiline SMTP errors properly (sample in private mail from
Earl Chew, 2007-07-30T02:28)
- publish SA-2007-02 after release
- Debian Bug#449179, smbutil.c:90: unicodeToString: Assertion `len+1 < sizeof
buf' failed, from Stepan Golosunov <stepan@golosunov.pp.ru>
- Peter O'Gorman 2007-10-31 fetchmail-6.3.8 portability patches [-devel list]
questionable:
- Convert POP3 UIDs to X-UIDL?
- fetch IMAP message in one go (fetchmail-devel by Adam Simpkins
<simpkins@cisco.com> around Nov 2nd)?
- Debian Bug #452907 .fetchmailrc not permitted to be a symlink
(restriction not mentioned in manpage, also affects .idfile)
6.4:
- download only messages whose headers match a filter (by Toby, Usenet
Nov 2007 de.comm.software.mailserver
Message-ID: <1195033726.123704.296060@k79g2000hse.googlegroups.com>)
- feature request by Daniel Goering <g_daniel@gmx.net> on
fetchmail-devel 2007-11-15: populate .fetchids from current messages.
(it'll probably be useful to limit this to "all but the 10 latest" or
"all before date this-and-that")
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374514
"Deleting fetchids file" vs. POP3 - probably unneeded if we use IMAP UIDs.
- change SSL/TLS UI incompatibly, making it easier to use
- allow selection of SSL/TLS Ciphers
- perhaps switch to libgsasl and libgnutls (which doesn't talk SSLv2)
- make the SSL default v3 (rather than v23).
- put more hints to the FAQ (should we call it FGA?) as first support place
- make sure we print socket error messages such as connection reset by
peer to hint users the problem is not in fetchmail
- > b) When the envelope header is specified, but it isn't found, a
> warning is logged and the mail is forwarded to the postmaster
> ("WARNING: Envelope header $HEADER found, cannot identify the
> recipient. Forwarding to the postmaster")
Rob MacGregor 2007-03-16 Patch to the man page, fetchmail-devel@
- integrate Isaac Wilcox's test rig
- look at Tony Earnshaw's .spec file
- look at Gentoo patches
- remove dead replacement functions: strdup (Andreas Krennmair), ...
- more SMTP/LMTP error detail on message rejections even outside verbose mode.
Ian D. Allen, fetchmail-users. Two messages with examples.
What goes here? fetchmailrc location, server, port, user, folder, anything else?
- see if "AUTH SSH" can be made to work for POP3
- revisit BerliOS patches
- check recent list mail
- check Debian BTS and other bug trackers
- better logging (log all headers, log forward destination + method)
- check strict envelope N Received parsing,
see mail from Admin Att on fetchmail-users
- 6.3.4-pending-deletes.patch
- fetchmail -s with running daemon complains rather than silently
restarting daemon
- send warning message when connection fails?
- when logging to syslog, disable locale?
- check FAQ O5 - do we really prefer From: over envelope?!?
- add code to allow safe authentication schemes if TLS fails
- make APOP an authenticator, integrate with regular auto authentication
but stuff it at the end
- use SASL?
DOCUMENTATION:
- Add info whether Keywords are global, server or user keywords
- consolidate multidrop documentation
|
