xfs
[Top] [All Lists]

Re: [OT: virus] Re: SELECTED

To: stimits@xxxxxxxxx
Subject: Re: [OT: virus] Re: SELECTED
From: "Blizbor (IMA)" <tb670725@xxxxxx>
Date: Wed, 28 Aug 2002 21:52:44 +0200
Cc: linux-xfs@xxxxxxxxxxx
References: <200208281053.MAA18676@ady.hdsnet.hu> <3D6D04B1.5050508@attbi.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0) Gecko/20020530
IMVHO: most of that could be avoided using procmail sanitizer.
It can do enough sanity checks to remove most of existing
mail viruses.

All I can do to help - I can setup mail routing on my mail servers
so each incoming message will be routed back to linux-xfs list
server after virus checking using professional antyvirus software.
If somebody who is responsible for this list is interrested, please 
contact me.

Regards,
Blizbor

D. Stimits wrote:
> Yet another shining example of a filter line that could be added. This 
> list would never receive a valid message with "Content-Type: 
> audio/x-midi". Filtering this and type application/octet-stream would 
> decimate many of the windows virii. I am curious what kind of current 
> ability the list has for rejecting based on content type or header 
> information?
> 
> kosiki wrote:
> 
>>--Q8714e2L66enF661u68kOrxZ6
>>Content-Type: text/html;
>>Content-Transfer-Encoding: quoted-printable
>>
>><HTML><HEAD></HEAD><BODY>
>><iframe src=3Dcid:HZ42Du2b961 height=3D0 width=3D0>
>></iframe>
>><FONT></FONT></BODY></HTML>
>>
>>--Q8714e2L66enF661u68kOrxZ6
>>Content-Type: audio/x-midi;
>>      name=Clears.pif
>>Content-Transfer-Encoding: base64
>>Content-ID: <HZ42Du2b961>
> 
> 
> 




<Prev in Thread] Current Thread [Next in Thread>