duplicate key value violates unique constraint "bayes_seen_pkey"

2015-01-29 Thread ML mail
Hi, I am using SA on Debian 7 with all Debian standard packages as well as a PostgreSQL database to store all Bayes data. >From time to time I see the following error in the PostgreSQL log file: 2015-01-29 11:56:26 CET ERROR: duplicate key value violates unique constraint "bayes_seen_pkey"

Re: duplicate key value violates unique constraint "awl_pkey"

2014-07-30 Thread ML mail
Thanks for confirming!  I will then simply ignore... On Wednesday, July 30, 2014 3:43 PM, Kevin A. McGrail 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 someth

Re: duplicate key value violates unique constraint "awl_pkey"

2014-07-30 Thread ML mail
expected/normal and not an error from my side (for example having done something wrong in the config file or so). On Wednesday, July 30, 2014 3:02 PM, Kevin A. McGrail wrote: On 7/30/2014 6:28 AM, ML mail wrote: Hi, > >I am using a PostgreSQL database to store the AutoWhiteList

duplicate key value violates unique constraint "awl_pkey"

2014-07-30 Thread ML mail
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,

Re: SA on a backup MX

2014-07-08 Thread ML mail
test and see if this is doable. In the worst case the INSERT queries would fail but maybe SA can handle that properly and still work or else I simply disable Bayes on the backup MX. On Wednesday, July 9, 2014 12:40 AM, RW wrote: On Tue, 8 Jul 2014 12:48:58 -0700 ML mail wrote: > He

Re: SA on a backup MX

2014-07-08 Thread ML mail
My backup MX will be on located on another continent this is the main reason (latency) why I would like a local read-only replica of my database on the backup MX server. On Tuesday, July 8, 2014 9:57 PM, Antony Stone wrote: On Tuesday 08 July 2014 at 21:48:58, ML mail wrote: > He

SA on a backup MX

2014-07-08 Thread ML mail
Hello, I would like to run SpamAssassin on my backup MX as well in order to avoid spam and backscatter. My backup MX will have a similar setup and configuration as my main MX, that would be Postfix+amavisd-new+ClamAV+SpamAssassin. Now I have all my user configuration including SpamAssassin Ba

Re: AWL in SQL with amavisd-new

2014-06-26 Thread ML mail
promising btw! On Thursday, June 26, 2014 6:26 PM, Benny Pedersen wrote: ML mail skrev den 2014-06-26 16:42: > Ok so if I understand you correctly you are saying that it is possible > to use AWL as site-wide having just one part of the e-mail exchange > (the "To:" field)

Re: AWL in SQL with amavisd-new

2014-06-26 Thread ML mail
Ok so if I understand you correctly you are saying that it is possible to use AWL as site-wide having just one part of the e-mail exchange (the "To:" field) and this works fine/reliabily? On Thursday, June 26, 2014 4:34 PM, Kevin A. McGrail wrote: On 6/26/2014 10:31 AM, ML mail

AWL in SQL with amavisd-new

2014-06-26 Thread ML mail
Hi, I am using the auto-whitelist feature of SpamAssassin stored into a PostgreSQL database. It works fine but I have got one issue: as I am calling SA from amavisd-new, the username stored in the AWL SQL table is always "amavis". Now this renders my AWL useless as the username should actually