On Mon, 11 Aug 2008 11:33:00 -0400 (EDT), Charles Gregory wrote:
it concerns me as to whether these remarks about 'big name' non-compliant
MTA's still apply specifically to greylisting. I mean, I can't really
imagine a 'big' (fortune 500?) company having an MTA that does not attempt
to resend mai
On 11.08.08 09:30, Dennis Peterson wrote:
> There are some big names that play badly with greylisting. They play
> badly with greet-pause, too. A problem I've seen with greylisting is the
> round-robin MTA pool. Each is told in turn to come back later and if the
> pool is large it can take a long t
Am 11.08.2008 12:05 schrieb Ian Eiloart:
In fact, if you accept the email, then silently discard it, then you
effectively endorsing the validity of the email. You'll be improving the
reputation of the original sender in the eyes of the ISP.
Worse, it can even be a punishable offense. At least
On Mon, 11 Aug 2008, Dennis Peterson wrote:
> . A problem I've seen with greylisting is the round-robin MTA pool.
> Each is told in turn to come back later and if the pool is large it can
> take a long time to cycle through all of them.
I don't suppose anyone has a list of these available for
This is what I have in my milter-greylist's greylist.conf.
The google entries are accurate as of a week or so ago, taken from their
SPF record.
list "broken mta" addr { \
12.5.136.141/32\ # Southwest Airlines (unique sender)
12.5.136.142/32\ # Southwest Airlines
On 12 Aug 2008 at 7:57, Charles Gregory wrote:
> On Mon, 11 Aug 2008, Dennis Peterson wrote:
> > . A problem I've seen with greylisting is the round-robin MTA pool.
> > Each is told in turn to come back later and if the pool is large it can
> > take a long time to cycle through all of them.
>
On Tue, Aug 12, 2008 at 01:15:13PM +0100, Paul Whelan wrote:
> On 12 Aug 2008 at 7:57, Charles Gregory wrote:
>
> > On Mon, 11 Aug 2008, Dennis Peterson wrote:
> > > . A problem I've seen with greylisting is the round-robin MTA pool.
> > > Each is told in turn to come back later and if the poo
I am configuring Clamav for the 1st time ever on my own server. I have
so far installed and configured the following:
Postfix 2.5
Dovecot 1.0.15
Amavisd-New 2.4.2
Now I am installing Clamav on Debian:
=
email:/var/log# apt-cache policy clamav
clamav:
Inst
On Tue, Aug 12, 2008 at 07:57:57AM -0400, Charles Gregory wrote:
>
> I don't suppose anyone has a list of these available for a "whitelist" or
> "avoid greylisting"? Preferably a list of IP's not domains?
>
I been using the dnswl.org DNSWL.
___
Help us
Hi, Carlos--
On Aug 12, 2008, at 5:30 AM, Carlos Williams wrote:
> Now once I have that installed, I am confused as to where to get
> guidance to start getting Clamav to work with Amavisd. Anyone have any
> tips on how this works with my distribution?
Look in your amavisd.conf for the "@av_scanne
Chuck Swiger wrote:
> Hi, Carlos--
Thanks for the reply!
> Look in your amavisd.conf for the "@av_scanners" section; you should
> check that you have a section like this:
>
> # ### http://www.clamav.net/
> ['ClamAV-clamd',
> \&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd"],
>
On Aug 12, 2008, at 10:25 AM, Carlos Williams wrote:
> I just installed amavisd so it has a very small vanilla config and I
> don't see what you mentioned above in my config. Here is what I have:
Your config looks to be about the smallest valid config, but there
might be a bigger one with comm
Chuck Swiger wrote:
> Your config looks to be about the smallest valid config, but there might
> be a bigger one with comment'ed out examples called amavisd.conf-dist or
> amavisd.conf-sample floating around somewhere. Of course, I am working
> under the assumption that you are using amavisd-ne
13 matches
Mail list logo
