>...
>I'm getting quite a bit of spam with
>Return-Path: <>
>in the headers.
>
>Will I likely see valid e-mail with this? Searching my previous mail,
>it appears to all be bounce warnings.
>
>If so, what's the best way to just blackhole this? I have postfix, and put
>/Return-Path: <>/ Reject in the header_checks, but that seems to not
>be correct.
>
>Here's a example of one of the headers:
>
>Return-Path: <>
>X-Original-To: [EMAIL PROTECTED]
>Delivered-To: [EMAIL PROTECTED]
>Received: from aamer-e5bc809e7.chello.nl (a49245.upc-a.chello.nl
>[62.163.49.245])
> by espphotography.com (Postfix) with SMTP id B4BCF35A80D
> for <[EMAIL PROTECTED]>; Thu, 5 Jan 2006 10:56:24 -0800 (PST)
>Message-Id: <[EMAIL PROTECTED]>
>Date: Thu, 5 Jan 2006 10:56:24 -0800 (PST)
>From: MAILER-DAEMON
>To: undisclosed-recipients:;
>
>
>Thanks.
>
>Evan
>
If you ever purposely request delivery notification, it will
come with "<>". Also, any failure to deliver mail sent out and accepted
(e.g. user over quota) comes with a DSN/"<>". And finally, someone might
list you at rfci (not me though) - See:
http://www.rfc-ignorant.org/policy-dsn.php.
There are generally better methods for this, but they are not
nearly so simple as just refusing DSNs. (Also you header check misses
the more common cases with a "real name" of "MAILER-DAEMON", so if you
do stick with this scheme, you probably want an expression like:
/Return-Path: [^<]*<>/
Paul Shupak
[EMAIL PROTECTED]
