Pileus Git - ~andy/fetchmail/blob

1 <?xml version="1.0" encoding="ISO-8859-1"?>

2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

3 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

4 <html xmlns="http://www.w3.org/1999/xhtml">

5 <head>

6 <link rev="made" href="mailto:esr@snark.thyrsus.com" />

7 <meta name="description"

8 content="Known bugs and to-do items in fetchmail" />

9 <meta name="keywords" content="fetchmail, POP3, IMAP, bugs" />

10 <title>Fetchmail Bugs and To-Do Items</title>

11 <style type="text/css">

12 /*<![CDATA[*/

13 h1.c1 {text-align: center}

14 /*]]>*/

15 </style>

16 </head>

17 <body>

18 <h1 class="c1">Fetchmail Bugs and To-Do Items</h1>

19

20 <p>I try to respond to urgent bug reports in a timely way. But

21 fetchmail is now pretty mature and I have many other projects, so I

22 don't personally chase obscure or marginal problems. Help with any

23 of these will be cheerfully accepted.</p>

24

25 <h2>Serious</h2>

26

27 <p>Let IMAP code use UID and UIDVALIDITY rather than relying on flags

28 that everyone can alter.</p>

29

30 <h2>Normal</h2>

31

32 <p>POP3 hang when polling mail with NUL char that is rejected (David

33 Greaves) <a

34 href="https://lists.berlios.de/pipermail/fetchmail-devel/2004-October/000154.html">https://lists.berlios.de/pipermail/fetchmail-devel/2004-October/000154.html</a></p>

35

36 <p>It has been reported that multidrop name matching fails when the

37 name to be matched contains a Latin-1 umlaut. Dollars to doughnuts

38 this is some kind of character sign-extension problem. Trouble is,

39 it's very likely in the BIND libraries. Someone should go in with a

40 debugger and check this.</p>

41

42 <p>The <a

43 href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=fetchmail&archive=no">

44 Debian bug-tracking page for fetchmail</a> lists other bug

45 reports.</p>

46

47 <h2>Cosmetic</h2>

48

49 <p>Alan Munday suggests message change MULTIDROP without ENVELOPE:</p>

50 <pre>

51 fetchmail: warning: MULTIDROP configuration for pop.example.org requires the envelope option to be set!

52 fetchmail: warning: Check ENVELOPE option if fetchmail sends all mail to postmaster!

53 </pre>

54

55 <h2>Feature requests/Wishlist items</h2>

56

57 <p>Feature request from "Ralf G. R. Bergs" <rabe@RWTH-Aachen.DE> "When

58 fetchmail downloads mail and Exim+SpamAssassin detecs an incoming

59 message as spam, fetchmail tries to bounce it. Unfortunately it uses

60 an incorrect hostname as part of the sender address (I've an internal

61 LAN with private hostnames, plus an official IP address and hostname,

62 and fetchmail picks the internal name of my host.) So I'd like to have

63 a config statement that allows me to explicitly set a senderaddress

64 for bounce messages."</p>

65

66 <p>In the SSL support, add authentication of Certifying Authority

67 (Is this a Certifying Authority we recognize?).</p>

68

69 <p>Laszlo Vecsey writes: "I believe qmail uses a technique of

70 writing temporary files to nfs, and then moving them into place to

71 ensure that they're written. Actually a hardlink is made to the

72 temporary file and the destination name in a new directory, then

73 the first one is unlinked. Maybe a combination of this will help

74 with the fetchmail lock file."</p>

75

76 <p>Maybe refuse multidrop configuration unless "envelope" is _explicitly_

77 configured (and tell the user he needs to configure the envelope

78 option) and change the envelope default to nil. This would

79 prevent a significant class of shoot-self-in-foot problems.</p>

80

81 <p>Given the above change, perhaps treat a delivery as "temporarily

82 failed" (leaving the message on the server, not putting it into

83 .fetchids) when the header listed in the "envelope" option is not

84 found. (This is so you don't lose mail if you configure the wrong

85 envelope header.)</p>

86

87 <p>Matthias Andree writes:</p>

88

89 <blockquote>

90 <p>NOTE that the current code need optimization, if I have

91 unseen articles 3 and 47, fetchmail will happily request LIST for

92 articles 3...47 rather than just 3 and 47. In cases where the message

93 numbers are far apart, this involves considerable overhead - which

94 could be alleviated by pipelining the list commands, which needs

95 either asynchronous reading while sending the commands, or knowing the

96 send buffer, to avoid deadlocks. Unfortunately, I don't have the time

97 to delve deeper into the code and look around.</p>

98

99 <p>Note that such a pipelining function would be of universal use, so it

100 should not be in pop3.c or something. I'd think the best approach is to

101 call a "sender" function with the command and a callback, and the sender

102 will call the receiver when the send buffer is full and call the

103 callback function for each reply received.</p>

104

105 <p>See the ESMTP PIPELINING RFC for details on the deadlock avoidance

106 requirements.</p>

107 </blockquote>

108

109 <hr />

110 <br clear="left" />

111 <address>-2003 Eric S. Raymond <a

112 href="mailto:esr@thyrsus.com"><esr@thyrsus.com></a><br />

113 2004- Matthias Andree <a

114 href="mailto:matthias.andree@gmx.de"><matthias.andree@gmx.de></a></address>

115 </body>

116 </html>

117