mailsync-list

[Mailsync-list] Trouble Syncing Remote Courier to Local Store

[Michael H. <pd...@gm...>]

Hi, all,

I've been trying to sync a remote Courier IMAP server with a local
store in hopes of using mutt with the local files.  I'm certain I've
bolloxed something in my configuration, but I'm not sure what.

This is the Courier store:

store puddingbowl {
        server  {mail.foo.org/ssl/novalidate-cert/user=foo}
        ref     {mail.foo.org}
        pat     INBOX.*
        prefix  INBOX.
        passwd  bar
}

This is the local store:

store localdirectory {
        pat     Mail/%
        prefix  Mail/
}

When I run Mailsync, it fails on the first subdirectory:

Sent/sent_0904: Error: Can't open mailbox Mail/Sent/sent_0904: no such mailbox
Error: Couldn't open Mail/Sent/sent_0904

On the remote store, that'd be INBOX.Sent.sent_0904.

I'm pretty sure my local configuration is what I've messed up, because
when I run "mailsync puddingbowl," it reports all folders and
subfolders.  I guess the problem I'm having is configuring the local
store to recreate the Maildir structure of the remote Courier store.

I read most of the list archives last night before subscribing and
bothering everybody, and I saw a few similar issues, but not any
matches that helped.  I will be deeply appreciative of any help
offered.

Regards,
Michael

-- 
Michael Hall
mp...@pu... | http://mph.puddingbowl.org
"Y'know, spoons are the forks of silverware!"
- Charlie the Australopithecine

Re: [Mailsync-list] Trouble Syncing Remote Courier to Local Store

[Tomas P. <tp...@so...>]

On Tue, 1 Mar 2005, Michael Hall wrote:

> I've been trying to sync a remote Courier IMAP server with a local
> store in hopes of using mutt with the local files.  I'm certain I've
> bolloxed something in my configuration, but I'm not sure what.

Not necessarily.

> This is the Courier store:
>
> store puddingbowl {
>        server  {mail.foo.org/ssl/novalidate-cert/user=foo}
>        ref     {mail.foo.org}
>        pat     INBOX.*
>        prefix  INBOX.
>        passwd  bar
> }
>
> This is the local store:
>
> store localdirectory {
>        pat     Mail/%
>        prefix  Mail/
> }
>
> When I run Mailsync, it fails on the first subdirectory:
>
> Sent/sent_0904: Error: Can't open mailbox Mail/Sent/sent_0904: no such mailbox
> Error: Couldn't open Mail/Sent/sent_0904
>
> On the remote store, that'd be INBOX.Sent.sent_0904.

* have you tried to synchronize *one single* mail folder only? Does that
   work?
* are you using the latest mailsync?
* does the mail folder that fails above allready exist locally?
* how does the local Mail/Sent look like? Does it contain mails by itself
   as well as subfolders?
* how does the remote mail folder look like? Does that one contain mails
   as well as subfolders?
* what is your local mailformat? mbox?

Greets,
*t

-- 
--------------------------------------------------------
   Tomas Pospisek
   http://sourcepole.com -  Linux & Open Source Solutions
--------------------------------------------------------

Re: [Mailsync-list] Trouble Syncing Remote Courier to Local Store

[Tomas P. <tp...@so...>]

On Thu, 3 Mar 2005, Michael Hall wrote:

> On Thu, 3 Mar 2005 10:15:05 +0100 (CET), Tomas Pospisek
> <tp...@so...> wrote:
>> On Tue, 1 Mar 2005, Michael Hall wrote:
>>
>>> I've been trying to sync a remote Courier IMAP server with a local
>>> store in hopes of using mutt with the local files.  I'm certain I've
>>> bolloxed something in my configuration, but I'm not sure what.
>>
>> Not necessarily.
>>
>
> Well, this is embarrassing.
>
> I thought I had the latest version through fink's unstable branch. It
> turns out that hasn't been updated since 4.5. I wrote the maintainer
> asking for some help building the newest version and he said he's
> pretty much retired and running Debian now, and asked if I wanted to
> take over the package.
>
> So for now I'm going to follow some pointers he gave me to get the
> latest version built.
>
> Sorry to spend so much time on a message that implied I had all the
> bases covered but the configuration.

Absolutely no problem :-)
*t

-- 
--------------------------------------------------------
   Tomas Pospisek
   http://sourcepole.com -  Linux & Open Source Solutions
--------------------------------------------------------