[MacPorts] #59707: neomutt @20191111_0+gdbm+idn+mutt does not read header cache properly

[MacPorts]

#59707: neomutt @20191111_0+gdbm+idn+mutt does not read header cache properly
----------------------+------------------------
  Reporter:  arappe   |      Owner:  lbschenkel
      Type:  defect   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.6.2
Resolution:           |   Keywords:
      Port:  neomutt  |
----------------------+------------------------

Comment (by arappe):

 Dear Leonardo,

 Thanks for asking. I have done some more debugging.
 Yes, I still have the same problem.
 Working theory: neomutt caching fails if the INBOX folder is too big.

 1. I did a fresh install of everything. (Mac with OS X 10.15.3)
 % sudo rm /opt/local
 deleted /Applications/Xcode.app
 installed Xcode from App Store
 % sudo xcode-select --install
 installed macports
 % sudo port selfupdate
 % sudo port upgrade outdated
 % sudo port install neomutt +gdbm+idm+mutt

 I find that every time I run mutt to get my work INBOX, it scans the
 header cache, rejects it, decides to get a new header cache, loads the
 whole header cache from the server, and says that it cannot open the
 inbox.
 On this same installation, several other things succeed:
 I can get header cache and body cache for a gmail account. (small, , 1GB)
 I can get header cache and body cache for a subdirectory of my work email.
 For example, I have one month's worth of mail stored in +INBOX/apr2013
 (small, 50MB total for folder)
 So my only guess is that the 55 GB folder +INBOX is too big?

 2. On another Mac, neomutt @20180716_1+gdbm+idn+mutt works for my full
 work INBOX. It scans the header cache, agrees that it's OK, only gets the
 few new headers since last run, and functions more or less as normal. I
 don't know how and/or have not been successful in compiling this old 2018
 snapshot on the computer mentioned in point #1 above. I have followed
 instructions for how to acquire an old snapshot but I haven't been able to
 get it to work. (I'm sure I'd prefer that we get the current version to
 succeed rather than running back to this old snapshot anyway.) So this
 suggests that mutt can in principle handle this iNBOX and IMAP setup and
 etc. So I am just left with thinking that we have hit a size limit that
 was recently imposed? Just a guess.

 I have been investigating moving my INBOX stuff into lots of subfolders.
 But if neomutt could be fixed to handle the full INBOX, that'd be ideal.
 Any questions for me? ideas to try?

 Andrew

-- 
Ticket URL: <https://trac.macports.org/ticket/59707#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS