>Yes, but doing it this way - unless I'm missing what you are saying -
>you totally lose one of the more valuable anti-spam tools - recipient
>validation.
You are absolutely correct. I have chosen that email to [EMAIL PROTECTED]
will land in a
Nice pit and never bounce. No address harvesting, no validation,
nothing. Obvious
Spam is naturally handled by ASSP, its what gets though I want to know
about.
Note that in my case 'somedomain' is actually a set of seven domains,
all of which
Fall to the same tar pit.
For myself, the '[EMAIL PROTECTED] -> [EMAIL PROTECTED]' is not important, as I
don't do
Domain translation, simply direct everything to a tar pit.
BTW, I find recipient validation is not as important as you would
imagine. Certainly
mail to unknown users is normally bounced immediately, but that
merely assists in
harvesting attacks.
I prefer to accept all email (which otherwise passes spam checking)
and validate
that it is in fact junk. Apart from backscatter, which seems to be
a growing problem
even with ASSP, most of the non-junk misaddressed email is simply
that. Usually due
to the number of unpronounceable European names in our (very small)
organisation.
>If you do apply something like this, be damn sure you don't bounce
>messages to unknown recipients *after* accepting them through one of
>these catch-call type addresses.
Not sure where you are going with this. Why would a catch all address
bounce? And
What would the problem be? (Unless you are referring to the automatic
whitelisting
of the outgoing bounce message..., but I would hope enabling
' Do Not Collect Bounced Mails (DoNotCollectBounces)'
would cover that scenario..
Cheers.
David
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Charles
Marcus
Sent: Tuesday, 6 May 2008 7:51 PM
To: ASSP development mailing list
Subject: Re: [Assp-test] Domainname translation
On 5/5/2008, David le Blanc ([EMAIL PROTECTED]) wrote:
> mail for '[EMAIL PROTECTED]' delivered as '[EMAIL PROTECTED]' and mail for
> '[EMAIL PROTECTED]' and '[EMAIL PROTECTED]' delivered as
> '[EMAIL PROTECTED]'..
>
> (The first merely translates the domain part, the second directs an
> entire domain and subdomains worth of email to a single user. more
> specific cases would be an advantage for many.)
--
Best regards,
Charles
------------------------------------------------------------------------
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/j
avaone
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
