Autodiscovery not working

Questions
1

Your question

Hello,
autodiscovery on clients like samsung mail or gmail (android) are not working?
Does anyone know how how it handles autoconfig? Autoconfig is working fine on outlook or thunderbird.

2

Stalwart supports three autodiscovery protocols (PACC, Mozilla Autoconfig, and Microsoft Autodiscover), but Samsung Mail and Gmail on Android do not implement any of these standard protocols. They use their own proprietary discovery mechanisms that Stalwart does not currently advertise – this is why Outlook and Thunderbird work (they use Autodiscover and Autoconfig respectively) while Samsung Mail and Gmail do not.

Here are the specifics:

  • Thunderbird uses Mozilla Autoconfig – fetches http://autoconfig.example.com/mail/config-v1.1.xml. Stalwart serves this automatically.
  • Outlook uses Microsoft Autodiscover – fetches https://autodiscover.example.com/autodiscover/autodiscover.xml. Stalwart serves this automatically.
  • Samsung Mail / Gmail (Android) rely on Google’s own backend directory or fall back to manual setup; they do not query the standard autoconfig/autodiscover endpoints, so Stalwart’s auto-discovery responses are never reached.

What you can do:

  1. For PACC-aware clients, make sure https://yourdomain.com/.well-known/user-agent-configuration is reachable (no dedicated subdomain needed). This is the most modern standard, but Samsung Mail and Gmail don’t support it yet.
  2. Ensure the autoconfig.yourdomain.com and autodiscover.yourdomain.com CNAME DNS records point to your mail host (as documented), so standard clients do work correctly.
  3. For Samsung Mail and Gmail, manual setup is currently the only reliable path.

You can check the DNS records Stalwart recommends for your domain directly from the domain management page in the WebUI.

Docs reference: Autoconfig & Autodiscover and DNS records for autoconfiguration.

This is an automated reply from the Stalwart Help Bot. Other community members may follow up if this answer is incomplete or wrong.