Re: [fetchmail-devel] Fetchmail IMAP with FETCH x RFC822

[Georges-Etienne L. <le...@le...>]

On 24-Apr-08, at 4:32 AM, Matthias Andree wrote:

> On Thu, 24 Apr 2008, Matthias Andree wrote:
>
>> Georges-Etienne Legendre <le...@le...> writes:
>>
>>> When fetchmail fetch a message, it does this in 2 steps:
>>>
>>> 1) . FETCH x RFC822.HEADER
>>> 2) . FETCH x BODY.PEEK[TEXT]
>>>
>>> However, there is a problem with the Gmail IMAP implementation.  
>>> Gmail IMAP doesn't return a valid header if there is an encoded  
>>> field in the header.
>>> Instead, we have to use to get the whole mail in only one fetch:
>>>
>>> 1) . FETCH x RFC822
>>>
>>> The problem is documented here:
>>> http://groups.google.com/group/Gmail-Help-POP-and-IMAP-en/browse_thread/thread/06b49fde4a8dde08/d283b040984e4054
>>>
>>> Is there a way to tell to fetchmail to use the second approach?
>>
>> Sorry, fetchmail cannot do this at the moment.
>>
>> Is there a way to tell Google not to violate the protocol? Standards
>> are there for a purpose... please ask Google support to fix the  
>> server
>> software.

In fact, for this specific issue, I consider this as a bug in their  
IMAP implementation. For a strange reason they have decided to change  
the encoding from UTF-8 to ISO-8859-1 (bad thing, this doesn't follow  
standards), but have introduced a bug in doing so.

In any case, I think it would be great to support both way to fetch a  
message in IMAP (header+body, or header then body). I tried to  
enhanced fetchmail to add a configuration (like "single header-body  
fetch"). It looks like a bit more complicated and my modified version  
isn't able to completely fetch the message. It freeze.

Anyone willing to co-develop a patch for this feature? I don't think  
it's a big modification.
-- 
Georges-Etienne Legendre