In Automatic Setup: Prefer DNS SRV Records over Office365 Accounts

In moderationThis post is currently in the moderation queue! It is not visible on the feedback board until it is approved by our team.

Open

Mail

steffenl

If you have an Office365 Account that is not used for Mailing and Calendars (only for e.g. Teams) and you are adding an account in eM Client with the automatic setup, the setup ignores the DNS SRV entries for imap/submission/smtp entries. It directly tries to add the Office365 Account without giving you a choice to use something else.
It would be nicer if eM Client don't automatically tries to add the Office365 Account if DNS SRV entries for the Mailserver exists, but give you a choice what you want to add (normal Mailaccount or Office365 Account).
That would make Live easier for companies (like us) that try to move away from Microsoft.
Or at least it should tell me during the setup, that it tries to configure an Office365 account. There is no notice during the setup that it tries to do this.

3 months ago

olivia_rust

We do prefer _autodiscover._tcp.<domain> over Microsoft 365 autodiscover already.

Also, if you use the Microsoft account only for Teams it would NOT be triggered by the M365 detection. It only triggers if mail server was setup for that domain / account at some point. It may cache the value for a month after the M365 account was decommissioned.
Could that perhaps be the case for your domain?

3 months ago

steffenl

@olivia_rust Hi Olivia,
sorry for the delay. I had to check out what's the problem, that took a
while, since we are normally not using M365.
Looks like the M365 Exchange Server accidentally has been activated and
for some users (not all) mailboxes have been automatically created. The
problem is: You can't deactivate these mailboxes without removing the
license for that user or delete the user itself. So once activated, it
looks like there is no way back, even if you don't use the M365 Exchange
as official mailserver.
I read up into the whole autodiscover thing, there is a lot of
documentation, but because it's normally automatically set up by
Exchange, there is not much good documentation for people without
Exchange. Especially how the autodiscover.xml is build or can be
manually be build. Would be great if you on eM Client could write a good
documentation about that and about which autodiscover options eM Client
supports (e.g.: looks like it does not support the option). Or
provide an example for the autodiscover.xml with all options that are
supported by eM Client. That would help a lot 🙂
Anyway, at least I managed it to create an autodiscover.xml by hand and
set everything up including the DNS SRV _autodiscover entry. And you are
right, eM Client prefers this settings now.
So this is working, thanks 🙂
But what I now found out during the automatic setup is that he don't ask
for a username and password if that is not given in the
autodiscover.xml. And even if it's given, eM Client is automatically
using the "Use Integrated Windows authentication (SSO)" Option in the
setting. Is there a way I can avoid this and tell eM Client to ask for
the username and password?
Thanks for your support!
Kind regards
Steffen
------ Original Message ------
From "eM Client"
To steffen.langenbach@card.de
Date 12.11.2024 15:44:04
Subject New comment on In Automatic Setup: Prefer DNS SRV Records over
Office365 Accounts

3 months ago

Share and vote for eM Client ideas!

Changelog

Feedback

In Automatic Setup: Prefer DNS SRV Records over Office365 Accounts