I just set up a standlone SPS2013 installation on a Server 2012 Standard box.
I have outgoing email settings configured and for the most part, those are working. Alerts to documents and lists are received. And when someone is “followed,” those emails are sent and received as well. However, email notifications for newsfeeds are never received.
I found a few mentions of this on the MS Technet forums and the suggested fixes in those instances were a.) an additional MX record for SharePoint and b.) authentication methods settings for the send connector on the Exchange server. In both cases, the details were very sketchy and I’m not sure it applies in this case anyway.
Anyone have any ideas? Maybe a symptom of the limitations in a standalone enviroment? I know the User Syncronization server isn’t the same as in a Farm Envirnoment…
Thanks in advance for any comments.
Wayne
Hi
This issue has plagued me for a few hours on an otherwise sucessful SharePoint 2013 implementation. I thought is was an issue with persmissions on notifciation timer job.
I ran the PS test and immediately received an email – However I will instruct IT to follow the steps mentioned inc the important “enable annomous users ” bit .
Will report back.
I was also able to get the alerts to work by creating a second receive connector on our Exchange server for the specific IP addresses of our servers. The Anonymous permissions is important!
Stephen, thanks for your replies. I apologize for not following up, my emails from @sharepoint-community.net were caught in our Junk Mail filter and I just now realized that someone had replied to my post.
I was thinking it was a limitation of my ‘standalone’ environment, so I’m in the process of creating a virtual farm (this is a back burner project for us at this point.)
I’ll review your steps thoroughly and post back to the community ASAP. Again, thanks so much for your effort!
Ok so I tried again with adding in a receive connector to exchange. Â
I followed this guide
I created it specifically for my environment by adding in all the IP addresses of the machine and NLB that are allowed to send emails. I left the local IP addresses that can receive email to all (default).
I then enabled anonymous users on the receiver under the Permission group tab  Left it for a bit and then tested. Â
Tested by @mentioning a user and running the daily notification job, It works now which is good but I’m still not 100% sure why it’s even needed. Â
I’m beginning to think the Mailbox unavailable message is misleading and it’s perhaps a limitation of which ever method SharePoint is using to send those emails.
On a side note I’m also getting the welcome email SharePoint send when you first create a MySite (never got that before).
I hope this helps someone else or maybe someone else will be able to shed a bit more light on the reasoning behind it.
Cheers
Stephen
Hi Wayne I’m having the same problem too.
I’m not sure exactly what causes it but I can guess that normal alert email are using the sp utility mechanism to send emails and for some reason the newsfeed notification are using direct smpt.
First thing to do is make sure your email is relaying through exchange. Â On which ever server is running your timer jobs run the following powershell command to send a test email:
$smtp = New-Object Net.Mail.SmtpClient("ho-ex2010-caht1.exchangeserverpro.net")
$smtp.Send("reports@exchangeserverpro.net","administrator@exchangeserverpro.net","Test Email","This is a test")
Source
If you get an email then you are relaying if not you will need to add a receive connector in exchange to allow your servers IP addresses to send emails.
I followed this guide
Here are the things I’ve tried which aren’t working for me:
I came accross a post about a bamboo solutions alert product not working
http://community.bamboosolutions.com/forums/t/32333.aspx
Basically the error I’m getting in the logs is:
System.Net.Mail.SmtpException: Mailbox unavailable. The server response was: 5.7.1 Client does not have permissions to send as this sender
So I gave the Farm account which is running the timer jobs a mailbox, restarted the timer service even all machines in the farm but still didn’t work.
I gave everyone send permissions on that mailbox but again still didn’t work.
Next I gave the app pool that was running MySItes a mailbox in case that was the problem and again nope didn’t workÂ
So I gave up and created a new receive connector in exchange but that hasn’t worked either so I’m back to sq 1.
I’ve been looking into this since yesterday so might give it the weekend before i take another look.
On a side note I’ve never had to give the farm account a mailbox in any other setups I’ve done so this is pretty strange. Â Also because emails relay from my farm there is really no need for the connector or MX record, it’s got to be something else.
I will keep you posted if I manage to get it working, you could try the things i have done as one might work for you.
Cheers
Stephen
