![]() ![]() What I just did is use the integrated testing features in Outlook (+right click on the traybar icon, test email auto configuration). I removed some of the elements including the tag, however the error remains. Lastly, there were some improvements to be made to SMTP authentication resiliency. You can also remove some other values because they are either unsupported, not recommended or irrelevant as they were set to their default value. Most likely it trips over the element as although it is part of the schema, it isn't supported by Outlook. ![]() How can I convince Outlook to do the same with auto configuration? If I switch to manual configuration and enter all account and server details, only a single (successful) attempt is made. The log files of the mail server show multiple lines that indicate that Outlook starts multiple connections, in some of them no authentication attempt seems to be made, in some of them the user name is only the user part and so on. *** Email address is removed for privacy *** ), it can be accessed via HTTP POST and produces the following result: IMAP(s) on port 993, TLS/SSL, user name: e-mail address, password required, authentication: plain or encrypted POP3(s) on port 995, TLS/SSL, user name: e-mail address, password required, authentication: plain or encrypted SMTP on port 587, STARTTLS, user name: e-mail address, password required, authentication: plain or encrypted Here is the settings that are required to connect to the server: Account to be set up: *** Email address is removed for privacy *** This is not desired since intrusion detection system disable the access by an IP address if to many login attempts are made. Especially, it first tries to connect without using a user name or using only the local part of the e-mail address (see log file extract below) instead of using the full e-mail address as a login name (even though the autodiscover serviceĬlearly tells to use it). As a result, Outlook tries to connect to the IMAP and POP3 using multiple methods I looked at the different log files and my assumption is that Outlook can access the autodiscover service but either misses or ignores some information in the autodiscover file. However, some days ago, I noticed that while setting up a mail account in Outlook 2013 that the automated configuration did no longer work. So far, I assumed that everything worked properly. In order to facilitate account setup, we use Automx () that generates the required output for typicalĪutodiscover requests (see below). ![]() We have a server server running Ubuntu with Dovecot for IMAP+POP3 and Postfix for SMTP, which some users connect to using Outlook 2013. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |