aboutsummaryrefslogtreecommitdiffstats
path: root/README.packaging
blob: 08d115d03d3bf3a476df4663ef9af34fcd4983ff (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
README.packaging
================

fetchmail 6.3 changes relevant for packagers
--------------------------------------------

Greetings, dear packager!

The bullet points below mention a few useful hints for package(r)s:

- Please use OpenSSL and add --with-ssl to the ./configure command line.  
  SSL/TLS support hasn't been enabled in the default build in order to maintain 
  fetchmail 6.2 compatibility as far as possible.  SSL/TLS however is a highly 
  recommended compilation option.

- Fetchmail now uses automake and supports all common automake targets and 
  overrides such as "make install-strip" or "DESTDIR=..." for staging areas.

- The fetchmailconf script has been renamed to fetchmailconf.py, automake will 
  install it into Python's top-level site-packages directory and byte-compile 
  it (so you need to package or remove fetchmailconf.pyc and fetchmailconf.pyo 
  as well).

- If you want to defeat Python byte-code compilation and would rather like to 
  install fetchmailconf.py yourself, you can add

      PYTHON=:

  to the ./configure command or pass this in the environment.  This pretends 
  that no Python interpreter were installed.

- The Makefile generates a two-line "fetchmailconf" /bin/sh wrapper script that 
  executes the actual fetchmailconf.py with the python installation found at 
  configuration time, so that users can still type "fetchmailconf" rather than 
  "python fetchmailconf".

- Note that fetchmailconf.py supports a few command line arguments, so if you 
  use local wrapper scripts, be sure they pass on their own arguments properly. 
  Remember to use "$@" (with quotes) in shells, not $*.

- There is now a dummy fetchmailconf manual page which will just source (roff's 
  ".so" command) the fetchmail manual page for now. You can of course keep your 
  symlinks in place and ignore this dummy. IF you install the dummy and 
  compress your man pages, be sure to test "man fetchmailconf", on some 
  systems, you'll need to adjust the ".so" command to point to the compressed 
  version.
nal//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <link rev="made" href="mailto:esr@snark.thyrsus.com" /> <meta name="description" content="Known bugs and to-do items in fetchmail" /> <meta name="keywords" content="fetchmail, POP3, IMAP, bugs" /> <title>Fetchmail Bugs and To-Do Items</title> <style type="text/css"> /*<![CDATA[*/ h1.c1 {text-align: center} /*]]>*/ </style> </head> <body> <h1 class="c1">Fetchmail Bugs and To-Do Items</h1> <p>Note that there is a separate <a href="TODO.txt">TODO.txt</a> document of different content than this.</p> <p>I try to respond to urgent bug reports in a timely way. But fetchmail is now pretty mature and I have many other projects, so I don't personally chase obscure or marginal problems. Help with any of these will be cheerfully accepted.</p> <h2>Serious</h2> <p>Let IMAP code use UID and UIDVALIDITY rather than relying on flags that everyone can alter.</p> <h2>Normal</h2> <p>POP3 hang when polling mail with NUL char that is rejected (David Greaves) <a 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> <p>It has been reported that multidrop name matching fails when the name to be matched contains a Latin-1 umlaut. Dollars to doughnuts this is some kind of character sign-extension problem. Trouble is, it's very likely in the BIND libraries. Someone should go in with a debugger and check this.</p> <p>The <a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=fetchmail&amp;archive=no"> Debian bug-tracking page for fetchmail</a> lists other bug reports.</p> <h2>Cosmetic</h2> <p>Alan Munday suggests message change MULTIDROP without ENVELOPE:</p> <pre> fetchmail: warning: MULTIDROP configuration for pop.example.org requires the envelope option to be set! fetchmail: warning: Check ENVELOPE option if fetchmail sends all mail to postmaster! </pre> <h2>Feature requests/Wishlist items</h2> <p>Feature request from "Ralf G. R. Bergs" &lt;rabe@RWTH-Aachen.DE&gt; "When fetchmail downloads mail and Exim+SpamAssassin detecs an incoming message as spam, fetchmail tries to bounce it. Unfortunately it uses an incorrect hostname as part of the sender address (I've an internal LAN with private hostnames, plus an official IP address and hostname, and fetchmail picks the internal name of my host.) So I'd like to have a config statement that allows me to explicitly set a senderaddress for bounce messages."</p> <p>In the SSL support, add authentication of Certifying Authority (Is this a Certifying Authority we recognize?).</p> <p>Laszlo Vecsey writes: "I believe qmail uses a technique of writing temporary files to nfs, and then moving them into place to ensure that they're written. Actually a hardlink is made to the temporary file and the destination name in a new directory, then the first one is unlinked. Maybe a combination of this will help with the fetchmail lock file."</p> <p>Maybe refuse multidrop configuration unless "envelope" is _explicitly_ configured (and tell the user he needs to configure the envelope option) and change the envelope default to nil. This would prevent a significant class of shoot-self-in-foot problems.</p> <p>Given the above change, perhaps treat a delivery as "temporarily failed" (leaving the message on the server, not putting it into .fetchids) when the header listed in the "envelope" option is not found. (This is so you don't lose mail if you configure the wrong envelope header.)</p> <p>Matthias Andree writes:</p> <blockquote> <p>NOTE that the current code need optimization, if I have unseen articles 3 and 47, fetchmail will happily request LIST for articles 3...47 rather than just 3 and 47. In cases where the message numbers are far apart, this involves considerable overhead - which could be alleviated by pipelining the list commands, which needs either asynchronous reading while sending the commands, or knowing the send buffer, to avoid deadlocks. Unfortunately, I don't have the time to delve deeper into the code and look around.</p> <p>Note that such a pipelining function would be of universal use, so it should not be in pop3.c or something. I'd think the best approach is to call a "sender" function with the command and a callback, and the sender will call the receiver when the send buffer is full and call the callback function for each reply received.</p> <p>See the ESMTP PIPELINING RFC for details on the deadlock avoidance requirements.</p> </blockquote> <hr /> <br clear="left" /> <address>-2003 Eric S. Raymond <a href="mailto:esr@thyrsus.com">&lt;esr@thyrsus.com&gt;</a><br /> 2004- Matthias Andree <a href="mailto:matthias.andree@gmx.de">&lt;matthias.andree@gmx.de&gt;</a></address> </body> </html>