On 9/19/2018 3:48 PM, Chris Pollock wrote:
> I noticed in a post that Kevin McGrail made that the 'sought' rules are
> no longer published. So, my update-channels file that SA-Update reads
> should have only one entry:
>
> updates.spamassassin.org
>
> Is that correct
>
Alex, sought isn't published,
I noticed in a post that Kevin McGrail made that the 'sought' rules are
no longer published. So, my update-channels file that SA-Update reads
should have only one entry:
updates.spamassassin.org
Is that correct
--
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
14:38:23 up 3
On 19/09/2018 19:42, Kevin A. McGrail wrote:
auto-whitelist: sql-based get_addr_entry
ign...@compiling.spamassassin.taint.org|none: SQL error: Unknown
column 'last_hit' in 'order clause'
I got the same error when drop-upgraded 3.4.1 to 3.4.2. In my case it
was a conflict between txrep and aw
On 9/19/2018 11:06 AM, Alex Woick wrote:
> I'd like to report some things I noticed while updating from SA 3.4.1
> to SA 3.4.2 on CentOS 7. No serious problems, but I'd like to mention
> if someone also tries to update on CentOS 7.
Great info, thanks.
> - upon starting spamd, I got this message in
I'd like to report some things I noticed while updating from SA 3.4.1 to
SA 3.4.2 on CentOS 7. No serious problems, but I'd like to mention if
someone also tries to update on CentOS 7.
I created the 3.4.2 rpm by downloading the latest Fedora Core 3.4.1 src
rpm. Then I did:
- remove all patches
On Tue, Sep 18, 2018 at 12:16 PM Giovanni Bechis wrote:
I noticed that Google servers started blocking emails with "suspicious spf
records" like for example:
"v=spf1 include:musvc.com include:turbo-smtp.com mx a +all".
Any idea on how to write a rule to catch something like that ?
On 18.09.18
Thanks for the feedback!
On Sep 19, 2018 03:14, "Groach" wrote:
Thanks Kevin
Both of my installations had stopped updating since 11th September due to
this. Now the updates are working again.
>From this:
11th Sep
20:00:26.57 Performing Spamassassin Update check...
Update available for chann
Thanks Kevin
Both of my installations had stopped updating since 11th September due
to this. Now the updates are working again.
From this:
11th Sep
20:00:26.57 Performing Spamassassin Update check...
Update available for channel updates.spamassassin.org: 1840397 -> 1840441
http: (lwp) GET h
