aboutsummaryrefslogtreecommitdiffstats
path: root/fetchmail.man
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>1996-10-25 06:22:14 +0000
committerEric S. Raymond <esr@thyrsus.com>1996-10-25 06:22:14 +0000
commit3c2b96ae3364a3bc206679f49a858f8fee505ba4 (patch)
tree7bbd532dc625beaa7ec0baaf6cfd0f7f5f890d20 /fetchmail.man
parent60966f2e9a50c1f0c1b40f1739e7475cb4a67825 (diff)
downloadfetchmail-3c2b96ae3364a3bc206679f49a858f8fee505ba4.tar.gz
fetchmail-3c2b96ae3364a3bc206679f49a858f8fee505ba4.tar.bz2
fetchmail-3c2b96ae3364a3bc206679f49a858f8fee505ba4.zip
Another pass at making multidrop work OK.
svn path=/trunk/; revision=376
Diffstat (limited to 'fetchmail.man')
-rw-r--r--fetchmail.man10
1 files changed, 7 insertions, 3 deletions
diff --git a/fetchmail.man b/fetchmail.man
index 5cab1cf5..0cfb5af0 100644
--- a/fetchmail.man
+++ b/fetchmail.man
@@ -683,14 +683,18 @@ to the mailserver. This creates a risk that name/password pairs
might be snaffled with a packet sniffer or more sophisticated
monitoring software.
.PP
-Retrieval and forwarding from multi-drop server mailboxes is only as
-reliable as your mail server host's DNS service. Each host
+Retrieval and forwarding from multi-drop server mailboxes is at most
+as reliable as your mail server host's DNS service. Each host
address part in each message of a multi-drop mailbox is checked
with
.BR gethostbyname (2)
to see if it's an alias of the mail server. If it is, but the
lookup fails due to network congestion or a crashed server, forwarding
-will not get done correctly.
+will not get done correctly. Note: this check will \fInot\fR catch
+equivalences created by MX records!
+.PP
+The multi-drop mailbox code was hard to test thoroughly and may have obscure
+failure modes, especially in the presence of DNS flakiness.
.PP
Under Linux, if fetchmail is run in daemon mode with the network
inaccessible, each poll leaves a socket allocated but in CLOSE state