Michael Fox: > > So, are there other obvious ways to recognize encrypted contents, other > than > > "Content-Type: multipart/encrypted"?
Albrecht: > Basically, you need to check for > - OpenPGP/Inline (inspect every body, see rfc 2440, sect. 6.2) > - OpenPGP/Mime (multipart/encrypted, see rfc 3156, sect. 4) > - S/MIME (application/pkcs7-mime with a proper protocol type, see rfc > 2633, sect. 3.8) Ah, OK. That will give me a good start. Thanks. Rob0: > you can use an alternate cleanup service on an alternate > smtpd instance, see postconf.5.html#cleanup_service_name and also > cleanup.8.html . Interesting. I hadn't thought of that. I'll check into that. And thanks to everyone for the rest of the comments, legal or otherwise. I don't want to hijack this list with amateur radio stuff. But to briefly respond to those who took the time to respond to me: -- Encryption should be encouraged: Generally agreed. But it's not allowed on US amateur radio frequencies. -- All comments about the FCC rules: I have talked to the FCC and am confident that I understand the requirements. -- You can never block it all: Understood. I'm looking to block the obvious stuff to avoid inadvertent mistakes. Those who resort to subterfuge (which hasn't been a problem so far) can be dealt with on an individual basis as a violation of the acceptable use policy. Thanks again to all, Michael
