On Sat, Jan 12, 2019 at 02:10:37PM -0500, listsb wrote:
>
> that said, i don't quite follow the second statement, if i'm honest. i
> suppose that some people may run sa-update or spamassassin as root, but i
> don't, and would be filing bugs against any packagers or distributors that
> were
> On Jan 11, 2019, at 10.55, Henrik K wrote:
>
> On Wed, Jan 09, 2019 at 11:59:36PM -0500, listsb wrote:
>>
>>> sa-update -vvv --allowplugins ...
>
> Just a general note, I would never ever use --allowplugins unless it's your
> personal channel. There is no reason why official channels should
On Jan 11, 2019, at 00.24, Bill Cole
wrote:
>
> 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
On 11 Jan 2019, at 10:22, Kris Deugau wrote:
Bill Cole wrote:
On 10 Jan 2019, at 23:15, listsb wrote:
Update available for channel sought.rules.yerp.org: -1 ->
3402014020421
And finally: that rule channel has not been updated in almost 4 years
and almost surely will never be updated again.
On Fri, 11 Jan 2019 10:22:13 -0500
Kris Deugau wrote:
> Bill Cole wrote:
> > On 10 Jan 2019, at 23:15, listsb wrote:
> >> Update available for channel sought.rules.yerp.org: -1 ->
> >> 3402014020421
>
> > And finally: that rule channel has not been updated in almost 4
> > years and almost
On Wed, Jan 09, 2019 at 11:59:36PM -0500, listsb wrote:
>
> >sa-update -vvv --allowplugins ...
Just a general note, I would never ever use --allowplugins unless it's your
personal channel. There is no reason why official channels should ever
distribute plugins as it would be basically remote
Bill Cole wrote:
On 10 Jan 2019, at 23:15, listsb wrote:
Update available for channel sought.rules.yerp.org: -1 -> 3402014020421
And finally: that rule channel has not been updated in almost 4 years
and almost surely will never be updated again.
I'm pretty sure it's been longer than that
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
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
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:
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
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
hi-
the subject expresses my uneducated hypothesis as to what might be causing a
problem i seem to have encountered after upgrading to 3.4.2.
i have an additional channel defined [sought.rules.yerp.org], and updates of
this channel seem to have broken upon updating to 3.4.2:
>sa-update -vvv
13 matches
Mail list logo
