Does the 1.17.x OAUth2 change affect outbound aliases?

Codewow

When I setup 1.16.3 I was able to get outbound aliases working almost instantly. (Had to wait for exchange to propagate)

But upgrading to 1.17.2 seems to change things. I have enabled header spoofing on the email and configured OAuth2 for the mailbox. But outbound emails still come from the system email. No logs stating there was an error while trying to send as the alias or anything. My exchange settings are configured to enable aliases and I can confirm it works with

Is there something else that needs to be setup?

KevinTheJedi

Codewow

Are you talking about sending on behalf of another email or send as another email?

Cheers.

Codewow

KevinTheJedi

This is an alias on an email. I have customerservice@
and partnername@ as an alias of customerservice@

When attempting to send an email out (Registered in OSTicket as a second mailbox/email, but only configured for outbound smtp) the outbound still uses customerservice@ when partnername@ was selected to be used as the reply address.

KevinTheJedi

Codewow

We fixed this in the subsequent maintenance releases and have no problems with this in our hosted platform. Maybe you need to enable "send as" permissions for the real email on the alias?

Cheers.

Codewow

KevinTheJedi

"Maintenance releases" as in the github dev branch?

There's no way to add a "Send as" permission because it's the same mailbox.

KevinTheJedi

Codewow

I mean v1.17.1 and v1.17.2. We call v1.17 a major release and then any subsequent minor versions we call maintenance and/or security releases.

I see, well how do you have the email config setup?

Cheers.

Codewow

KevinTheJedi

Not sure which side of the configuration you're asking about.

On OSTicket:

On exchange:

KevinTheJedi

Codewow

Okay, what does your Admin Panel > Emails > Settings look like? And what are the Outgoing Email settings for your Departments?

Cheers.

Codewow

KevinTheJedi

Default department:

2nd Dept using the alias email.

KevinTheJedi

Codewow

Set your Default System Email to the partner address. Also, make sure your Departments all use system default outgoing email.

Cheers.

Codewow

KevinTheJedi

Using the diagnostics page to attempt sending from it isn't working either. Inbound works fine and even routes emails to the correct department without needing a filter. I just can't figure out what has changed since 1.16.3

KevinTheJedi

Codewow

When using the partner email on the diagnostic tab what do the headers look like?

Cheers.

Codewow

I think I figured it out and I am very annoyed.

It looks like Outlook is suddenly not displaying the alias as the alias email when it is an internal email address that is being replied to. This wasn't the case a month ago, so something may have changed on the client side.

It appears, externally, clients display the email it actually came from.

Anyways, thanks for all your help as always!