Closed Bug 190521 Opened 21 years ago Closed 21 years ago

bug_email.pl attachment might not be named

Categories

(Bugzilla :: Attachments & Requests, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Bugzilla 2.18

People

(Reporter: williams, Assigned: williams)

Details

Attachments

(1 file)

User-Agent:       Mozilla/4.76 [en] (X11; U; Linux 2.4.2-2 i686)
Build Identifier: 

When a bug is created via bug_email.pl, and it has attachments, if the
Content-Description header is blank, the attachment will have no description.
This is mildly annoying because you cannot click on the name of the attachment
to look at it (since there is no name).

Reproducible: Always

Steps to Reproduce:
1. Bugzilla must be configured to use bug_email.pl
2. send an email to bugzilla with an attachment (the Content-Description: header
on the attachment should be missing or blank).

Actual Results:  
The attachment created on the bug will have no name.

Expected Results:  
Bugzilla should use the filename or assign a default name.
This patch fixes the problem.

If the Content-Description header is blank,
it uses MIME::Head::recommended_filename to get a default name.
If that fails, it uses the default of "unnamed attachment".
-> patch author
Assignee: myk → john_williams
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Attachment #112546 - Flags: review?
Comment on attachment 112546 [details] [diff] [review]
recommended_filename patch

Assuming that you've tested this and head->recommended_filename has always been
in MIME::Parser (as we say in the docs that any version is OK) and taking into
consideration that this is in contrib/, this seems simple enough that I'll
rubber-stamp it.
Attachment #112546 - Flags: review? → review+
Flags: approval+
Checking in bug_email.pl;
/cvsroot/mozilla/webtools/bugzilla/contrib/bug_email.pl,v  <--  bug_email.pl
new revision: 1.15; previous revision: 1.14
done
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Target Milestone: --- → Bugzilla 2.18
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.