I believe this is a known issue fixed in svn. We need to get 3.4.3 out the
door for this. Are you able to test with the 3.4 branch from svn?
On Wed, Jan 9, 2019, 23:59 listsb hi-
>
> the subject expresses my uneducated hypothesis as to what might be causing
> a problem i seem to have encountere
W dniu 2019-01-10 o 12:05, Kevin A. McGrail pisze:
> I believe this is a known issue fixed in svn. We need to get 3.4.3 out
> the door for this. Are you able to test with the 3.4 branch from svn?
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7623
OK, I'm confused.
I'm trying to get spamd to log to my maillog but can't figure out what's going
wrong.
I'm invoking spamd like this ...
/usr/bin/perl -T -w /usr/bin/spamd --syslog=mail -d -c -m5 -H
--razor-home-dir=/var/lib/razor/ --razor-log-file=sys-syslog -r /var/run/spamd.pid
I have t
On 1/10/19 6:03 PM, David Gibbs wrote:
I'm trying to get spamd to log to my maillog but can't figure out what's
going wrong.
Also, spamd is logging oddly even in the messages file...
Jan 10 18:11:32 listmail spamd[21867]: logger: removing stderr method
Jan 10 18:11:33 listmail check[21869]: sp
On Jan 10, 2019, at 06.05, Kevin A. McGrail wrote:
>
> I believe this is a known issue fixed in svn. We need to get 3.4.3 out the
> door for this. Are you able to test with the 3.4 branch from svn?
thanks. i've done a crude test just grabbing sa-update from svn, with some
progress:
>sa-upd
listsb skrev den 2019-01-11 05:15:
sa-update -v --allowplugins --channelfile
/etc/spamassassin/sa-update-conf.d/channels.txt --gpgkeyfile
/etc/spamassassin/sa-update-conf.d/sa-update-keys.txt --gpghomedir
/var/lib/spamassassin/sa-update-keys
Update available for channel sought.rules.yerp.org:
On 10 Jan 2019, at 23:15, listsb wrote:
On Jan 10, 2019, at 06.05, Kevin A. McGrail
wrote:
I believe this is a known issue fixed in svn. We need to get 3.4.3
out the door for this. Are you able to test with the 3.4 branch from
svn?
thanks. i've done a crude test just grabbing sa-update
