On Tue, Jul 26, 2005 at 02:12:19AM +0200, Matthias Andree wrote:
> Please try adding a line like this to your .fetchmailrc and let me know
> if it helps (yes it will report errors for obvious reasons - note that
> "skip" doesn't work):
> 
> poll dummy.invalid with proto ETRN no dns

Yes, it does help (once I'd instructed Exim to listen on all interfaces, 
anyway).

Before, the last two received headers were:

Received: from localhost ([127.0.0.1])
        by rilynn.demon.co.uk with esmtp (Exim 4.50)
        id 1EFINH-0005b9-AF
        for [EMAIL PROTECTED]; Tue, 13 Sep 2005 22:31:31 +0100
Received: from pop3.demon.co.uk
        by localhost with POP3 (fetchmail-6.2.5.2)
        for [EMAIL PROTECTED] (multi-drop); Tue, 13 Sep 2005 22:31:31+0100 (BST)

Now, I get:

Received: from rilynn.demon.co.uk ([80.177.15.151])
        by rilynn.demon.co.uk with esmtp (Exim 4.50)
        id 1EFIU2-0005iG-4f
        for [EMAIL PROTECTED]; Tue, 13 Sep 2005 22:38:30 +0100
Received: from pop3.demon.co.uk
        by rilynn.demon.co.uk with POP3 (fetchmail-6.2.5.2)
        for [EMAIL PROTECTED] (multi-drop); Tue, 13 Sep 2005 22:38:30+0100 (BST)

It also makes bounce messages clearer:

Reporting-MTA: dns; rilynn.demon.co.uk

Thanks,

Roger

PS. I've only just noticed that Fetchmail doesn't give the numeric IP 
address for the upstream server (eg 
"Received: from pop3.demon.co.uk ([194.217.242.253])"). I'm not bothered 
about it, but it is something other MTAs include.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to