#1487700 closed Bugs (fixed)
The wrong mail charset
| Reported by: | umount | Owned by: | |
|---|---|---|---|
| Priority: | 5 | Milestone: | 0.5.1 |
| Component: | MIME parsing | Version: | 0.5 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
After Changeset 4340
Fix charset conversion for text attachments without charset specification (#1487634)
Some messages are incorrectly decoded.
I am revert this commit and all well done.
Attachments (4)
Change History (16)
comment:1 Changed 2 years ago by alec
- Component changed from Addressbook to MIME parsing
- Milestone changed from later to 0.5.1
Changed 2 years ago by umount
comment:2 Changed 2 years ago by umount
I am read last comment in that ticket.
Example message.
comment:3 follow-up: ↓ 6 Changed 2 years ago by alec
- Resolution set to worksforme
- Status changed from new to closed
This message has no attachment and it works for me.
comment:4 Changed 2 years ago by alec
Provide imap_debug log and describe your environment.
Changed 2 years ago by umount
Changed 2 years ago by umount
comment:5 Changed 2 years ago by umount
After Changeset 4340 0.png
Should 1.png
Changed 2 years ago by umount
comment:6 in reply to: ↑ 3 Changed 2 years ago by umount
Replying to alec:
This message has no attachment and it works for me.
Yes it is massage has no attachment but it don't works for me.
comment:7 follow-up: ↓ 8 Changed 2 years ago by alec
Wontfix. Your server response is wrong
BODYSTRUCTURE ("text" "plain" NIL NIL NIL "8bit" 33 3 NIL NIL NIL)
comment:8 in reply to: ↑ 7 Changed 2 years ago by umount
Replying to alec:
Wontfix. Your server response is wrong
BODYSTRUCTURE ("text" "plain" NIL NIL NIL "8bit" 33 3 NIL NIL NIL)
thanks
comment:9 Changed 2 years ago by umount
I am found error message dont have header
MIME-Version: 1.0
comment:10 Changed 2 years ago by alec
- Resolution worksforme deleted
- Status changed from closed to reopened
comment:11 follow-up: ↓ 12 Changed 2 years ago by alec
- Resolution set to fixed
- Status changed from reopened to closed
I've added some code in [82414421] that should workaround this issue.
comment:12 in reply to: ↑ 11 Changed 2 years ago by umount
Replying to alec:
I've added some code in [82414421] that should workaround this issue.
thank you. all work perfect.

Did you read my last comment in that ticket? Provide example message.