Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies. Only from Platform Scholar.
COURSE of the MONTH
9 days, 16 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
4
3
3
11 Comments
Which version of Exchange are you running and what have your tests shown when trying to resolve your secondary smtp domain from the Internet?
SBS 2003 Exchange 2003 SP2.
220 mail.domain1.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.4675 ready at Mon, 7 Mar 2011 11:04:20 -0700
OK - 63.230.214.70 resolves to mail.doxacentral.com
OK - Reverse DNS matches SMTP Banner
0 seconds - Good on Connection time
May be an open relay.
0.484 seconds - Good on Transaction time
Session Transcript:
HELO please-read-policy.mxtoolb
250 mail.domain1.com Hello [64.20.xxx.xxx] [94 ms]
MAIL FROM: <supertool@mxtoolbox.com>
250 2.1.0 supertool@mxtoolbox.com...
RCPT TO: <test@example.com>
250 2.1.5 test@example.com [78 ms]
QUIT
221 2.0.0 mail.domain1.com Service closing transmission channel [78 ms]
220 mail.domain1.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.4675 ready at Mon, 7 Mar 2011 11:04:20 -0700
OK - 63.230.214.70 resolves to mail.doxacentral.com
OK - Reverse DNS matches SMTP Banner
0 seconds - Good on Connection time
May be an open relay.
0.484 seconds - Good on Transaction time
Session Transcript:
HELO please-read-policy.mxtoolb
250 mail.domain1.com Hello [64.20.xxx.xxx] [94 ms]
MAIL FROM: <supertool@mxtoolbox.com>
250 2.1.0 supertool@mxtoolbox.com...
RCPT TO: <test@example.com>
250 2.1.5 test@example.com [78 ms]
QUIT
221 2.0.0 mail.domain1.com Service closing transmission channel [78 ms]
Did it always work or is this an additional SMTP domain?
Have you taken a look at this tutorial? http://www.petri.co.il/configure_exchange_2000_2003_to_receive_email_for_other_domains.htm
Have you taken a look at this tutorial? http://www.petri.co.il/configure_exchange_2000_2003_to_receive_email_for_other_domains.htm
It always worked. But the guy before me did something and the server is an opened relay. So I am trying to close the relay and get the domains the ability to be delivered.
If the previous article does not illustrate your needs to add the secondary SMTP domain into the RUS. Try this page from technet.
http://support.microsoft.com/kb/260973
Unfortunately I have no idea what the other person may have configured. Your best bet is to run a few telnets in between your configurations. The technet article should help most as it illustrates what you need.
http://support.microsoft.com/kb/260973
Unfortunately I have no idea what the other person may have configured. Your best bet is to run a few telnets in between your configurations. The technet article should help most as it illustrates what you need.
Active today
Please have a read of the following link to resolve your open relay and when that is done, check on www.checker.com
http://www.amset.info/exchange/spam-cleanup.asp
Once the relaying is resolved, we can move on to the mail-flow issue.
http://www.amset.info/exchange/spam-cleanup.asp
Once the relaying is resolved, we can move on to the mail-flow issue.
I made teh necessary changes and now I am no longer a mail relay. But I no longer can receive email at the secondary domains.
Delivery to the following recipient failed permanently:
jebadmin@domain2.com
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.7.1 Unable to relay for jebadmin@domain2.com (state 14).
Delivery to the following recipient failed permanently:
jebadmin@domain2.com
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.7.1 Unable to relay for jebadmin@domain2.com (state 14).
Active today
Okay - please check your Recipient Policies to see if the secondary domain name is an accepted domain and that the server is authoritative for the domain.
For info on where to check (in case you are not sure):
http://support.microsoft.com/kb/823158
For info on where to check (in case you are not sure):
http://support.microsoft.com/kb/823158
Featured Post
Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Find out what you should include to make the best professional email signature for your organization.
This article will help to fix the below error for MS Exchange server 2010
I. Out Of office not working
II. Certificate error "name on the security certificate is invalid or does not match the name of the site"
III. Make Internal URLs and External…
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center.
Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center.
Navigate to the Recipients >> Sha…
The video tutorial explains the basics of the Exchange server Database Availability groups.
The components of this video include:
1. Automatic Failover
2. Failover Clustering
3. Active Manager
Suggested Courses
Course of the Month9 days, 16 hours left to enroll
762 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.