After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 318301 - "attachments" button at the beginning of e-mails very annoying
"attachments" button at the beginning of e-mails very annoying
Status: RESOLVED DUPLICATE of bug 312413
Product: evolution
Classification: Applications
Component: Mailer
2.4.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-10-08 21:13 UTC by Antoine Pitrou
Modified: 2005-10-08 22:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Antoine Pitrou 2005-10-08 21:13:51 UTC
When viewing an e-mail which has attachments, there is an attachment button just
beneath the headers and before the body (together with a "save" button).

The problem is there are many situations when this button is useless and disrupting:
- some mailing-lists include the footer as an attachment (e.g. when the charsets
are different)
- some images may be displayed inline
- etc.

In all these situations, there is this button which unnecessarily catches the
eye at a very prominent place. It is quite bothering (akin to visual pollution).

The button should either be removed, or be displayed only when there are "real"
attachments present ("real" being determined by a clever algorithm ;-)).


Other information:
Comment 1 André Klapper 2005-10-08 22:35:59 UTC
hi antoine,
thanks for taking the time to report this.

i assume that this is a duplicate of bug 312413, feel free to reopen if you
disagree.

a "clever algorithm" simply cannot exist according to the specifications of
multipart messages in the rfc's. cannot tell you more details (i'm not a
programmer), but it's extremely hard to tell what are attachments and what are
message parts, for example see the comments of bug 237623 or of bug 

*** This bug has been marked as a duplicate of 312413 ***