John Goerzen <[EMAIL PROTECTED]> writes:

> On Wed, May 03, 2006 at 02:11:47PM -0700, Brian Nelson wrote:
>> >> trying to sync between two IMAP servers (both courier 0.47-13, the
>> >> remote one using ssl), I get:
>> >
>> > Did you enable restoreatime in your config file?
>> 
>> Nope.
>
> OK, I'm going to need some more information from you then.  I'm using
> 4.0.12 here and am not having trouble at all.
>
> Can you send me along your config file, and also tell me at what point
> do you get the error?

The error happens immediately on the first folder.  Here's the config
file:

[general]
accounts = Personal, Lists
ui = Noninteractive.Basic, Noninteractive.Quiet
maxsyncaccounts = 2

[Account Lists]
localrepository = Local
remoterepository = RemoteLists
autorefresh = 10
maxconnections = 3

[Account Personal]
localrepository = Local
remoterepository = RemotePersonal
maxconnections = 3
autorefresh = 1

[Repository Local]
type = IMAP
remotehost = localhost
ssl = no
remoteuser = nelson
remotepassfile = ~/.offlineimap.pass
holdconnectionopen = yes

[Repository RemoteLists]
type = IMAP
remotehost = mail.bignachos.net
ssl = yes
remoteuser = nelson
remotepassfile = ~/.offlineimap.pass
#preauthtunnel = ssh -q mail.bignachos.net '/usr/bin/imapd ./Maildir'
holdconnectionopen = no
folderfilter = lambda foldername: foldername not in ['INBOX', 
'INBOX.catchmedia',
                                                 'INBOX.debian']
#nametrans = lambda foldername: re.sub('^INBOX\.', '.', foldername)

[Repository RemotePersonal]
type = IMAP
remotehost = mail.bignachos.net
ssl = yes
remoteuser = nelson
remotepassfile = ~/.offlineimap.pass
#preauthtunnel = ssh -q mail.bignachos.net '/usr/bin/imapd ./Maildir'
holdconnectionopen = no
folderfilter = lambda foldername: foldername in ['INBOX', 'INBOX.catchmedia',
                                                 'INBOX.debian']
#nametrans = lambda foldername: re.sub('^INBOX\.', '.', foldername)
> Are you sure you have the current OfflineIMAP installed?  (Can you try
> removing and reinstalling it?)

Yeah, it was definitely 4.0.12, and the same error occurred on two
different machines after upgrading.  I'm using 4.0.11 right now though
so that I can still get my mail.  :)

-- 
Captain Logic is not steering this tugboat.

Reply via email to