Bug 125409 - Set Content-transfer-encoding per outgoing account
Summary: Set Content-transfer-encoding per outgoing account
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-12 10:36 UTC by Andras Georgy Bekes
Modified: 2012-08-19 00:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Andras Georgy Bekes 2006-04-12 10:36:03 UTC 
Version:            (using KDE KDE 3.5.1)

Currently, the Content-transfer-encoding of outgoing mails (or "Message property" in KMail's terminology) is a "Common option" --- common for all "Outgoing account".

I'd need to set it differently for different outgoing accounts, and I think it is also more logical that way.
Comment 1 Thiago Macieira 2006-04-14 18:09:53 UTC 
It makes sense, but it puts a greater burden on KMail because it may have to re-encode the email before transmitting. That means the email has to be stored in pure 8-bit and unsigned in the Outbox folder and must be signed only when it's about to be delivered -- when the outgoing server is known.

If you have a server that is broken WRT 8-bit MIME, set to Quoted Printable for all accounts and it should work.
Comment 2 Myriam Schweingruber 2012-08-18 08:25:55 UTC 
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented.
Thank you for your understanding.
Comment 3 Luigi Toscano 2012-08-19 00:35:17 UTC 
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.