From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] Mailscanner or amavisd-new
Date: Tue, 29 Nov 2011 15:08:47 +0100 [thread overview]
Message-ID: <4ef9adae73f8187e5281f141ba0f311d.squirrel@www.antarean.org> (raw)
In-Reply-To: <CAA2qdGX1x1Aa1O=5Q9cVWfDDe0fPmZUQQX-Vm-CNdgGBy4QZVQ@mail.gmail.com>
On Tue, November 29, 2011 2:36 pm, Pandu Poluan wrote:
> On Nov 29, 2011 8:25 PM, "VinÃcius Ferrão"
> <viniciusferrao@cc.if.ufrj.br>
> wrote:
>>
>> Agreed.
>>
>> Filtering Windows executables will only make the system admin to be
> recognized as an asshole and windows-hater.
>>
>> On Nov 29, 2011, at 10:11 AM, J. Roeleveld wrote:
>>
>> > On Mon, November 28, 2011 7:27 pm, MiÃâ¢u Moldovan wrote:
>> > <SNIPPED>
>> >> Also, a good idea is to block
>> >> extensions such as exe, pif, bat (in zip files also) before scanning
>> >> for viruses (if such a scan is really needed).
>> >
>> > I disagree. There are valid reasons to send "*.exe" and "*.bat" files
> via
>> > email. Braindead filters on extensions only cause problems.
>> >
>
> With my current setup, I already block .exe, .pif, .com, .lnk, .scr, and
> their ilks.
>
> But I do allow .zip and .rar, though.
Do you have a good reason to block on extensions?
Virus-scanners work quite nicely already and are not fooled by changing
the extensions.
I have received viruses where the email contained instructions to change
the extension to .exe. Filtering on extension will not stop those.
--
Joost
next prev parent reply other threads:[~2011-11-29 14:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 6:02 [gentoo-server] Mailscanner or amavisd-new Pandu Poluan
2011-11-28 6:23 ` Matt Thode
2011-11-28 6:40 ` Pandu Poluan
2011-11-28 9:14 ` Alessandro Ratti
2011-11-28 10:25 ` Mișu Moldovan
2011-11-28 11:09 ` Alessandro Ratti
2011-11-28 11:15 ` Mișu Moldovan
2011-11-28 11:28 ` Hannes Erven
2011-11-28 11:46 ` Mișu Moldovan
2011-11-28 12:04 ` Pandu Poluan
2011-11-28 13:44 ` Mișu Moldovan
2011-11-28 14:31 ` Pandu Poluan
2011-11-28 15:49 ` Pandu Poluan
2011-11-28 16:32 ` Mișu Moldovan
2011-11-28 16:50 ` Pandu Poluan
2011-11-28 18:27 ` Mișu Moldovan
2011-11-29 12:11 ` J. Roeleveld
2011-11-29 13:22 ` Vinícius Ferrão
2011-11-29 13:36 ` Pandu Poluan
2011-11-29 14:08 ` J. Roeleveld [this message]
2011-11-29 14:20 ` Pandu Poluan
2011-11-29 14:04 ` J. Roeleveld
2011-11-29 18:02 ` Mișu Moldovan
2011-11-30 7:38 ` J. Roeleveld
2011-11-30 8:02 ` Pandu Poluan
2011-11-29 18:26 ` kashani
2011-11-29 18:48 ` Pandu Poluan
2011-11-30 7:44 ` J. Roeleveld
2011-11-29 14:22 ` Alessandro Storti Gajani
2011-11-30 7:35 ` J. Roeleveld
2011-11-30 9:46 ` Mișu Moldovan
2011-11-28 12:26 ` [gentoo-server] " Pandu Poluan
2011-11-28 15:22 ` [gentoo-server] " Eduardo Schoedler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ef9adae73f8187e5281f141ba0f311d.squirrel@www.antarean.org \
--to=joost@antarean.org \
--cc=gentoo-server@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox