I appreciate that you would like to see it working right, Daryl. To
that, I'd add, "me, too." But, like I said, I had to move on, and I
hope to get back to it soon. And, by the way, I played with setting
the update paths to all kinds of places, and all kinds of
permissions, too. ;-) I'm sure
Andy Norris wrote:
No, it was not a permissions issue. I'll get back to working on it soon,
but, yes there were newer versions than what I was seeing on my server.
There are so many posts about sa-update not working. I'm sure sa-update
works, for some folks, but it wasn't for me, and I had to
No, it was not a permissions issue. I'll get back to working on it
soon, but, yes there were newer versions than what I was seeing on my
server. There are so many posts about sa-update not working. I'm sure
sa-update works, for some folks, but it wasn't for me, and I had to
quit spending time
Daniel J McDonald wrote:
On Tue, 2007-10-30 at 08:35 -0500, Andy Norris wrote:
So a down and
dirty approach I took was writing a crop job that removes that
directory just before running sa-update.
So, you delete it every time, even when there are no updates? And since
updates occur about
On Tue, 2007-10-30 at 08:35 -0500, Andy Norris wrote:
> Hi,
>
> I don't know if this is relevant for you or not, but on our mail
> server I could not get sa-update to work, either. I noticed that if
> the directory was not there, however, it would work.
Sounds like a permissions issue.
>
inal Message-
> From: Rob Starr [mailto:[EMAIL PROTECTED]
> Sent: 30 October 2007 13:30
> To: users@spamassassin.apache.org
> Subject: RE: Custom rules working, but not sa-updates
>
>
> Boy, that's a handy command. I'll have to write that one down.
>
> I&
t;>
>>> In /etc/MailScanner/MailScanner.conf check the
>> "Spamassassin Local State
>>> Dir" line.
>>>
>>> Mine reads:
>>>
>>> SpamAssassin Local State Dir = # /var/lib/spamassassin
>>>
>>> Cheers,
&
ug --debug-sa
output say it is using?
Cheers,
Phil
--
Phil Randal
Network Engineer
Herefordshire Council
Hereford, UK
-Original Message-
From: Rob Starr [mailto:[EMAIL PROTECTED]
Sent: 30 October 2007 12:29
To: users@spamassassin.apache.org
Subject: RE: Custom rules working, but not sa
g?
>
> Cheers,
>
> Phil
> --
> Phil Randal
> Network Engineer
> Herefordshire Council
> Hereford, UK
>
>> -Original Message-
>> From: Rob Starr [mailto:[EMAIL PROTECTED]
>> Sent: 30 October 2007 12:29
>> To: users@spamassassin.apach
t; To: users@spamassassin.apache.org
> Subject: RE: Custom rules working, but not sa-updates
>
>
> Thanks for your response Phil,
>
> In an attempt to resolve the issue, I'm now using MailScanner
> 4.64.3 and
> have started from a fresh config file, so my "Spam
re Council
> Hereford, UK
>
>> -Original Message-
>> From: Rob Starr [mailto:[EMAIL PROTECTED]
>> Sent: 30 October 2007 11:54
>> To: users@spamassassin.apache.org
>> Subject: Re: Custom rules working, but not sa-updates
>>
>>
>> I
Randal
Network Engineer
Herefordshire Council
Hereford, UK
> -Original Message-
> From: Rob Starr [mailto:[EMAIL PROTECTED]
> Sent: 30 October 2007 11:54
> To: users@spamassassin.apache.org
> Subject: Re: Custom rules working, but not sa-updates
>
>
> I should
I should also mention that SA 3.1.3 was working flawlessly until the update
to 3.2.3. I've used the newer config files and been through most of the
options, but still no luck.
Rob Starr wrote:
>
> Hi,
>
> I'm using Postfix + MailScanner + MailWatch + SpamAssassin 3.2.3.
>
> My problem is
13 matches
Mail list logo
