Noel Jones escribió:

> If you have a large number of domains, keep a separate list of the domains 
> and let the computer build the different tables for you.  Use a Makefile to 
> make it easy. 

Or I could use two different mysql queries, over the same table containing
the vdomains...

> Some web invites / rotten mail lists / web notifications etc. will
> arrive with the recipient's address as the sender.  While this is
> generally poor form, a few legit sites do it.  I don't have any specific
> examples, but know they exist.  "trust me"

Yes, you're right (I trust you! :-)). I did a quick search in my inbox and
found an example: notices from Ubuntu bug tracking system ("Launchpad" at
canonical.com) use that (poor) technique. But I'm wondering:
1) How often could you find this "nasty errors" (yes, difficult question;
impossible to answer, I'd add)
2) How important are this kind of "notices"...

Although it's a personal opinion, it seems that I can afford "loosing" such
mails... On the other hand, perhaps they're identifiable by other means, I
mean, headers, such as:

Return-Path: <[EMAIL PROTECTED]>
X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
...
Received: from gangotri.ubuntu.com (localhost.localdomain [127.0.0.1])
        by gangotri.ubuntu.com (Postfix) with ESMTP id 0C222318376
        for <[EMAIL PROTECTED]>; Fri, 28 Jul 2006 04:10:09 +0100 (BST)
From: RoMaNSoFt <[EMAIL PROTECTED]>
Reply-To: Bug 26119 <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
X-Launchpad-Bug: distribution=ubuntu; sourcepackage=linux-source-2.6.15;
        component=main; status=Needs Info; importance=Medium;
        [EMAIL PROTECTED];
To: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
X-Generated-By: Launchpad (canonical.com)

Perhaps the "reply-to" header could be an indication of this kind of notices?

You are (again) right, perhaps spamassasin is better for performing this
kind of check... with the added bonus that filtered mail is not dropped,
but quarantined (so you could always rescue a false negative). Do you know
"how well" does it (SA) perform at blocking this spam case (src dom=dst
dom) while recognizing "legit" (but nasty) notices?

For the very same reason, isn't it better to let Spamassassin make
"intelligent" SPF-checks instead of using some other policy server with
Postfix?

Thank you for your responses.

-- 

Saludos,
-Roman

PGP Fingerprint:
09BB EFCD 21ED 4E79 25FB  29E1 E47F 8A7D EAD5 6742
[Key ID: 0xEAD56742. Available at KeyServ]

Reply via email to