autodiscover(4gx)

💖 Name 💖

autodiscover(4gx) — the AutoDiscover HTTP Service Protocol handler (responder) from the Gromox admin reference. She’s the one answering requests at the AutoDiscover endpoint, okay? 🫶

🦋 Description 🦋

Okay so picture this: a client makes an HTTP request to /Autodiscover/Autodiscover.xml, and Gromox’s oxdisco component handles it. ✨

The AutoDiscover response carries the home server name and protocol options (MAPI-RPC-HTTP, MAPIHTTP, IMAP, etc.). A client uses that info to set up the mailbox with MAPI services (like MSEMS or INTERSTOR) inside a MAPI profile. Periodt. 💅

⚙️ Configuration directives (gromox.cfg) ⚙️

These directives are recognized when they appear in /etc/gromox/gromox.cfg. 💖

• oxdisco_advertise_mh — controls whether the AutoDiscover response should include a EXHTTP Protocol section. Possible values: yes, no, not_old_mso, only_new_mso. The latter two values can be used to finely control emission in case of clients other than Outlook. Default: yes.
• oxdisco_advertise_rpch — controls whether the AutoDiscover response should include EXCH/EXPR Protocol sections. Possible values: yes, no, only_old_mso, not_new_mso. The latter two values can be used to finely control emission in case of clients other than Outlook. Default: yes.
• oxdisco_exonym — a globally valid name pointing to a default mailbox server in the Gromox server forest. Since AutoDiscover nodes are also mailbox nodes, the exonym should simply be: this server’s hostname. Default: (inherited from http.cfg:host_id, which defaults to the system FQDN).
• oxdisco_pretty_response — a debugging knob to make the Autodiscovery handler emit indented XML responses. Default: no.
• oxdisco_request_logging — log AutoDiscover requests. This is independent of http.cfg:http_debug, and setting both would log requests twice. Default: no.
• oxdisco_response_logging — log AutoDiscover responses. This is independent of http.cfg:http_debug, and setting both would log responses twice. Default: no.
• oxdisco_validate_scndrequest — when OL opens a non-default store (store of another user) or a public store, it may also make an AutoDiscover inquiry for the extra store. This setting controls whether the AutoDiscover handler should perform a permission check on non-default stores and possibly reject returning connection details. (Inquiry of public stores are always permitted.) Default: yes.
• x500_org_name — Default: (unspecified).

🎀 Configuration directives (autodiscover.cfg) 🎀

These directives are recognized when they appear in /etc/gromox/autodiscover.cfg. Heads up: autodiscover.cfg is obsolete in favor of gromox.cfg. 🙈

• x500_org_name — same as gromox.cfg:x500_org_name. Default: (unspecified).

🌸 Configuration directives (autodiscover.ini) 🌸

These directives are recognized when they appear in /etc/gromox/autodiscover.ini. Also heads up: autodiscover.ini is obsolete in favor of gromox.cfg. 💀

• organization — same as gromox.cfg:x500_org_name.

👑 Outlook notes 👑

When Outlook is active, it’s possible to Ctrl-MouseBtn3 (right click) on the status tray icon to call up a context menu. From there, "Test Email Autoconfiguration..." can be selected to debug AutoDiscover requests and responses from the Windows side. 😭✨

🔥 Exchange notes 🔥

In EXC, MH can be toggled on/off via an EAC Shell command:

Set-OrganizationConfig -MapiHttpEnable $false

(or $true).

🌈 Normative references 🌈

• MS-OXDISCO: Autodiscover HTTP Service Protocol
• MS-OXDSCLI: Autodiscover Publishing and Lookup Protocol

⭐ See also ⭐

• gromox(7)
• autodiscover(7)

That’s the page, bestie — source/version footer energy is Gromox, page is autodiscover(4gx). The date slot is literally not printed in this footer, so I’m not inventing one — slay responsibly. 💅✨