ActiveSync uses the primary domain and not the domain alias used in the account setup

ActiveSync uses the primary domain and not the domain alias used in the account setup.

We have setup SmarterMail with domainA.com as primary domain and domainB.com as an alias domain.

On the clients we have setup an ActiveSync account using user@domainB.com

Everything works fine, until the user are sending an email, because it's received as user@domainA.com

In the ActiveSync log I can see that the connection are done using the alias domain, user@domainB.com, but in the "Add" element I can see that it's using the primary domain, like <From xmlns="Email">"User" <user@domainA.com></From>

What to do?

markus Replied

2/10/2016 at 3:23 AM

Same problem here.
It looks like each user connecting through EAS (ActiveSync) is always using his primary mailbox- and domain-name (that one licensed for EAS) as Return-Path, From, Reply-to or whatever else the recipient could use to answer to the message.

The client account (we testet on the original gmail-app on a Android 5.1 device) can be configured with the Alias mailbox- and domain-name. Fetching incoming and sending outgoing messages is working fine. Even is nowhere on client side is configured the EAS-licensed username, every outgoing message is using exactly this one as mailfrom... Up to now we haven't found any way to change this limiting behavior.

Allan Romme Replied

5/18/2016 at 3:06 PM

Are this issue fixed in the newest version of SmarterMail ?

Michael Price Replied

1/24/2017 at 3:46 PM

Same question - have the latest version of SM 15.5.x.

In Exchange you can set the primary email address. Not sure if SM has an equivalent feature?

3 Replies

Reply to Thread

Related Knowledge Base Articles

3 Replies

Reply to Thread

Tags

Related Knowledge Base Articles