Closed stalhaw closed 5 years ago
Yes. Our solution supports SMTP clients. We have provided detailed documentation for setting up Office 365 accounts in our documentation available at aka.ms/laas.
Hi Elton, I did followed the documentation you pointed above and also the video 2 in which you have explained it but somehow I am not able to get it through. I exactly did what you have told. Those parameters including the smtp.office365.com 587 for the port Notifications@domain.com Distribution list for the clusteradminemail the smtp auth user and pass And the enrollments@domain.com as platformemail Similar to what is documented in the guide. Am I missing something? And as you told its really important to have emails working and you get all the notification emails for the deployment stages for the successful deployment and emails properly function afterwards Appreciate your kind help.
But in the video 2 you were talking about the smtp relay service. So it looks contradictory to me. https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-office-3#option-3-configure-a-connector-to-send-mail-using-office-365-smtp-relay
Also does this have to to do anything with the ssl certificate names we have for the TM endpoints
No, TM has no relationship with the smtp email relay. This is what you need. Check the SSMTP logs for the specific error message.
OK I will look for the ssmtp logs on the vmss
These are the excerpts from logs which repeats several times.
Unable to set TLS_CA_File="/etc/ssl/certs/ca-certificates.crt" /var/log/syslog:Feb 14 23:17:05 LaaSvmss000000 sSMTP[16632]: Creating SSL connection to host /var/log/syslog:Feb 14 23:17:05 LaaSvmss000000 sSMTP[16632]: SSL connection using ECDHE_RSA_AES_256_GCM_SHA384 /var/log/syslog:Feb 14 23:17:13 LaaSvmss000000 sSMTP[16632]: 554 5.2.0 STOREDRV.Submission.Exception:InvalidRecipientsException; Failed to process message due to a permanent exception with message Recipient "root" isn't resolved. All recipients must be resolved before a message can be submitted. InvalidRecipientsException: Recipient "root" isn't resolved. All recipients must be resolved before a message can be submitted. [Hostname=BN8PR16MB2868.namprd16.prod.outlook.com]
Could you point me to something. Why isn't root resolving. I tried to use ssmtp and I could receive the email from there if I used the ssmtp from the shell
Normal SSMTP troubleshooting would apply here. Is the "Unable to set TLS" related to a missing cert? If you can successfully send a message and receive it from cmdline, the application should work.
I think the same. But I didn't received any deployment emails so I did wanted to confirm if there could be something wrong. And would we be able to send the emails afterwards. Right which certificate is this one. We only had the ssl certs for the endpoints.
Our basic "smoke test" of operational email settings is getting deployment notifications. The deployment notification system uses cmdline configurations to send progress updates related to the deployment. If it doesn't work, that generally means the email configuration has problems. For additional troubleshooting, all linux & ssmtp administration apply. There isn't anything custom on our side for this.
Given this isn't an issue related to the code, i am closing it.
Unable to get any deployment emails although I am able to connect to the traffic manager endpoints successfully. Could you please let me know if this supports the smtp client submission as the settings that were suggested in the deployment guide looks similar to that. And if we are using the connector on office 365 end for the relay what should I put in the IP address from where the email would be relayed to office 365 as we don't have that in advance unless we have the deployment started. Please let me know how to go about this. And what can be done for this. Thank you in advance