From: Dan Melomedman [mailto:da...@devonit.com]
Bowie Bailey wrote:
From: Dan Melomedman [mailto:da...@devonit.com]
Bowie Bailey wrote:
What I need is a way for the server at the edge of my network to
be able to reject all non-legitimate mail. This gives the
sending MTA responsibility for the bouncebacks.
This way double bounces for your users will end up in the sender
MTA postmaster's inbox, not yours. Chances are they'll just ignore
them. I don't know if this is important or not for you, but
certainly something to remember.
I'm not sure I follow you here. The only double-bounce scenario I
can think of is if one of my users mistypes his email address in his
MUA and
No, that message was about the incoming scenario. I am new to Courier,
it may be the case that Courier always throws 550 before accepting
mail into the queue, so it would be the default behavior as described
in prior email. If a message with invalid sender and recipient
addresses is given to a server which throws 550, then the doublebounce
is generated on the sending server. If it's accepted into the queue,
then a bounce and a subsequent double bounce is going to be on the
receiving server. Which may or may not be what you want. Personally,
I gave up on double bounces, as most of them are SPAM, and there are
too many of them to watch over.
Courier will reply with a 550 if the domain is local and the username
doesn't exist. Only mail for valid local users and mail that is allowed
for relay will make it into the queue.
Bowie
13 messages in net.sourceforge.lists.courier-usersRE: [courier-users] Smart mail relay
