Duane Hill wrote:
On Mon, 5 Jan 2009, Corey Chandler wrote:
Magnus B?ck wrote:
That's because "@example.com" is not the correct syntax for transport
table domain wildcards. Do read transport(5) (hint: drop the "@").
Doh, that'd do it. It started life as a relay recipient map, so
that'd explain it-- I THINK that's where I got the @DOMAIN syntax
from, at any rate...
You also need to put recipient address validation in place with either
relay_recipient_maps or recipient address verification.
http://www.postfix.org/STANDARD_CONFIGURATION_README.html#firewall
http://www.postfix.org/transport.5.html
http://www.postfix.org/postconf.5.html#relay_recipient_maps
http://www.postfix.org/ADDRESS_VERIFICATION_README.html
Why? It's not an outscatter source, as all possible recipients are
directed to a (non quota'd) catchall on the endpoint server. Sure,
they'll get metric craploads of spam, but The Business(tm) overrode
my objections to it, so as far as I'm concerned they can drown in it...
And, when someone misspells an email address, they won't get a
rejection stating their message was undeliverable. Therefore, whoever
that be, will assume the message was delivered.
*nods* This was also pointed out, but given that 99% of mail to this
particular domain goes to one recipient, it was decided this was
"statistically unlikely." There are days I wonder why they pay me. :-p
-- CJC
