On Tue, 12 Feb 2008, Patrick Hamel (path) wrote:
I have little information on the server side library used, I'm querying
that at the moment.
What does the server say in its greeting banner? You can see this in
mtest when the session starts up. Most servers identify what they are.
-- Mark -
Thank you Mark,
I have little information on the server side library used, I'm querying
that at the moment. C-client on the end user app side for sure.
Thanks for the RFC reference, that helps to sort it all.
Cheers,
PatH
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTE
Here's some additional information about your problem:
According to test, the server sent the following as a BODYSTRUCTURE:
(("audio" "wav" ("name" "My.wav") NIL NIL "Base64" 113287
NIL ("inline" ("filename" "My.wav")) NIL NIL)("message" "rfc822" NIL NIL
NIL NIL 113287 NIL) NIL NIL NIL NIL N
Bad news: the IMAP server you are using is defective and sends a
BODYSTRUCTURE that does not comply with the IMAP specification.
Consequently, the rule of GIGO ("garbage in, garbage out") applies.
The only thing that you can do is fix/replace the broken server.
On Tue, 12 Feb 2008, Patrick Hame
Thanks,
I never used mtest before, but that nice to have :)
Here's how it looks like from mtest (below); I'm thinking the parser is
expecting something that is not there in the enclosed message (bad
message).
The message contains these parts:
[multipart/mixed]
+-[audio/wave]
+-[message/rfc822]
mail_fetchstructure() (or one of its alternative forms) is most certainly
the correct thing to get the body structure of a message and run it down.
You certainly should not be playing with any driver settings either.
Have you tried running the mtest tool (bundled with the UW IMAP toolkit)
on t
Hi,
I'm not sure I'm doing something wrong but just in case, let me bounce
that off of the experts.
I'm trying to walk all the parts of a multipart message. One of the part
is a message/rfc822 part which contains a multipart message too.
So the code I have looks a little like this:
BODY *bo
