• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 610
  • Last Modified:

Exchange 2010 send connector being ignored

We created a send connector for a sharepoint 2013 farm for the requirement of supporting incoming email for a sharepoint 2013 farm and for some reason all emails sent by the sharepoint server are being relayed through exchange server rather than the sharepoint farm. I have found numerous articles on building a send connector and have created the connector many times but still with no success. I have even followed this article using the send connector for exchange ONLY and still no success http://digitalmacgyver.wordpress.com/2013/04/22/step-by-step-guide-in-configuring-incoming-email-in-sharepoint-2010-with-exchange/

What I found strange was in creating send connectors in the past at least a queue would be appear in the toolbox section of the exchange queue viewer. This apparently does not show up but understand that email queues are persistent and close if not used. Logging directly into the sharepoint server where smtp is installed when trying to send via command line powershell we receive an unable to mail relay 5.7.1 error message using a fake user. I understand that sharepoint can send email two ways. One by AD/EXCHANGE and the other without a mailbox but pointed to a document library. Please help if you can thanks
0
techdrive
Asked:
techdrive
  • 2
2 Solutions
 
Peter HutchisonSenior Network Systems SpecialistCommented:
Do you have any details of how you setup the send connector?
Address space, source servers, network addresses etc.
0
 
techdriveAuthor Commented:
Yes I do the address space would reveal the company so lets use the following

address space=servername.contoso.com
source servers= exchange servers in our environment
network addreses= sharepoint smart host ip address
0
 
Simon Butler (Sembee)ConsultantCommented:
Ensure that the Cost for all other connectors are set to 2, and the cost of this specific one is set to 1. Then restart the transport service.

Simon.
0
 
techdriveAuthor Commented:
It was two things. I ended up creating a MX record pointing toward the host and making a fake domain something.something.com and that worked with the send connector to sharepoint, thanks
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now