| Summary | Incorrect encoding type for base64 email |
| Queue | IMP |
| Queue Version | 4.2-RC3 |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | fazevedo (at) netmadeira (dot) com |
| Created | 03/14/2008 (6295 days ago) |
| Due | 03/14/2008 (6295 days ago) |
| Updated | 05/05/2008 (6243 days ago) |
| Assigned | 03/16/2008 (6293 days ago) |
| Resolved | 03/21/2008 (6288 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
with an attachment with the following headers:
Content-Type: application/msword
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="=?iso-8859-1?Q?Distribui=E7=E3o_do_trabalho2.doc?="
The content was avaiable to download as a birany file (which didnt
work btw), under the name "unamed".
I take it isnt a bug since everyone who posted here said it was
working for them, but do you have any idea of what might be wrong then?
State ⇒ Not A Bug
displaying, or something you're having trouble spending?
base64. It seems to me that imp is not recognizing the
content-transfer-encoding header.
State ⇒ Feedback
displaying, or something you're having trouble spending?
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Incorrect encoding type for base64 email
Due ⇒ 03/14/2008
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
New Attachment: source.txt
State ⇒ Unconfirmed
messages. (tried 4.1, 4.2 RC2 and 4.2 RC3)