Hmm... I get PGP stuff as a separate attachment, which I have to delete manually (since I don't have Eudora set to delete attachments when I delete messages), and consider PGP signatures to be a nuisance. Why are messages to this list PGP-signed at all? I'd be happy with a per-list option to return any postings with encoding other than text/plain or text/quoted-printable(?); perhaps this could run alongside the Sender/Reply-To filter that causes our bewildered cc:Mail users so much trouble.... I would definitely want text/html rejected on most of our lists, even though it doesn't require base-64 decoding. A configurable list of rejected Content-Type values (which I would probably configure to include text/html and multipart/signed) would be an excellent 1.8d feature. Chris At 10:53 AM -0500 03/11/98, Valdis Kletnieks wrote: >Hmm.. major wierdness... my mail *SHOULD* be showing up as a MIME >message, of the following format: > >multipart/signed > text/plain All the text is here > application/pgp-signature *only* the PGP signature is here. >I'm of mixed feeling on the "prohibit attachments" aspect. This >sounds like it needs a bit more work to be a useful general-case >solution. What (for instance) should you do with a multipart/mixed >that contains only message/external-body references to FTP or HTTP? >What if it's 4 body parts, all of the text/plain persuation? > >Maybe what you *REALLY* wanted is "reject any application/ attachment", >Or perhaps you want a table of "known OK' application/ to allow to >be passed. > >It could be that what you *really* wanted is "disallow message if >any of the parts require base-64 encoding" (which would allow through >my messages, and anything of several text/plain, but would stop >people attaching Microsoft Word documents). > >I won't get into the text/html can of worms, other than to note that >I see more complaints about *single* bodypart text/html than I do >about attachments.... -- Chris Pepper | National Audubon Society: Web & List Manager 212 979 3092 | <http://www.audubon.org/staff/pepper/>