Successfully pulled token and authenticated, can't resolve SMTP recipient

Xeph

With the graph endpoint I can get an auth token, but can't authenticate.

I was able to get OAuth2 token and authentication using the older outlook resource details endpoint. With that set up I am able to fetch emails and it generates tickets! But I can't send. SMTP still throws this:

Unable to email via SMTP: ticketing@mydomain.com (smtp.office365.com:587) 5.2.0 STOREDRV.Submission.Exception:InvalidRecipientsException; Failed to process message due to a permanent exception with message [BeginDiagnosticData]Recipient ' MyLastName' is not resolved. All recipients must be resolved before a message can be submitted. InvalidRecipientsException: Recipient ' MyLastName' is not resolved. All recipients must be resolved before a message can be submitted.[EndDiagnosticData] [Hostname=xxx.prod.outlook.com]

I'd assume some kind of permission error? Like it can't read and resolve the name?

Daedalus01

Xeph Depends. Check the recipient in AD to make sure that they actually have something in the Last Name column. You can create accounts with only a Firstname. For Instance, I have a test account named "Bob" that doesnt have a last name or an email address and I would guess that I might get the same error if I was trying to send an email to "Bob".

Xeph

Daedalus01 - The recipient is me. The "MyLastName" in the post above is my actual last name. All of our users have both first and last names defined in their AD objects. My last name is pretty unique so I'd imagine it should be able to resolve to my email address, but I must be missing something.

Daedalus01

Xeph Sorry I couldn't be of more help. I was just guessing. Maybe someone else on here or one of the wizards that helped create this can help.

Xeph

Daedalus01 I appreciate it!

Something else to add. If I use the diagnostic tool and send from the account I have set up using OAuth2 it does send properly. It's just not sending properly on the ticket activities.

Daedalus01

Xeph Ok. Just another guess. There is a space here in the error message before MyLastName.

Recipient ' MyLastName'

I am not sure if that is just how the error message generates or if there is an accidental space in the lastname field and O365 doesn't know how to handle it and errors out.

edit--- Also, is it everyone that is being affected or just you?

Xeph

Daedalus01 It's affecting everyone. I noticed the thing with the extra space, too. It's like it's grabbing the wrong attribute or something.

Xeph

Ayyy I just got the email a bit ago about the 1.17 stable release. So I downloaded that and installed it. It works!!