Difference between revisions of "EmailAutoDiscover"
m (Added to email category) |
|||
Line 4: | Line 4: | ||
https://github.com/jamesiarmes/php-ews/wiki/Autodiscovery | https://github.com/jamesiarmes/php-ews/wiki/Autodiscovery | ||
+ | |||
+ | http://technet.microsoft.com/en-us/library/cc511507%28v=office.14%29.aspx#AutodiscoverXMLSchema | ||
+ | |||
+ | https://bugzilla.mozilla.org/show_bug.cgi?id=521538 | ||
+ | |||
+ | http://www.emaildiscussions.com/showthread.php?t=62769 | ||
It is unlikely that autodiscover can be configured without a valid SSL certificate for the domain in the email address. Implementing a mass-hosting version of autodiscover would be prohibitively expensive due to this. It would however be possible to configure it on a per-domain basis provided the SSL certificate is purchased (or a self-signed one is installed on all client machines - Would this work?) | It is unlikely that autodiscover can be configured without a valid SSL certificate for the domain in the email address. Implementing a mass-hosting version of autodiscover would be prohibitively expensive due to this. It would however be possible to configure it on a per-domain basis provided the SSL certificate is purchased (or a self-signed one is installed on all client machines - Would this work?) | ||
[[Category:Email]] | [[Category:Email]] |
Revision as of 23:51, 2 August 2014
http://www.andrewyager.com/blog/2008-09-13/outlook-2007-email-autodiscovery-php-server
http://www.winblogs.net/index.php/2012/08/07/autodiscover-with-smartermail-or-any-other-mail-server/
https://github.com/jamesiarmes/php-ews/wiki/Autodiscovery
http://technet.microsoft.com/en-us/library/cc511507%28v=office.14%29.aspx#AutodiscoverXMLSchema
https://bugzilla.mozilla.org/show_bug.cgi?id=521538
http://www.emaildiscussions.com/showthread.php?t=62769
It is unlikely that autodiscover can be configured without a valid SSL certificate for the domain in the email address. Implementing a mass-hosting version of autodiscover would be prohibitively expensive due to this. It would however be possible to configure it on a per-domain basis provided the SSL certificate is purchased (or a self-signed one is installed on all client machines - Would this work?)