Outlook 2016 not sending e-mail

Hi alkaufmann

I just tried it on mine, but 2013.

Seems if you even open that option box it prevents sending, at least it did with mine.

Then I started a new email and it went immediately.

Maybe give that a try, start a new email, click send and see if that restriction is on. (and that sounds different from your original issue as it was an error message on send and this issue is it just holding the mail to send.)

I think you are dealing with a supplier issue, one they are tweaking, as you said it worked for a while this morning.

I would check if they have revised set up instructions online. You haven't said which supplier you are using. Bell is likely scrambling after the hack notice they issued last week and Rogers (Yahoo) starting asking for an app password last week on my brothers account. You could be using a different supplier, being the West coast, but they are all likely tightening the screws.

Depending on supplier you can also request level 2 support and they may know be more informed about what is happening at their end.

Ken

alkaufmann said:

Outlook 2016 has suddenly stopped sending out my e-mail, it keeps reporting the server responded 452.4.1.0 the requested action aborted. Try again later. I tried a lot of things yesterday even re-installing Office and nothing fixed this problem. I called my Internet Service Provider and that got cut off when I was told to try Webmail.

This morning everything was back to normal and my e-mail was going out. Just a few minutes ago I started getting that server error message again.

Could this problem be caused by this Window 16199.1000?

I'm having trouble with Outlook wanting me to give my password to my outlook.com emaill addy over and over and over, ad nauseum. So far, I can't receive email for that account.

I looked in the "known issues" of Build 16199 and found this:

Outlook 2016 may hang on launch due to an issue where the spam filter gets stuck reading the Outlook Data File and the UI waits indefinitely for it to return. We’re investigating.

That's all I could find, and it probably related to either of our problems, but it is making me wonder. . .

That is likely it. Wish error messages were a little more relevant to issue, in this case, server by name not responding.