It seems that my problem occurs everytime when a mail has attachments and EmbeddedRessourses:
In that case ImapX only recognizes the EmbeddesRessourses and ignores the attached files. When I'm trying to download the files via ImapX_Sample its also only recognizes the EmbeddedRessourses but when I'm trying to download them it saves the first attached file with the filename of the inline-file, pretty odd..
Heres my Bodystructure from the debug-file:
```
BODYSTRUCTURE
(
(
(
(
"text" "plain"
(
"charset" "iso-8859-1"
)
NIL NIL "quoted-printable" 5511 346 NIL NIL NIL NIL
)
(
"text" "html"
(
"charset" "iso-8859-1"
)
NIL NIL "quoted-printable" 33863 585 NIL NIL NIL NIL
)
"alternative"
(
"boundary" "----=_NextPart_002_0149_01D01946.F86E2EC0"
)
NIL NIL NIL
)
(
"image" "png"
(
"name" "image001.png"
)
"<image001.png@01D01946.F7C89FF0>" NIL "base64" 14582 NIL NIL NIL NIL
)
"related"
(
"boundary" "----=_NextPart_001_0148_01D01946.F86E2EC0"
)
NIL NIL NIL
)
(
"image" "jpeg"
(
"name" "Wifi_neu_1.jpg"
)
NIL NIL "base64" 420260 NIL
(
"attachment"
(
"filename" "Wifi_neu_1.jpg"
)
)
NIL NIL
)
(
"image" "jpeg"
(
"name" "Wifi_neu_2.jpg"
)
NIL NIL "base64" 328606 NIL
(
"attachment"
(
"filename" "Wifi_neu_2.jpg"
)
)
NIL NIL
)
(
"image" "jpeg"
(
"name" "Wifi_neu_3.jpg"
)
NIL NIL "base64" 467488 NIL
(
"attachment"
(
"filename" "Wifi_neu_3.jpg"
)
)
NIL NIL
)
(
"image" "jpeg"
(
"name" "Wifi_neu_4.jpg"
)
NIL NIL "base64" 447626 NIL
(
"attachment"
(
"filename" "Wifi_neu_4.jpg"
)
)
NIL NIL
)
"mixed"
(
"boundary" "----=_NextPart_000_0147_01D01946.F86E2EC0"
)
NIL
(
"de"
)
NIL
)
```
I think the problem is very similiar to the resolved "bodyparsing"-issues.. But I don't have a clue how to solve it.
Im using the latest files from the sourcecode-section (08-Jan-15).
Comments: ** Comment from web user: themummy **
In that case ImapX only recognizes the EmbeddesRessourses and ignores the attached files. When I'm trying to download the files via ImapX_Sample its also only recognizes the EmbeddedRessourses but when I'm trying to download them it saves the first attached file with the filename of the inline-file, pretty odd..
Heres my Bodystructure from the debug-file:
```
BODYSTRUCTURE
(
(
(
(
"text" "plain"
(
"charset" "iso-8859-1"
)
NIL NIL "quoted-printable" 5511 346 NIL NIL NIL NIL
)
(
"text" "html"
(
"charset" "iso-8859-1"
)
NIL NIL "quoted-printable" 33863 585 NIL NIL NIL NIL
)
"alternative"
(
"boundary" "----=_NextPart_002_0149_01D01946.F86E2EC0"
)
NIL NIL NIL
)
(
"image" "png"
(
"name" "image001.png"
)
"<image001.png@01D01946.F7C89FF0>" NIL "base64" 14582 NIL NIL NIL NIL
)
"related"
(
"boundary" "----=_NextPart_001_0148_01D01946.F86E2EC0"
)
NIL NIL NIL
)
(
"image" "jpeg"
(
"name" "Wifi_neu_1.jpg"
)
NIL NIL "base64" 420260 NIL
(
"attachment"
(
"filename" "Wifi_neu_1.jpg"
)
)
NIL NIL
)
(
"image" "jpeg"
(
"name" "Wifi_neu_2.jpg"
)
NIL NIL "base64" 328606 NIL
(
"attachment"
(
"filename" "Wifi_neu_2.jpg"
)
)
NIL NIL
)
(
"image" "jpeg"
(
"name" "Wifi_neu_3.jpg"
)
NIL NIL "base64" 467488 NIL
(
"attachment"
(
"filename" "Wifi_neu_3.jpg"
)
)
NIL NIL
)
(
"image" "jpeg"
(
"name" "Wifi_neu_4.jpg"
)
NIL NIL "base64" 447626 NIL
(
"attachment"
(
"filename" "Wifi_neu_4.jpg"
)
)
NIL NIL
)
"mixed"
(
"boundary" "----=_NextPart_000_0147_01D01946.F86E2EC0"
)
NIL
(
"de"
)
NIL
)
```
I think the problem is very similiar to the resolved "bodyparsing"-issues.. But I don't have a clue how to solve it.
Im using the latest files from the sourcecode-section (08-Jan-15).
Comments: ** Comment from web user: themummy **
Hi Pavel,
I just downloaded 2.0.0.18. Unfortunately, the issue is still there.