Re: [policyd-users] sender throttling by ip

2007-07-24 Thread John Beaver
Juan Pablo Bagnon wrote: > >> thanks for the tip. >> > i'm in the middle of that, throttling not working as expected. >> > >> > i dont know what im doing wrong >> >> post postconf -n for each instance of postfix >> post logs >> >> >> > oh jesus, dont know how to say this: > > SENDERTHROTTLE=1 >

Re: [policyd-users] Questions Regarding Turning On Spamtrap

2007-07-24 Thread John Beaver
Joe Lanager wrote: > Thanks John and everyone else for all the advise. So, I entered the > domain in the spamtrap table as '@mybogusdomain.com' but it didn't work > so I changed the entry to '[EMAIL PROTECTED]' but spamtrapping still > doesn't seem to be catching the attempted delivery to that bog

Re: [policyd-users] sender throttling by ip

2007-07-24 Thread Juan Pablo Bagnon
>> thanks for the tip. > i'm in the middle of that, throttling not working as expected. > > i dont know what im doing wrong post postconf -n for each instance of postfix post logs oh jesus, dont know how to say this: SENDERTHROTTLE=1 sorry to all for the spam and thanks for the help john -

Re: [policyd-users] sender throttling by ip

2007-07-24 Thread Juan Pablo Bagnon
> what im doing wrong? > is it needed 2 postfix instances or just 2 calls to 2 diff policyd > instances, one on smtp_client_restrictions and the other in > smtp_recipient_restrictions? You best bet is to run 2 instances of policyd Instance 1 - greylisting, etc. Instance 2 - Throttling Call the

Re: [policyd-users] sender throttling by ip

2007-07-24 Thread John Beaver
Juan Pablo Bagnon wrote: >> >> >> > what im doing wrong? >> > is it needed 2 postfix instances or just 2 calls to 2 diff policyd >> > instances, one on smtp_client_restrictions and the other in >> > smtp_recipient_restrictions? >> >> You best bet is to run 2 instances of policyd >> Instance 1 - gre

Re: [policyd-users] sender throttling by ip

2007-07-24 Thread John Beaver
Juan Pablo Bagnon wrote: > i need to control de message rate hitting my content filter server (CFS). > > i have installed 2 instances of postfix > > 1- recipient check, greylisting and holding mail > 2- throttling to the content filter server. > > i have followed the README file. > i have insert

Re: [policyd-users] chroot breaking name lookups

2007-07-24 Thread Antonio Querubin
On Tue, 24 Jul 2007, Jan-Frode Myklebust wrote: > I changed it to resolve the name once it reads it from the config file. > Now my completely empty CHROOT=/var/empty/policyd works fine. > > -- > --- generic.c.original 2007-07

[policyd-users] sender throttling by ip

2007-07-24 Thread Juan Pablo Bagnon
i need to control de message rate hitting my content filter server (CFS). i have installed 2 instances of postfix 1- recipient check, greylisting and holding mail 2- throttling to the content filter server. i have followed the README file. i have inserted in throttle one line as advised in

Re: [policyd-users] chroot breaking name lookups

2007-07-24 Thread Jan-Frode Myklebust
On 2007-07-24, Cami Sardinha <[EMAIL PROTECTED]> wrote: > > The resolution could take place before the chroot() occurs. I changed it to resolve the name once it reads it from the config file. Now my completely empty CHROOT=/var/empty/policyd works fine. ---

Re: [policyd-users] chroot breaking name lookups

2007-07-24 Thread Cami Sardinha
Jan-Frode Myklebust wrote: > We run policyd v1.81 as user/group policyd, chroot to an empty > directory /var/empty/policyd/. But then policyd isn't able to > resolve my MYSQLHOST hostname. If I use ip-address it works fine. > > It complains: > > policyd: connecting to mysql database: >

[policyd-users] chroot breaking name lookups

2007-07-24 Thread Jan-Frode Myklebust
We run policyd v1.81 as user/group policyd, chroot to an empty directory /var/empty/policyd/. But then policyd isn't able to resolve my MYSQLHOST hostname. If I use ip-address it works fine. It complains: policyd: connecting to mysql database: policyd: mysql_real_connect(): Unkno