RE: Greylisting?

From: Svavar Örn Eysteinsson (no email)
Date: Thu Jul 01 2004 - 09:51:05 EDT


Thanks alot guys. :0)

So there are no worries about SpamAssassin and postgrey together?

Best regards,

Svavar O
Reykjavik - Iceland

-----Original Message-----
From: [mailto:] On Behalf Of Kevin Coyner
Sent: 1. júlí 2004 13:41
To:
Subject: Re: Greylisting?

On Thu, Jul 01, 2004 at 02:51:55PM +0200, Magnus B?・ck wrote......

> On Thursday, July 01, 2004 at 14:46 CEST,
> Svavar 遵ムrn Eysteinsson <> wrote:
>
> > I whant to implement Greylisting in my Postfix 2.1.3,
> > amavisd-new,SpamAssassin,CLAMAV Server.
> >
> > What is the best solution out there, and most efficient?
>
> Use a policy daemon. Take a look at the postgrey project.

I just finished setting up postgrey and so far it's great. Has worked
much better than SA for me on a system that does email for a dozen
websites using a virtual setup. I still have SA running too, and
amavisd-new and Clamav all on a Debian box.

Postgrey can be found at:

http://isg.ee.ethz.ch/tools/postgrey/

Configuration is straightforward.

1. Make sure you have all of the Perl modules that are needed.
2. Add an entry like this to postfix main.cf:

smtpd_recipient_restrictions = permit_mynetworks,
        ...
        ...
        ...
        reject_unauth_destination,
        check_policy_service inet:127.0.0.1:10023
        permit

Make sure the check_policy_service line follows the
reject_unauth_destination line.

You'll have to create a postgrey user and set up a directory for the DB.
These details can be found in 'perldoc postgrey' once you've downloaded
the postgrey program.

You'll also want to set up a startup script for postgrey so if your
box goes down or gets rebooted, postgrey will start automatically BEFORE
postfix.

Good luck.

Kevin








Hosted Email Solutions

Invaluement Anti-Spam DNSBLs



Powered By FreeBSD   Powered By FreeBSD