[quote user="Rolf Lindby"]
As you already noticed there is no built-in option to remove MIME parts with HTML coding for mailing list messages. It would certainly be possible to create a policy or daemon to do that, though. Maybe someone already did?[/quote]
That's what I'm hoping; but I know of no such animal.  Is there a "central repository" or similar for Merc add-ons that I could search?

[quote]Rejecting certain attachments during the SMTP session is a bit tricky as the entire message is sent at once. All data is already received when it's decoded and split into MIME parts.[/quote]
Yes, I am aware of that, which is why I'm only looking at this in the context of messages destined for redistribution by the mailing list.  I would then make an exception to my already-existing Global Filtering Rule which (currently) bounces any message with HTML content.

Frankly, I'd like to get rid of that Rule altogether.  Several years ago I lobbied here for expanding the Transaction-Level Filtering function to at least permit testing all the headers, if not the full message (including the body), before having to make the decision to accept or reject; but AFAIK, nothing ever came of that.  Now that "backscatter" is even more unacceptable than it was then, perhaps David will take another look at that idea.

Hi, Folks --

It's been awhile since I checked in here. I've already seen enough to know that I have some major catching up to do, which I will get to as time permits. But in the meantime, I'd like an answer to couple quick questions:

 
I'm looking at setting up a small (no more than a dozen or so users) private (posting restricted to only those IDs I pre-approve; but once approved, they can post at will) mailing list. But some of my users are... well... um... "naive" in terms of operating their mail clients, to the point that I've (regrettably) already given up on ever sufficiently educating some of them so as to NOT send HTML-obotomized dreck. So some means of protecting the *other* list users from their foibles is needed. Therefore...

Can Merc's MAISER facility be configured to automagically strip off any HTML "parts" (i.e., "Content-Type: text/html") of MIME multipart messages it receives *before* re-transmitting those messages to the list membership? I know such a configuration option exists in several other mail-list packages -- such as for example, LISTSERV, EZMLM, and MailMan -- but I could find no reference to such in the Mercury Help files.

 
Failing some simple "set & forget" configuration switch, has anyone written an external utility which could perhaps be run as a "policy" on any message directed at the list's posting address? (I have found a perl script called "Stripmime" <http: www.phred.org="" stripmime.html=""> which purports to provide this function; but beyond the issue of setting up &amp; running a perl interpreter under Windows on the mail server box, it *also* strips ALL attachments, regardless of type or purpose --- something I'd prefer to avoid, since some of them (jpeg images, AutoCAD .DXF files, etc.) could be quite useful. (FWIW, I already have a Global Filtering Rule set up to reject -- well, "bounce", actually; I *wish* I could truly do it as a reject during the SMTP handshake -- common executable attachment types such as bat, com, cmd, doc, exe, js, jse, lnk, pif, reg, scr, shs, vbe, vbs, wsf.) </http:>

As you already noticed there is no built-in option to remove MIME parts with HTML coding for mailing list messages. It would certainly be possible to create a policy or daemon to do that, though. Maybe someone already did?

Rejecting certain attachments during the SMTP session is a bit tricky as the entire message is sent at once. All data is already received when it's decoded and split into MIME parts.

/Rolf