 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
14 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] filters only work som...| From | Sent On | Attachments |
|---|---|---|
| Robert Stoeber | Feb 25, 2003 10:19 am | |
| Devin Rubia | Feb 25, 2003 12:23 pm | |
| Robert Stoeber | Feb 25, 2003 4:02 pm | |
| Devin Rubia | Feb 26, 2003 5:20 am | |
| Robert Stoeber | Feb 26, 2003 12:18 pm | |
| Devin Rubia | Feb 26, 2003 12:43 pm | |
| Robert Stoeber | Feb 26, 2003 2:23 pm | |
| Devin Rubia | Feb 27, 2003 6:27 am | |
| Robert Stoeber | Feb 28, 2003 9:36 am | |
| Devin Rubia | Feb 28, 2003 10:24 am | |
| Sam Varshavchik | Feb 28, 2003 2:28 pm | |
| Robert Stoeber | Feb 28, 2003 3:54 pm | |
| Robert Stoeber | Feb 28, 2003 5:54 pm | |
| Sam Varshavchik | Feb 28, 2003 7:18 pm |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: [maildropl] filters only work sometimes? | Actions... |
|---|---|---|
| From: | Devin Rubia (dev...@thezone.net) | |
| Date: | Feb 28, 2003 10:24:40 am | |
| List: | net.sourceforge.lists.courier-maildrop | |
On Fri, Feb 28, 2003 at 10:36:33AM -0700, Robert Stoeber wrote:
At 07:26 AM 2/27/2003, Devin Rubia wrote:
Now that is odd. If that is the first rule in your mailfilter, then that mail should not be getting through. Do you have a copy of the headers from the message that slipped through? Maybe there is something in there that could be causing maildrop not to match "jsmith"?
If you still have a copy of the message, you could also try manually feeding it to maildrop and see what happens.
Hi Devin,
I found a perfect example of my problem. This morning I realized why maildrop isn't catching some messages - it's because the delivery address doesn't even appear in the header. Now I'm left wondering why/how this got into the queue trying to be delivered to this particular non-existent user?
I started the day with an empty queue and watched until the following:
------ messages in queue: 1 messages in queue but not yet preprocessed: 0 28 Feb 2003 15:39:52 GMT #16229 3835 <regi...@hotmail.com> local usab...@usabusiness.net
------
There is no local user (or alias) called szai...@usabusiness.net so why it didn't get bounced is one question. The maildrop rule is scanning the header for /szailyk/ and should be dropping those messages anyway, but more on that below.
Then I went looking around the queue and apparently found the message in /var/qmail/queue/mess/14/16229 so here's the header of the message:
------ Received: (qmail 27884 invoked by uid 508); 28 Feb 2003 15:39:52 -0000 Received: from regi...@hotmail.com by mail2.usabusiness.net by uid 89 with qmail -scanner-1.15 (clamscan: 0.54. Clear:. Processed in 0.360409 secs); 28 Feb 2003 15:39:52 -0000 Received: from unknown (HELO smtp1.misdevelopment.com) (65.209.124.33) by 0 with SMTP; 28 Feb 2003 15:39:51 -0000 Received: from mx1.hotmail.com [210.10.50.10] by smtp1.misdevelopment.com with E SMTP (SMTPD32-7.00) id A2922A00BC; Fri, 28 Feb 2003 10:38:58 -0500 Message-ID: <0000733434f7$00002dd8$0000...@mx1.hotmail.com> To: <Subscribers> From: "Brittney RUldo" <regi...@hotmail.com> Subject: GET CUT GET FIT GET INTO IT RZ Date: Fri, 28 Feb 2003 23:41:34 -2000 MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
------
The header doesn't mention the invalid user so that would explain, I guess, why maildrop isn't trapping the message. But then how is it getting into the queue for that user?
Ah. They're probably using a Bcc: line which would get stripped before the message is passed on to local delivery and thus not available for filtering.
-- Devin