Skip to contentSkip to conversation

feature request: DIR/mimereject

DISCUSSION Kurt Lieber 3 participants 8 messages Nov 4, 2004 – Nov 5, 2004

lore
Share & tools
lore
#0 lore raw

I didn't see this feature listed on the mlmmj page -- apologies if it already exists.

That said, one thing we *really* need is the DIR/mimereject feature of ezmlm. (might be an ezmlm-idx specific feature, come to think of it) This feature scans list messages prior to sending them and rejects messages with pre-defined attachment types. "application/octet-stream" is the one we block on most of our lists as those attachments are generally worms/viruses.

I'd *like* to have a global option that allowed me to say, "for any/all lists on this machine, reject messages with the following MIME types". IF that's more difficult, then I'm content with at least being able to do it on a list-by-list basis. Another option would be some sort of /etc/skel type functionality, but that's a separate feature request, so I'm going to send that in a separate email.

--kurt

#1 lore raw
Quoted 10 lines · Kurt Lieber

I didn't see this feature listed on the mlmmj page -- apologies if it already exists.

That said, one thing we *really* need is the DIR/mimereject feature of ezmlm. (might be an ezmlm-idx specific feature, come to think of it) This feature scans list messages prior to sending them and rejects messages with pre-defined attachment types. "application/octet-stream" is the one we block on most of our lists as those attachments are generally worms/viruses.

Quoted 6 lines

I'd *like* to have a global option that allowed me to say, "for any/all lists on this machine, reject messages with the following MIME types". IF that's more difficult, then I'm content with at least being able to do it on a list-by-list basis. Another option would be some sort of /etc/skel type functionality, but that's a separate feature request, so I'm going to send that in a separate email.

How about using the functionality already there? Here's a snippet from README.access (tar-ball and http://mlmmj.mmj.dk/files/README.access):

A third example. Deny any mails with "discount", "weightloss", or "bonus" in the subject. Allow PGP signed and plain text mails. Anything else is denied:

deny ^Subject:.*discount
deny ^Subject:.*weightloss
deny ^Subject:.*bonus
allow ^Content-Type: multipart/signed
allow ^Content-Type: text/plain

That should make it possible to do what you want no? And for the global reject file, just make one access file in a central place and symlink it everywhere.

Signature · 4 lines
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
 and totally illogical, with just a little bit more effort?"
                                -- A. P. J.
#2 lore raw
In reply to Kurt Lieber
Quoted 2 lines · Kurt Lieber

I didn't see this feature listed on the mlmmj page -- apologies if it already exists.

Sure, no problem. It's a bit hidden.

Quoted 6 lines

That said, one thing we *really* need is the DIR/mimereject feature of ezmlm. (might be an ezmlm-idx specific feature, come to think of it) This feature scans list messages prior to sending them and rejects messages with pre-defined attachment types. "application/octet-stream" is the one we block on most of our lists as those attachments are generally worms/viruses.

In DIR/control/access:

deny Content-Type:.*application/octet-stream
allow

Signature · 4 lines
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
 and totally illogical, with just a little bit more effort?"
                                -- A. P. J.
#3 lore raw
In reply to Kurt Lieber
Quoted 11 lines · Mads Martin Joergensen
Quoted 6 lines

That said, one thing we *really* need is the DIR/mimereject feature of ezmlm. (might be an ezmlm-idx specific feature, come to think of it) This feature scans list messages prior to sending them and rejects messages with pre-defined attachment types. "application/octet-stream" is the one we block on most of our lists as those attachments are generally worms/viruses.

In DIR/control/access:

deny Content-Type:.*application/octet-stream
allow

I don't think that's what Kurt want. Our access check only checks the mail's headers. He probably wants to check the headers of each MIME part in the mail body. That would require parsing the body, and checking the headers of each part - not an easy task. And definitely not an easy thing to do correctly.

Morten

Signature · 2 lines
Morten K. Poulsen <[email protected]>
http://www.afdelingp.dk/
#4 lore raw
In reply to Kurt Lieber
Quoted 4 lines · Morten K. Poulsen

I don't think that's what Kurt want. Our access check only checks the mail's headers. He probably wants to check the headers of each MIME part in the mail body. That would require parsing the body, and checking the headers of each part - not an easy task. And definitely not an easy thing to do correctly.

Correct. This request comes from the all the worms that exist out there which spoof both the From: and the To: address. We've had a number of occasions where a virus got through to the list because it appeared to come from a valid subscriber.

An argument can certainly be made that the MTA should handle this instead of the ML manager and, if you make that argument, I'll accept it. :) However, it is a feature of ezmlm(-idx) so I figured I'd at least ask for it.

--kurt

#5 lore raw
In reply to Kurt Lieber
Quoted 5 lines · Kurt Lieber
Quoted 3 lines

He probably wants to check the headers of each MIME part in the mail body. That would require parsing the body, and checking the headers of each part
- not an easy task. And definitely not an easy thing to do correctly.

Correct.

[snip]

Quoted 3 lines

An argument can certainly be made that the MTA should handle this instead of the ML manager and, if you make that argument, I'll accept it. :) However, it is a feature of ezmlm(-idx) so I figured I'd at least ask for it.

It would be a very nice feature to have, no doubt. In out LUG we just disallow multipart messages (unless they are multipart/signed) but that is probably a bit to BOFH'ish for most lists :-) It would indeed make sense to allow - for instance - multipart/related if each part was text/plain, application/x-patch or image.

It would require that we recursively parsed the body and its parts. mmj and I have planed a coding session later today, so maybe we should look a bit more into it. The more I think about it, the nicer it sounds.

Morten

Signature · 2 lines
Morten K. Poulsen <[email protected]>
http://www.afdelingp.dk/
#6 lore raw
In reply to Kurt Lieber
Quoted 4 lines · Morten K. Poulsen

It would require that we recursively parsed the body and its parts. mmj and I have planed a coding session later today, so maybe we should look a bit more into it. The more I think about it, the nicer it sounds.

Indeed, but it's post 1.1 :-)

Hopefully we'll see 1.1-RC1 this weekend.

Signature · 4 lines
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
 and totally illogical, with just a little bit more effort?"
                                -- A. P. J.