administrivia: posting traps in the current majordomo installation

[Richard Welty <rwelty@domain.elided>]

the majordomo installation on digest.net (aka krusty-motorsports.com) has a
number of traps in it. some are spam traps that detect and put out common
and annoying spammers. others detect certain types of problem postings;
articles that for one reason or another create problems for various
subscribers.

i'm in the process of adding a couple due to popular demand. i felt that
the readership of the various lists should know what's being trapped:

1) 8 bit postings -- these include various national character sets and
special characters. many readers are at sites whose mail transport bounces
these back to me. i get these in my inbox, one way or another, but i get a
great deal less of it if i trap these on the first pass through.

2) winmail.dat files -- these are generated by some M$ products; as time
permits i now edit out the winmail.dat files and forward the messages to
the appropriate list. this can delay getting your message out.

3) <x-html> -- these are html formatted messages from certain M$ clients
that i know of. a recent posting to one of the lists of this type includes
the header line
   X-Mailer: Microsoft Internet Mail 4.70.1161
if you are using such a product, turn off the html features when you send
postings

4) Content-type: text/html; -- these are html formatted messages from a
variety of clients; again, make sure you have html features turned off when
sending to the digest. i know M$ Outlook may generate these, and i believe
that certain netscape mail clients may do so as well. since the copy of
eudora light i am using can display them, eudora may well be able to
generate them. please turn it off.

i will add other traps as i identify strings to match in message bodies. i
will definitely be trying to trap things like word documents and base64
encoded binaries. i will edit and resend where possible, subject to
potential delays, but some html formatted messages will require
unreasonable amounts of work on my part, and may just get mailed back to
the sender with instructions to resend without the encoding.

richard