Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

Add support for global folder prefixes #39

Open
rgrove opened this issue Jan 12, 2011 · 9 comments
Open

Add support for global folder prefixes #39

rgrove opened this issue Jan 12, 2011 · 9 comments
Labels

Comments

@rgrove
Copy link
Owner

rgrove commented Jan 12, 2011

See https://groups.google.com/forum/#!topic/larch/jc7cllhbnD4

@kars7e
Copy link

kars7e commented Feb 14, 2013

I would love if this feature got implemented... any chances?

@sudoremo
Copy link

+1, this is a must-have for me.

@jxchong
Copy link

jxchong commented May 4, 2015

Did this ever get implemented?

@rgrove
Copy link
Owner Author

rgrove commented May 4, 2015

Nope. I no longer actively develop or use Larch, and nobody has submitted a pull request that adds this feature.

@rahul286
Copy link

rahul286 commented May 5, 2015

@rgrove

use Larch

Are you using something else or don't need to move mails as part of daily job routine? We use larch quite frequently so wondering.

@rgrove
Copy link
Owner Author

rgrove commented May 5, 2015

I just haven't had a need to move large amounts of email in many years.

@rahul286
Copy link

rahul286 commented May 5, 2015

Great. I used this many times and can't thank you enough :-)

@rgrove
Copy link
Owner Author

rgrove commented May 5, 2015

That means a lot, @rahul286! I'm glad you found Larch useful.

@jxchong
Copy link

jxchong commented May 5, 2015

I found Larch because apparently Microsoft's support for "migrating" from our internal IMAP to Exchange Online/Offic365 consists of setting up email forwarding but not actual migrating the existing email content from one server to the other. While support for a global folder prefix would've helped a bit, I was able to mess around with folder structures enough to at least get my email migrated to office365... using Larch and only 11 emails failed to transfer (out of ~12k) because of the "Net::IMAP::ResponseParseError: unexpected token EOF (expected CRLF)"

So thanks so much! Hopefully Larch will keep working for a while and/or someone will pick up development in the future. This was a way better option than relying on imapsync.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants