[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug-mailutils] Re: Bugs in movemail with IMAP folders

From: Thomas Guyot-Sionnest
Subject: [bug-mailutils] Re: Bugs in movemail with IMAP folders
Date: Tue, 10 Feb 2009 07:39:51 -0500
User-agent: Thunderbird (X11/20090105)

On 10/02/09 04:11 AM, Sergey Poznyakoff wrote:
> Thomas Guyot-Sionnest <address@hidden> ha escrit:
>> The first two can be debugged without access to an IMAP server (URL
>> parsing bugs). I experienced them with an url of the form
>> "imap://user:address@hidden/Public Folders/Test"
> This URL is invalid. The correct way to write it is:
>   imap://user:address@hidden/Public%20Folders/Test

The exact url above triggers the parse error too. Even removing the %20
does it. If I skip it, I get the Invalid Argument error as well
(with/without %20)

It does work (just like the one with a space) with 1.2.

>> 1. Parse Error in mailbox/url.c:363
> It is not. If the scheme part does not contain ':', it is not a valid
> URL, and url_parse0 should bail out immediately, which it does.
>> I'm not sure what the exact fix is, but returning 0 instead of
>> MU_ERR_PARSE works around it and leads to the 2nd bug
> No, that's wrong. This will trigger a cascade of mishandlings (which are
> not necessarily bugs, because the calling code does not expect that
> mu_parse can return 0 on a malformed URL), which is what you experienced.

I figured - that's just a dirty hack to get past this wrongly failing
check. :)

>> 3. On the default folder (INBOX) or once the two bugs above are fixed, I
>> always get the following error if movemail can successfully connect to
>> IMAP and get the folder's content:
>> Default folder: Cannot append message 1: Cannot allocate memory
> I cannot reproduce it. Could you please give exact steps needed to get
> this error?

$ /opt/mailutils/bin/movemail -p imap://<user>:<pw>@<host>/ /tmp/mbox
Cannot append message 1: Cannot allocate memory

The server is Exchange 2003

I'm not sure how I can debug this with a debugger, but I traced the
error (printed in movemail/movemail.c:244) using printf's

The status is cascaded from these:

libproto/mbox/mbox.c:1293  status = mbox_append_message0()

libproto/mbox/mbox.c:1435  status = mu_envelope_aget_sender() - returned
trough the default statement in switchcase

mailbox/envelope.c:154 - I'm lost in defines now ;)

Anything else I can do to help figuring out?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]