This content has been marked as final. Show 2 replies
The problem you will have here Trey is that a decent Exchange/Mail environment wont allow just any random connection to send email. Unless the Exchange admin is willing to unsecure their mail server by adding an SMTP exception for everyone internally, it wont work by default.
Great point Bryan. I forgot to mention the pre-req. With my customer yesterday we ran the custom action with a service account. This is important because as Bryan mentions 1 of 2 things needs to be in place to send the emails with a PowerShell custom action:
"Send-MailMessage uses authenticated SMTP connections. By default it will use the credentials of the user executing the command. So you need to make sure you’re using an SMTP server that either:
• Permits that authenticated user credential to send email messages via SMTP
• Accepts anonymous SMTP/relay for the IP address of the sending host (you can see how to configure a relay connector for Exchange here<http://exchangeserverpro.com/how-to-configure-a-relay-connector-for-exchange-server-2010>)"