Good morning, mutt-dev:
At the beginning of this year, our Exchange servers were updated to Exchange
2013 (15.0.1365.7), at which point I and other MIT mutt users began to suffer
greatly from mutt connections to the Exchange IMAP server timing out after 5
minutes if mutt was anywhere other than
On Sat, Sep 15, 2018 at 11:23:55AM -0400, John Hawkinson wrote:
> I wonder if there's any appetite for reducing the default
> "imap_keepalive," either uncondionally all the time [...] or
> adaptively in response to servers identifying themselves
I feel your pain, but 5 minutes is way below the RFC
Thanks, Kevin.
Kevin J. McCarthy wrote on Sat, 15 Sep 2018
at 15:51:47 -0700 in <20180915225147.gb5...@afu.lan>:
> > I wonder if there's any appetite for reducing the default
...
> I feel your pain, but 5 minutes is way below the RFC specified minimum.
> I think likely the admins of the server d
On Sat, Sep 15, 2018 at 07:33:21PM -0400, John Hawkinson wrote:
> > Peeking in the function myself, in the "normal" case where the mailcap
> > contains a '%s', Mutt calls mutt_system(), which would send keepalives.
> > However, if the mailcap entry is missing a '%s' filename specifier, I
> > see Mu
