Glad you found the issue.
Your trouble shooting approach was spot on with the step by step
tweaking and checks.
Thanks for keeping us updated :)
Evan
On 2019/02/13 02:00, Ken Wright wrote:
Success!
I got so frustrated I reformatted the hard drive and started over. This
time, after
Success!
I got so frustrated I reformatted the hard drive and started over. This
time, after installing SA and before any tweaking, I tried to start it,
and it worked. So I started checking after every tweak, so I could find
where the problem lay. Turns out the Options line in
On 2/12/19 9:53 AM, Bill Cole wrote:
> On 12 Feb 2019, at 1:14, Ken Wright wrote:
>
>> On 2/11/19 11:42 PM, Bill Cole wrote:
>>> On 11 Feb 2019, at 21:40, Ken Wright wrote:
>>>
On 2/11/19 9:33 PM, Bill Cole wrote:
> On 11 Feb 2019, at 20:24, Ken Wright wrote:
>
>> it does say
On 12 Feb 2019, at 1:14, Ken Wright wrote:
On 2/11/19 11:42 PM, Bill Cole wrote:
On 11 Feb 2019, at 21:40, Ken Wright wrote:
On 2/11/19 9:33 PM, Bill Cole wrote:
On 11 Feb 2019, at 20:24, Ken Wright wrote:
it does say it's loading the Mail::SpamAssassin::Plugin::Check
module
This is
It seems to be a legacy setting in Ubuntu for backwards compatibility...
On 2019/02/12 15:45, RW wrote:
On Tue, 12 Feb 2019 08:33:09 +0200
Evan Booyens wrote:
Also check that the actual spamassassin config directory is
/etc/spamassassin and that there is a symlink
at /etc/mail/spamassassin ->
On Tue, 12 Feb 2019 08:33:09 +0200
Evan Booyens wrote:
> Also check that the actual spamassassin config directory is
> /etc/spamassassin and that there is a symlink
> at /etc/mail/spamassassin -> /etc/spamassassin
>
> If not, create it with ln -s /etc/spamassassin /etc/mail/spamassassin
On 2/12/19 1:56 AM, Evan Booyens wrote:
>
> Hi Ken
>
> My only other fix would be to specify the config path in
> /etc/default/spamassassin at the OPTIONS="" section - add in
> "--configpath=/etc/spamassassin " at the start of the configs.
>
> Hope it helps.
>
I checked, and it's already there.
Hi Ken
My only other fix would be to specify the config path in
/etc/default/spamassassin at the OPTIONS="" section - add in
"--configpath=/etc/spamassassin " at the start of the configs.
Hope it helps.
On 2019/02/12 08:38, Ken Wright wrote:
On 2/12/19 1:33 AM, Evan Booyens wrote:
Also
On 2/12/19 1:33 AM, Evan Booyens wrote:
>
> Also check that the actual spamassassin config directory is
> /etc/spamassassin and that there is a symlink at
> /etc/mail/spamassassin -> /etc/spamassassin
>
> If not, create it with ln -s /etc/spamassassin /etc/mail/spamassassin
>
Just checked. The
Also check that the actual spamassassin config directory is
/etc/spamassassin and that there is a symlink at /etc/mail/spamassassin
-> /etc/spamassassin
If not, create it with ln -s /etc/spamassassin /etc/mail/spamassassin
On 2019/02/12 08:14, Ken Wright wrote:
On 2/11/19 11:42 PM, Bill
On 2/11/19 11:42 PM, Bill Cole wrote:
> On 11 Feb 2019, at 21:40, Ken Wright wrote:
>
>> On 2/11/19 9:33 PM, Bill Cole wrote:
>>> On 11 Feb 2019, at 20:24, Ken Wright wrote:
>>>
it does say it's loading the Mail::SpamAssassin::Plugin::Check module
>>>
>>> This is evidence that one or more
On 11 Feb 2019, at 21:40, Ken Wright wrote:
On 2/11/19 9:33 PM, Bill Cole wrote:
On 11 Feb 2019, at 20:24, Ken Wright wrote:
it does say it's loading the Mail::SpamAssassin::Plugin::Check
module
This is evidence that one or more of the following is true about
spamd:
1. It is using a
On 2/11/19 9:33 PM, Bill Cole wrote:
> On 11 Feb 2019, at 20:24, Ken Wright wrote:
>
>> it does say it's loading the Mail::SpamAssassin::Plugin::Check module
>
> This is evidence that one or more of the following is true about spamd:
>
> 1. It is using a different SpamAssassin config than you
On 11 Feb 2019, at 20:24, Ken Wright wrote:
it does say it's loading the Mail::SpamAssassin::Plugin::Check module
This is evidence that one or more of the following is true about spamd:
1. It is using a different SpamAssassin config than you use from the
command line
2. It is using a
On 2/11/19 7:23 PM, sha...@shanew.net wrote:
> I'd suggest running spamassassin directly from the command line with
> the -D and --lint options to see if that provides more detail about
> what exactly is going wrong. This is going to give you a lot of
> output so you'll probably want to run it
I'd suggest running spamassassin directly from the command line with
the -D and --lint options to see if that provides more detail about
what exactly is going wrong. This is going to give you a lot of
output so you'll probably want to run it like:
spamassassin -D --lint 2>&1 | less
On Sun, 10
On 2/10/19 3:56 AM, Giovanni Bechis wrote:
> On Sun, Feb 10, 2019 at 02:30:28AM -0500, Ken Wright wrote:
>> I've been trying to set up an email server and I want to use
>> Spamassassin to prevent it from becoming Spam Central. I've installed
>> SA and spamass-milter, but when I try to restart
On 2/10/19 7:35 AM, @lbutlr wrote:
Don't do it!
Why not?
Seriously, running and maintaining a mail server is practically a
full-time job.
I profoundly disagree.
I spend less than 30 minutes a week administering my email / web / dns /
news / shell servers. I've been spending about the
On 10 Feb 2019, at 00:30, Ken Wright wrote:
> I've been trying to set up an email server
Don't do it!
Seriously, running and maintaining a mail server is practically a full-time
job. Do you really want to spend a lot of time (and some time nearly every day)
maintaining and patching and
On Sun, Feb 10, 2019 at 02:30:28AM -0500, Ken Wright wrote:
> I've been trying to set up an email server and I want to use
> Spamassassin to prevent it from becoming Spam Central. I've installed
> SA and spamass-milter, but when I try to restart it after customizing
> the config files, I get
I've been trying to set up an email server and I want to use
Spamassassin to prevent it from becoming Spam Central. I've installed
SA and spamass-milter, but when I try to restart it after customizing
the config files, I get this:
Job for spamassassin.service failed because the control process
21 matches
Mail list logo
