A TLS API failure occurred. Error = 0x80090326

Hi Steve,

We would like to ask a few questions for clarification to know the best possible resolution to offer.

• What is the domain of the account you are trying to add into your Outlook.com?
• Were you able to add or connect the said account before the Outlook.com migration?

We look forward to your response.

Jarius,

I have tried all of your suggestions and learned a little in the process.  Using IMAP instead of POP3 did not make any difference. 

Even though I don't see how the browser could affect communication between the OUTLOOK.COM server and the VISI.COM servers, I did try using Chrome without any different results.  I also cleared cookies and tried all options I tried before without success. 

Here is what I learned, though.  When I happened to try sending email with the VISI.COM address but using the OUTLOOK.COM server option, the problem disappeared and the account was connected.  This is not really a good alternative, though, since the inconsistency between the from address and the headers can increase the chance of a message being filtered out as junk from what I have read.  It does seem to indicate that the problem is with the SMTP connection and not with the IMAP or POP3 connections.  It should have been possible for OUTLOOK.COM to have displayed something indicating this message was related to the SMTP connection, allowing concentration on the real source of the problem.  Again, though, this isn't really a solution. 

To repeat, the settings I have used on other email programs, including with OUTLOOK 2016, have continued to work as expected, including SMTP settings for VISI.com, and I have not changed these in some time. 

I do not understand your suggestion that "You can also try to connect a different account first and try to add the VISI.com domain as a connected account instead  in Outlook.com."  Since I am logged into the OUTLOOK.COM website, I am logged into an OUTLOOK.COM account and do not believe there is a way to connect another account without involving an OUTLOOK.COM account.  If after all I am writing here, please help me understand this if you think this still seems to be worth pursuing.

I know a little of my own frustration is showing here, and I do not mean to take it out on you.  However, when reading in other forums, I see that similar problems to mine have been regularly reported with the new OUTLOOK.COM migration and there is now another person here experiencing something like this.  Further, it came up in the OUTLOOK.COM preview phase as well, and when following through the threads, Microsoft generally asked to be contacted privately and the threads died without explanation.  I only read those preview messages and was not part of the preview program.  It seems likely that someone in the OUTLOOK.COM sphere knows why something that worked but has stopped working with at least some SMTP servers since the migration has occurred.  I don't want to spend time trying to make something work that is known not to work.  I have appeared to have done just that with my experimenting with POP3 and IMAP, although I assume your best intentions in having me try that.  Surely the error code in the subject of this conversation has a specific meaning to people that understand these types of protocols that might allow me to ask the right questions of my email provider.

In addition, the "Send Only" option remains available, but I learned only by digging that this option no longer works.  I can work around this option not being available, but what is upsetting is that it remains an option and that Microsoft has not generally indicated that it does not work.  The option should be removed or a warning that it is temporarily unavailable should be right on the web page.  I do appreciate the fact that you have taken the time to look into this and have confirmed this is the case, though.  Further, the fact that you have taken time to tried to address my concerns is very much appreciated.  Would you do what you can to get clarification from the appropriate places in Microsoft as to what might be happening?

I have the same problem trying to connect using outlook.com. Always get tls api error 326.  Have used multiple browsers.  My zoho email account is set to imap.  Windows 10 mail app works flawlessly.

Steve, we would like to recommend that you follow the steps below and check if it will help you connect your account in Outlook.com

1. Go to your email domain and change the configuration as IMAP
2. Try to clear all the cache and cookies of your browser
3. Try to use a different browser to check if the issue would still persist.
4. Try to connect your account again as is.

You can also try to connect a different account first and try to add the VISI.com domain as a connected account instead in Outlook.com.

To address your other concern with the option to set your account as Send only, we would like to inform you that this is no longer available. We would suggest that you use the feedback in Outlook.com by clicking the question mark icon (?) on the top right. You can add your suggestions regarding the Send only option in Outlook.com.

Jarius, thank you for your questions. 

The domain I am connecting to is VISI.COM using pop3mail.visi.com and smtpmail.visi.com as instructed by the provider.  I tried both ports 110 and 995 for POP3 and 587, 465, and even 80 as SMTP ports.  Outlook always changed this back to 587 when I went in and edited the connected account again.

To answer your second question, as stated in my original note, I was sending messages through the same account for a year-and-a-half before the Outlook migration.  I used the "Send Only" option which I am told no longer works.  I received mail by having it forwarded to my account instead of pulling it as was recommended.  I tried the "Send Only" option after the migration and that did not work.  Therefore, I tried setting the connected account up as pop3 and SMTP and received the errors.  The same settings continued to work with other email programs.

Yesterday, I received a note saying I needed to reconnect to this OUTLOOK.COM account from the desktop version of Outlook.  I had done this already, and it happened again when I moved from Office 2013 to 2016, but I did it again anyway.  I don't know if this means there is more migrating going on or not, but I don't look forward to doing all this again without some knowledge of what changed with the migration.

Any help appreciated.