(setq mu4e-mu-binary "/usr/local/bin/mu")
(setq mu4e-maildir (expand-file-name "~/.email/work"))
(setq mu4e-drafts-folder "/Drafts")
(setq mu4e-sent-folder "/Sent Items")
(setq mu4e-refile-folder "/Archives/.2015")
(setq mu4e-trash-folder "/Trash")
(setq mu4e-get-mail-command "~/config/mbsync/sort_and_fetch.sh"
mu4e-update-interval 120
mu4e-headers-auto-update t)
!#/bin/bash
imapfilter
mbsync -c ~/config/mbsync/.mbsyncrc work
pkill -2 -u 1000 mu
sleep 1
mu index --maildir=/home/makkus/.email/work
Hi,
Le mer 1 avr. 2015 02:06, makkus <mak...@gmail.com> a écrit :
Ah, right. Good catch, thanks.
Turns out mbsync didn't like me just moving my email directory to a new computer for some reason. Re-downloaded all mail from scratch and
FWIW, I use offlineimap and did not get this kind of error. At best it is configured in the init file, at worst you can create an offlineimap.py python script. I am not clear what the advantages of mbsync over offlineimap are by the way.
Best,
Charles.
FWIW, I use offlineimap and did not get this kind of error. At best it is configured in the init file, at worst you can create an offlineimap.py python script. I am not clear what the advantages of mbsync over offlineimap are by the way.
Hi allI started using mu4e today and have a similar issue but it also maybe that i dont know what im doing ;-)i setup mu4e with offline imap and it does auto launch offlineimap and sends/receives emails yet if im in my inbox i have to go out of the inbox to the default mu4e buffer view and re-enter the inbox to see new emails?any clue anyone?