Re: Multiple SMTP addresses for uses/messages being rejected

Leif,

I was able to resolve this by using the following procedure I found
elsewhere.

Based on my further research, the "5.7.1 Unable to relay" problem can
also
occur if the recipient policy configuration is not added into Metabase.
We
can see the domains that the Exchange organization is hosting in
Metabase->[/SmtpSvc/1/Domain/<domain name>]. If the expected domain is
absent, the emails sent to this domain will be rejected and the 5.7.1
NDR
will be generated. To resolve this, we can add the domain manually in
Metabase.

1. Install MBExplorer by installing IIS 6 Resource Kit Tools.

2. After the installation, click ''Start''->''All Programs''->''IIS
Resources''->''Metabase Explorer''->''Metabase Explorer''.

3. In the Metabase Explorer, right-click ''LM'' and select ''Export to
file''. Export the key to a mbk file for backup purpose.

4. Navigate to LM\SmtpSvc\1\Domain\. For a normal Exchange server, you
should see the second domain name under this key. If you don't have,
you
need to manually add one key for the second domain. Right-click the key
of
primary SMTP domain, choose ''Copy''. Then, right-click ''Domain'' and
choose ''Paste''. In the key already exists box, select ''Copy to a new
key'' and input the second domain name in the box. Click ''OK'' and
then
you will see a new key with the second SMTP domain name.

5. Close Metabase Explorer. Click ''Start''->''Run''->Input
''iisreset''
and press Enter.

Leif Pedersen [MVP] wrote:
Hi,

Make sure that the old address is also included in a recipient policy.
Otherwise the server won't accept mails for the domain.

Leif

<doug.dockter@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:1150488686.667241.173390@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Our e-mail domain used to be xxxx.com. About a year ago we changed it
to yyyy.com. In Exchange you can have multiple SMTP e-mail addresses.
So we kept both the new address (yyyy.com and marked it as the primary)
and the old address. It appears since we upgraded to Exchange 2003
that any e-mails sent to xxxx.com are getting rejected - see the error
below. I still have the SMTP service running on another server because
of GFI MailEssentials. This has a remote SMTP domain set up for
xxxx.com as it does for yyyy.com with a smart host IP address of the
Exchange server. This is the same setup as before the Exchange
conversion except for changing the IP address to point to the new
Exchange server.

Message delivery to the remote domain xxxx.com failed. The error
message is An SMTP protocol error occurred.


The SMTP verb which caused the error is RCPT. The response from the
remote server is 550 5.7.1 Unable to relay for xxx@xxxxxxxx


.

Relevant Pages

  • [NT] Vulnerability in Exchange Server Allows Remote Code Execution (MS05-021)
    ... A remote code execution vulnerability exists in Microsoft Exchange Server ... their choice in the security context of the SMTP service. ...
    (Securiteam)
  • Re: SMTP Sharing HELP!!
    ... If your Recipient Policy applies to Contacts, ... your smtp domainalso in the email addresses tab. ... Are there any KB articles for setting up the Exchange Server on the ...
    (microsoft.public.exchange.setup)
  • Re: ActiveSync warning
    ... in short the binding is wrong on the exchange server. ... I have run it with my local account and with my domain administrator account ... up-to-date notifications on their device until the correct SMTP address is ...
    (microsoft.public.exchange.clients)
  • Re: MS EXchange behind NAT
    ... > server as an Exchange server if we have to. ... >> 1) open smtp on your firewall to internal Exchange. ... >> gateway in your dmz, open smtp from Internet to that box in dmz, open ...
    (microsoft.public.exchange.design)
  • Exchange 2003/Windows 2003 Multiple Domains, 1 Exchange Server
    ... Exchange server for years now. ... In an attempt to save money we wanted to use the same exchange server. ... Which does not seem to be an issue but I can not get the second domain ...
    (microsoft.public.exchange.admin)