On 09 Aug 19:34, Chris G wrote:
<snippity class="dnsfoo" />
You're doing what I used to do. I used to run mutt on a shell account at my hosting service. I do find that mutt over IMAP is (relatively) slow and clumsy compared with mutt and a real 'unix' mail spool though which is why I have moved to my present setup.
Weirdly, I've found using mutt and imap even on the vm itself is *quicker* than using mutt itself to access my mailspool. Less IO involved with my dovecot setup, and I have the header cache turned on, so it takes mutt less time to mess with the imap server than it does for it to scan the hdd every time it updates. Dovecot generates indexes (and because I use dovecot's deliver program to drop my mail in to my Maildirs, they're updated as the mail comes in...) which make accessing mail a lot quicker.
Unless you're talking mbox, in which case, it's all a complete loss!
I have two ADSL connections with different ISPs so, as long as the physical connection doesn't get killed (which means I'm stuffed anyway) I can get to my mail. In addition I 'spool' my incoming mail to a system at the hosting service in parallel with sending it to my home system so if I really screw things up (not a *rare* event) I can still get to see my mail.
Erm, so, it comes in your ADSL line and then gets streamed back out of it to the hosting service? Sounds like an interesting waste of bandwidth! Why not MX the hosting service first and then get that to forward to ADSL connection?