aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2000-07-03 19:35:11 +0000
committerEric S. Raymond <esr@thyrsus.com>2000-07-03 19:35:11 +0000
commitb481a92175821bd7e2d014282cbf01c457b52d3a (patch)
tree954c48139cd199ada803b66e5e034b41108b2902
parentd8539b4e42699b69ca0ea2742239fa0ba34b245a (diff)
downloadfetchmail-b481a92175821bd7e2d014282cbf01c457b52d3a.tar.gz
fetchmail-b481a92175821bd7e2d014282cbf01c457b52d3a.tar.bz2
fetchmail-b481a92175821bd7e2d014282cbf01c457b52d3a.zip
Typo fixes.
svn path=/trunk/; revision=2926
-rw-r--r--fetchmail.man4
1 files changed, 2 insertions, 2 deletions
diff --git a/fetchmail.man b/fetchmail.man
index e1daa2b9..bc988e8e 100644
--- a/fetchmail.man
+++ b/fetchmail.man
@@ -902,7 +902,7 @@ The protocols \fIfetchmail\fR uses to talk to mailservers are next to
bulletproof. In normal operation forwarding to port 25, no message is
ever deleted (or even marked for deletion) on the host until the SMTP
listener on the client has acknowledged to \fIfetchmail\fR that the
-message has been accepted for delivery or rejected due to a apam
+message has been accepted for delivery or rejected due to a spam
block. When forwarding to an MDA, however, there is more possibility
of error (because there's no way for fetchmail to get a reliable
positive acknowledgement from the MDA).
@@ -1305,7 +1305,7 @@ fetchlimit -B T{
Max # messages to fetch in single connect
T}
expunge -e T{
-Perform an expunge on every #th message (IMAP only)
+Perform an expunge on every #th message (IMAP and POP3 only)
T}
properties \& T{
String value is ignored by fetchmail (may be used by extension scripts)