Problem Configuring Email Alerts with File Server Resource Manager 2012

I am trying to configure the File Resource Manager to send me email notifications when quotas are hit and so forth.  I have configured the Email Notifications tab as follows:

SMTP Server Name: exchange.ad.mydomain.com
Default Administrator Recipient: administrator@mydomain.com
Default "From" email address: fileserver@mydomain.com

When I try to send the test email I get the following error:

"Failed to send the test email due to the following error: Cannot send the email due to an error.  Check the application event log for more information."

Upon checking the event log, I see the following:

"The SMTP server requires a secure connection or the client was not authenticated.  The server response was 5.7.1. Client was not authenticated."

Upon my research, the server needs the Send-As privileges on the user account.  With that said, I created a user account "svc_FSRM" and ran the following powershell command:

Add-ADPermission -Identity “svc_FSRM” –user “ad.mydomain.com\fileserver$” -ExtendedRights “Send-as”

When I go into the Exchange ECP and access the svc_FSRM user account, under mail delegation section "fileserver" is listed under the "Send As" section.

Unfortunately, when I try to send the test email again from File Server Resource Manager....I am still given the same error as before.  For the life of me, I cannot seem to figure out why the test message will not come through.  Any thoughts?
csimmons1324IT ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

RantCanSr. Systems AdministratorCommented:
Allow anonymous authentication on the receive connector.
0
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
In order for this to work, the logged on user must be svc_farm.  Best way for things such as this (as well as any future monitoring/alerting), what you should do is to use an IIS server for mail relay and lock it down by IP address.  Create a remote domain pointing to your Exchange server and forward all messages to your CAS server.  Just ensure to configure CAS server to accept messages from the IIS server.  This way, you are not making changes to Exchange and you can control very easily as to what machines can relay messages.
0
csimmons1324IT ManagerAuthor Commented:
I forgot to mention that I am using Server 2012 R2 and Exchange 2013 which are both run in-house.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
I think the issue is that you are specifying the computer name as the username which will not work.  Try it with a username.
0
csimmons1324IT ManagerAuthor Commented:
Mohammed,

From what I have read, FSRM attempts to send the email using the computer account.  For this reason, the computer account needs to be granted "Send-As" permissions on the mailbox that is used in the "FROM" email address.
0
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
I have a suggestion and that is to create a new/separate SMTP connection which will be used by FSRM only.  To do this, you could run the powershell listed below:

new-receiveconnector -FSRMmail -usage custome -bindings y.y.y.y:25 -remoteIPranges x.x.x.x -authmechanism basicauth -permissiongroup anonymous

y.y.y.y would be the IP of the SMTP server (your Exchange server) and x.x.x.x would be the IP of the FSRM.  Later on you could add more IPs to the allowed relay list.
0
csimmons1324IT ManagerAuthor Commented:
I had to enable "Exchange Users" on the Send Connector to resolve the problem.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
csimmons1324IT ManagerAuthor Commented:
I discovered the solution on my own.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.