blob: 8c58a969c98a9d4d3e68d320311ae7370f394970 (
plain)
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
|
For 6.3.X:
==========
Casper Gripenberg's 6.3.2 no-IDLE/NOOP hang with EXISTS (see full trace
and patch on fetchmail-devel).
Roger Lynn's Debian Bug#353575 and Bug#316446 comment.
Quick SDPS-specific workaround is implemented (rev 4693:4694)
but needs testing.
Use Errors-To: as envelope sender fallback?
20060213T122015 [ 53: Frederic Marchal] [fetchmail-users] Incorrect header line and lost mails
See if fetchmail still segfaults (see quotes of Frederic Marchal
2006-02-17):
> In fetchmail, the problem is clearly located in transact.c (I wouldn't
> call it a bug until I get some clarification from the one who wrote
> it). The part of the code that rejects the mail is preceded by a comment
> stating
>
> * At least one brain-dead website (netmind.com) is known to
> * send out robotmail that's missing the RFC822 delimiter blank
> * line before the body! Without this check fetchmail segfaults.
> * With it, we treat such messages as spam and refuse them.
>
> But the test after this comment doesn't test for the beginning of the
> body but for a header line not starting with a blank and not containing
> a colon.
Validate --mda/mda option so that single quotes (') around the
placeholders are rejected Debian Bug #347909
Add FAQ entry about procmail configuration with 1. ORGMAIL/DEFAULT, 2.
:0e { EXITCODE=75 HOST }, 3. explicit default recipe, 4. LOGFILE
location?
Yves Boisjoly reports that NTLM auth needs to use the real Wks field
rather than duplicating the user name (see l. 211 in smbutil.c).
Make fetchmailconf a noarch RPM (needs %ifarch hacks and running
rpmbuild twice).
For later:
==========
Add a warning when mda contains sendmail but not -i, -oi, -O IgnoreDots
IDN
Pipeline commands
Allow to query multiple servers simultaneously.
Privilege separation model for added security.
Check if fetchmail's notion of \Recent vs. * <n> RECENT is a working
model at all. In concurrent sessions, fetchmail might not be notified of
\Recent and will have to check UID instead.
RFC2047 encode X-Fetchmail-Warning?
X-Fetchmail-Warning: Empfängeradresse root@example.org stimmt mit keinem lokalen Namen überein
X-Virus-Scanned: amavisd-new at m2a2.dyndns.org
X-Amavis-Alert: BAD HEADER Non-encoded 8-bit data (char C3 hex) in message header 'X-Fetchmail-Warning': X-Fetchmail-Warning: +Empf\303\244ngeradresse ro...
check if --monitor still works properly
and complete CAN_MONITOR vs. interface checks
complete CAN_MONITOR replacement
put all getaddrinfo compat cruft into an easy-to-use m4 macro for
autoconf and Makefile.am snippet for automake, so people can just use it
without further hassle.
fetchmail -vvvv --syslog prints blank lines on the screen.
Probably uid.c lines 254 and 265.
|
