| Summary: | Attachments it is seen as the (Base64) text of the letter | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Alexandr Zaika <zaz> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 1.5.3 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Sample mail | ||
|
Description
Alexandr Zaika
2003-08-01 09:43:25 UTC
Created attachment 2128 [details]
Sample mail
Just for your information: This way of sending "attachments" has been superseded by the MIME standard more than 10 years ago. It seems that only the horrible Outlook Express still uses inline uuencoding instead of adhering to standards which all email clients support. I thank for the information, but other mail clients supported the given format and KMail are not present. I itself was going to write patch but all to not allocate in any way time :( Subject: Re: Attachments it is seen as the (Base64) text of the letter Well, KMail is only about 6 years old. Therefore it doesn't support a lot of stuff that was already obsoleted several years before the birth of KMail. The other email clients you are mentioning (you are probably referring to mutt, Netscape or Outlook Express) are much older and it's therefore not surprising that they still support this outdated stuff. If you want to write a patch for this then go ahead. If we like it then we'll add it to KMail. Otherwise you'll have to wait until someone else implements support for inline uuencoding. |