Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

After migration to MSS2010, we realized that the alerts, that we used to send to a distribution group in our company, do not work. There was an option to create alert for the group (e. g. group_all), assign an e-mail to the group and add permissions for this group to the web site and the alerts started working. When I do that in Sharepoint 2010, nothing is sent, not even the initial e-mail.

share|improve this question
add comment

3 Answers 3

Were any other changes made outside of SharePoint? I know Exchange has an option to set distribution groups to only be available for use by "authenticated or trusted senders" (this prevents email/spam from the internet from being sent to internal distro groups). We ran into this problem, because SharePoint does not "authenticate" to the Exchange server, it is not, by default, trusted/authenticated.

share|improve this answer
    
Kudos to lwbecker2. Going into the distribution group properties and unchecking "Require that all senders are authenticated" resolved this issue for me. Thanks! –  user6259 Jan 4 '12 at 16:47
    
@Byron: Don't forget to upvote an answer that is helpful to you! –  Kit Menke Jan 4 '12 at 19:20
    
This also helped me! Thanks @lwbecker2 –  Mike Apr 20 '12 at 18:49
add comment

Sending SharePoint 2010 alerts to an Exchange distribution list.

  1. Create the distribution list/group in Active Directory and assign an email address. Do not use any dashes "-" in the group name.
  2. Edit the properties of the group to change its Group Type to Security (from Distribution). Make sure the group is a Universal group. Only security groups show up in SharePoint's address book. They show up as "domain groups" in SharePoint.
  3. Give the domain group at least visitor permissions on the list that are you are creating the alerts for in SharePoint. Alerts won't be sent if the domain group doesn't have appropriate permissions.
  4. Then setup the alert and use the address book to locate the domain group.
  5. Test out your alerts. If you have "require approval" turned on for the list, make sure you approve the items so alerts will be sent.
share|improve this answer
    
MJams, Let's say I set up an alert on a distribution group, not knowing that. If I add the SharePoint permission to the list at a later time, would that work? Or would I have to re-do the alert altogether? –  Matt Apr 26 '12 at 20:49
add comment

Did you check the outgoing email settings to be sure that they migrated? Also, is the timer job started?

share|improve this answer
    
Yes, of course. Other alerts work normally. Thanks anyway :) –  user1667 Dec 22 '10 at 8:45
    
Ravie-thanks for not being offended that I started with a simple response. :). I wasn't sure how experienced you are. Other things I have seen are the emails getting stopped by antivirus or spam filter. Since other emails work, I doubt this is the case unless the spam filter recognizes it as a bulk email. Do the ULS logs or Windows Event Viewer shed additional light? Also, search for my responses that mention SMTP4DEV and see if that tool will help you debug where the disconnect is. –  Rob Wilson Dec 22 '10 at 15:31
    
No problem :). I have some experience with Sharepoint (5 years), but this problem is still a mystery to me. I thought that if the user has an e-mail, permissions and also other alerts work normally, it should work as well. The only difference is that this "user" is an e-mail enabled security group, which should not make any difference if the group is a site member. The cols in EventLog and EventCache seem fine. TestSMTP works. I will try SMTP4DEV. –  user1667 Jan 27 '11 at 10:10
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.