NDRs sent to incorrect domain

From: David Farm (nobody_at_nowhhere.com)
Date: 10/26/04 

Date: Tue, 26 Oct 2004 18:48:52 +0200

Hello,

I have an Exchange 2003 server handling mails for several domains and the
mails themselfs work fine, the NDRs however do not.

The setup is:
domain.local is the local domain, Exchange does not handle mail for this
one.
domain1.com answers on IP1 and is the primary address in the reciepient
policy
domain2.com answers on IP2 and is in the recipient policy

Both domain1.com and domain2.com have their own SMTP Virtual Servers with
masquerade domain etc set.

Now, users with a mailadress to domain1 (user@domain1.com) have no problems
at all but users with ONLY an adress in domain2 (user@domain2.com) cannot
receive NDRs.

If their clients tries to send a mail with an incorrect adress (such as
nosuchuser@nowhere.com) the server will send the NDR to user@domain1.com,
which will fail since no such adress exist.

If I change the primary adress in the recipient policy from domain1 to
domain2 then it will be postmaster@domain2.com sending the mail (This I've
read about, and how to implement a sink to fix it) but it will STILL be sent
to user@domain1.com

Doesn't help to remove the masquerade domain from the virtual server either.
The NDR does have SOMETHING to do with the default SMTP virtual server
though, since I get a copy of the NDR and that rule exists only on that
server.

Also, if I stop the default SMTP virtual server (which handles domain1) then
the mail seems to be stuck.
The queue that the mail gets stuck in seems to be for the SMTP connector
though. I only have one of those, but there are no domain names in there...

The domain1 SMTP server and domain2 SMTP server answers on different IP
addresses, and as I said, I can turn off the default SMTP server and still
send in mail so I know the client is connected to the correct virtual server
(not that this should matter though).

I have no idea of what's going on... Does my domain2 SMTP server send the
mail to the SMTP connector that sends the mail to the domain1 SMTP server
that sends it out to the internet? That can't be the case, can it...?

Needless to say, the users in domain2.com are not very happy... and I can't
solve it by giving them adresses in domain1.com.

Hopefully, someone can help me with this since I'm out of ideas.

Best regards,

David

Relevant Pages

  • Re: You do not have permission to send to this recipient......
    ... NDRs that contain a 5.7.1 error code occur if the Allow computers ... Simple Mail Transfer Protocol (SMTP) virtual server. ... the matching recipient policy might not exist. ...
    (microsoft.public.exchange.admin)
  • Re: Spam attack
    ... No NDR is generated for an SMTP message denied with a 550 regardless of whether you've configured NDRs or not. ... Once enabled and properly added to the SMTP virtual server, exchange will now generate a 550 for invalid mailboxes instead of accepting and later sending an NDR. ... Somebody can connect and just start throwing addresses at your server and seeing which ones generate 550 or 250, thus eventually gathering legitimate emails. ...
    (microsoft.public.windows.server.sbs)
  • Re: 5.7.1 smtp;550 5.7.1 Requested action not taken:
    ... NDRs that contain a 5.7.1 error code occur if the Allow computers ... the Simple Mail Transfer Protocol (SMTP) virtual server. ... Recipient policies control the behavior of SMTP in addition to the ...
    (microsoft.public.inetserver.iis.smtp_nntp)
  • Re:#5.7.1 smtp;550 5.7.1 Requested action not taken: message refused
    ... NDRs that contain a 5.7.1 error code occur if the Allow computers ... the Simple Mail Transfer Protocol (SMTP) virtual server. ... Recipient policies control the behavior of SMTP in addition to the ...
    (microsoft.public.exchange.connectivity)
  • Re: Exchange Server 2000 relay problem.
    ... These may be NDRs from spam. ... Block Open SMTP Relaying and Clean Up Exchange Server SMTP ...
    (microsoft.public.exchange.connectivity)
Loading