Bug 162195 - Composer breaks long lines from external files
Summary: Composer breaks long lines from external files
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-17 08:19 UTC by Josef Spillner
Modified: 2018-09-04 18:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Josef Spillner 2008-05-17 08:19:09 UTC
Version:            (using KDE 3.5.8)
Installed from:    Debian testing/unstable Packages

I'm trying to send a GnuPG-encrypted SSH key which I insert with "insert file". The SSH public key format is "[bytes] [key] [owner]" and these three parts get split by kmail with a line break. This makes the GnuPG signature invalid.
SMTP mandates a line limit of 998 characters, and recommends one of 78 characters for human-readable mails since some mail clients don't support soft-wrap for displaying text. But this mail is only read by an account bot. Therefore, kmail should ask whether it's ok to break the text into pieces. Considering that the middle part (the key) is the longest part, the line breakage doesn't really help anyway for user readability.

The workaround was to save the mail, edit it with vim (just removing the two line breaks), and saving it under some obscure file name into the outbox folder since kmail's "open mail" doesn't support send actions.
Comment 1 FiNeX 2009-04-04 12:07:17 UTC
@Josef: Does it happen even if the "automatic word wrap" is disabled?

On KDE4 (current trunk) I'm not able to reproduce it.
Comment 2 Andrew Crouthamel 2018-09-04 18:23:38 UTC
Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you!