[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Looping message delivery - qmail and fetchmail problem
- To: qmail@xxxxxxxxxxxxx
- Subject: Looping message delivery - qmail and fetchmail problem
- From: Tomasz Nidecki <tonid@xxxxxxxxx>
- Date: Mon, 05 Jan 2004 03:25:12 +0000 (UTC)
- Delivered-to: de5-qmail@sws5.ornl.gov
- Delivered-to: mailing list qmail@list.cr.yp.to
- Mailing-list: contact qmail-help@list.cr.yp.to; run by ezmlm
- Organization: Endemic Zone
- Reply-to: tonid@xxxxxxxxx
- Sender: news <news@xxxxxxxxxxxxx>
- User-agent: Xnews/06.07.17 Mime-proxy/1.2.c.0 (Win32) Hamster/2.0.0.1
Well, I've tried searching for a solution for a long time,
but I give up, I don't know what's going on...
I recently decided to set up fetchmail on my home server.
My girlfriend picks mail from a couple of free accounts and gets a lot
of spam on them, so I wanted to centralize the system by fetching all
the mail from those accounts [using fetchmail] to one account on my
server and running this through bogofilter.
But a strange thing started happening.
The same messages [not all, just some of them] fetched from her free accounts
are being delivered to her local account over and over and over.
Thousands a day. And I can't seem to be able to either pinpoint what
causes this or stop it.
OK here's, hopefully, all the data needed for this. I substituted the domain
part of email addressess with .invalid so that harvesters don't get them.
Here's an example of headers of one of those looping messages [just some spam]:
=== cut ===
Return-Path: <cialiss@xxxxxxxxx>
Delivered-To: kinga-wp@xxxxxxxxxxxxx
Received: (qmail 27322 invoked by uid 610); 5 Jan 2004 03:03:07 -0000
Received: from cialiss@xxxxxxxxx by phssthpok.tonid.net by uid 517 with qmail-scanner-1.20
(clamuko: 0.65. Clear:RC:1(127.0.0.1):.
Processed in 0.314849 secs); 05 Jan 2004 03:03:07 -0000
Received: from localhost (127.0.0.1)
by tonid.net with SMTP; 5 Jan 2004 03:03:04 -0000
Delivered-To: kingabl@xxxxxxxxxx
Received: from pop3.wp.pl
by localhost with POP3 (fetchmail-5.9.0)
for kinga-wp@xxxxxxxxxxxxx (single-drop); Mon, 05 Jan 2004 04:03:04 +0100 (CET)
Received: (WP-SMTPD 7955 invoked from network); 3 Jan 2004 14:34:47 -0000
Received: from 69.37.68.3.adsl.snet.net (HELO inboxcredit.com) ([69.37.68.3])
(envelope-sender <cialiss@xxxxxxxxx>)
by smtp.wp.pl (wp-smtpd) with SMTP
for <kingabl@xxxxxxxxxx>; 3 Jan 2004 14:34:46 -0000
From: cialiss@xxxxxxxxx
To: kingabl@xxxxx
Subject: fwd: you have to see this
Date: Sat, 03 Jan 2004 09:39:52 -0500
MIME-version: 1.0
Content-type: multipart/alternative; boundary=NextPart_056D6AE1F5648DE5610B
=== cut ===
The fetchmail logs show that the message is only picked up once.
And the messages come one after another, while fetchmail fetches
them every 5 minutes or so.
Here's the line from fetchmailrc for this account:
=== cut ===
poll pop3.wp.pl proto pop3:
here;
user "kingabl",
with password "password",
is "kinga-wp@xxxxxxxxxxxxx" here keep;
=== cut ===
Here's the qmail-default file for her local account:
=== cut ===
| preline /usr/bin/bogofilter -u -e -p | /usr/local/bin/maildrop
=== cut ===
and .mailfilter for maildrop contains:
=== cut ===
to "$HOME/Maildir/"
=== cut ===
The qmail-send logs just keep showing over and over:
=== cut ===
@400000003ff8c877349bf2ec new msg 24572
@400000003ff8c877349c44f4 info msg 24572: bytes 2095 from <cialiss@xxxxxxxxx> qp 24537 uid 610
@400000003ff8c87734f63464 starting delivery 38550: msg 24572 to local log@xxxxxxxxxxxxx
@400000003ff8c87734f699f4 status: local 1/2 remote 0/2
@400000003ff8c87734f6c104 starting delivery 38551: msg 24572 to local kinga-wp@xxxxxxxxxxxxx
@400000003ff8c87734f6ff84 status: local 2/2 remote 0/2
@400000003ff8c8781297d97c delivery 38550: success: did_0+0+1/
@400000003ff8c8781298373c status: local 1/2 remote 0/2
@400000003ff8c8782b331ec4 delivery 38551: success: did_0+0+1/
@400000003ff8c8782b33806c status: local 0/2 remote 0/2
@400000003ff8c8782b33ab64 end msg 24572
=== cut ===
and then the same thing, under the same msg number but different
delivery numbers.
The same thing with some other messages.
[BTW log@xxxxxxxxxxxxx is queue-extra-based logging]
Everything worked perfectly before fetchmail came into view.
If anyone could help in identifying the source of this problem,
I'd greatly appreciate it.
--
tomasz 'tonid' nidecki, zoliborz, warszawa, poland
tonid@xxxxxxxxx http://tonid.net http://endemic.org
jabber: tonid@xxxxxxxxx registered linux user #308829
'don't worry, hug an algae eater' (c)hubertus