Hi, I *think* i've found the reason for the lagginess. Hopefully what's here will be of use to others.
With mutt, for this address I make a config file, launch mutt in a screen with -F.On the remote system, I have a lot of different folders which I'll use with different email addresses. These email addresses are aliases to the main
account. What was happening before (mutt v.1.x) was mutt would log in, scan theimap folders i'd configured for it in .muttrc-lists (and *only* those folders, no others) then return and this was quick on an average dsl line.
What is happening now (mutt v.2.x) is it's scanning everything under themain account. There's a lot of mail there. It's this which is taking the time. This was found using -d 2 with mutt. If more than say 30s elapses between moving pages or moving the highlight bar, when it's moved again it scans the entire mailspool again. This is laggy on a 100MBit connection.
Right now I don't know if the old mutt to new mutt is the cause or if there's been a change that they at the mail hosting have done which has occurred at the same time as mutt v1 -> mutt v2. It might not be an issue with mutt at all.Maybe this isn't the ideal way to have mutt and imap? Some setups have an imap cache running locally. Is this better than running imaps access
from .muttrc ? -- J.
signature.asc
Description: PGP signature
