Tom Schneider wrote:

Hi - I put a message to GPC a while ago and some kind people responded, as I could find them in the archive. But my message and the response has not appeared on the daily digests. It seems that the daily digests are still for July!

Anja fixed the problem now (let us know if the digests are not catching up). At this occasion, she also found settings to deal with MIME types such as HTML. (You all remember the recent topic ...)

These are the possible relevant settings our MLM offers:

: # attachment_filters (level 1) : # The attachment_filters setting contains a table of rules, which describe : # how to process the different body parts of a posted message. : # : # A rule consists of a MIME type (or pattern matching a MIME type) : # and an action to perform when a message with this type or containing : # a part of this type is delivered to the subscribers of a mailing list. : # Each rule looks something like this: : # : # mime/type | action=argument : # : # Some common MIME types include text/plain, text/html, and image/jpeg. : # : # Possible actions are: : # : # allow - Let the body part pass untouched. Any subparts of : # this part will be processed as usual. : # clean - Remove portions of a HTML part that could pose a : # security hazard. : # discard - Remove the part from the message and pass the rest. : # (This has no effect upon single-part messages.) : # format - Convert the body part to plain text. A numerical : # argument will adjust the right margin of the text, : # which occurs at position 72 by default. : # keep - Let this body part, including any subparts, : # pass untouched. : # : configset gpc attachment_filters <<ENDAAK : ENDAAK : : # attachment_rules (level 1) : # The attachment_rules setting contains a list of rules, which describe : # what content types of a posted message are considered acceptable. : # : # A rule consists of a MIME type (or pattern matching a MIME type) and an : # action to perform when a message with this type or containing a part : # of this type passes through the list. Each rule looks something : # like this: : # : # mime/type | action=argument : # : # Some common MIME types are text/plain, text/html, and image/jpeg. : # : # Possible actions are: : # : # allow - Accept the body part. : # consult - Set the "mime_consult" access variable. By default, this : # will cause the message to be sent to the list moderators : # for approval. : # deny - Set the "mime_deny" access variable. By default, this will : # cause the entire message to be discarded. : # require - Set the "mime_require" access variable. By default, this : # has no effect. : # : # See "help configset_access_rules" and "help access_variables" for an : # explanation of how to use access variables in the access rules. : # : # This value was determined by the installation settings. : configset gpc attachment_rules <<ENDAAL : ENDAAL

As far as I understand it, I'd propose to set

text/html | action=discard

for the first option, and nothing for the second one. (I don't think we should discard HTML mails, if less invasive measures turn out to work, and Anja probably won't like getting forwarded all HTML mails. ;-)

Of course, someone who really wants to send HTML in their mail would have to put it in an archive or something then. IMHO that's acceptable (and should mostly happen on gpc-doc when discussing the web site, if at all).

Frank