This project is read-only.

Unable to get body

Topics: Issues
Nov 4, 2013 at 4:01 PM
Hello,

I'm currently testing the imapx libary. The libary itself seems to work fine, until I try to recieve the content of a specific message. The Body only contains the following text.
  • 1 FETCH (UID 6 BODY[11.2.MIME] NIL BODY[11.2] NIL
Embeded objects and attachements are ok, but the body is "empty". It seems like this problem concerns only messages with one or more attachements AND html body. The body from Mails without attachements is OK.

The debug output from the SendAndRecevie out of the sample application is this.
IMAPX665 UID FETCH 6 (BODY.PEEK[11.2.MIME] BODY.PEEK[11.2])

* 2 FETCH (UID 6 BODY[11.2.MIME] NIL BODY[11.2] NIL)
IMAPX665 OK Completed (0.000 sec)
IMAPX666 UID FETCH 6 (BODY.PEEK[11.1.MIME] BODY.PEEK[11.1])

* 2 FETCH (UID 6 BODY[11.1.MIME] NIL BODY[11.1] NIL)
IMAPX666 OK Completed (0.000 sec)
What can I do to provide more debug information?
Coordinator
Nov 4, 2013 at 9:37 PM
Hi slxSlashi,

thank you for the provided debug information!
As you can see, the body part numbers which are being requested are invalid. This issue is connected with the issue I recently mentioned. I'm working on an update now, it should be ready in a couple of days.

Best regards,

Pavel
Dec 17, 2013 at 12:19 PM
Hi Pavel,
I was testing version 15 through the sample program on my mail server.
Unfortunately, in many emails I always have this 'BODY [1.1.MIME] NIL BODY [1.1] NIL)' or 'BODY [1.2.2.MIME] NIL BODY [1.2.2] NIL)' as the body of the message.
instead the embedded resource are quickly download now, great.
in a couple of messages instead the body is correct but does not show me the attachment.
Coordinator
Dec 17, 2013 at 4:50 PM
Hi GDEffe,

to solve this problem i need to know the structure of the message.

Please download the sample application from here: http://imapx.org/ImapX.Sample.zip

It contains an update, now you can use the context menu of each message to see the body structure. Please post here the body structures of the messages with which you experience the issue. (rmbr to post them as code, so it is easier to read)

Greets,

Pavel
Dec 17, 2013 at 5:07 PM
Hi Pavel,
thank you very much for your support!!!

This is the body structure for a message with body 'BODY [1.1.MIME] NIL BODY [1.1] NIL)': (I change to @xxxxxxxxxxxx.com :D)
(("TEXT" "PLAIN" ("CHARSET" "ISO-8859-15" "FORMAT" "flowed") NIL NIL "8BIT" 689 27 NIL NIL NIL)(("TEXT" "HTML" ("CHARSET" "ISO-8859-15") NIL NIL "8BIT" 4869 90 NIL NIL NIL)("IMAGE" "PNG" ("NAME" "dbabhgeb.png") "<part3.08010305.03000603@xxxxxxxxxxx.com>" NIL "BASE64" 7572 NIL ("INLINE" ("FILENAME" "dbabhgeb.png")) NIL) "RELATED" ("BOUNDARY" "------------060209060509010704000303") NIL NIL) "ALTERNATIVE" ("BOUNDARY" "------------010404030302080405070909") NIL NIL) BODY[HEADER.FIELDS (FROM DATE SUBJECT CONTENT-TYPE IMPORTANCE)
this is the body structure of a message with correct body but without the attachment (with thunderbird I see correctly the attachment):
((("TEXT" "PLAIN" ("CHARSET" "ISO-8859-15" "FORMAT" "flowed") NIL NIL "8BIT" 361 19 NIL NIL NIL)("TEXT" "HTML" ("CHARSET" "ISO-8859-15") NIL NIL "8BIT" 2988 61 NIL NIL NIL) "ALTERNATIVE" ("BOUNDARY" "------------020601080603050809010208") NIL NIL)
this is the body structure of a message with the body 'BODY[1.2.2.MIME] NIL BODY[1.2.2] NIL)' and the attachment instead is showed correctly
(((("TEXT" "PLAIN" ("CHARSET" "iso-8859-1") NIL NIL "QUOTED-PRINTABLE" 2714 118 NIL NIL NIL)("TEXT" "HTML" ("CHARSET" "iso-8859-1") NIL NIL "QUOTED-PRINTABLE" 9681 183 NIL NIL NIL) "ALTERNATIVE" ("BOUNDARY" "----=_NextPart_002_0037_01CEF728.3E0B8D20") NIL NIL)("IMAGE" "JPEG" ("NAME" "image002.jpg") "<image002.jpg@01CEF727.EBC95AB0>" NIL "BASE64" 6146 NIL NIL NIL)("IMAGE" "JPEG" ("NAME" "image004.jpg") "<image004.jpg@01CEF727.EBC95AB0>" NIL "BASE64" 2272 NIL NIL NIL)("IMAGE" "JPEG" ("NAME" "image006.jpg") "<image006.jpg@01CEF727.EBC95AB0>" NIL "BASE64" 2296 NIL NIL NIL)("IMAGE" "GIF" ("NAME" "image007.gif") "<image007.gif@01CEF727.EBC95AB0>" NIL "BASE64" 2230 NIL NIL NIL) "RELATED" ("BOUNDARY" "----=_NextPart_001_0036_01CEF728.3E0B8D20") NIL NIL)("APPLICATION" "VND.OPENXMLFORMATS-OFFICEDOCUMENT.SPREADSHEETML.SHEET" ("NAME" "Elenco dipendenti numerati.xlsx") NIL NIL "BASE64" 16312 NIL ("ATTACHMENT" ("FILENAME" "Elenco dipendenti numerati.xlsx")) NIL) "MIXED" ("BOUNDARY" "----=_NextPart_000_0035_01CEF728.3E0B8D20") NIL ("IT")) BODY[HEADER.FIELDS (FROM DATE SUBJECT CONTENT-TYPE IMPORTANCE)
these are some example.. but there are many other similar,
thanks
Coordinator
Dec 17, 2013 at 5:11 PM
The second message you have mentioned has no attachment in its structure, only two alternate views - text ad html. Are you sure there should be an attachment?
Dec 18, 2013 at 7:40 AM
Hi Pavel,
yes, I'm sure because I read these message with Thunderbird client on my pc and I see correctly the XLS attachment.
Coordinator
Dec 18, 2013 at 11:13 AM
Are you sure you have copied the whole body structure? It's not complete.
Dec 18, 2013 at 12:26 PM
yes, I'm sure;
that is what appears when I select 'show body structure'
Jan 8, 2014 at 8:41 AM
Hi Pavel,
any news for my trouble? How can I help you to solve this?
Coordinator
Jan 8, 2014 at 8:51 AM
Hi GDEffe,

yeah, i'm working on this issue, the code will updated this weekend, maybe earlier. I will let you know as soon as a fix is ready!

Best regards,

Pavel
Jan 12, 2014 at 9:00 AM
Hi Pavel,

I'm experiencing the same issue as GDEffe. I was able to connect & login to our outlook.office365.com corporate account and get the list of all messages from Inbox folder just fine. However, when I try to read the message.Body.Text property (originally sent from Outlook 2010 formatted as Plain text) all I get is "* 1 FETCH (" string. I've tried your Sample application and this is reported body structure:
("text" "plain" ("charset" "us-ascii") NIL NIL "quoted-printable" 683 20 NIL NIL "en-US" NIL) UID 14313)
I can provide complete original email saved in EML file from Outlook 2010 if necessary. If you could provide the fix until Jan 20 I'd be mostly graceful. Donation would not miss your efforts, thanks.
Coordinator
Jan 12, 2014 at 2:57 PM
Hi pdzugas,

I not yet had a chance to fix this íssue completely, as next Tuesday have a deadline in an important project. After that I'll be free for around a week, so a fix until 20th is possible.

I will let you know when the fix is available or if I need additional information!

Greets,

Pavel
Jan 23, 2014 at 6:32 PM
Hi Pavel,

any progress with resolving this issue? It's getting quite urgent for me because it was supposed to be used in our production environment. Thanks a lot for whatever reply so I can arrange accordingly with my project managers.
Coordinator
Jan 23, 2014 at 6:40 PM
Hi pdzugas,

i'm currently preparing an update on this issue, the release is planned for this sunday. After it, the issue should b eliminated completed.

Greets,

Pavel
Jan 24, 2014 at 6:14 AM
Excellent news! I'm looking forward to test your new release next week then. Much appreciated and thank you for your support.
Peter
Coordinator
Jan 27, 2014 at 12:16 AM
Hi Peter,

I'm going to upload the updated version for you in the morning, so you can test if the issue is resolved. If some problems still persist, I can take care of it right away as having a free day.

Greets,

Pavel
Coordinator
Jan 27, 2014 at 9:34 AM
You can check out te latest source code in repository. If the problem still persists, let me know, I will make another update today.
Jan 28, 2014 at 6:55 PM
Hi Pavel,

unfortunately your update didn't work. I've downloaded the latest sources and built ImapX.sln in Visual Studio 2010. I've used your ImapX.Sample.exe utility to test my problematic message and body is still not parsed properly. __* 1 FETCH (__ is all there is displayed. Please advise what can I do next. Could it help if I sent the same message directly to your mailbox so you can test body parser straight at your desk?
Coordinator
Jan 28, 2014 at 10:48 PM
Edited Jan 28, 2014 at 10:48 PM
Hi pdzugas,

sending me the message would be a great help! Please use this address: p13a92@gmail.com .

best regards,

Pavel
Jan 29, 2014 at 5:58 AM
Alright, sample email DataIntakeEmailService Test #1 was sent to your address, thanks for your support!

Peter
Coordinator
Jan 29, 2014 at 3:02 PM
Edited Jan 29, 2014 at 3:03 PM
Hi Peter,

I tested the message you sent me, however, on GMail I don't experience any issues. Can you send me another message to my outlook.com account? This should be nearly same environment as you tested youself.

Please use this address: pavel-azanov@outlook.com .

Greets,

Pavel
Feb 3, 2014 at 5:15 AM
Hi Pavel,

sorry for late reply, I was busy with other projects. Sample message was sent to your outlook.com account as you requested.

Thanks and good luck,
Peter
Coordinator
Feb 3, 2014 at 10:43 AM
Hi Peter,

thank you, I will take a look at it tonight!

Greets,

Pavel
Feb 10, 2014 at 8:26 AM
Hi Pavel,
any (good) news on body parser with my email sample?
Coordinator
Feb 10, 2014 at 12:41 PM
Hi Peter,

yeah, your sample message was very useful! I nearly finished the update for the parser, so it's gonna be public in the next few days. The code update itself might be ready tonight, depends on how much time I have.

Greets,

Pavel
Feb 11, 2014 at 6:22 PM
That's great to hear. Keeping my fingers crossed to get your new build soon! :)
Feb 20, 2014 at 7:56 AM
HI Pavel,
I was taken with many other jobs and only today I could try the new code but I get the same problem.
I wait for the next update!!
thanks
Mar 13, 2014 at 2:26 PM
Hi Pavel,

I can hardly wait to get hands on version 2.0.0.16! Hopefully it won't take long to release this new build. Good luck, thanks.
Apr 3, 2014 at 5:08 AM
Hello again,

I don't want to sound ungrateful but it's been really long time since you replied about the status last time. Could you please release whatever you have currently? I hoped to have the issue fixed by the end of January. My project is terribly behind schedule and I'm hopeless without your help.

Thanks a lot,
Peter
Coordinator
Apr 3, 2014 at 10:28 PM
Hi Peter,

thank you for the message, I know it took more time to work on this issue than planned, this is due to two factors, it's difficulty and also my daily. Anyway, I will push the latest code this weekend to the repository, so you can test it with your application.

Best regards,

Pavel
Coordinator
Apr 8, 2014 at 8:18 PM
Good evening!

Please have a look at the latest code in the repository. Various fixes have been done. I'd be happy if you can test it and give some feedback!

Best regards,

Pavel
Apr 29, 2014 at 2:10 PM
Hello Pavel,

I've downloaded your latest sources (revision 35615) and built the solution in VS2013 successfully.
I've seen the message body parsed correctly when testing with ImapX.Sample application.
Well, the line breaks and multiple spaces were lost and replaced with single spaces but this is not an issue for me since we are parsing XML data where beautiful formatting is not that important.

Thank you very much for your efforts, really appreciated!

Peter