Jump to content
accfanz

Office 365 migration

Recommended Posts

I am migrating from Exchange to O365  and am testing mailit using the supplied EmailClient Filemaker database provided. I get the following error. 

530 5.7.57 SMTP; Client was not authenticated to send anonymous mail during MAIL FROM [BN6PR1001CA0036.namprd10.prod.outlook.com]

Is this 365 related or plugin related?

Edited by accfanz

Share this post


Link to post
Share on other sites

This is an error back from the server.

Microsoft gives this explanation of the error:

Quote

This indicates that you are connecting to the SMTP client submission endpoint (smtp.office365.com), which can't be used for direct send. For direct send, use the MX endpoint for your Office 365 tenant, which ends with "mail.protection.outlook.com." You can find your MX endpoint by following the steps here.

It typically means that you authenticated with one account in the EmailConnectSMTP function but set the From address to another account in EmailCreate which is not allowed. You may be able to configure Office365 to allow this but I cannot tell you how to do so. 

Share this post


Link to post
Share on other sites
Posted (edited)

I am also running into this issue and believe I have it set up correctly. 

EmailConnectSMTP Username: globals_USERS::Email

EmailCreate From: globals_USERS::Name_Full & "<" & globals_USERS::Email & ">"

Could it be because I'm adding the full name? I thought that was a suggested way to do it to avoid being put in a spam filter.

Additionally (only because it's tangentially related) I do have EmailConnectIMAP disabled. Don't think that's relevant but felt like I should mention it. 

 

Update: FWIW I just checked my plugin version and I'm on 3.1 while the machines that are unable to send are on 3.3.

Update 2: If I log in as one of the affected users I get the same error on my machine as well. So it's not plugin version, it's account related. 

Update 3: I'm a dope. I didn't migrate passwords to the new file this error was happening in. I will say microsoft's error was pretty bad. I only realized because I re-enabled IMAP and that kicked a password error. 

Edited by MileFaker3000

Share this post


Link to post
Share on other sites

I would strongly encourage you to start using the Office 365 APIs for this kind of integration.  I have a series of blog posts coming up that walk you through the setup.  These APIs are a lot more powerful than talking to the old-style protocols like SMTP, POP, IMAP,...

Share this post


Link to post
Share on other sites
On 3/3/2020 at 8:27 AM, Wim Decorte said:

I would strongly encourage you to start using the Office 365 APIs for this kind of integration.  I have a series of blog posts coming up that walk you through the setup.  These APIs are a lot more powerful than talking to the old-style protocols like SMTP, POP, IMAP,...

Have the blog posts with this information been released?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.