Hi Allie, On Tuesday, May 17, 2005, you wrote: >>> Because TB! doesn't yet observe all the rules of the IMAP protocol >>> and just ignores many of the commands issued by the server.
>> Interesting enough. Do you have any concrete examples handy?
> Early in my Mulberry days, I had a problem with Mulberry not
> recognizing some signed messages as such. However, TB! had no such
> problems. It turned out that Mulberry followed the IMAP protocol to the
> letter and retrieves only that much message header information
> required. If the IMAP server was not buggy it would send the
> information about whether or not the message was signed. I reported
> this to MDaemon support and a fix was soon implemented.
This is an odd statement. The IMAP server doesn't know if a message
is signed or not, all it knows is text. The only way a client knows
a message is signed is if it does a BODYSTRUCTURE call on the
message, and examines the results. Take for example Martin Schoch's
email with the subject "Connection center observation". That is a
signed message, and here is the IMAP communication to find out what
the format of the message is.
A05 UID FETCH 41489 (BODYSTRUCTURE)
* 41026 FETCH ( UID 41489 BODYSTRUCTURE ( ( ( "text" "plain" (
"charset" "us-ascii" ) NIL NIL "quoted-printable" 605 20 NIL NIL
NIL)("application" "pgp-signature" NIL NIL NIL "8bit" 261 NIL NIL NIL)
"signed" ("protocol" "application/pgp-signature" "micalg" "pgp-sha1"
"boundary" "----------7A1A31253B732244") NIL NIL)("text" "plain"
("charset" "us-ascii") NIL NIL "7bit" 271 4 NIL ("inline" NIL) NIL)
"mixed" ("boundary" "===============1216487755==") NIL NIL))
A05 OK FETCH completed.
Okay, that's a big mess, and not easily understandable for most...
gives me a headache, but the IMAP server really doesn't know what any
of that means... when I say that, I mean, it doesn't know what PGP
protocols are, or it doesn't know that this email is a signed email.
It just knows that the email is made up of 4 parts, and the parts
break down like this:
Entity Content-Type Encoding
1 multipart/signed
1.1 text/plain quoted-printable
1.2 application/pgp-signature
2 text/plain 7bit
Correct me if I'm wrong of course, or I am way off on what you mean.
Could it be that Mulbery was just not handling the bodystructure
response correctly? Or was following the RFCs to the letter, and
the IMAP server was sending data back slightly "broken"?
I'd be interested to see the thread on this error from Mulbery to
find out what they "fixed" or how they handled this issue.
> Tony's issue is just another example of how Mulberry depends on the
> IMAP server for parsing headers. This is part of the protocol.
[..]
This makes little sense at all... The only headers the IMAP server
should be "parsing" are the ones used to generate the BODYSTRUCTURE
response. The headers involved for this can easily be fetched using
IMAP, the IMAP server shouldn't be "doing" anything with them, but
just returning the content. Unless his IMAP server is doing
something else to it... Here is a quick chat I had with my IMAP
server...
A04 UID FETCH 41256 (BODY[HEADER.FIELDS(Message-ID In-Reply-To References)])
* 40793 FETCH (UID 41256 BODY[HEADER.FIELDS ("Message-ID" "In-Reply-To"
"References")] {248}
Message-ID: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
)
I guess to some extent the IMAP server "parses" the headers, but
that is meerly to read them. Unless I'm totally miss-understanding
what you are talking about. It certainly is curious that the mail
behaves correctly when copied to a local store, and not server side.
All the information required to reply and compose a properly
formatted message are on the IMAP server, unless they're just not
fetching it correctly, or parsing it when they do fetch it.
--
Jonathan Angliss
<[EMAIL PROTECTED]>
pgpUCqzkzGdqo.pgp
Description: PGP signature
________________________________________________________ Current beta is (none) | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
