[fatal] mailbox not found: work/foo/bar

[phay]

First of all, thanks a lot for larch - its very useful.

I found that I couldn't transfer the entire tree in go (--all), as
larch choked on one particular folder:

From-server IMAP extract (insane logging):
S: * CAPABILITY IMAP4rev1 UIDPLUS IDLE LOGIN-REFERRALS NAMESPACE QUOTA
CHILDREN AUTH=DIGEST-MD5
S: * LIST (\HasChildren) "/" work/foo
S: * LIST (\HasNoChildren) "/" work/foo/bar
S: * LSUB (\HasChildren) "/" work/foo
S: * LSUB (\HasNoChildren) "/" work/foo/bar

Gmail IMAP extract:
S: * LIST (\HasNoChildren) "/" "work/foo"
S: * LSUB (\HasNoChildren) "/" "work/foo"

Gave this:

[Jun 15 19:40:37] [fatal] mailbox not found: work/foo/bar

I worked around the problem by pulling one folder at a time, which
worked fine, including for the folder which it had originaly choked
on.

My install on gentoo linux/workaround for the above:

1. git clone git://github.com/rgrove/larch.git
2. git clone git://gitorious.org/trollop/mainline.git
3. emerge highline
4. Make a list of folders on the 'from' server - I used the
contents of a thunderbird directory. E.g. something like:

find . -name '*.msf' | sed -e 's/.msf//' -e's/.sbd//g' -e
's/-1//' -e 's/.\///'|sort|uniq

5. create a file, with one line for each folder with a
simple format (allows mapping of folder names to different
labels on gmail):

from_format to_label

3. Feed into something like:

while read from to ; do
ruby -Imainline/lib:larch/lib \
larch/bin/larch \
--from imap://imap.example.foo --from-user XYZ --from-pass
OPW \
--to imaps://imap.gmail.com --to-user ABC --to-pass DEF \
--from-folder $from --to-folder $to
done

Thanks,

Paul

[Ryan Grove]

On Mon, Jun 15, 2009 at 12:04 PM, phay<lmi...@gmail.com> wrote:
> I found that I couldn't transfer the entire tree in go (--all), as
> larch choked on one particular folder:

*snip*

Thanks for the detailed report, Paul. I've created a ticket in the
Larch issue tracker to track this problem:
http://github.com/rgrove/larch/issues#issue/6

I'll try to reproduce (and hopefully fix) as soon as I have some free time.

- Ryan

[Martin Møller]

A possible hint in this case:

On the original account the, one IMAP folder is called:

* LIST (\Unmarked) "/" "Cabinet/Undervisning, optagelsespr&APg-ver, eksaminer, projekter, skema"

On the new account, after being created by Larch, the folder is instead called:

* LIST (\Unmarked) "/" "Cabinet/Undervisning, optagelsespr&-APg-ver, eksaminer, projekter, skema"

This extra '-' seems to be messing things up... Wonder what I can do to avoid that...

This is probably not the only issue, but certainly the first one I have spotted so far.

/Martin.

Den tirsdag den 11. september 2012 11.14.30 UTC+2 skrev Martin Møller:

I have experienced something similar the last few days when trying to migrate mails from one GroupWise account to another GroupWise account on the same server via Larch.

I noticed you couldn't reproduce the issue in 2009, but it seems there are still cases where this occurs...

I started with Thunderbird, which created a lot of folders, but seemed to run into trouble copying the mails in the folders.

Now it looks like Larch is happy, if the folder already exists on the recipient side, but if it does not, it seems to be fatal?

Would Larch not be supposed to try to create the folder, then? This is with dry runs, if it matters...

Would it be possibly to have a mode that simply skipped these 'fatal' folders and then you could do multiple runs of larch?

This is running the production version of larch as of 2012-09-11 (1.1.1)

Presently I'm excluding folder after folder in the hopes that Larch will eventually run the entire way through and I'll then have to look at the excludes after that...

/Martin.