Cannot configure Outlook 365 to use oauth
I currently have a strange setup for email and I've been using Outlook 365 up until now. My concern is that Microsoft is saying that they don't want people using passwords and I'm not sure that I can continue doing what I'm doing today and still use Outlook 365.
I have an Outlook.com email address and I have a second email account from a totally different provider. I forward all of my outlook.com email to this second, alternative email account however I do not use the alternative email accounts SMTP server to send my mail. I instead have my SMTP settings in Outlook 365 to use Outlooks SMTP server. I do this just in case someone decides to look at the email's header information so it the outbound information in the header does not expose the email address of my second alternative email account. Doing this pretty much ensures that I get very little spam as outlook.com scans it before it gets forwarded and my alternative account scans all forwarded email a second time before it appears in my inbox. So to be perfectly clear my inbound pop server settings are configured for my alternative email address and my SMTP settings are configured to use Outlook.Com's SMTP server.
Getting down to the heart of the problem Microsoft says that soon I will no longer be able to use my password with their SMTP server and they indicated that Thunderbird could be configured to use OAuth2 instead and they even provided an screen shot of the setup. Unfortunately, Outlook 365 does not provide the ability to configure the SMTP server to use OAuth2 so this is why I would like to know from a Thunderbird expert if it can be configured with different inbound and outbound server settings and that I can use OAuth2 instead of passwords.
Zmodyfikowany przez Wayne Mery w dniu
Wybrane rozwiązanie
I have no idea at all how you will go with your account forwarding. That has nothing to do with Thunderbird.
As for your second item, all that is changing is the authentication methods is changing from Normal password to OAuth and the resultant OAuth key is stored in Thunderbird's password manager instead of a password. As Thunderbird already has that capability there is no impact from the Thunderbird development side. You just need to make the change to your outgoing settings. (note the server name has to be the appropriate office365 server name before the OAUTH option becomes available in settings.
A restart of Thunderbird is required between changing the server name and changing the authentication method to OAuth.
As an aside, current spam checkers and most provider submission rules man that you generally can not submit an email from say @Outlook.com from a mail transfer agent that is not described in the domains DNS. So sending that mail from MySever.com say, will see it treated as spam by most systems in the world. Some will reject the submission, others will refuse to accept the mail and yet others will place the mail in the SPAM folder. So what you are doing on sending is basically required and has nothing to do with your desire to hide your email address.
You double passing of mail address to address is as far as I can see basically a long winded approach to trying to defeat spam. Why not just get the mail from both accounts in Thunderbird directly and let Thunderbird check for spam.
Przeczytaj tę odpowiedź w całym kontekście 👍 0Wszystkie odpowiedzi (1)
Wybrane rozwiązanie
I have no idea at all how you will go with your account forwarding. That has nothing to do with Thunderbird.
As for your second item, all that is changing is the authentication methods is changing from Normal password to OAuth and the resultant OAuth key is stored in Thunderbird's password manager instead of a password. As Thunderbird already has that capability there is no impact from the Thunderbird development side. You just need to make the change to your outgoing settings. (note the server name has to be the appropriate office365 server name before the OAUTH option becomes available in settings.
A restart of Thunderbird is required between changing the server name and changing the authentication method to OAuth.
As an aside, current spam checkers and most provider submission rules man that you generally can not submit an email from say @Outlook.com from a mail transfer agent that is not described in the domains DNS. So sending that mail from MySever.com say, will see it treated as spam by most systems in the world. Some will reject the submission, others will refuse to accept the mail and yet others will place the mail in the SPAM folder. So what you are doing on sending is basically required and has nothing to do with your desire to hide your email address.
You double passing of mail address to address is as far as I can see basically a long winded approach to trying to defeat spam. Why not just get the mail from both accounts in Thunderbird directly and let Thunderbird check for spam.
Aby odpowiadać na posty, musisz zalogować się na swoje konto. Zadaj pytanie, jeśli nie masz jeszcze konta.