Please don't top-post. Thank you.
On Wed March 4 2009 17:10:49 Jim McIver wrote:
> Guess I'm confused. I have a relay_recipient and recipient_access
> files listing only valid user's email addresses for my company.
> ie..
> relay_recipients
> bg...@lmtribune.com any_value
> bi...@lmtribune.com any_value
> bjohn...@lmtribune.com any_value
>
> recipient_access
> bg...@lmtribune.com permissive
> bi...@lmtribune.com permissive
> bjohn...@lmtribune.com permissive
This sounds right. You could use the same map for both purposes.
There's nothing magical about "any_value", in fact, the lookup result
for relay_recipient_maps is ignored. So it might as well be
"permissive" or "restrictive" or whatever.
> and nothing in virtual_alias_maps. I just seem to be getting hammered
> with yahoo.co.jp and wanted to block .co.jp or even .jp.
>
> Putting info in putting .jp in access_client, sender_access or
> client_access doesn't seem to stop it.
> Sorry for my lack of understanding.
Show the logs for the suspicious mailq entries when they first arrived.
Not the smtp(8) logs showing you being blocked by yahoo.co.jp's MX
hosts.
My WAG here: your Postfix configuration is correct, rejecting unknown
recipients, but the @yahoo.co.jp senders originated from your own
server. Compromised HTTP+PHP service?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
