Feature #3413: Exclude attachments from incoming emails based on mime type - Redmine

Feature #3413

Exclude attachments from incoming emails based on mime type

Added by Marco Tralles about 3 years ago. Updated 3 months ago.

Status:

New

Start date:

2009-05-25

Priority:

Normal

Due date:

Assignee:

% Done:

Category:

Email receiving

Target version:

Candidate for next major release

Resolution:

Description

i use a digital signature in mail.app and if i reply to a issue-mail my answer will be added to the issue, but redmine adds also a smime.p7s file wich is my signature (attachment).
It would be helpful, if redmine learns to ignore s/mime attachments.

smime.png - a lot of smime-files are added to the issue if using the mail-interface (11.1 kB) Marco Tralles, 2009-05-25 16:34

History

#1 Updated by Jean-Philippe Lang about 3 years ago

Subject changed from digital-signature-attachments to Exclude attachments from incoming emails

#2 Updated by Jean-Philippe Lang about 3 years ago

Tracker changed from Defect to Feature

#3 Updated by Jean-Philippe Lang about 3 years ago

Subject changed from Exclude attachments from incoming emails to Exclude attachments from incoming emails based on mime type

#4 Updated by Patrick Cummins over 2 years ago

+1 for this.

It seems like a very easy change from looking at the source. Even ignoring files by extension would work.

I'm new to ruby... but I'll try to write a patch if I have time.

#5 Updated by marc maurice almost 2 years ago

We have a lot of users sending mails to redmine tickets with included images in html signatures.

Each time we have to delete the attachments manually in the ticket. and each time we delete an attachment a notification is sent.

Some attachments that are not real ones must be ignored. Just looking the file extension is not sufficient.

I'm not an email RFC expert, but Looking in two mail sources :

From a mail source with a real attachment :

------_=_NextPart_001_01CB3E16.D938DEBE
Content-Type: application/msword;
    name="=?iso-8859-1?Q?R=E9union_du_18082010=2Edoc?=" 
Content-Transfer-Encoding: base64
Content-Description: =?iso-8859-1?Q?R=E9union_du_18082010=2Edoc?=
Content-Disposition: attachment;
    filename="=?iso-8859-1?Q?R=E9union_du_18082010=2Edoc?="

From a mail source with an included attachment :

------_=_NextPart_002_01CB3D29.23FDF48F
Content-Type: image/gif;
    name="image001.gif" 
Content-Transfer-Encoding: base64
Content-ID: <image001.gif@01CB3D39.E7847940>
Content-Description: image001.gif
Content-Location: image001.gif

In the "real" attachment, there is a "Content-Disposition: attachment;" ligne.

Maybe it's the way to detect real attachments from others ?

#6 Updated by Toshi MARUYAMA about 1 year ago

Category set to Attachments

#7 Updated by Egidijus Zideckas 8 months ago

#8 Updated by Max Albrecht 4 months ago

+1
i agree that filtering based on mime makes sense in the long run, but for now a small patch would be appreciated. just a comma-seperated list of extension to ignore, defaulting to the very obvious ones: vcf,p7s and other signatures.