I am attempting to set up a subscription on my report server that will send out an email to a outlook email group. However when I specify the group in the To: field on the report server I get the following email in response when the subscription is actually ran. Your message did not reach some or all of the intended recipients. Subject: Report was executed at 4/20/2011 9:39:02 AM Sent: 4/20/2011 9:39 AM The following recipient(s) cannot be reached Outlook Email Group on 4/20/2011 9:39 AM You do not have permission to send to this recipient. For assistance, contact your system administrator. <exchange server> However, when I change the TO: to include members of that group they receive the emails fine. My question is, is it possible to specify out email group names in the TO: field of a report server subscription or do you have to put all of the individual email addresses of the members of that group in there for it to work? One of the responses that I got so far was: Consider that the Report Processor "logs on" with specific credentials. This is the Service Account. Try to open a Windows Session using these credentials and send the mail. I expect it will fail. Make sure this account has group-send rights. Is this correct and if so should I be consulting with our exchange server admin to get group send rights added and to which user account? Greg Lorenz

Hi GregPLS, According to your description, my understanding is that, you would like to type group account or user account in TO: fields instead of putting e-mail address when create a subscription, right? Please correct me if my understanding is wrong. If you are using Windows Server 2003, you can user an alias instead of an e-mail address. This operation system resolves the correct e-mail address automatically. However, you must use an e-mail address if you are using Windows Vista or Windows Server 008, because neither of these operation systems performs the same type of alias resolution as windows server 2003. Moreover, if you have any concern about this, please submit a feedback at http://connect.microsoft.com/SQLServer/Feedback and hope Microsoft improve this feature in the next service pack or product release. If you have any question, please feel free to ask. Thanks, Eileen