Solved

unable to send email for exchange 2010 users after exchange 2013 installation

Posted on 2014-03-03
6
839 Views
Last Modified: 2014-03-04
Unable to send email for exchange 2010 users after exchange 2013 installation.  

Only users created in exchange 2013 after the installation of Exchange 2013 can send emails out.

Everyone can receive.

I've tried to add the new Exchange 2013 (all roles installed including cas)  to the send connector.  I've tried to switch server in the nat rule in the firewall.  I've tried smarthost.

Users that have their mailbox in Exchange 2010 are no longer able to send emails

Thanks for your help
0
Comment
Question by:quadrumane
[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
  • 3
  • 3
6 Comments
 
LVL 8

Expert Comment

by:Lee Ingalls
ID: 39900761
Can you receive external email?
0
 

Author Comment

by:quadrumane
ID: 39900778
yes

It's very confusing.  We never had this problem during the previous Exchange 2010 to Exchange 2013 migration.  

Usually Exchange 2010 doesn't really care when a new Exchange 2013 is installed.    

We're not ready to move all users to the new Exchange 2013.  But as I said the user created in Exchange 2013 can send and receive.  All user mailboxes stored in Exchange 2010 can still receive, but users are unable to send out any email.
0
 
LVL 8

Expert Comment

by:Lee Ingalls
ID: 39900788
Sorry, I re-read and saw that you were receiving? Are you receiving both internal and external messages? What's happening to Sent mail? Going to Drafts for internal? Any bounce messages from external? Were you using Receive Connectors previously?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 

Author Comment

by:quadrumane
ID: 39900803
Ok yes I see that all the email I'm trying to send are going to drafts, internal and external.
0
 
LVL 8

Accepted Solution

by:
Lee Ingalls earned 500 total points
ID: 39900869
Any DNS changes?
http://thoughtsofanidlemind.com/2013/03/25/exchange-2013-dns-stuck-messages/

Make sure OS and Outlook/Office are patched to current.
Do the 2010 Outlook clients have a second mailbox? Try removing and re-adding second mailbox.
http://social.technet.microsoft.com/Forums/en-US/24d3c7ff-6378-4086-a035-dfa9ecea46bb/exchange-2013-issues-new-send-email-stuck-in-drafts-not-send?forum=exchangesvrsecuremessaging

I used these two links to resolve my similar issue.
0
 

Author Comment

by:quadrumane
ID: 39905097
DNS indeed,  thanks a lot
0

Featured Post

Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
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
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question