| Summary | Problem with signed messages |
| Queue | IMP |
| Queue Version | 4.1.6 |
| Type | Bug |
| State | Duplicate |
| Priority | 2. Medium |
| Owners | |
| Requester | hilda (at) unina (dot) it |
| Created | 07/08/2008 (6220 days ago) |
| Due | |
| Updated | 07/09/2008 (6219 days ago) |
| Assigned | |
| Resolved | 07/08/2008 (6220 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
The problem i noticed has two aspects.
The first is surely mime objects treatment but i believe tha demime
functions don't work correctly because (second aspect) the object (in
my own case a digitally signed message) is corrupted in a some way. In
fact, if i try to redirect the message to another account (or saving
it on desktop) and to view it using another client (i.e. OE) the
signature is not recognized at all and message is notified as
corrupted (in both cases). If the same message is directly sent to an
account managed by a different client, it is correctly displayed.
The, i argue that is not only a visualization problem but a decoding failure.
State ⇒ Duplicate
Priority ⇒ 2. Medium
New Attachment: test.eml
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ Problem with signed messages
Type ⇒ Bug
State ⇒ Unconfirmed
visualized at all.
In particular, the attacched message appears to be empty.
The same mail, viewed with every else clients we tested as squirrel,
OE, etc., is correctly displayed.