On Nov 24, 2008, at 7:50 PM, mouss wrote:
*snip*
So far, so good. Now, we try:
[EMAIL PROTECTED] = relays internally like the others above.
How can I prevent this from happening? [EMAIL PROTECTED]/org does not
have a valid virtual resolution, and does not exist in
relay_recipient_maps, and yet it's still happily forwarding along
internally.
but you have a mapping for joe in your virtual:
[EMAIL PROTECTED] [EMAIL PROTECTED]
so [EMAIL PROTECTED] is accepted.
I only want legitimate users to forward, and the one place I
thought I
might be able to filter the list down, relay_recipient_maps, isn't
doing
anything to stop him, even though I have a user from each domain
listed,
which from what I read in the Postfix docs means it's inclusive, and
only should allow those users to relay, and everyone else gets a
bounce.
addresses found in virtual_alias_maps are accepted during the smtp
transaction. they may result in a later bounce if they cannot be
delivered.
This is useful if this is the case. Unfortunately, all the resolution
MUST happen at this server, as the spam gateway requires that I only
send it real users, not users that have any translations left to apply
to their user account or do not exist. This requirement is
unfortunately hard and fast due to the functionality and licensing
requirements of the gateway.
Is there something else in Postfix I can do that could force the
address resolution to be fully resolved before relaying? If the
virtual tables were left to their own devices and not tied to
relaying, this would work fine, because the virtual would attempt to
resolve [EMAIL PROTECTED] -> [EMAIL PROTECTED] -> FAIL, and bounce the
message. That's the behavior I want here, I just want all valid ones
to move to another server instead of delivering locally.
Thanks,
George
