rgrove / larch
- Source
- Commits
- Network (8)
- Issues (7)
- Downloads (3)
- Graphs
-
Branch:
master
-
I am running Larch 1.0.2 and getting this error which stops the transfer process.
[fatal] can't dup NilClassComments
-
I just completed moving email from an IMAP account into Gmail. Unfortunately, I now have a folder in my Gmail account called INBOX/Sent Items while my Gmail's Sent Items is empty.
What is the proper syntax to move email into Gmail's Sent Mail?
I tried:
--from-folder 'INBOX.Sent Items' --to-folder 'Sent Mail'but that created a new folder on Gmail called [Imap]/Sent Mail.
Comments
-
Got the latest source and got bitten by:
undefined method `strip'
when passing "--exclude Trash Spam" on the commandline, without a config file.Same as reported in:
http://groups.google.com/group/larch/browse_thread/thread/4ec6ee1a5c754c60/6e045bba542fbde2?#6e045bba542fbde2Comments
-
1 comment Created about 1 month ago by rgroveGmail doesn't allow leading or trailing whitespace in folder namesgmail quirkxApparently Gmail doesn't allow whitespace before or after folder names, but many other IMAP servers do. Larch should trim folder names when Gmail is the destination in order to prevent problems.
Comments
-
1 comment Created about 1 month ago by rgroveLarch doesn't recopy deleted messages to the destination until a second attemptbugx- Use Larch to copy a bunch of messages from server A to server B.
- Delete those messages on server B.
- Run Larch again. It will see that the messages have been deleted, but will not recopy them.
- Run Larch again. This time it will recopy the deleted messages.
Larch should recopy the deleted messages the first time it sees that they're gone.
Comments
- Use Larch to copy a bunch of messages from server A to server B.
-
1 comment Created 2 months ago by rgrovebugx"all" config option is not being respected in 1.1.0.devnot yet reproducedxA user has reported that the "all" config option is not being respected in the latest Larch dev gem. See http://groups.google.com/group/larch/msg/bc80ea058a9ca123
Comments
-
1 comment Created 2 months ago by rgroveDon't use case-sensitive name comparisons for INBOXbugxLarch currently uses some case sensitive folder name comparisons, which can cause problems when dealing with the INBOX folder, which is defined in RFC 3501 as being case insensitive.
See http://groups.google.com/group/larch/browse_thread/thread/79b3797603654d13
Comments
-
1 comment Created 2 months ago by rgroveVerify that destination supports flags before setting thembugxLarch currently does not verify that the destination server supports all the flags/keywords being transferred from the source server before attempting to set them, which can result in failures.
Comments
-
1 comment Created 3 months ago by rgroveCertain domain names cause invalid URI errorinvalidxA user reported on the Larch mailing list that the IMAP URI
imaps://mail.example.noresults in an invalid URI error, whereasimaps://mail.example.comworks fine. Ruby's URI lib appears to be trying (and failing) to validate actual domain names.Comments
-
1 comment Created 3 months ago by rgroveProblems with Gmail folder names containing accented charactersbugxReported on the Larch mailing list at http://groups.google.com/group/larch/browse_thread/thread/294af0368c309bd
I 'am trying to synchronize my personnal IMAP (Dovecot) with my gmail account. The gmail locals are set to french, so Sent Mail folder is written in french with an accent. The problem is i connot use --to-folder option with an accent
Log messages:
creating mailbox: [Gmail]/Messages envoyés (this is the french name of Sent Mail folder) Net::IMAP::BadResponseError: Invalid Command (will retry)Looks like it tries to create a folder which should already exist on gmail...
Any clue? I've set my gmail account to english and used the "Sent Mail" name instead, but i really would like to find a better solution.
Comments
-
3 comments Created 3 months ago by rgroveGmail doesn't allow folder names longer than 40 characters (including delimiters)gmail quirkxReported on the Larch mailing list at http://groups.google.com/group/larch/browse_thread/thread/2f8e8dbc2fab0af5
/var/lib/gems/1.8/bin/larch --from imap://server1 --from-user user1@domain1 --from-pass password1 --to imaps://imap.gmail.com --to-user user2@gmail.com --to-pass password2 --all [Sep 01 17:30:01] [info] user2@gmail.com@imap.gmail.com: creating mailbox: INBOX/blabla/blablabla/blabla blabla 2008 [Sep 01 17:30:02] [info] user2@gmail.com@imap.gmail.com: Net::IMAP::NoResponseError: Folder name is not allowed. (Failure) (will retry) [Sep 01 17:30:03] [info] user2@gmail.com@imap.gmail.com: Net::IMAP::NoResponseError: Folder name is not allowed. (Failure) (will retry) [Sep 01 17:30:05] [info] user2@gmail.com@imap.gmail.com: Net::IMAP::NoResponseError: Folder name is not allowed. (Failure) (will retry) [Sep 01 17:30:09] [fatal] Net::IMAP::NoResponseError: Folder name is not allowed. (Failure) (giving up) [Sep 01 17:30:09] [info] 0 message(s) copied, 0 failed, 1 untouched out of 1 totalComments
According to the user who reported this, manually renaming the folder wasn't an option. I haven't had a chance to investigate this myself yet.
Actually, after some investigation, it appears that the spaces aren't the problem. The problem is that Gmail doesn't allow label names longer than 40 characters. Gmail doesn't actually support folder hierarchies and treats "INBOX/blabla/blablabla/etc." as a single label name, which is what causes the error.
-
0 comments Created 5 months ago by rgroveLarch incorrectly tries to set \Recent flag on messagesbugxWhen copying messages that have the
\Recentflag set on the source server, Larch tries to set the flag on the destination server as well. However, the IMAP spec prohibits clients from setting this flag. It seems many IMAP servers ignore this, but some (including Zimbra) return an error.Comments
-
The BlitzMail IMAP server implementation reportedly fails to adhere to the IMAP standard when sending ENVELOPE responses. It fails to quote or properly escape strings in some cases, which can cause Net::IMAP's response parser to hang.
Comments
-
1 comment Created 6 months ago by rgrovegmail quirkxPossible problem creating nested folders on Gmailnot yet reproducedxExcerpt from a user email to the Larch mailing list:
"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."Comments
-
Need to add an --exclude option to specify folder names (or regexes?) to exclude when using --all or --all-subscribed.
Should also add an --exclude-file option to allow exclusions to be specified in a text file.
Comments





This issue has already been fixed in the development version.