Feature #98
closedimplement e-mail autoconfiguration
Added by Florian Effenberger about 10 years ago. Updated over 4 years ago.
0%
Description
E-mail autoconfiguration is a neat feature to be deployed on our servers for the @tdf and especially the @libreoffice accounts. Details can be found at http://www.hostblogger.de/blog/archives/5977-Autokonfiguration-fuer-E-Mail-Konten-von-Webhosting-Kunden.html
Updated by Alexander Werner about 10 years ago
- Category set to Mail system
- Assignee set to Alexander Werner
Updated by Alexander Werner about 10 years ago
- Priority changed from Normal to Low
Updated by Florian Effenberger almost 10 years ago
- Assignee deleted (
Alexander Werner)
IMHO nothing for Alex' table - nice addendum, but really only of use for a few people, so any takers, feel free to take this :)
Updated by Dennis Roczek over 9 years ago
well having fun on a bit scripting and new stuff... why not. but for testing I would need at least a @libo address ^^
Updated by Florian Effenberger over 9 years ago
Are you a TDF member? Then you have been offered one already :)
Updated by Dennis Roczek over 9 years ago
I'm a TDF member, but no, I never got an offer. I only got by mail following mail:
Dear Dennis Roczek,
We are pleased to inform you that, as of 2014-10-01, your membership
has been officially filed. You are now acknowledged as member of
The Document Foundation according to its bylaws.
Kind Regards,
No mention on the possibility of a mail account (through I know that it is possible as it is documented in the wiki :-p)
Is something borked? No spam mail in my junk folder.
Updated by Florian Effenberger over 9 years ago
I poked Sophie, maybe the mail was lost or forgotten :)
Updated by Dennis Roczek over 9 years ago
- Assignee set to Dennis Roczek
I'll take this. This is fun and maybe this helps me in my own company. ;-)
Updated by Dennis Roczek over 9 years ago
first run: thunderbird. Mostly the easiest way. ;-)
Well if I understand the MDN pages (Section "Small company") correctly, the file should be located at
http://libreoffice.org/.well-known/autoconfig/mail/config-v1.1.xml
and
All config files must be served as Content-Type: text/xml (or application/xml), otherwise the file will be ignored. Also, they must use charset UTF-8 (esp. if there are any non-ASCII-characters).
The file itself should (well somehow untested until now) look like:
<?xml version="1.0" encoding="UTF-8"?> <clientConfig version="1.1"> <emailProvider id="libreoffice.org"> <domain>libreoffice.org</domain> <displayName>LibreOffice.org</displayName> <displayShortName>LibreOffice</displayShortName> <incomingServer type="imap"> <hostname>mail.jpberlin.de</hostname> <port>993</port> <socketType>SSL</socketType> <authentication>password-encrypted</authentication> <username>%EMAILADDRESS%</username> </incomingServer> <incomingServer type="imap"> <hostname>mail.jpberlin.de</hostname> <port>143</port> <socketType>STARTTLS</socketType> <authentication>password-encrypted</authentication> <username>%EMAILADDRESS%</username> </incomingServer> <outgoingServer type="smtp"> <hostname>mail.jpberlin.de</hostname> <port>465</port> <socketType>SSL</socketType> <authentication>password-encrypted</authentication> <username>%EMAILADDRESS%</username> </outgoingServer> <outgoingServer type="smtp"> <hostname>mail.jpberlin.de</hostname> <port>587</port> <socketType>STARTTLS</socketType> <authentication>password-encrypted</authentication> <username>%EMAILADDRESS%</username> </outgoingServer> <documentation url="https://wiki.documentfoundation.org/MailAccounts"> <descr lang="de">Generische Einsetellungen und Rechtliches</descr> <descr lang="en">Generic settings and legal page</descr> </documentation> <documentation url=""> <descr lang="de">Webmailer</descr> <descr lang="en">Webmailer</descr> </documentation> <documentation url="https://www.jpberlin.de/verwaltung/index.php?lang=en"> <descr lang="de">Verwaltungskonsole zum Ändern des Passwortes und zum Einstellen von Serverseitige Emailfilterung</descr> <descr lang="en">Control Panel for changing password and installing serverside email filters</descr> </documentation> </emailProvider> </clientConfig>
Moreover there is a webmailer part for the XML, but I don't think this is needed or useful in any kind. I also don't know how the user can get this part of information without looking in the xml file so skipping that.
Updated by Florian Effenberger over 9 years ago
Thanks for that!
Any chance you can test with a modified /etc/hosts locally before we put this live?
Updated by Dennis Roczek over 9 years ago
Yeah, I wanted to set up a local mediawiki for testing and thus I would need a xampp installation --> I will test it locally. maybe even today as I might find the time to do this. (/me is playing with the idea of reimplementing / updating http://www.mediawiki.org/wiki/Extension:BrokenLinks so that we can check automatically for broken web links in out tdf wiki...)
Updated by Dennis Roczek over 9 years ago
:-)
File should be located at:
http://autoconfig.libreoffice.org/mail/config-v1.1.xml
It works like a sharm. Well maybe I will try the outlook stuff out as well... ;-)
new file (small modification in the SMTP auth)
<?xml version="1.0" encoding="UTF-8"?> <clientConfig version="1.1"> <emailProvider id="libreoffice.org"> <domain>libreoffice.org</domain> <displayName>LibreOffice.org</displayName> <displayShortName>LibreOffice</displayShortName> <incomingServer type="imap"> <hostname>mail.jpberlin.de</hostname> <port>993</port> <socketType>SSL</socketType> <authentication>password-encrypted</authentication> <username>%EMAILADDRESS%</username> </incomingServer> <incomingServer type="imap"> <hostname>mail.jpberlin.de</hostname> <port>143</port> <socketType>STARTTLS</socketType> <authentication>password-encrypted</authentication> <username>%EMAILADDRESS%</username> </incomingServer> <outgoingServer type="smtp"> <hostname>mail.jpberlin.de</hostname> <port>465</port> <socketType>TLS</socketType> <authentication>password-encrypted</authentication> <username>%EMAILADDRESS%</username> </outgoingServer> <outgoingServer type="smtp"> <hostname>mail.jpberlin.de</hostname> <port>465</port> <socketType>SSL</socketType> <authentication>password-encrypted</authentication> <username>%EMAILADDRESS%</username> </outgoingServer> <documentation url="https://wiki.documentfoundation.org/MailAccounts"> <descr lang="de">Generische Einsetellungen und Rechtliches</descr> <descr lang="en">Generic settings and legal page</descr> </documentation> <documentation url=""> <descr lang="de">Webmailer</descr> <descr lang="en">Webmailer</descr> </documentation> <documentation url="https://www.jpberlin.de/verwaltung/index.php?lang=en"> <descr lang="de">Verwaltungskonsole zum Ändern des Passwortes und zum Einstellen von Serverseitige Emailfilterung</descr> <descr lang="en">Control Panel for changing password and installing serverside email filters</descr> </documentation> </emailProvider> </clientConfig>
Updated by Dennis Roczek over 9 years ago
- Assignee deleted (
Dennis Roczek)
should I assign Alex for that ticket to implement that on the server? (/me is out although I will do check the outlook stuff)
Updated by Florian Effenberger over 9 years ago
Assignee:
Thanks a lot for your work!
I propose we leave this as open task for one infra volunteer, as this is
a low-hanging fruit now and might help to get people in :)
Updated by Dennis Roczek over 9 years ago
Just FYI:
The Outlook part is mostly finished. I have to find a way so that the complete email address will be used. sadly that isn't that easy as MS do want to provide a dynamic XML (so per request generated) and thus I do need to figure out if there is a generic parameter which simply uses the given mail address like in mozillas way...
Updated by Christian Lohmaier over 9 years ago
if the necessary parts of the email-address are passed as URL or post-request parameters or similar, then silverstripe can be used to create that xml on-the-fly
Updated by Dennis Roczek over 9 years ago
Christian Lohmaier wrote:
if the necessary parts of the email-address are passed as URL or post-request parameters or similar, then silverstripe can be used to create that xml on-the-fly
Yeah, we have to do something. Alternatively (to the silverstripe solution) I found a PHP script which does this already. See http://web.archive.org/web/20120828065248/http://moens.ch/2012/05/31/providing-email-client-autoconfiguration-information/ (search for the heading "Getting the user’s email address in the response XML")
OK, then I will test my existing configuration today and will post the preconfigurated XML file.
Updated by Dennis Roczek over 9 years ago
OK, that code works for Outlook (tested with win 8.1 and ms outlook 2013 with the registry test path)
replace dennisroczek@libreoffice.org with the email address which is in the request as described in that section http://technet.microsoft.com/en-us/library/cc511507.aspx#AutodiscoverXMLSchema
Sadly there aren't many options for configuration. :-(
<?xml version="1.0" encoding="utf-8" ?> <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> <Account> <AccountType>email</AccountType> <Action>settings</Action> <!-- Image: Optional / Does anybody have a better JPG image? --> <Image>https://wiki.documentfoundation.org/images/b/b9/Facebook-five.jpg</Image> <ServiceHome>https://wiki.documentfoundation.org/MailAccounts</ServiceHome> <Protocol> <Type>IMAP</Type> <TTL>168</TTL> <Server>mail.jpberlin.de</Server> <Port>993</Port> <DomainName>libreoffice.org</DomainName> <LoginName>dennisroczek@libreoffice.org</LoginName> <DomainRequired>on</DomainRequired> <SPA>off</SPA> <SSL>on</SSL> <AuthRequired>on</AuthRequired> </Protocol> <Protocol> <Type>IMAP</Type> <TTL>168</TTL> <Server>mail.jpberlin.de</Server> <Port>143</Port> <DomainRequired>on</DomainRequired> <LoginName>dennisroczek@libreoffice.org</LoginName> <SPA>off</SPA> <AuthRequired>on</AuthRequired> </Protocol> <Protocol> <Type>SMTP</Type> <TTL>168</TTL> <Server>mail.jpberlin.de</Server> <Port>465</Port> <DomainRequired>on</DomainRequired> <LoginName>dennisroczek@libreoffice.org</LoginName> <SPA>off</SPA> <SSL>on</SSL> <AuthRequired>on</AuthRequired> </Protocol> <Protocol> <Type>SMTP</Type> <TTL>168</TTL> <Server>mail.jpberlin.de</Server> <Port>465</Port> <DomainRequired>on</DomainRequired> <LoginName>dennisroczek@libreoffice.org</LoginName> <SPA>off</SPA> <AuthRequired>on</AuthRequired> </Protocol> </Account> </Response> </Autodiscover>
Updated by Dennis Roczek over 9 years ago
I missed my prewritten comments regarding the Outlook parts:
The file should be located at https://libreoffice.org/autodiscover/autodiscover.xml (or alternatively at https://autodiscover.libreoffice.org/autodiscover/autodiscover.xml) (the connection has to be in SSL with a valid certificate, I (or anybody else who want to test this out) can test this scenario by modifying a registry using
[HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Autodiscover] "libreoffice.org"="C:\temp\libreoffice.xml"
)
Everything can be tested by using Microsoft's official page (for the case you don't have any outlook 2007+)
https://testconnectivity.microsoft.com/
Updated by Guilhem Moulin over 4 years ago
- Status changed from New to Closed
- Assignee set to Guilhem Moulin
Done for libreoffice.org and documentfoundation.org domains using /.well-known/autoconfig/mail
URIs a while back. Works at least for Thunderbird, autoconfiguration is not standardized so we won't find a solution that works for all MUAs.