On Thu, 14 Nov 2024, Thomas Gramstad via Alpine-info wrote:
> Office365 has been enforced at work, and I'm now using "Alpine
> with MS365 using OAuth2" and Alpine 2.26.
Similar for me. I don't know if you're having Alpine talk to MS365
using IMAP, or instead using something like fetchmail to get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, 2024-11-14 at 11:00 -0600, Milt Epstein via Alpine-info wrote:
On Thu, 14 Nov 2024, Thomas Gramstad via Alpine-info wrote:
Office365 has been enforced at work, and I'm now using "Alpine
with MS365 using OAuth2" and Alpine 2.26.
Sim
On Thu, 14 Nov 2024, Carlos E. R. via Alpine-info wrote:
[ ... ]
> There are two things to do:
>
> - remove the junk/spam flag, if it exists (I don't know how it is
> stored)
> - move the mail to the inbox folder.
>
> Thunderbird can do this; but whether the server learns and retrains th
Office365 has been enforced at work, and I'm now using "Alpine
with MS365 using OAuth2" and Alpine 2.26.
Some legitimate e-mail is now in the Spam folder. How do I tell
Alpine that they are NOT spam?
A few legitimate e-mails sent directly to me -- that people tell
me they have sent -- are nowh
On Thu, 14 Nov 2024, Thomas Gramstad via Alpine-info wrote:
Office365 has been enforced at work, and I'm now using "Alpine
with MS365 using OAuth2" and Alpine 2.26.
Some legitimate e-mail is now in the Spam folder. How do I tell
Alpine that they are NOT spam?
Hmm.
It is MS365, not Alpine, th
The information that is below is correct. The folder that you use for junk mail
is junk. I remember having to deal with the authentication and all of the
tokens and all of that stuff, when I had to upgrade to Alpine 2.26, and if it
wasn’t for Eduardo, and his patience and understanding during se
