Re: reject_unlisted_recipient

----- Original Message -----
From: "Victor Duchovni" <Victor.Duchovni@MorganStanley.com>
To: <postfix-users@postfix.org>
Sent: Wednesday, February 16, 2005 1:29 PM
Subject: Re: reject_unlisted_recipient


> On Wed, Feb 16, 2005 at 01:01:58PM -0700, JB wrote:
>
>> smtpd_recipient_restrictions = reject_unknown_sender_domain,
>> reject_unknown_recipient_domain, check_recipient_access
>> mysql:/etc/postfix/pre_recipient.cf permit_mynetworks,
>> check_client_access hash:/etc/postfix/pop-before-smtp
>> reject_unauth_destination, check_sender_access
>> mysql:/etc/postfix/sender_access.cf check_client_access
>> mysql:/etc/postfix/client_access.cf check_recipient_access
>> mysql:/etc/postfix/recipient_access.cf reject_invalid_hostname,
>> reject_non_fqdn_hostname, reject_non_fqdn_sender,
>> reject_non_fqdn_recipient, reject_unauth_pipelining,
>> reject_rbl_client relays.ordb.org, reject_rbl_client
>> sbl.spamhaus.org,
>> reject_rbl_client bl.spamcop.net, reject_rbl_client
>> relays.visi.com,
>> reject_rbl_client blackholes.mail-abuse.org, reject_rbl_client
>> list.dsbl.org, reject_unlisted_recipient, permit
>
> The is equivalent to the same thing with the last two elements left out.
> Whatever problem you are trying to solve needs to be solved in some other
> way.

I know, it's more of a mental note than anything else. I read the docs, I
know the default is yes.

The problem I'm trying to solve is this:
I have an @domain.dom in virtual sending all messages to me that aren't
otherwise defined. A few days ago some loser of a spammer started forging
the domain name and now I have thousands and thousands of bounces coming to
me. I would just remove the @domain.dom but that will just clog the queue.
So when I remove the @domain.dom I want the inital smtpd process that remote
mail servers first hit to prevent the bounce from being queued because the
recipient of the bounce doesn't exist.

Each test message I send to other domains that don't have wildcard addresses
setup still queue the messages, even for invalid addresses. It sends it
through the content filter and then in the second postfix instance, it
realizes the user doesn't exist and then sends back the bounce.

>
>> relay_domains = $mydestination, mysql:/etc/postfix/relay_domains.cf
>
> And yet don't define "relay_recipient_maps", that is far more likely
> to be your problem.
>


I've upgraded postfix several times from older versions. In the past, There
was no virtual_alias_domains or virtual_mailbox_domains, etc...and the only
way I could get postfix to accept mail for my domains with my virtual setup
was to put them in relay_domains.

Besides, I don't know if you noticed, but in my master.cf relay_domains is
redefined to be nothing for the first smtpd instance anyway.

Thanks,
JB