On 30 Aug 2019, at 12:32, @lbutlr wrote:
> That is probably my error then. I remove the -Q flag manually and didn’t
> check -u since there is a scan user on the system.
Found the problem, it wasn’t spam assassin at all, it was an old crontab script
that someone how was re-enabled. removed it fr
On 30 Aug 2019, at 11:49, RW wrote:
> On Fri, 30 Aug 2019 10:58:30 -0600
> @lbutlr wrote:
>
>> I have a lot of processes that look like this:
>>
>> root 48359 100.0 1.4 55984 47680 - R17:53 989:39.50
>> /usr/local/bin/perl -T -w /usr/local/bin/sa-learn --spam -u vscan
> ...
>>
On 30 Aug 2019, at 11:49, RW wrote:
> On Fri, 30 Aug 2019 10:58:30 -0600
> @lbutlr wrote:
>
>> I have a lot of processes that look like this:
>>
>> root 48359 100.0 1.4 55984 47680 - R17:53 989:39.50
>> /usr/local/bin/perl -T -w /usr/local/bin/sa-learn --spam -u vscan
> ...
>>
On Fri, 30 Aug 2019 10:58:30 -0600
@lbutlr wrote:
> I have a lot of processes that look like this:
>
> root 48359 100.0 1.4 55984 47680 - R17:53 989:39.50
> /usr/local/bin/perl -T -w /usr/local/bin/sa-learn --spam -u vscan
...
> /var/spool/spamd/.spamassassin/bayes_toks Aug 30 1
I have a lot of processes that look like this:
root 48359 100.0 1.4 55984 47680 - R17:53 989:39.50
/usr/local/bin/perl -T -w /usr/local/bin/sa-learn --spam -u vscan
/usr/local/virtual/kr...@kreme.com/Maildir/.Junk/cur/15670…
/usr/local/virtual/kr...@kreme.com/Maildir/.Junk/cu
