m4rk Posted November 1, 2022 Posted November 1, 2022 Hi All, I know i am missing something within Office 365 and authentication to FMS and our printers scan to email. With the depreciation of one of the Office 365 basic authentication. I have on the user account Authenticated SMTP ticked and the account itself works when you login and send mail but not via our printers scan to email function nor FMS and it automatically sending the messages. My brain keeps leading me in circles so any advice would be great. Thanks mark
chaplic Posted November 1, 2022 Posted November 1, 2022 (edited) You also need to enable the mailbox for SMTP send Get-CASMailbox mailboxname | ft SmtpClientAuthenticationDisabled will show current setting, note the double negative. When you say it works when you login and send, how exactly? Suggest testing with a powershell script that will be closer to what the MFD is doing # Get the credential $credential = Get-Credential ## Define the Send-MailMessage parameters $mailParams = @{ SmtpServer = 'smtp.office365.com' Port = '587' # or '25' if not using TLS UseSSL = $true ## or not if using non-TLS Credential = $credential From = 'Noreply-Cloudprint@yourorg' To = 'chaplic@yourorg' Subject = "SMTP Client Submission - $(Get-Date -Format g)" Body = 'This is a test email using SMTP Client Submission' DeliveryNotificationOption = 'OnFailure', 'OnSuccess' } ## Send the message Send-MailMessage @MailParams Edited November 1, 2022 by chaplic CRLF 2
m4rk Posted November 1, 2022 Author Posted November 1, 2022 I can log into 365 as the user account and send mail directly. Checked using Powershell and the flag is showing False, so it should be enabled correct?
chaplic Posted November 1, 2022 Posted November 1, 2022 Sending as user in webmail is not the same as sending as user using SMTP. If smtpClientAuthenticationDisabled is set to False then we should be good. (Clearly the program manager worked on group policy in a previous life) What happens when you send an email using the powershell script ? (alse note [MENTION=96984]Mail[/MENTION] should be @ m a i l p a r a m s without spaces. Once that fails, visit the Azure AD logs and look for the sign in attempt related to the powershell, it may show a conditional access fail. 1
gaz350b Posted November 1, 2022 Posted November 1, 2022 Look at configuring a connector in There you should be able to whitelist your network. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now