, as I cannot dedicate too much
time to it.
Ivo Truxa (the creator of TxRep)
-Original Message-
From: Benny Pedersen [mailto:m...@junc.eu]
Sent: Friday, August 1, 2014 12:26 AM
To: Joe Quinn; users@spamassassin.apache.org
Cc: Ivo Truxa
Subject: Re: duplicate key value violates unique
On July 30, 2014 9:33:07 PM Joe Quinn jqu...@pccc.com wrote:
TxRep is currently in trunk with instructions for migrating from AWL, if
you want to try and reproduce the bug.
i have tried to keep up on gentoo with sa 3.4 with is sadly not in portage
yet, so i begined make it into my own
Hi,
I am using a PostgreSQL database to store the AutoWhiteList entries but from
time to time I see in my PostgreSQL log file the following entries:
2014-07-30 12:07:42 CEST ERROR: duplicate key value violates unique constraint
awl_pkey
2014-07-30 12:07:42 CEST DETAIL: Key (username, email
On 7/30/2014 6:28 AM, ML mail wrote:
Hi,
I am using a PostgreSQL database to store the AutoWhiteList entries
but from time to time I see in my PostgreSQL log file the following
entries:
2014-07-30 12:07:42 CEST ERROR: duplicate key value violates unique
constraint awl_pkey
2014-07-30 12
PostgreSQL log file
the following entries:
2014-07-30 12:07:42 CEST ERROR: duplicate key value violates
unique constraint awl_pkey
2014-07-30 12:07:42 CEST DETAIL: Key (username, email,
signedby, ip)=(amavis, em...@domain.tld, , none) already exists.
2014-07-30 12:07:42 CEST
On 7/30/2014 9:37 AM, ML mail wrote:
So if I understand correctly this behavior is expected/normal and not
an error from my side (for example having done something wrong in the
config file or so).
That would be my synopsis, yes.
Thanks for confirming! I will then simply ignore...
On Wednesday, July 30, 2014 3:43 PM, Kevin A. McGrail kmcgr...@pccc.com wrote:
On 7/30/2014 9:37 AM, ML mail wrote:
So if I understand correctly this behavior is expected/normal and not an error
from my side (for example having done
On July 30, 2014 12:28:44 PM ML mail mlnos...@yahoo.com wrote:
It looks like SpamAssassin tries to INSERT an entry (e-mail address) which
already exists. Shouldn't SpamAssassin AWL code first check if an entry
exists or not and use UPDATE instead of INSERT if an entry already exists?
awl
On 7/30/2014 10:47 AM, Benny Pedersen wrote:
On July 30, 2014 12:28:44 PM ML mail mlnos...@yahoo.com wrote:
It looks like SpamAssassin tries to INSERT an entry (e-mail address)
which already exists. Shouldn't SpamAssassin AWL code first check if
an entry exists or not and use UPDATE instead
