Jon Duggan wrote:
> This email can be ignored. The .conf had SENDERMSGLIMIT=512 and users
> getting caught were the heavy ones.
>
> I guess the limit in the conf overrides the '0' placed in sql?
Correct.
Cami
-
This SF.net
This email can be ignored. The .conf had SENDERMSGLIMIT=512 and users
getting caught were the heavy ones.
I guess the limit in the conf overrides the '0' placed in sql?
Many thanks
Jon Duggan
Nuco Technologies Ltd
[EMAIL PROTECTED]
Tel. 0870 165 1300
-Original Message-
From: [EMAIL PRO
Hi All,
We're using policyd for sasl sender throttling. It's working great and
helps give us a good break down of monthly usage etc
Occasionally we get the odd user who gets rejected with quota exceeded even
though they're either;
a) way below the quotas
b) sometimes have 0 set for quota (none)
Olivier Smedts wrote:
>
> I now think that policyd doesn't need even a little modification to make
> it work perfectly with MySQL replication. It seems that there is no need
> for "IF EXIST" or "IF NOT EXIST" because UPDATE and DELETE can be made
> on non-existent keys, and INSERT DELAYED doesn
Nate a écrit :
> At 12:00 PM 10/9/2007, Olivier Smedts wrote:
>
>> I agree to the idee that replication should not happen in policyd, but
>> in MySQL, cause MySQL already supports replication and redundancy. And
>> it works nearly like a charm. But here is the problem :
>> policyd doesn't use an
Tobias Kreidl wrote:
> I am getting some odd results when I try to send mail that contains one
> or more invalid addresses -- I don't want the mail client to reject
> sending the message altogether, just report back the errors. It seems as
> if I get greylisted almost immediately, which shouldn'
I am getting some odd results when I try to send mail that contains one
or more invalid addresses -- I don't want the mail client to reject
sending the message altogether, just report back the errors. It seems as
if I get greylisted almost immediately, which shouldn't happen (I
thought) unless
