GNOME Bugzilla – Bug 790681
Outdated autoconfig for AOL servers
Last modified: 2017-11-23 16:27:31 UTC
Auto configuration in Evolution doesn't work for AOL at the moment. There was change on AOL side around 7.11.2017 and port 993/995 should be used for imap/pop secure connection. Auto configuration provided by api.gnome.org still contain old information (port 143/110): https://api.gnome.org/evolution/autoconfig/1.1/aim.com https://api.gnome.org/evolution/autoconfig/1.1/aol.com </incomingServer> <incomingServer type="imap"> <hostname>imap.aol.com</hostname> <port>143</port> <socketType>STARTTLS</socketType> <username>%EMAILLOCALPART%</username> <authentication>password-cleartext</authentication> </incomingServer> </incomingServer> <incomingServer type="pop3"> <hostname>pop.aol.com</hostname> <port>110</port> <socketType>STARTTLS</socketType> <username>%EMAILLOCALPART%</username> <authentication>password-cleartext</authentication> </incomingServer> I did a test with Mozilla Thunderbird and auto configuration worked, so I compared data used by Thunderbird, they don't use 143/110 anymore. https://autoconfig.thunderbird.net/v1.1/aol.com https://autoconfig.thunderbird.net/v1.1/aim.com AOL reference: https://help.aol.com/articles/how-do-i-use-other-email-applications-to-send-and-receive-my-aol-mail Could you please update data provided by api.gnome.org for aol.com and aim.com domains? I know that auto configuration is not part of Evolution anymore, but couldn't figure out which section in bugzilla should be used.
Thanks for a bug report and pointers. That part of api-web is under Evolution hands, thus you filled it properly here. I made the change here [1], which is already available. I'd appreciate if you could confirm it is working properly now. Thanks in advance. [1] https://git.gnome.org/browse/api-web/commit/?id=323a4e6d2272959d163a2665ae30f988e0b6db74
Thanks for the fix. I confirm that autoconfig works in Evolution for aim.com now.