From d07ce47c2a87046469474d8c7f30a3626f90f0ca Mon Sep 17 00:00:00 2001 From: Matthias Andree Date: Thu, 17 Aug 2006 21:16:24 +0000 Subject: Reviewed FAQ sections T, S, I, K and R1 - R6. svn path=/branches/BRANCH_6-3/; revision=4900 --- fetchmail-FAQ.html | 116 +++++++++++++++-------------------------------------- 1 file changed, 32 insertions(+), 84 deletions(-) (limited to 'fetchmail-FAQ.html') diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index df7d3f8c..fb9bdc09 100644 --- a/fetchmail-FAQ.html +++ b/fetchmail-FAQ.html @@ -131,7 +131,7 @@ host?.

How to make fetchmail work with various servers

-S1. How can I use fetchmail with qpopper?
+S1. How can I use fetchmail with qpopper?
S2. How can I use fetchmail with Microsoft Exchange?
S3. How can I use fetchmail with HP OpenMail?
S4. How can I use fetchmail with Novell GroupWise?
@@ -170,8 +170,8 @@ connect failed' messages.
work.
R3. Fetchmail dumps core when given an invalid rc file.
-R4. Fetchmail dumps core in -V mode, but operates -normally otherwise.
+R4. Fetchmail dumps core in -V mode, but operates + normally otherwise.
R5. Running fetchmail in daemon mode doesn't work.
R6. Fetchmail randomly dies with socket errors.
@@ -1553,38 +1553,10 @@ IMAP?

How to make fetchmail work with various servers

-

S1. How can I use fetchmail with -qpopper?

- -

Qualcomm's qpopper is probably the best-of-breed among POP3 -servers, and is very widely deployed. Nevertheless, it has some -problems which fetchmail exposes. We recommend using IMAP instead if at all possible. If you must talk to -qpopper, here are some problems to be aware of:

- -

Problems with retrieving large messages from qpopper 2.53

- -

Tony Tang <tony@atn.com.hk> reports -that there is a bad intercation between fetchmail and qpopper 2.5.3 -under Red Hat Linux versions 5.0 to 5.2, kernels 2.0.34 to 2.0.35. -When fetching very large messages (over 700K) from 2.5.3, fetchmail -will hang with a socket error.

- -

This is probably not a fetchmail bug, but rather a symptom of -some problem in the networking stack that qpopper's transmission -pattern is tickling, as fetchpop (another Linux POP client) also -displays the hang but Netscape running under Win95 does not. The -problem can also be banished by upgrading to -qpopper 3.0b1.

- -

Bad interaction with fetchmail 4.4.2 to 4.4.7

+

S1. How can I use fetchmail with + qpopper?

-

Versions of fetchmail from 4.4.2 through 4.4.7 had a bad -interaction with Eudora qpopper versions 2.3 and later. See X5 for details. The solution is to upgrade your -fetchmail.

+

The information that used to be here was obsolete and dropped.

S2. How can I use fetchmail with Microsoft Exchange?

@@ -1715,10 +1687,8 @@ usernames and mailbox names are the same. explicitly to your mailbox name. -

But, the best option involves a tactical nuclear weapon (an old -ASROC will do), pissing off a lot people who live downwind from -Redmond, and your choice of any Linux, NetBSD, FreeBSD, or Solaris -CD-ROM.

+

But, the best option involves finding a server that runs better +software.

S3. How can I use fetchmail with HP OpenMail?

@@ -1736,7 +1706,7 @@ OpenMail's project manager claims these bugs have been fixed in 6.0.

We've had a more recent report (December 2001) that the TOP -command fails, returning only one line regrardless of its argument, +command fails, returning only one line regardless of its argument, on something identifying itself as "OpenMail POP3 interface".

S4. How can I use fetchmail with Novell GroupWise?

@@ -1747,15 +1717,14 @@ broken. Among other things, it doesn't include a required content length in its BODY[TEXT] response.

Fetchmail works around this problem, but we strongly recommend -voting with your dollars for a server that isn't brain-dead. If you -stick with code as shoddy as GroupWise seems to be, you will -probably pay for it with other problems.

+voting with your dollars for a server that isn't brain-dead.

S5. How can I use fetchmail with InterChange?

You can't. At least not if you want to be able to see -attachments. InterChange has a bug similar to the MailMax server; +attachments. InterChange has a bug similar to the MailMax server (see below): it reports the message length with attachments but doesn't download them on TOP or RETR.

@@ -1914,10 +1883,6 @@ it to use RETR instead.

You may need to raise the MaxHopCount parameter in your sendmail.cf to avoid having fetched mail rejected.

-

(Note: Other failure modes have been reported on usa.net's -servers. They seem to be chronically flaky. We recommend finding -another provider.)

-

I4. How can I use fetchmail with geocities POP3 servers?

@@ -1939,9 +1904,6 @@ mda "sed -e '1s/^\t/Received: /' | formail | /usr/bin/procmail -d <user>" Geocities' servers sometimes think that the first 45 messages have already been read.

-

Fix: Get an email provider that doesn't suck. The pop-up ads on -Geocities are lame, you should boycott them anyway.

-

I5. How can I use fetchmail with Hotmail or Lycos Webmail?

You can't directly. But you can use fetchmail with hotmail or lycos @@ -2066,15 +2028,11 @@ shouldn't be a problem.

IMAP-GSS protocol?

Fetchmail can use RFC1731 GSSAPI authorization to safely -identify you to your IMAP server, as long as you can share Kerberos -V credentials with your mail host and you have a GSSAPI-capable -IMAP server. UW-IMAP (available via FTP at ftp.cac.washington.edu) -is the only one I'm aware of and the one I recommend anyway for -other reasons. You'll need version 4.1-FINAL or greater though, and -it has to have GSS support compiled in.

- -

Neither UW-IMAP nor fetchmail compile in support for GSS by +identify you to your IMAP server, as long as you can share +Kerberos V credentials with your mail host and you have a GSSAPI-capable +IMAP server - those are few.

+ +

fetchmail does not compile in support for GSS by default, since it requires libraries from the Kerberos V distribution (available via FTP at athena-dist.mit.edu). @@ -2105,21 +2063,18 @@ cleartext in your .fetchmailrc, or across the network.

SSL?

You'll need to have the OpenSSL libraries installed. +href="http://www.openssl.org/">OpenSSL libraries installed, and they +should at least be version 0.9.6. Configure with --with-ssl. If you have the OpenSSL libraries installed in the default location (/usr/local/ssl) ths will suffice. If you have them installed in a non-default location, you'll need to specify it as an argument to --with-ssl after an equal sign.

-

Note that there is a known bug in the implementation of SSL_peek -under OpenSSL versions 0.9.5 and older that fetchmail occasionally -tripped over, causing hangs. It is recommended that you install -0.9.6 or later.

-

Fetchmail binaries built this way support ssl, sslkey, and sslcert options that control -SSL encryption. You will need to have an SSL-enabled mailserver to +SSL encryption, and will automatically use tls if the +server offers it. You will need to have an SSL-enabled mailserver to use these options. See the manual page for details and some words of care on the limited security provided.

@@ -2136,7 +2091,8 @@ fetchmail is primarily designed to run forever as a background daemon, that option is not available in this case.

If you don't have the libraries installed, but do have the -OpenSSL utility toolkit, something like this may work:

+OpenSSL utility toolkit, something like this may work (but will not +authenticate the server):

 poll MYSERVER port 993 plugin "openssl s_client -connect %h:%p"
@@ -2324,6 +2280,10 @@ broken.

 
R3. Fetchmail dumps core when given an
 invalid rc file.

 
+
Note that this bug should no longer occur when using prepackaged
+fetchmail versions or installing unmodified original tarballs, since
+these ship with a proper parser .c file.

+
 
This is usually reported from AIX or Ultrix, but has even been
 known to happen on Linuxes without a recent version of
 flex installed. The problem appears to be a result of
@@ -2334,23 +2294,11 @@ building with an archaic version of lex.

 
Fix: build and install the latest version of flex.

 
-
R4. Fetchmail dumps core in -V mode, but
-operates normally otherwise.

-
-
We've had this reported to us under Linux using libc-5.4.17 and
-gcc-2.7.2. It does not occur with libc-5.3.12 or earlier
-versions.

-
-
Workaround: link with GNU malloc rather than the stock C library
-malloc.

+
R4. Fetchmail dumps core in -V mode, but
+	operates normally otherwise.

 
-
We're told there is some problem with the malloc() code in that
-version which makes it fragile in the presence of multiple free()
-calls on the same pointer (the malloc arena gets corrupted).
-Unfortunately it appears from doing gdb traces that whatever free()
-calls producing the problem are being made by the C library itself,
-not the fetchmail code (they're all from within fclose, and not an
-fclose called directly by fetchmail, either).

+
The information that used to be here referred to bugs in Linux libc5
+    systems, which are deemed obsolete by now.

 
 
R5. Running fetchmail in daemon mode
 doesn't work.

@@ -2360,7 +2308,7 @@ doesn't work.

 fetchmail in detached daemon mode doesn't work, but that using the
 same options with -N (nodetach) is OK. We have another report of
 similar behavior from one Linux user, but many other Linux users
-reportt no problem.

+report no problem.

 
 
If this happens, you have a specific portability problem with
 the code in daemon.c that detaches and backgrounds the daemon
-- 
cgit v1.2.3