This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.
[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
Task Manager for Hyper-V provides critical information that allows you to monitor Hyper-V performance by displaying real-time views of CPU and memory at the individual VM-level, so you can quickly identify which VMs are using host resources.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
One-stop solution for Exchange Administrators to address all MS Exchange Server issues, which is known by the name of Stellar Exchange Toolkit.
- Software-Other
- Exchange
- Email Servers
- Email Software
- Exchange 2007
- *Exchange Server 2010
Are you an Exchange administrator employed with an organization? And, have you encountered a corrupt Exchange database due to which you are not able to open its EDB file. This article will explain all the steps to repair corrupt Exchange database.
In this video we show how to create a Contact 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 >> Contact ta…
In this video we show how to create an Accepted Domain 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 Mail Flow >> Ac…
Suggested Courses
Course of the Month8 days, 2 hours left to enroll
610 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.