![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
On Wed, 03 Jan 2001 23:57:53 -0500 (EST), you wrote: >1. Should the IETF elist messages be scanned for viruses? This would require that appropriate virus detection software exist in the environment that the mail list is operated. Are you aware of eg an Acorn Archimedes virus scanner that runs in a vax/vms environment? >2. Should the IETF elist restrict the type of content that can be > submitted? I see no reason that the IETF list(s) should not be restrictd to plaintext[1], with either a remove-the-attachment or even drop-the-message approach (possibly with an automated unsubscribe) to non text attachments / content. Anyone who wants to distribute non plaintext can post it on a website or ftp directory somewhere for collection by those who actually want it. Rgds Denis [1] Text based markup eg html is *NOT* plaintext in this context. -- Denis McMahon Usenet: Trim quotes Mobile: +44 7802 468949 Reply at the end Email: denis at pickaxe.demon.co.uk Don't use html I trim ng when posting! Email domain blocking in use
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.