mrwolf

My feedback

  1. 83 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Feature Suggestions » Web  ·  Flag idea as inappropriate…  ·  Admin →
    mrwolf supported this idea  · 
  2. 524 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    142 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    mrwolf commented  · 

    I have written an autodiscovery mechanism for my clients which works.
    It works for Outlook and for Thunderbird.
    I know of 3 mechanisms to autodiscover mail settings.
    As far as I discovered, these are:

    * Microsoft's autodiscover (used by Outlook)
    * Thunderbird's autoconfig (used by Thunderbird)
    * rfc6186 (afaik not used by any mail client)

    I have written scripts that are running on the DNS-server (mine is a seperate Plesk server) that create the DNS-records for each domain that has an MX-record pointing to a server of mine. It will delete those records if the MX goes foreign.

    On the mailservers I have a wildcard certificate of the company I work for.
    Each domain will connect to a subdomain of my company's domain where the subdomain is the FQDN of the client's domain with its dot replaced by a dash (wildcard certificates go only 1 level deep).

    The SRV records (rfc6186 and outlook) and the CNAME (thunderbird) will be created in the client's domain.
    The target of these records are pointing to a CNAME in my company's domain.
    The CNAME in the company's domain will point to mail.<clientdomain>.

    It's explained (partly) here: https://talk.plesk.com/threads/ssl-certificates-for-mail-server.342531/
    I don't have a full write-up.
    The main reason is time and it's also very customized to my situation

Feedback and Knowledge Base