Issues - rgrove/larch

rgrove / larch

Description:

Larch syncs messages from one IMAP server to another. Awesomely.

Sort by: Priority | Votes | Last Updated

Loading…

16.

0 votes

bug
x

Larch 1.1.0.dev dies with an 'Illegal instruction' error.
1 comment Created about 1 month ago by rgrove

Title

Body
A user has reported that Larch dies consistently with an 'Illegal instruction' error while scanning a large Gmail mailbox. Some preliminary research indicates this error may be coming from SQLite, and may be caused by memory exhaustion, but more investigation is needed. See http://groups.google.com/group/larch/msg/83bc2f3f90186944
or cancel

A user has reported that Larch dies consistently with an 'Illegal instruction' error while scanning a large Gmail mailbox. Some preliminary research indicates this error may be coming from SQLite, and may be caused by memory exhaustion, but more investigation is needed.

See http://groups.google.com/group/larch/msg/83bc2f3f90186944

Comments

rgrove Sun Nov 08 15:54:27 -0800 2009 | link

Reproduced this once after a very long (hours and hours) transfer session, but still haven't identified the cause, and I haven't been able to reproduce it since.

Comment
Reproduced this once after a *very* long (hours and hours) transfer session, but still haven't identified the cause, and I haven't been able to reproduce it since.
or cancel

Parsed with GitHub Flavored Markdown
15.

0 votes

gmail quirk
x

Work around Gmail "Some messages could not be FETCHed" errors
0 comments Created about 1 month ago by rgrove

Title

Body
When Gmail returns a "Some messages could not be FETCHed" error in response to a batch fetch operation, Larch should retry the fetch, gradually decreasing the batch size each time until it succeeds and then marking and ignoring the corrupt message. See http://groups.google.com/group/larch/msg/6e045bba542fbde2
or cancel

When Gmail returns a "Some messages could not be FETCHed" error in response to a batch fetch operation, Larch should retry the fetch, gradually decreasing the batch size each time until it succeeds and then marking and ignoring the corrupt message.

See http://groups.google.com/group/larch/msg/6e045bba542fbde2

Comments

Parsed with GitHub Flavored Markdown
19.

0 votes

bug
x

Net::IMAP
x

Message with newline in subject hangs Net::IMAP
0 comments Created 27 days ago by rgrove

Title

Body
A message with a newline in the subject causes Net::IMAP (and thus Larch) to hang when the message is FETCHed. This message can be used to reproduce the problem: http://pieisgood.org/misc/larch/subjplusonly.eml
or cancel

A message with a newline in the subject causes Net::IMAP (and thus Larch) to hang when the message is FETCHed.

This message can be used to reproduce the problem: http://pieisgood.org/misc/larch/subjplusonly.eml

Comments

Parsed with GitHub Flavored Markdown
9.

1 vote

feature
x

Option to use Date header to set internal date on destination
0 comments Created 4 months ago by rgrove

Title

Body
Add an option to use the Date header of a message to set the internal date on the destination server rather than using the internal date from the source server (which in some cases is incorrect).
or cancel

Add an option to use the Date header of a message to set the internal date on the destination server rather than using the internal date from the source server (which in some cases is incorrect).

Comments

Parsed with GitHub Flavored Markdown
21.

0 votes

feature
x

Larch should continue processing after exhausting retries on a recoverable error
0 comments Created 23 days ago by rgrove

Title

Body
Currently, when Larch encounters a recoverable error, it retries 3 times and then gives up if the error still occurs, halting all mail processing. Ideally, Larch should just skip the problematic message and continue processing other messages.
or cancel

Currently, when Larch encounters a recoverable error, it retries 3 times and then gives up if the error still occurs, halting all mail processing. Ideally, Larch should just skip the problematic message and continue processing other messages.

Comments

Parsed with GitHub Flavored Markdown
22.

1 vote

feature
x

Option to delete messages from source
0 comments Created 22 days ago by rgrove

Title

Body
Add an option to delete message from the source after syncing or if they already exist an the destination.
or cancel

Add an option to delete message from the source after syncing or if they already exist an the destination.

Comments

Parsed with GitHub Flavored Markdown
24.

1 vote

gmail quirk
x

Gmail error: 'Unable to append message to folder'
3 comments Created 12 days ago by marc10

Title

Body
when i try to copy emails with blank subject lines to Gmail, i get an error: "Unable to append message to folder." Any idea how to resolve this? [Dec 07 03:06:18] [info] copying message: user@email.com - Re: [Dec 07 03:06:19] [info] user@email.com@imap.gmail.com: Net::IMAP::NoResponseError: Unable to append message to folder (Failure) (will retry) [Dec 07 03:06:21] [info] user@email.com@imap.gmail.com: Net::IMAP::NoResponseError: Unable to append message to folder (Failure) (will retry) [Dec 07 03:06:24] [info] user@email.com@imap.gmail.com: Net::IMAP::NoResponseError: Unable to append message to folder (Failure) (will retry) [Dec 07 03:06:27] [error] Net::IMAP::NoResponseError: Unable to append message to folder (Failure) (giving up)
or cancel
when i try to copy emails with blank subject lines to Gmail, i get an error: "Unable to append message to folder."

Any idea how to resolve this?
```
[Dec 07 03:06:18] [info] copying message: user@email.com - Re: 
[Dec 07 03:06:19] [info] user@email.com@imap.gmail.com: Net::IMAP::NoResponseError: Unable to append message to folder (Failure) (will retry)
[Dec 07 03:06:21] [info] user@email.com@imap.gmail.com: Net::IMAP::NoResponseError: Unable to append message to folder (Failure) (will retry)
[Dec 07 03:06:24] [info] user@email.com@imap.gmail.com: Net::IMAP::NoResponseError: Unable to append message to folder (Failure) (will retry)
[Dec 07 03:06:27] [error] Net::IMAP::NoResponseError: Unable to append message to folder (Failure) (giving up)
```
Comments

rgrove Mon Dec 07 10:05:39 -0800 2009 | link

In my testing, Gmail accepts blank subject lines just fine. In any case, this message does appear to have a subject line (notice the 'Re:').

Gmail returns the "Unable to append message to folder" error when it can't parse the message for some reason, so it's likely there's something else wrong with this message that's causing the problem.

I don't suppose you'd be willing to share the raw message source with me, would you? I understand if you'd rather not.

Comment
In my testing, Gmail accepts blank subject lines just fine. In any case, this message does appear to have a subject line (notice the 'Re:'). Gmail returns the "Unable to append message to folder" error when it can't parse the message for some reason, so it's likely there's something else wrong with this message that's causing the problem. I don't suppose you'd be willing to share the raw message source with me, would you? I understand if you'd rather not.
or cancel

rgrove Mon Dec 07 10:15:27 -0800 2009 | link

Possibly related: https://bugzilla.mozilla.org/show_bug.cgi?id=465670

Comment
Possibly related: https://bugzilla.mozilla.org/show_bug.cgi?id=465670
or cancel

marc10 Mon Dec 07 10:22:25 -0800 2009 | link

yes, I have read about others having the same problem:
http://groups.google.com/group/gmail-power-users/browse_thread/thread/bfd949e7a2e19c2b/b958689303b88935?pli=1

thanks rgrove. you are right, the subject does have 'Re:'

But there is something about certain subjects that causes a problem. I had the same issue when I used my mail client (Mail.app for OSX) to copy email messages. It always get hung up on blank subject lines (or those with just Re:).

I would be more than happy to share the raw message with you. I'd love to isolate the issue myself. I have your email address from your GitHub profile. I'll send it over.

Thanks.

Comment
yes, I have read about others having the same problem: http://groups.google.com/group/gmail-power-users/browse_thread/thread/bfd949e7a2e19c2b/b958689303b88935?pli=1 thanks rgrove. you are right, the subject does have 'Re:' But there is something about certain subjects that causes a problem. I had the same issue when I used my mail client (Mail.app for OSX) to copy email messages. It always get hung up on blank subject lines (or those with just Re:). I would be more than happy to share the raw message with you. I'd love to isolate the issue myself. I have your email address from your GitHub profile. I'll send it over. Thanks.
or cancel

Parsed with GitHub Flavored Markdown