Reading multiple folders from multiple devices

with mailboxes, but Dreamhost hasn't upgraded to a version that supports it yet. Andy -- Andrew D. Arenson (he/him) H 317.964.0493 arenson (at) spatzel.netC 317.679.4669

Re: Why uw.edu not accepted my signed email?

On Wed, Nov 17, 2021 at 07:53:47PM +0100, Daniel Tameling wrote: > On Tue, Nov 16, 2021 at 04:36:43PM -0500, Andrew D. Arenson wrote: > > I receive email using IMAP via a davmail process that in turn interacts > > with Indiana University's Office 365 Exchange instance.

Re: Why uw.edu not accepted my signed email?

On Wed, Nov 17, 2021 at 07:24:02AM +, Claus Assmann wrote: > On Wed, Nov 17, 2021, Andrew D. Arenson wrote: > > > Oct 21 19:52:35 redsolar sm-mta[1465905]: STARTTLS=client, error: > > connect failed=-1, reason=dh key too small, SSL_error=1, errno=0, > > It see

Re: Why uw.edu not accepted my signed email?

On Wed, Nov 17, 2021 at 05:36:43AM +, Claus Assmann wrote: > On Tue, Nov 16, 2021, Andrew D. Arenson wrote: > > > I don't see any obvious configurations that set how email is > > sent, so my guess is that it is being send via sendmail on my > >

Re: Why uw.edu not accepted my signed email?

On Tue, Nov 16, 2021 at 03:32:15PM -0500, Jon LaBadie wrote: > On Tue, Nov 16, 2021 at 07:29:01PM +, Claus Assmann wrote: > >On Tue, Nov 16, 2021, Andrew D. Arenson wrote: > > > >>Deferred: 403 4.7.0 TLS handshake failed. > > > >This has nothing to d

Re: Why uw.edu not accepted my signed email?

On Tue, Nov 16, 2021 at 07:29:01PM +, Claus Assmann wrote: > On Tue, Nov 16, 2021, Andrew D. Arenson wrote: > > > Deferred: 403 4.7.0 TLS handshake failed. > > This has nothing to do with the content of the mail, it's a problem > between the program you use to se

Why uw.edu not accepted my signed email?

this. I'm hoping to learn enough that I could either fix something on my end or offer a suggestion to the mail server admins at uw.edu about what they might change. Andy -- Andrew D. Arenson (he/him) H 317.964.0493 arenson (at) spatzel.netC 317.679.4669

Thank you for threading!

I recently upgraded my work workstation from RHEL6 to Ubuntu 20.04, so was able to move from mutt 1.5.20 to 1.13.2 ... and now I have threading! I know it's still far behind the latest versions, but it's very exciting, and I'm very thankful. Andy -- Andrew D. Arenson (he/him

Re: Moving from mutt 1.5 to 1.13.2

Thanks for the explanation, Kevin. Andy On Thu, Jun 03, 2021 at 09:29:18AM -0700, Kevin J. McCarthy wrote: > On Thu, Jun 03, 2021 at 11:42:25AM -0400, Andrew D. Arenson wrote: > >Update: > > > >Setting both of the following solves the first problem: "Encrypted

Re: Moving from mutt 1.5 to 1.13.2

n 03, 2021 at 11:29:08AM -0400, Andrew D. Arenson wrote: > On a RHEL6 box, using mutt 1.5, I got mutt to work w/ davmail, enabling > me to get email from my work Office365 account. > > I'm transitioning to Ubuntu 20.04, which provides mutt 1.13.2 and have > run int

Moving from mutt 1.5 to 1.13.2

ssl_starttls=no ... but that had no effect. Any ideas on where to look next? -- Andrew D. Arenson (he/him) H 317.964.0493 arenson (at) spatzel.netC 317.679.4669

Re: support for Office365?

On Tue, Sep 15, 2020 at 01:45:01PM -0400, Andrew D. Arenson wrote: > On Sat, Jun 27, 2020 at 07:49:14AM +0100, isdtor wrote: > > > Andrew D. Arenson writes: > > > My organization is moving to Office365 and have decided, sadly, not to > > > support IMAP. >

Re: support for Office365?

On Sat, Jun 27, 2020 at 07:49:14AM +0100, isdtor wrote: > Andrew D. Arenson writes: > > My organization is moving to Office365 and have decided, sadly, not to > > support IMAP. > > > > Anyone have insight in how mutt might still be able to connect to >

support for Office365?

of translates from Office365's other protocols to IMAP, as they use a (non-mutt) IMAP mail client. So, I'll follow up with using that intermediary if need be, but would love to hear that mutt could talk directly to Office365 without using IMAP. Andy -- Andrew D. Arenson (he/him