[Users] [Bug 3128] New: Claws Mail inserts only one line after a "Content-Type: multipart/mixed" and thus may confuse other clients

[noreply at thewildbeast.co.uk]

http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3128

            Bug ID: 3128
           Summary: Claws Mail inserts only one line after a
                    "Content-Type: multipart/mixed" and thus may confuse
                    other clients
    Classification: Unclassified
           Product: Claws Mail
           Version: GIT
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P3
         Component: Other
          Assignee: users at lists.claws-mail.org
          Reporter: pt8614-599 at online.de

Created attachment 1359
  -->
http://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=1359&action=edit
a short patch to implement a comment line

===Overview===

There is a bug report for KMail mentioning Claws Mail. See:
https://bugs.kde.org/show_bug.cgi?id=332036

The Problem described there is most likely a bug in KMail. However, Claws Mail
is not totally blameless on that matter.

When Claws Mail composes an email containing text and an attached file, the
outline of the email will contain something like this:

Content-Type: multipart/mixed; boundary="MP_/oLQPONLQse/eBnQ1ahObw=B"

--MP_/oLQPONLQse/eBnQ1ahObw=B

Although this is correct, most clients insert a comment before the boundary.
Like this:

Content-Type: multipart/mixed; boundary="MP_/oLQPONLQse/eBnQ1ahObw=B"

This is a mime message.
--MP_/oLQPONLQse/eBnQ1ahObw=B

The comment will not be displayed by a MIME-compatible client, but it seems
that at least KMail is expecting it. Unfortunately, KMail takes the matter in
its own hands and inserts an extra line where it expects the comment. If the
email is signed, this invalidates the signature.

The malfuction of other clients may not be the fault of Claws Mail, but the
problem can be solved by composing emails with a comment line.

Please find a possible way to do so in the attached diff-file.

===Build Date & Platform===

I checked the behavior of Claws Mail with a git clone of today.

-- 
You are receiving this mail because:
You are the assignee for the bug.