<hr/>
<h1 id="FAQ">Frequently Asked Questions About Fetchmail</h1>
-<p><strong>Support? Bug reports?</strong> Please read <a
-href="#G3">G3</a> for what information is required to get your problem
+<p><strong>Support? Bug reports?</strong> Please read <a
+href="#G3">G3</a> for what information is required to get your problem
solved as quickly as possible.</p>
<p>Note that this FAQ is occasionally updated from the SVN repository
<li>Any command-line options you used.</li>
-<li>The output of <kbd>env LC_ALL=C fetchmail -V</kbd> called with
+<li>The output of <kbd>env LC_ALL=C fetchmail -V</kbd> called with
whatever other command-line options you used.</li>
-<li><strong>The output of <kbd>env LC_ALL=C fetchmail --nodetach -vvv
---nosyslog</kbd> with whatever other command-line options you use
+<li><strong>The output of <kbd>env LC_ALL=C fetchmail --nodetach -vvv
+--nosyslog</kbd> with whatever other command-line options you use
routinely.</strong>
<p>It is very important that the transcript include your
POP/IMAP server's greeting line, so I can identify it in case of server
<p>It may helpful if you include your .fetchmailrc file, but not
necessary unless your symptom seems to involve an error in
configuration parsing. If you do send in your .fetchmailrc, mask
-the passwords first! Otherwise, fetchmail -V – as directed above
+the passwords first! Otherwise, fetchmail -V – as directed above
– will usually suffice.</p>
<p>If fetchmail seems to run and fetch mail, but the headers look