Sharepoint Foundation 2010 - Problems sending email thru Exchange 2007 from Sharepoint site

Here's my set up:

Sharepoint Foundation 2010
Exchange Server 2007
Windows Server 2008

A system-generated email is sent okay when creating a new Farm Administrator in Central Administration, but when creating a new Member on our Team Site, I get the following error:

The user or users have been added successfully, but there was an error in sending the e-mail message. The server may not be set up correctly to send e-mail. To verify that e-mail is configured correctly, contact your server administrator.

Here is what I've tried:

1. Creating a new Receive Connector as described at http://sharepointgeorge.com/2010/configuring-outgoing-email-sharepoint-2010/
2. Checked settings at Central Administration > Web Applications > General Settings > Outgoing Email: Have tried both the IP address for my Exchange/Sharepoint server (e.g. 10.1.10.11) and my regular mail.xxxx.com smtp address with the same results.
3. Checked settings at Central Administration > System Settings > Configure outgoing e-mail settings: Have tried both the IP address for my Exchange/Sharepoint server (e.g. 10.1.10.11) and my regular mail.xxxx.com smtp address with the same results.
4. Confirmed that I can connect to my Exchange server using telnet

As I said, email from the main admin page (Central Administration) seems to work fine, but it doesn't work when setting up users on my Team Site. Exchange server works fine for our corporate email--it just doesn't seem to work with the Sharepoint team site.

I've run across advice to check Exchange logs, but have no idea where to start.

Any ideas?

Thanks,
John


jscifersAsked:
Who is Participating?
 
mossliveCommented:
Hi,

regarding the relay you should check this blog post by the exchange team:
http://msexchangeteam.com/archive/2006/12/28/432013.aspx

SharePoint needs relay permissions to send mails to users outside your organization.

Despite the fact that ou shouldn't use your user accountas service account ;-) the configuration seems ok (assuming you were able to do the telnet check with that user as well).

Do you get th error message even when adding an internal user?

/Daniel
0
 
mossliveCommented:
Hi,

did you try to send an email using telnet?
If not, try to send an email using telnet (http://exchange.mvps.org/smtp_frames.htm) to one of the users causing the error message. This might give you a starting point.

Are your users all located within the same Exchange?
(Exchange will only be able to sen emails to users of its own organization, due to relaying restrictions)

Which users are configured on your AppPools (Central Admin AppPool and WebApp AppPool)?
(maybe the WebApp AppPool user cannot send mails)

/Daniel
0
 
jscifersAuthor Commented:
Thanks for the feedback!

Sending email to an external user using telnet produces an "Unable to Relay 5.7.1" error when I use the "rcpt to: <external address>" command with any external email address. Sending mail via telnet works fine when using an internal address (e.g. "name@mydomain.com").

Yes, all users are located in the same Exchange server.

Regarding App pools, I do have a Security warning ("Accounts used by application pools or service identities are in the local machine Administrators group."), but I'm not sure whether this is related. Browsing to http://mydomain:45400/_admin/FarmCredentialManagement.aspx, I have the following service accounts set up:

Farm Account: sadmin
Windows Service - Claims to Windows Token Service: Local System
Windows Service - MS SharePoint Foundation Sandboxed Code Service: sadmin
Windows Service - SharePoint Foundation Search: jscifers
[All] Web Application Pools (41782, 80, site1, site 2): jscifers
Service Application Pool - SecurityTokenServiceApplicationPool: sadmin
Service Application Pool - SharePoint Web Services Default: sadmin
Service Application Pool - SharePoint Web Services System: sadmin

jscifers is my account and has Admin priviledges. sadmin was an admin account i set up for Sharepoint.

Any thoughts?
0
 
jscifersAuthor Commented:
Ah, fixing the relay issue solved the problem!

After running the following command, the problem went away:

Get-ReceiveConnector "CRM Application" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Any-Recipient"

THANKS!

John
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.