-If
-.I fetchmail
-is used with a POP or an IMAP server, it has two fundamental modes of
-operation for each user account from which it retrieves mail:
-\fIsingledrop\fR- and \fImultidrop\fR-mode. In singledrop-mode,
-.I fetchmail
-assumes that all messages in the user's account are intended for a single
-recipient. An individual mail message will not be inspected for recipient
-information, rather, the identity of the recipient will either default to
-the local user currently executing \fIfetchmail\fR,
-or else will need to be explicitly specified in the configuration file.
-Singledrop-mode is used when the fetchmailrc configuration contains at
-most a single local user specification for a given server account.
-.PP
-With multidrop-mode,
-.I fetchmail
-is not able to assume that there is only a single recipient, but rather
-that the mail server account actually contains mail intended for any
-number of different recipients. Therefore,
-.I fetchmail
-must attempt to deduce the proper "envelope recipient" from the mail
-headers of each message. In this mode of operation,
-.I fetchmail
-almost resembles an MTA, however it is important to note that neither
-the POP nor IMAP protocols were intended for use in this fashion, and
-hence envelope information is often not directly available. Instead,
-.I fetchmail
-must resort to a process of informed guess-work in an attempt to
-discover the true envelope recipient of a message, unless the ISP stores
-the envelope information in some header (not all do). Even if this
-information is present in the headers, the process can
-be error-prone and is dependent upon the specific mail server used
-for mail retrieval. Multidrop-mode is used when more than one local
-user is specified for a particular server account in the configuration
-file. Note that the forgoing discussion of singledrop- and
-multidrop-modes does not apply to the ESMTP ETRN or ODMR retrieval
-methods, since they are based upon the SMTP protocol which
-specifically provides the envelope recipient to \fIfetchmail\fR.
-.PP
-As each message is retrieved, \fIfetchmail\fR normally delivers it via SMTP to
-port 25 on the machine it is running on (localhost), just as though it
-were being passed in over a normal TCP/IP link. \fIfetchmail\fR provides
-the SMTP server with an envelope recipient derived in the manner described
-previously. The mail will then be
-delivered locally via your system's MDA (Mail Delivery Agent, usually
-\fIsendmail\fR(8) but your system may use a different one such
-as \fIsmail\fR, \fImmdf\fR, \fIexim\fR, \fIpostfix\fR, or \fIqmail\fR). All the
-delivery-control mechanisms (such as \fI.forward\fR files) normally
-available through your system MDA and local delivery agents will
-therefore work automatically.
-.PP
-If no port 25 listener is available, but your fetchmail configuration
-was told about a reliable local MDA, it will use that MDA for local
-delivery instead.
-.PP
-If the program
-.I fetchmailconf
-is available, it will assist you in setting up and editing a
-fetchmailrc configuration. It runs under the X window system and
-requires that the language Python and the Tk toolkit be present on your
-system. If you are first setting up fetchmail for single-user mode, it
-is recommended that you use Novice mode. Expert mode provides complete
-control of fetchmail configuration, including the multidrop features.
-In either case, the 'Autoprobe' button will tell you the most capable
-protocol a given mailserver supports, and warn you of potential problems
-with that server.
+For troubleshooting, tracing and debugging, you need to increase
+fetchmail's verbosity to actually see what happens. To do that, please
+run \fBboth of the two following commands,
+adding all of the options you'd normally use.\fP
+
+.IP
+.nf
+env LC_ALL=C fetchmail \-V \-v \-\-nodetach \-\-nosyslog
+.fi
+.IP
+(This command line prints in English how fetchmail understands your
+configuration.)
+
+.IP
+.nf
+env LC_ALL=C fetchmail \-vvv \-\-nodetach \-\-nosyslog
+.fi
+.IP
+(This command line actually runs fetchmail with verbose English output.)
+.PP
+Also see
+.URL "http://fetchmail.berlios.de/fetchmail-FAQ.html#G3" "item #G3 in fetchmail's FAQ"
+.PP
+You can omit the LC_ALL=C part above if you want output in the local
+language (if supported). However if you are posting to mailing lists,
+please leave it in. The maintainers do not necessarily understand your
+language, please use English.
+
+
+
+.SS CONCEPTS
+If \fBfetchmail\fP is used with a POP or an IMAP server (but not with
+ETRN or ODMR), it has two fundamental modes of operation for each user
+account from which it retrieves mail: \fIsingledrop\fP- and
+\fImultidrop\fP-mode.
+.IP "In singledrop-mode,"
+\fBfetchmail\fP assumes that all messages in the user's account
+(mailbox) are intended for a single recipient. The identity of the
+recipient will either default to the local user currently executing
+\fBfetchmail\fP, or will need to be explicitly specified in the
+configuration file.
+.IP
+\fBfetchmail\fP uses singledrop-mode when the fetchmailrc configuration
+contains at most a single local user specification for a given server
+account.
+.IP "In multidrop-mode,"
+\fBfetchmail\fP assumes that the mail server account actually contains
+mail intended for any number of different recipients. Therefore,
+\fBfetchmail\fP must attempt to deduce the proper "envelope recipient"
+from the mail headers of each message. In this mode of operation,
+\fBfetchmail\fP almost resembles a mail transfer agent (MTA).
+.IP
+Note that neither the POP nor IMAP protocols were intended for use in
+this fashion, and hence envelope information is often not directly
+available. The ISP must stores the envelope information in some message
+header \fBand\fP. The ISP must also store one copy of the message per
+recipient. If either of the conditions is not fulfilled, this process is
+unreliable, because \fBfetchmail\fP must then resort to guessing the
+true envelope recipient(s) of a message. This usually fails for mailing
+list messages and Bcc:d mail, or mail for multiple recipients in your
+domain.
+.IP
+\fBfetchmail\fP uses multidrop-mode when more than one local user and/or
+a wildcard is specified for a particular server account in the
+configuration file.
+.IP "In ETRN and ODMR modes,"
+these considerations do not apply, as these protocols are based on SMTP,
+which provides explicit envelope recipient information. These protocols
+always support multiple recipients.
+.PP
+As each message is retrieved, \fBfetchmail\fP normally delivers it via
+SMTP to port 25 on the machine it is running on (localhost), just as
+though it were being passed in over a normal TCP/IP link.
+\fBfetchmail\fP provides the SMTP server with an envelope recipient
+derived in the manner described previously. The mail will then be
+delivered according to your MTA's rules (the Mail Transfer Agent is
+usually \fBsendmail\fP(8), \fBexim\fP(8), or \fBpostfix\fP(8)).
+Invoking your system's MDA (Mail Delivery Agent) is the duty of your
+MTA. All the delivery-control mechanisms (such as \fI.forward\fP files)
+normally available through your system MTA and local delivery agents
+will therefore be applied as usual.
+.PP
+If your fetchmail configuration sets a local MDA (see the \-\-mda
+option), it will be used directly instead of talking SMTP to port 25.
+.PP
+If the program \fBfetchmailconf\fP is available, it will assist you in
+setting up and editing a fetchmailrc configuration. It runs under the X
+window system and requires that the language Python and the Tk toolkit
+(with Python bindings) be present on your system. If you are first
+setting up fetchmail for single-user mode, it is recommended that you
+use Novice mode. Expert mode provides complete control of fetchmail
+configuration, including the multidrop features. In either case,
+the 'Autoprobe' button will tell you the most capable protocol a given
+mailserver supports, and warn you of potential problems with that
+server.