On Tue, May 16, 2017 at 02:51:50PM +0800, Feng Liu wrote:
> This bothers me too. I'd rather use Fastmail instead since I suffered
> from this problem. Or just change the Gmail UI to English. This made me
> feel Gmail is not as good as it suppose to be.
If you wish I can share my .offlineimaprc with you:
[general]
accounts = Gmail
# this is used for folder name decode/encode.
pythonfile = ~/.offlineimap.py
[Account Gmail]
localrepository = Gmail-Local
remoterepository = Gmail-Remote
[Repository Gmail-Local]
type = Maildir
localfolders = ~/Mail/Gmail
nametrans = lambda foldername:
foldername.decode('utf-8').encode('imap4-utf-7')
[Repository Gmail-Remote]
type = Gmail
remoteuser = <youracco...@gmail.com>
remotepass = <yourpassword>
ssl=true
# if you cannot find this file, install `OpenSSL'
sslcacertfile = /etc/ssl/certs/ca-certificates.crt
realdelete = no
maxconnections = 5
nametrans = lambda foldername:
foldername.decode('imap4-utf-7').encode('utf-8')
This works find for Gmail. The .offlineimap.py, which handles the
decoding/encoding stuff, can be found at:
https://gist.github.com/gauteh/5402888
By the way, can Fastmail advoid this problem? Doesn't it use imap?
--
Yubin
> 在 2017年05月16日 16:14, Yubin Ruan 写道:
> > On Sun, May 14, 2017 at 09:33:46AM +1000, Cameron Simpson wrote:
> >> On 13May2017 17:32, Yubin Ruan <ablacktsh...@gmail.com> wrote:
> >>> I am wondering whether it is possible to tell mutt to prefetch mails
> >>> folder by
> >>> folder so that I can read mails more quickly without waiting for the
> >>> "Fetching
> >>> mails..." every time.
> >>>
> >>> I have set up mutt's cache, so it helps a little, but it is still slow
> >>> because I
> >>> have to fetch the mails before mutt can cache them.
> >>>
> >>> I know there is something like `fetchmail', but, setting up it is tricky,
> >>> especially with a IMAP server (or, do you have good references?)
> >> The other common solution for IMAP mail accounts is offlineimap, which will
> >> mirror IMAP accounts to local storage.
> >>
> >> Because mutt is single threaded, all "prefetch" arrangements tend to store
> >> the mail locally. This is several advantages:
> >>
> >> - you don't need to configure mutt to access a remote mailbox
> >>
> >> - if you're offline all your mail is still there (as of the last update)
> >>
> >> - access is _very_ fast, because it is local file access
> >>
> >> - if you run a local mail system, you can reply to email even when
> >> offline;
> >> it will queue locally on your machine until there is network access.
> >> I find this great for train trips. This also means you don't need mutt
> >> to
> >> know SMTP settings; just deliver locally via the "sendmail" command.
> >>
> >> The advantage of offlineimap is that (by default) it mirrors your IMAP
> >> account, keeping a local set of mail folders matching upstream. This means:
> >>
> >> - you can still access you imap account (eg through a phone or other
> >> device)
> >>
> >> - changes you make locally via mutt, such as deletions of moving messages
> >> or marking them read etc, are pushed upstream to your IMAP account for
> >> you
> >>
> >> Offlineimap _is_ a little tricky to set up, but once running you can let it
> >> look after the mirroring in the background.
> > Yes offlineimap _is_ very tricky to setup. It cannot handle non-ascii
> > characters
> > correctly. I have several folders on the Gamil server whose name is in
> > Chinese.
> > I setup a `nametrans' in the .offlineimaprc:
> >
> > nametrans = lambda foldername:
> > foldername.decode('imap4-utf-7').encode('utf-8')
> >
> > it works great in the first download, but will throw some encoding/decoding
> > errors
> > in the sync afterwards:
> >
> > 'ascii' codec can't decode byte 0xe9 in position 8: ordinal not in
> > range(128)
> >
> > I don't know why a software would only support ascii in the 21st century...
> >
> > --
> > Yubin
>
>
