From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] clamav and spamassassin
Date: Sat, 3 Dec 2011 17:57:25 -0800 [thread overview]
Message-ID: <CAN0CFw38oqPKLU5-+W=C7aa5jfGi7_Tkdx7CQdznvMWZwR7cog@mail.gmail.com> (raw)
In-Reply-To: <4EDACE76.9060400@orlitzky.com>
>> Very cool. I found out clamscan and avgfree scan the filesystem so I
>> thought I should set it up, but if it's not necessary I won't bother.
>> All of my mail users are on Gentoo so do I need to bother having
>> clamav scan my incoming mail?
>
>
> Well, they aren't going to get infected with anything, but ClamAV could
> still keep the virus message (which is obviously unwanted) out of their
> inbox. There are also some third-party signatures[1] for ClamAV that catch
> scam/phishing mail.
There is info on Linux viruses here:
http://en.wikipedia.org/wiki/Linux_malware
I shouldn't be concerned about that?
>> I just did some reading on postscreen but it doesn't sound like a
>> greylister. Should I use postscreen in addition to postgrey, or are
>> they substitutes for each other?
>>
>
> Postscreen isn't a greylist daemon per se, but it has the same effect if you
> enable the "deep protocol" tests. Once it gets past the initial greeting
> (into the "deep" stages), postscreen can no longer hand off the session to a
> real smtpd. So, even if the client passes all of the tests, postscreen will
> send it a "4xx try again." That's essentially greylisting.
Got it. Sounds like postscreen is the successor to postgrey. I will
set that up ASAP.
Thanks,
Grant
next prev parent reply other threads:[~2011-12-04 1:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 19:52 [gentoo-user] clamav and spamassassin Grant
2011-12-03 22:54 ` Michael Orlitzky
2011-12-04 0:59 ` Grant
2011-12-04 1:35 ` Michael Orlitzky
2011-12-04 1:57 ` Grant [this message]
2011-12-04 2:10 ` Michael Orlitzky
2011-12-04 1:59 ` Pandu Poluan
2011-12-04 2:17 ` Michael Orlitzky
2011-12-04 2:48 ` Pandu Poluan
2011-12-04 3:06 ` Michael Orlitzky
2011-12-04 8:27 ` Pandu Poluan
2011-12-06 0:15 ` Grant
2011-12-06 0:45 ` Pandu Poluan
2011-12-06 0:52 ` Michael Orlitzky
2011-12-06 1:01 ` Pandu Poluan
2011-12-06 1:14 ` Michael Orlitzky
2011-12-06 3:24 ` Grant
2011-12-06 4:43 ` Michael Orlitzky
2011-12-06 16:32 ` Grant
2011-12-06 17:11 ` Michael Orlitzky
2011-12-06 19:17 ` Paul Hartman
2011-12-07 0:16 ` Pandu Poluan
2011-12-06 21:34 ` Grant
2011-12-06 22:20 ` Michael Orlitzky
2011-12-07 1:02 ` Grant
2011-12-07 16:38 ` Michael Orlitzky
2011-12-07 18:16 ` Grant
2011-12-07 18:56 ` Michael Orlitzky
2011-12-07 19:00 ` Michael Orlitzky
2011-12-08 0:49 ` Grant
2011-12-07 9:15 ` Pandu Poluan
2011-12-07 16:01 ` Grant
2011-12-07 16:47 ` Pandu Poluan
2011-12-07 0:57 ` Grant
2011-12-07 1:11 ` Pandu Poluan
2011-12-07 16:34 ` Michael Orlitzky
2011-12-07 18:08 ` Grant
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='CAN0CFw38oqPKLU5-+W=C7aa5jfGi7_Tkdx7CQdznvMWZwR7cog@mail.gmail.com' \
--to=emailgrant@gmail.com \
--cc=gentoo-user@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