Exchange 2013 allowing emails from spoofed domains

We upgraded from Exchange 2010 to 2013 about 6 months ago and are very disappointed. We were running Forefront protection for Exchange on the 2010 server, and had little to no spam every. Now with 2013 we are getting a ridiculous amount of spam, including
clearly spoofed phishing emails. The most recent are from
'[email protected]' with an attached zip. We get about 4-5 of those a day, and since we do use salesforce, I can't just block the address/domain.
I have followed the TechNet guide, and enabled all of the antispam features with the Exchange management shell. I have enabled the senderIDConfig, and have it set to delete spoofed domains. The reverse dns check is working, as it shows the
status on the messages that are sent to quarantine. We also have the content filter enabled, and every day I have to go through the spam and add keywords it actually blocks something.
So how is it that spoofed messages are still making it through? I have checked salesforce and they have their SPF records setup, so it should not be hard for Exchange to see the mail did not originate from any of the IPs in the list. We are seriously considering
moving back to our exchange 2010 server....

Here are the headers of the email, which show its not coming from an IP listed in the SPF record for that domain...
Received: from ExchServer.domain.local (EXCH_IP) by ExchServer.domain.local
(EXCH_IP) with Microsoft SMTP Server (TLS) id 15.0.775.38 via Mailbox
Transport; Fri, 21 Feb 2014 06:51:55 -0800
Received: from ExchServer.domain.local (EXCH_IP) by ExchServer.domain.local
(EXCH_IP) with Microsoft SMTP Server (TLS) id 15.0.775.38; Fri, 21 Feb
2014 06:51:55 -0800
Received: from nacha.org (176.103.168.1) by ExchServer.domain.local (EXCH_IP)
with Microsoft SMTP Server id 15.0.775.38 via Frontend Transport; Fri, 21 Feb
2014 06:51:42 -0800
Received: from 176.103.168.1 (account [email protected] HELO
hlijear.cieewgas.org) by (CommuniGate Pro SMTP 5.2.3) with ESMTPA id
993713337 for [email protected]; Fri, 21 Feb 2014 15:51:39 +0100
Received: from smtp01-was.mta.salesforce.com ([96.43.148.64]) by
m1pismtp01-011.prod.mesa1.secureserver.net with ESMTP; Fri, 21 Feb 2014
15:51:39 +0100
Return-Path: <[email protected]>
Received: from [10.236.73.76] ([10.236.73.76:58434]
helo=na10-app2-11-was.ops.sfdc.net) by mx2-was.mta.salesforce.com
(envelope-from <[email protected]>) (ecelerity 2.2.2.45 r()) with ESMTP
id 64/F1-22599-B8956259; Fri, 21 Feb 2014 15:51:39 +0100
Date: Fri, 21 Feb 2014 15:51:39 +0100
From: "[email protected]" <[email protected]>
To: <[email protected]>, <[email protected]>,
<[email protected]>
Message-ID: <[email protected]>
Subject: Check you payment data!
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------CE9B863200324FC"
X-Priority: 2
X-SFDC-LK: S82SNJ6CSHXLTTR
X-SFDC-User: KNAXCL1Y1DWN5IT
X-Sender: [email protected]
X-mail_abuse_inquiries: http://www.salesforce.com/company/abuse.jsp
X-SFDC-TLS-NoRelay: 1
X-SFDC-Binding: System
X-Nonspam: Whitelist
X-MS-Exchange-Organization-PRD: salesforce.com
X-MS-Exchange-Organization-SenderIdResult: SoftFail
Received-SPF: SoftFail (ExchServer.domain.local: domain of transitioning
[email protected] discourages use of 176.103.168.1 as permitted sender)
X-MS-Exchange-Organization-Network-Message-Id: 321bc164-8c39-43ea-f8af-08d0fd2b98f4
X-MS-Exchange-Organization-SCL: 1
X-MS-Exchange-Organization-PCL: 2
X-MS-Exchange-Organization-Antispam-Report: DV:3.3.5705.600;SID:SenderIDStatus SoftFail;OrigIP:176.103.168.1
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
X-MS-Exchange-Organization-AuthSource: ExchServer.domain.local
X-MS-Exchange-Organization-AuthAs: Anonymous

Similar Messages

Some external Users are getting Duplicate Emails from our domain

Some external Users are getting Duplicate Emails from our domain. I have Exchange 2013 and is properly configured. A user reported me that, I sent one email to the other domain's user, and it was delivered twice after 1 or 2 hours. I checked the Message
track log on exchange servers and email was resubmitted and sent from the edge server after 2 hours.
I have no idea why this is happening? can you please help me on this issue.

Hi Aleem,
Maybe some hidden rules cause this, I suggest use MFCMapi tool to double check whether there is any hidden rules exist.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Not recieveing email from certain domains

Hi,
I am having trouble getting to the bottom of an issue which I have had for a couple of weeks now.
We are unable to receive email from certain domains. The big problem is our sister company no one on there domain is unable to send to any party on our domain, this has only just started happening this morning, however email delivery form other domains has
been problematic for about two weeks now. We are receiving plenty of email form other parties still.
Our sister company is not getting any bounce backs and I have checked the message tracking within Exchange 2008 and I am unable to see any email come in at all from our sister company.
It is worth mentioning that the host of our domain is having a number of issues with "Nameserver" when I check on intodns.com and I'm not to sure if this is the problem or not, however we are currently in the process of transferring away form
them and setup with the same host as our sister company. The transfer hasn't happened yet as our current host hasn't released the tags.
Has anyone got any ideas that can help please??

What's the path from the sister company to your company?
Is it direct? Or does incoming email first transit through some online spam filtering service (like Postini).
Can the sister company connect using telnet?
Here's some very detailed directions:
http://www.port25.com/how-to-check-an-smtp-connection-with-a-manual-telnet-session-2/
And more concise:
http://exchange.mvps.org/smtp_frames.htm
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Can't access emails from my Domain webmail usging ...

Hello,
I have totally failed to access emails from my domain webmail. Is there anyway you can help me to access my webmail emails?
Your help will be highly appreciated
Thank you
Ronnie

Well, if it's *web*mail, then you only need the browser!
If you want to access it directly without using the browser, normally you have either POP3, IMAP or Exchange.
POP3 and IMAP are supported by the standard e-mail client, with or without Nokia Messaging (the latter is only needed if you need the push functionality).
If it's Mail for Exchange, you also have it integrated in your E75, so after typing your e-mail address you should get a question asking you which type of account is that.
But first check (with your provider) which type of access you have to your e-mail. If you only get webmail, then you're stuck with the browser..

Getting inner exception "dtd is prohibited in this xml document exchange" while reading emails from outlook

Getting error "The response received from the service didn't contain valid XML." with inner exception "dtd is prohibited in this xml document exchange" while reading emails from outlook(Not while reading every mail).
Can anybody please tell me what might be the issue. Below is the code where I am getting error
FindItemsResults<Item> RetrievedItems=null ;
RetrievedItems = service.FindItems(FIds, new ItemView(4));
String[] SignatureList = ConfigurationManager.AppSettings.Get("SignatureTypes").Split(',');
if (RetrievedItems != null && RetrievedItems.Count() > 0)
RetrievedItems.ToList().ForEach(x =>
try
List<String> Attachments = new List<String>();
List<String> ScanFileName = new List<String>();
bool IsAvailable = true;
//Getting error while Load() - below line of code
((Microsoft.Exchange.WebServices.Data.EmailMessage)x).Load();
Vo.EmailMessage msg = new Vo.EmailMessage();
msg.MessageId = ((Microsoft.Exchange.WebServices.Data.EmailMessage)x).Id.UniqueId;
msg.From = ((Microsoft.Exchange.WebServices.Data.EmailMessage)x).From.Address;
((Microsoft.Exchange.WebServices.Data.EmailMessage)x).ToRecipients.ToList().ForEach(z => msg.To += z.Address + ",");
((Microsoft.Exchange.WebServices.Data.EmailMessage)x).ReplyTo.ToList().ForEach(y => msg.ReplyToEmailAddress += y.Address + ",");
msg.Subject = ((Microsoft.Exchange.WebServices.Data.EmailMessage)x).Subject;
msg.Body = ((Microsoft.Exchange.WebServices.Data.EmailMessage)x).Body.Text;
msg.Dated = ((Microsoft.Exchange.WebServices.Data.EmailMessage)x).DateTimeSent;
Please help.

Hi,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
Niko Cheng
TechNet Community Support

Exchange 2013 prevent spam from my own domain

Dear All,
Back in Exchange 2007 we used to prevent spam from own domain by modifying permissions on the Receive Connector, as show on this link.
http://exchangepedia.com/2008/09/how-to-prevent-annoying-spam-from-your-own-domain.html
When I modify the same permissions on Exchange 2013 Default Front Receive Connector, the spam is still allowed threw.
Is there a different aproche to achieve the same result in Exchange 2013?
Thank you
Bujar

Hi Bujar,
Have you tried to modify the permissions on Exchange 2013 default Hub transport Receive connector?
As we know, for Exchange 2013, there have been major architectural changes to the Exchange server roles. Instead of the five server roles that were present in Exchange 2010 and Exchange 2007, in Exchange 2013, the number of server roles has been reduced
to three: the Client Access server and the Mailbox server, and with Service Pack 1, the Edge Transport server role.
The Exchange 2013 Mailbox server includes all many of the server components found in Exchange 2010: client access protocols, transport services, mailbox databases, and Unified Messaging services (the Client Access server redirects SIP traffic generated from
incoming calls to the Mailbox server). The Client Access server is a thin and stateless server that doesn’t do any data rendering. There’s never anything queued or stored on the Client Access server.
So, I recommend you try to modify the permissions on default hub transport receive connector, it may achieve your requirement .
Best regards,
Niko Cheng
TechNet Community Support

Sending email using Exchange 2013 defined email addresses not the account email address.

Currently we are using exchange 2013. Let's say a user has a mailbox account defined that has a default email reply address of [email protected] Now I define additional email address for the same account. When the user tries to send an email he can only send from
the default email address. Is it possible to send from a defined email anndress and not the default account email address?
Best Regards
Best Regards

Not natively with Exchange.
You will need 3rd party software if you want to have only one mailbox and the ability to send as any of the proxy addresses associated with it
Example:
http://www.ivasoft.biz/choosefrom2007.shtml
Not sure if Exchange 2013 is supported with it yet
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

How can I send email from my domain from my iPhone using Gmail

I want to send email from my iPhone using Gmail/Exchange but I want my emails to come from my own domain.
I've tried a few different methods but my email ends up crashing after a couple days.
Is there a simplified process to solve this annoyance?
Thanks in advance

lukefromsudbury wrote:
I have no idea what your're talking about.
Neither do I, nor any of the other posters in this thread.
Watch the Video Here:
http://www.theanywhereoffice.com/digital-lifestyle/how-to-send-mail-from-your-ow n-domain-using-gmail-and-iphone.htm
Shows you exactly how to do what you want.

Outlook can't connect with Exchange 2013 after migration from Exchange 2007

<style type="text/css">P { margin-bottom: 0.21cm; }</style>
Hello,
recently we've done a Exchange 2007 sp3 to 2013 sp1. Users can conect perfectly with OWA and with his iphone clients.
But the problem is they can't connect from his Outlook clients (2010, 2013), both internaly and externaly. Always fails with the message: The Connection to Exchange it is not avaliable.... Can't resolve the name of Exchange server.
To try to resolve it we've done:
- Check Outlook anywhere configuration en EAC: it is configure with and external url mail.company.com and internal server.domain.local. The security is the default Negociation, but we've tried all.
- Check the internal dns, there are records for mail.company.com and exchangeserverdomain.local pointing to the exchange local ip. Also there is a public zone company.com with the record mail.caompany.com pointing to the exchange local ip. Also we've made
records autodiscover.company.com and autodiscover.domain.local pointing to the exchange local ip.
- In the public dns from our domain there is the record A and MX pointing our public ip. There aren't any record Autodiscover but we think that the manial conection should work.
Check certificates: we've made a new self-signed certificate including all this internal and external domains and for all services.
- Check Outlook Anywhere block: we've cheked.
Currently server state:
- Old Exchange 07 server can't start, it was in very bad state and we achieved migrate the mailbox to the new server, after that we tried to uninstall, but it crashes with a public folder replication error. We got uninstall all the roles
unless the mailbox. After a restart it can't start.
-The new Exchange 2013 looks great, there isn't any trail of the old server, or we haven't seen anything in the EAC or shell.
I paste below the result of Microsoft Remote conectivity analaizer, with Outlook anywhere test. It is clear that there is a problem with that.
Sorry because the test is in spanish and I translated it with google, from here I only can access the tool in spanish.
We continue to try to resolve the problem.
Thanks to all in advance!
Testing RPC / HTTP connectivity.
Error in testing RPC / HTTP.
additional Details
Elapsed time: 24295 ms.
Test steps
Connectivity Analyzer Microsoft is trying to test Autodiscover for [email protected] .
Error in automatic detection test .
additional Details
Elapsed time: 24294 ms.
Test steps
Attempting each method of contacting the Autodiscover service .
Failed to properly contact the Autodiscover service using all methods.
additional Details
Elapsed time: 24294 ms.
Test steps
Trying to prove possible Autodiscover URL https://empresa.com/AutoDiscover/AutoDiscover.xml
Error in testing this potential Autodiscover URL .
additional Details
Elapsed time: 1509 ms.
Test steps
Attempting to resolve the host name in DNS empresa.com .
The host name is resolved correctly .
additional Details
IP addresses returned : 80.36.252.194
Elapsed time: 507 ms.
Testing TCP port 443 on the host to ensure empresa.com listening or is open.
The port was opened successfully.
additional Details
Elapsed time: 464 ms.
Testing the SSL certificate to make sure it is valid.
The SSL certificate is not exceeded one or more certificate validation checks .
additional Details
Elapsed time: 537 ms.
Test steps
Connectivity Analyzer Microsoft is attempting to obtain the SSL certificate from remote server on port 443 empresa.com .
Connectivity Analyzer Microsoft successfully obtained the remote SSL certificate.
additional Details
Remote Certificate Subject : CN = mail.empresa.com , issuer : CN = mail.empresa.com .
Elapsed time: 454 ms.
Validating the certificate name .
The certificate name was validated successfully .
additional Details
Hostname empresa.com was found at the entrance of the alternative subject name of the certificate.
Elapsed time: 1 ms.
Is validating the trusted certificate .
Validation Error trusted certificate.
Test steps
Connectivity Analyzer Microsoft is trying to build certificate chains for certificate CN = mail.empresa.com .
Could not build a certificate chain for the certificate.
Tell me more about this issue and how to resolve
additional Details
The certificate chain did not end in a trusted root . Root = CN = mail.empresa.com
Elapsed time: 31 ms.
Trying to prove possible Autodiscover URL https://autodiscover.empresa.com/AutoDiscover/AutoDiscover.xml
Error in testing this potential Autodiscover URL .
additional Details
Elapsed time: 21723 ms.
Test steps
Attempting to resolve the host name in DNS autodiscover.empresa.com .
The host name is resolved correctly .
additional Details
IP addresses returned : 46.16.56.40
Elapsed time: 498 ms.
Testing TCP port 443 on the host to ensure autodiscover.empresa.com listening or is open.
The specified port is blocked , not listening or does not generate the expected response .
Tell me more about this issue and how to resolve
additional Details
Network Error communicating with the remote host.
Elapsed time: 21224 ms.
Attempting to contact the Autodiscover service with the HTTP redirect method .
Error when trying to contact the Autodiscover HTTP redirect method .
additional Details
Elapsed time: 606 ms.
Test steps
Attempting to resolve the host name in DNS autodiscover.empresa.com .
The host name is resolved correctly .
additional Details
IP addresses returned : 46.16.56.40
Elapsed time: 14 ms .
Testing TCP port 80 on the host to ensure autodiscover.empresa.com listening or is open.
The port was opened successfully.
additional Details
Elapsed time: 202 ms.
Connectivity Analyzer Microsoft is checking the automatic detection of host empresa.com for an HTTP redirect to the Autodiscover service.
Connectivity Analyzer Microsoft could not get a HTTP redirect response for Autodiscover .
additional Details
Web exception occurred because an HTTP 404 response was received - Unknown NotFound . Headers received: Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27:58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 +
lenny3 with Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3 HTTP Response Headers : Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27: 58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 + lenny3 with
Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3
Elapsed time: 388 ms.
Attempting to contact the Autodiscover service using the method of DNS SRV redirect server.
Connectivity Analyzer Microsoft could not contact the Autodiscover service using the DNS SRV redirect method .
additional Details
Elapsed time: 186 ms.
Test steps
Trying to find the SRV record in DNS _autodiscover._tcp.empresa.com .
Not the Autodiscover SRV record in DNS found .
Tell me more about this issue and how to resolve
additional Details
Elapsed time: 186 ms.
Checking for a CNAME record for Autodiscover in DNS for your domain " empresa.com " to Office 365.
Could not validate the Autodiscover CNAME record in DNS. If your mailbox is not in Office 365 , you can ignore this warning.
Tell me more about this issue and how to resolve
additional Details
No Autodiscover CNAME record for your domain ' empresa.com ' .
Elapsed time: 268 ms.
jspt

Hello,
We have the Self-signed certificate that comes with Exchange, and we've created a new self-signed including all our domains mail.company.com, domain.local, exchange13.domain.local, autodiscover.company.com, autodiscover.domain.local.
below I print you the result os the comand Get-ClientAccesServer | fl . Now we've configured a SPC objetct folow the instructions of Wizard
Exchange Server Deployment from Microsoft. We've executed the commands in our new Exchange 13, but can't did it in the old Exchange:
$AutodiscoverHostName = "autodiscover.contoso.com"Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 8*") -And ($_.ServerRole -Like "*ClientAccess*")} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xmlThis is the result of
RunspaceId                           : 89c86f8e-d156-4480-b31d-59215976879b
Name                                 : EXCHANGE13
Fqdn                                 : EXCHANGE13.domain.local
ClientAccessArray                    :
OutlookAnywhereEnabled               : True
AutoDiscoverServiceCN                : EXCHANGE13
AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri       : https://autodiscover.company.com/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope                : {Nombre-predeterminado-primer-sitio}
AlternateServiceAccountConfiguration :
IsOutOfService                       : False
WorkloadManagementPolicy             : DefaultWorkloadManagementPolicy_15.0.825.0
Identity                             : EXCHANGE13
IsValid                              : True
ExchangeVersion                      : 0.1 (8.0.535.0)
DistinguishedName                    : CN=EXCHANGE13,CN=Servers,CN=Exchange Administrative Group
                                       (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=First Organization,CN=Microsoft
                                       Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
Guid                                 : e83055fe-217b-4ed6-9cd0-7711097baf99
ObjectCategory                       : domain.local/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass                          : {top, server, msExchExchangeServer}
WhenChanged                          : 09/03/2014 12:46:07
WhenCreated                          : 08/03/2014 19:15:54
WhenChangedUTC                       : 09/03/2014 11:46:07
WhenCreatedUTC                       : 08/03/2014 18:15:54
OrganizationId                       :
OriginatingServer                    : severdc.domain.local
ObjectState                          : Unchanged
I hope this stuff can help you.
Thanks!!
jspt

Not receiving email from one domain

Hi,
I am running Exchange 2003 on Windows Server 2003 SP2 and suddenly starting having the problem of not receiving mail from one domain. All other domains seem to be fine, although seem slower to receive mail than normal. The sender of the domain in question does not receive any NDR or bounce back error messages, so they are none the wiser the mail has come through. I have checked the junk/spam, I don't have any filters which could be blocking the domain.
Any ideas??
Thanks

Hi,
Please enable the protocol log on SMTP virtual server to check whether the remote domain has attempted to connect to your exchange server to send email to you.
If the remote domain has attempted to connect to your exchange server, please check whether the message is received by the SMTP server. If the message has been received, please use the message tracking log or queue viewer to check whether the message stuck on the server.
If the message is rejected, you can use protocol log to gather further information.
If the remote domain does not attempt to connect to your exchange server, I think you need to work with the remote domain admin regarding the issue as other domains are able to send email to you with no problem.
Mike

Exchange 2013 Allows Room/Resource Double Booking (By Design!)

Since upgrading to Exchange 2013 we have noticed a significant increase in users complaining about room double bookings. After a fair bit of testing we were able to narrow the behaviour down to a reproducible scenario.
First things first - we have AllowConflicts set to false on all room and resource mailboxes, so that is not the issue.
The problem manifests if the start date of a recurring meeting series is more than six months in the past.
This is the scenario which we can reproduce:
Find (or create) a meeting room which is configured to not allow booking conflicts (AllowConflicts:False)
Book one or more meetings in the room (or look for existing meetings)
Create a recurring meeting (or use an existing meeting)
with a start date which is more than six months in the past which will conflict with one or more of the bookings created or found in step 2.
The room will accept all instances of the new recurring meeting, even those which conflict with other bookings.
A variation of the scenario is to extend an existing recurring meeting series:
Find (or create) a meeting room which is configured to not allow booking conflicts (AllowConflicts:False)
Find (or create) a recurring meeting with a start date which is more than six months in the past
and which will end soon.
Book one or more meetings in the room in the same time slot as the recurring meeting
for dates past the end of the recurring meeting series.
Extend the recurring meeting from step 2 past the meetings from step 3.
The room will accept all instances of the extended meeting series, even those which conflict with other bookings.
This is new behaviour in Exchange 2013 - in Exchange 2010 these scenarios worked and Exchange didn't allow double bookings.
We opened a case with Microsoft and were eventually told that this new behaviour is 'by design'. We even appealed to the customer advocacy group and the Exchange product team still refuse to acknowledge this as a bug. As a workaround it
was suggested that we reduce the booking window horizon to 180 days, but this does not resolve the issue.
We are not happy; our users are not happy.
I'm posting here to share our findings with other Exchange users who may be seeing this issue, and to ask you to please share your experience and, if possible, contact Microsoft so that the product group might reconsider their position on this behaviour.
Ben Lye

So it seems like I should have been a little clearer - the scenarios above are for reproduction. I know that nobody normally creates a recurring meeting with the start date in the past - that step was just to emulate an existing meeting which was created
more than six months ago.
The current explanation from Microsoft is that Exchange 2013 only checks the first six months of a recurring meeting series for conflicts, so another way to encounter (or reproduce) this issue is this:
Find (or create) a meeting room which is configured to not allow booking conflicts (AllowConflicts:False)
Book a new recurring meeting which starts today and has an end date at least six months in the future.
Create a new single meeting instance in the same time slot as the recurring meeting, but after the end of the recurring meeting series.
Extend the meeting series beyond the date of the single meeting instance
The room will accept the update to the series and the room will be double booked.
Ben

Exchange 2013 (lab): emails stuck in OWA Drafts

Hello I have setup for testing purposes an Exchange 2013 CU5 on a 2012R2 which is also DC and DNS.Network wise I have two virtual interfaces one for the internal network (10.10.10.x/24) and another one linked to the Ethernet physical interface of my computer
which gets its properties from DHCP (usually my gateway router).
Everything seem to work normally but when I try to send emails to the outside world I only get a copy of it inside the Drafts folder. :-)
I thoroughly checked the DNS service (inside the Exchange too), A, PTR records and SOA, I tested the DNS server and nslookuped some internet addresses all resolving fine.The DNS service registers both interfaces DNS servers (the internal one which
is the DC and the external one which comes through DHCP).
Through Test-ServiceHealth in Exchange Management Shell I checked all required services are up and running.
With Setspn -L hostname I verified all required services are registered correctly on my server.
I also checked Event Viewer and besides some performance counters errors about exchange nothing else in there too.
I haven't registered an MX record because I don't need to receive mail just to send in that early stage.Am I right in that?
Any ideas are welcome and thanks in advance.

When you see this piling up in drafts, it is not even making it to transport.
OWA sends mail via drafts folder. So can you please restart the "Microsoft Exchange Mailbox Transport Submission" service and see what happens.
This is also a very bizarre setup. DCs do not normally have multiple interfaces, and while Exchange is supported on a DC (apart from DAG) its still not recommended.
You probably want to simplify this as you troubleshoot - can you remove the internal interface from the test box, and clean up DNS and host files etc.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

No receiving and sending emails from ceratin domain

Hi,
There is something funny with my Exchange 2007.
I cann't niether send or receive emails from 2 external domains. I have no problem receiving from any other one.
Please,
Any help will be appreciated.
Thank you

Hi Alkealkel,
Would you please let me confirm whether it’s SBS 2008 domain environment?
Based on your description, it’s hard to narrow down the root cause of this issue. Would you please let me know
more details? Those may help us to go further analyze.
à
I cann't niether send or receive emails from 2 external domains.
Did you get any error message when find that be unable to send or receive emails from certain external domains?
In addition, please run
Exchange BPA and
SBS BPA, then check if find some relevant issues.
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Exchange 2013 mailbox migration from third party cloud to on premises

Hi,
we are currently utilizing a third party exchange 2013 cloud service to host user's mailboxes ( intermedia), now we implemented an exchange 2013 on-premises environment in Hyper V infrastructure and want to plan migration of mailboxes and related configuration.
cloud and on-premises environment have same SMTP domain ( Eg: XYZ.ORG) and currently an additional Temporary SMTP domain ( XYZ.CO ) used to test the external mailflow of on-premises since xyz.org is registered with cloud.
we need to migrate all mailboxes to on premises and enable XYZ.ORG for on-premises.
Pls suggest the prerequisites,steps, best practices for migration
Thanks in advance.

Hi Sumesh,
1. Please make sure your mails are flowing correctly using XYZ.CO domain. Hope you have XYZ.ORG also created in Exchange.
2. Hope you already created the users in your Exchange2013 server and distribution groups for current users
3. You plan a weekend for changing your MX records.
4. Change MX and A records to a lower TTL days before the migration to decrease DNS update time on migration day
5. Export Hosted Exchange data for each user to PST files using the PST capture tool and move your PSTs to a centralized location.
6. Change MX and A records to point to on-premises Exchange 2013
7. Import Hosted Exchange data from PST files into the new Exchange profiles
Please check these as well
http://community.office365.com/en-us/b/office_365_community_blog/archive/2011/08/15/exchange-hybrid-configuration-tips-moving-cloud-based-mailboxes-to-the-on-premises-organization.aspx
http://technet.microsoft.com/en-us/library/hh781036(v=exchg.141).aspx
http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/microsoft-pst-capture-tool-part1.html
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2013 Servers booting from SAN

Hi,
One of my client has decided to go with NetApp Flexpods for implementing Exchange 2013 in their environment.
It has also been decided that these servers will boot from SAN and
Exchange 2013 will also be installed on SAN.
We are planning to Install Win 2012 R2 for OS and E2k13 CU8. Few questions:
1) Is it supported to boot Windows Server 2012 R2 from SAN, Specially if that server is going to used for E2k13
2) Is it supported to Install Exchange 2013 CU8 on SAN
I researched about this and understood that this is supported from Windows OS perspective. I am more concerned about the whole configuration falling within support boundary of Exchange 2013. I found an article which talks about the complexity involved in
troubleshooting and indicates that its mainly SAN vendor who would be troubleshooting if running into any issues.
https://support.microsoft.com/en-us/kb/305547- This article is not yet applicable to 2012 R2. Its applicable only till 2008 R2.
http://www.enterprisenetworkingplanet.com/datacenter/the-pros-cons-of-booting-from-san.html - Pro & Cons of booting from SAN
The booting from SAN for Exchange servers concerns me a lot as i have never seen any implementation in Exchange 2003, 2007 & 2010 doing this in my 10 years of experience. I have supported about 10 different enterprise exchange deployments and never saw
this. So this is an unknown territory for me, hence looking for some best practices, articles and guidance around this if its supported by Microsoft Exchange team to run Windows and Exchange from SAN.
Thanks
Siva

Hello,
Please see the “Supported storage architectures” in the following article:
https://technet.microsoft.com/en-us/library/ee832792%28v=exchg.150%29.aspx
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2013 allowing emails from spoofed domains

Similar Messages

Maybe you are looking for