From: (no name) (no email)
Date: Sun Dec 01 2002 - 13:59:43 EST
That's okay. What I actually wanted is these spam-lovers' e-mail to be
skipped before Postfix evaluates content_filter. Thanks for the advise
though.
-----Original Message-----
From: Tomasz Papszun [mailto:]
Sent: Thursday, November 28, 2002 7:37 PM
To:
Cc:
Subject: Re: Client who wants to receive spam
On Thu, 28 Nov 2002 at 15:54:46 +0800, wrote:
> Hi Rahul,
>
> I don't know if this be done using check_recipient_access in the
> smtpd_*_restrictions but I have a hunch it will. I've already placed some
> clients inside my recipient_checks.regexp:
>
> smtpd_recipient_restrictions =
> check_sender_access cdb:$config_directory/sender_access,
> check_sender_access cdb:$config_directory/sender_access_local,
> check_client_access cdb:$config_directory/client_access,
> reject_non_fqdn_sender,
> reject_non_fqdn_recipient,
> reject_unknown_sender_domain,
> reject_unknown_recipient_domain,
> permit_mynetworks,
> reject_unauth_destination,
> check_recipient_access regexp:$config_directory/recipient_checks.regexp
> reject_unauth_pipelining,
> reject_invalid_hostname,
> reject_non_fqdn_hostname,
> reject_maps_rbl
> permit
>
> /[@!%].*[@!%]/ 550 Please use user at domain address forms only.
> /postmaster@/ OK
> /abuse@/ OK
> // OK
>
[...]
Francis,
it won't work.
Your recipient_checks.regexp is checked _after_ sender_access,
sender_access_local and client_access, so a message will be rejected
_already_, before it reaches recipient_checks.regexp.
The list with "spamlovers" must be placed _before_ negative checks.
But be very careful because then you can open your server (you can make
it open relay).
So you must be very selective what you put into "spamlovers". E.g.,
do _not_ place /postmaster@/ nor /abuse@/ there!
Use full addresses, like and .
If not, your server will relay for any postmaster and any abuse.
--
Tomasz Papszun SysAdm @ TP S.A. Lodz, Poland | And it's only
http://www.lodz.tpsa.pl/ | ones and zeros.
|
|
|