Re: nnimap-request-accept-article vs Cyrus IMAP

[Daniel Pittman <daniel@rimspace.net>]

Dave Goldberg <david.goldberg6@verizon.net> writes:
>>> Gijs Hillenius <gijs@hillenius.net> writes:
>>>> I whirled a new gnus just now. Still not. (sorry). Is there a switch I
>>>> can throw to increase the verbosity in the *imap log*?
>
>>> Nope, sorry.
>
>>> Try edebugging through `nnimap-request-accept-article' and see what
>>> happens. 
>
>> OK, I'll try that when I get back to work tomorrow.  Unfortunately
>> remote access to work is limited to an interface that doesn't work
>> with Gnus.
>
> I stepped through nnimap-request-accept-article on both Cyrus and Exchange
> servers while doing GCC.  In the Exchange case, the function winds up with
> an "OK APPEND completed" message from the server.  In the Cyrus case I get
> "NO Message contains bare newlines" back from the server.

Oh, Cyrus, you picky thing.  It hates non-RFC email with a passion and will
reject it out of hand where other tools (eg: *everything* else) will accept
it and just cope.[1]

In this case the message that is being added ends, as noted, with something
other than the spec-mandated CR-LF sequence.  The same sort of fault will
occur for anything with non-7-bit characters in headers[2], and so on.


Gnus, or the IMAP thing, is going to have to be much more careful about
encoding of email as it goes in to IMAP for this to work.

        Daniel

Footnotes: 
[1]  They may fail in other ways, by guesstimating size, or not being able to
     search or sort that email, etc, though.

[2]  ...though there is a setting to have it mutilate them that /may/ apply
     other than in the LMTP protocol.

-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons