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 617187 - Add "Remove attachment" option
Add "Remove attachment" option
Status: RESOLVED DUPLICATE of bug 205927
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other All
: Normal enhancement
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[attachments]
Depends on:
Blocks:
 
 
Reported: 2010-04-29 15:07 UTC by tortugo
Modified: 2010-04-29 21:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description tortugo 2010-04-29 15:07:48 UTC
Hello!

It will be is usefull to add an option to allow remove an attachment without remove the mail itself.

The attachment is converted to a "<name of attachment file> removed" entry.


KMail and Thunderbird have this option and is very usefull for professionals who receive lot of mails with attachments that must be proccessed (once you process one, is no longer needed) but you can safely store a copy of the original mail for future reference.

Example:

1 - A client send me a file (5MB)
2 - I store the file into the folder (on hard disk) related with the project we are working
3 - I delete the attachment (cause I not need it anymore in the mail)
4 - I save the mail (moving it to a evolution folder) for future reference.
5 - Two months later, Client calls me asking about the project.
6 - I can search the mail, and I can see the mail was an attachment.
7 - I can search te attachment on the project folder.


Thank you for you efforts and nice work.

Salu2 de jEsuSdA 8)
Comment 1 André Klapper 2010-04-29 21:57:18 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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