On Wed, 8 Oct 2008, Duane Hill wrote:
On Wed, 8 Oct 2008, Paul Cocker wrote:
But isn't recipient maps purely checking the destination address to see
if it's valid? If so, why does it matter when you check the validity so
long as you do before it reaches its final destination for that domain
and is bounced?
Let's just assume your secondary server accepted a connection. It is your
secondary server's responsibility to deal with that connection. It can either
reject the connection telling the sending server to go away, or accept the
message for delivery (in your case, accept a message for delivery even if the
account doesn't exist). If your secondary server accepts the message,
connection to the sending server has already been closed. The ONLY thing it
can do at this time, is bounce.
We have two gateway servers that filter messages coming in. Those two servers
pass messages along to three internal servers. The two filter servers at the
gateway reject (not bounce) unknown accounts BEFORE the message is passed on
to its next destination via:
reject_unknown_recipients
This should be:
reject_unverified_recipient
