[Bug 311158] New: Attachment properties dialog doesn't understand "filename" attribute

[Bernd Oliver Sünderhauf]

https://bugs.kde.org/show_bug.cgi?id=311158

            Bug ID: 311158
          Severity: minor
           Version: 4.10 pre
          Priority: NOR
          Assignee: kdepim-bugs at kde.org
           Summary: Attachment properties dialog doesn't understand
                    "filename" attribute
    Classification: Unclassified
                OS: Linux
          Reporter: pancho.mz at riseup.net
          Hardware: Ubuntu Packages
            Status: NEW
         Component: general
           Product: kmail2

If an attachment is named using the Content-Disposition header's "filename"
parameter only, the attachment properties dialog doesn't display any name at
all, even though this is perfectly RFC conform behaviour.

Reproducible: Always



Expected Results:  
1. The "filename" parameter needs to be discovered and used in the properties
dialog.
2. When saving the attachment or editing the message, the filename however is
correctly determined. So obviously, our code has two ways of reading out the
parameters of attachments, which indicates code duplication. If that's the
case, it should be merged.
3. If in an incoming message, both the "filename" parameter
(Content-Disposition) and a "name" parameter (Content-Type) are given, but do
contradict (which is incorrect), then the "filename" parameter should take
precedence. If only one or the other is given, it is fine to be tolerant and
use whichever has been given.
4. In order to proliferate a standards-conform use of headers the corresponding
field in the properties dialog should be renamed to "filename".

For named MIME-parts, the use of the "filename" parameter within the
Content-Disposition header is strongly preferred to a non-standard "name"
parameter within the Content-Type header. The latter is only an optional
redundancy in order to be compatible with older systems that don't adhere to
the RFCs. (See: http://www.imc.org/ietf-smtp/mail-archive/msg05023.html)

The choice of parameter encodings etc. might also need some doublechecking, but
is not subject of this bug ticket.

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