[ Please don't CC me - I get the mail on the list ]
On 2/27/06, Craig at Adoofa <Craig(_at_)adoofa(_dot_)com> wrote:
Here are the headers:
Delivered-To: myadoofa_at_adoofa.com
Received: from pop3.zippymail.co.uk [81.201.128.18]
by localhost with IMAP (fetchmail-6.2.5)
for craig_at_adoofa.com (multi-drop); Fri, 24 Feb 2006 16:48:48 +0000 (GMT)
Headers above here added by your local setup, headers below added by
the ISP. Note that you're running an old, vulnerable, version of
fetchmail. See the URL I provided in the previous email.
Received: (qmail 8001 invoked by uid 89); 24 Feb 2006 16:25:38 -0000
Delivered-To: craig_at_adoofa.com
In other words, it looks you have something local that's adding the
second Delivered-To header. It isn't there before Fetchmail sees it.
The output of "fetchmail -v -v -v" for a problem email, along with the
contents of your mail log, would help identify the problem (and what's
adding the header). I'd also suggest some changes to your
.fetchmailrc
poll pop3.remotedomain.co.uk
localdomains uk.mydomain.com mydomain.com
# You don't appear to need the qvirtual line
qvirtual "pop3.remotedomain.co.uk"
envelope Delivered-To
username myname(_at_)mydoamin(_dot_)com
password secret
is * here
forcecr
# This doesn't appear to be working
dropdelivered
Can you provide the output of "fetchmail -V"?
--
Please keep list traffic on the list.
Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn't become a monster. Friedrich Nietzsche
������������������������������������z�!������zwl����x%��Ez�!������zwl�X����r)���!�����b���qȥ�����"����f��f��X��)ߣ��fj)�~��