Matthias Andree wrote:
martin frost <martin(_at_)herma(_dot_)co(_dot_)uk> writes:
I have a small network of 25 users & our e-mail recived by an
independant virus scaned POP3 Mail box.
I have Qmail setup as the smtp mail server & fetchmail is used to
forward all mail to it.
My fetchmailrc is as below.
poll pop3.ISP.co.uk
proto pop3
localdomains Domain.co.uk
user "User"
pass "pass"
is *
What is the "envelope" header? You should not use multidrop without
envelope option.
on a regular basis I recive e-mail as root of our mail server as follows
fetchmail: nameserver failure while looking for `smtp.mediapix.fr;'
during poll of pop3.ISP.co.uk.
Not a fetchmail problem.
Check your name server logs, /etc/nsswitch.conf if you have it and
/etc/resolv.conf. Check the corresponding manual pages for details.
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
I have looked through the Fetchmail documentation & the only referance I
can find on the envelope option is as below
-E <line> | --envelope <line>
(Keyword: envelope) This option changes the header fetchmail assumes
will carry a copy of the mail's envelope address. Normally this is
'X-Envelope-To' but as this header is not standard, practice varies. See
the discussion of multidrop address handling below. As a special case,
'envelope "Received"' enables parsing of sendmail-style Received lines.
This is the default, and it should not be necessary unless you have
globally disabled Received parsing with 'no envelope' in the
.fetchmailrc file.
Dose this meen that I have to enter the enveloe "Received" line into the
.fetchmailrc file & what dose it refer to.
Deliver-To postmaster(_at_)NewFileserver
Re