Ignore error responses from automated routines is pointless.
Why not just disable the mechanism?
In that case, adding $status to your output of your script, will allow you
to met your goal of not ignoring the reported error response:
if [ $status -ne 1 ]
then
MrC wrote:
Ignore error responses from automated routines is pointless.
Why not just disable the mechanism?
In that case, adding $status to your output of your script, will allow you
to met your goal of not ignoring the reported error response:
Eh? Status is a number, nothing more. We
I said that any number besides 0 or 1 wasn't important, that the
necessary information I needed would come from standard error. You
can't say that is false.
I'm done with this conversation. I'm not sure what you don't get and I
don't much care. Your constant accusations (and misreading of
Mark,
maybe a stupid question (not to familar with Perl):
but how does FuzzyOcr.cf fit into this picture?
Also: using Your additional_perl_modules-variable I still find
extra modules loaded: /etc/mail/spamassassin/FuzzyOcr.pm-entries in my
amavisd.log every time a mail with pictures attached
Mark wrote:
Running amavisd chrooted should not be a problem, SA loads
its rules files at startup time before chroot takes place.
It should not be necessary to provide a copy of rules files
in chroot jail.
This may not be a case with some additional custom SA plugins
which come with their
Gary,
Thanks for the correction, and new feature reminder. As you can see,
I will immediately put it to good use on my system:
Oct 31 16:03:23 mail amavis[9634]: (09634-03) extra modules loaded:
/etc/mail/spamassassin/WebRedirect.pm,
/usr/share/perl5/Mail/SpamAssassin/Plugin/FuzzyOcr.pm,
Gary V wrote:
Myself, I would be more inclined modify amavisd and run this once a day:
sa-update --nogpg --updatedir \
/var/amavisd/var/lib/spamassassin/3.001004 amavisd reload
SA-Update returns with code 1 when there are no new rules. Do you want
to restart amavisd when there are no new
Peter Huetmannsberger wrote:
thanks for pointing out the warning. I am just wondering if this is still
the case though. My setup is excactly like the one, which the warning
warns about, however the sa-update creates its own directory
updates_spamassassin_org with /usr/share/spamassassin,
Gary V wrote:
Myself, I would be more inclined modify amavisd and run
this once a day:
sa-update --nogpg --updatedir \
/var/amavisd/var/lib/spamassassin/3.001004 amavisd reload
Jo Rhett wrote:
SA-Update returns with code 1 when there are no new rules.
Do you want to restart
MrC wrote:
The is a short-circuting AND; it will only perform the next command *iff*
the previous command succeeds. Since 1 is a failure, the amavisd reload
does not occur.
yeah, but it doesn't do anything intelligent in the case that the update
fails either, which is why you shouldn't do
On Thu, Nov 02, 2006 at 03:32:27PM -0800, Jo Rhett wrote:
MrC wrote:
The is a short-circuting AND; it will only perform the next command *iff*
the previous command succeeds. Since 1 is a failure, the amavisd reload
does not occur.
yeah, but it doesn't do anything intelligent in the
Hi,
sa-update --nogpg --updatedir /var/amavisd/usr/local/share/spamassassin
'amavisd debug-sa' picks up the rules. I set the above command to run
as cronjob once a week.
Read the warning:
http://marc.theaimsgroup.com/?l=spamassassin-usersm=11546111299
Gary V
thanks for
Peter wrote:
Hi,
sa-update --nogpg --updatedir /var/amavisd/usr/local/share/spamassassin
'amavisd debug-sa' picks up the rules. I set the above command to run
as cronjob once a week.
Read the warning:
http://marc.theaimsgroup.com/?l=spamassassin-usersm=11546111299
Gary V
Peter wrote:
I ran 'sa-update' as root and the directory
/var/amavisd/var/spamassassin/3.001004/updates_spamassassin_org was
created and populated with rules. Yet before that I had
/var/amavisd/usr/local/share/spamassassin containing my rules. How do
I get SA to look in the right place?
Gary V wrote:
Peter wrote:
I ran 'sa-update' as root and the directory
/var/amavisd/var/spamassassin/3.001004/updates_spamassassin_org was
created and populated with rules. Yet before that I had
/var/amavisd/usr/local/share/spamassassin containing my rules. How do
I get SA to look in the
If running 2.4.2, and SA 3.1.4, add LOCAL_STATE_DIR = '/var/lib', here:
# LOCAL_RULES_DIR = '/etc/mail/spamassassin',
LOCAL_STATE_DIR = '/var/lib',
#see man Mail::SpamAssassin for other options
stop amavisd and run amavisd debug-sa, see if it now reads the rules
from the new
--- Gary V [EMAIL PROTECTED] wrote:
Peter wrote:
I ran 'sa-update' as root and the directory
/var/amavisd/var/spamassassin/3.001004/updates_spamassassin_org was
created and populated with rules. Yet before that I had
/var/amavisd/usr/local/share/spamassassin containing my rules. How
techlist06 wrote:
If running 2.4.2, and SA 3.1.4, add LOCAL_STATE_DIR = '/var/lib', here:
# LOCAL_RULES_DIR = '/etc/mail/spamassassin',
LOCAL_STATE_DIR = '/var/lib',
#see man Mail::SpamAssassin for other options
stop amavisd and run amavisd debug-sa, see if it now reads the rules
Peter wrote:
If running 2.4.2, and SA 3.1.4, add LOCAL_STATE_DIR = '/var/lib',
here:
# LOCAL_RULES_DIR = '/etc/mail/spamassassin',
LOCAL_STATE_DIR = '/var/lib',
#see man Mail::SpamAssassin for other options
stop amavisd and run amavisd debug-sa, see if it now reads the rules
Gary wrote:
sa-update --nogpg --updatedir /var/amavisd/usr/local/share/spamassassin
'amavisd debug-sa' picks up the rules. I set the above command to run
as cronjob once a week.
Read the warning:
http://marc.theaimsgroup.com/?l=spamassassin-usersm=11546111299
Myself, I would be more
--- Gary V [EMAIL PROTECTED] wrote:
Peter wrote:
If running 2.4.2, and SA 3.1.4, add LOCAL_STATE_DIR = '/var/lib',
here:
# LOCAL_RULES_DIR = '/etc/mail/spamassassin',
LOCAL_STATE_DIR = '/var/lib',
#see man Mail::SpamAssassin for other options
stop amavisd and run
Peter wrote:
I ran 'sa-update' as root and the directory
/var/amavisd/var/spamassassin/3.001004/updates_spamassassin_org was
created and populated with rules. Yet before that I had
/var/amavisd/usr/local/share/spamassassin containing my rules. How do
I get SA to look in the right place?
I am running amavisd-new 2.4.2 and spamassassin 3.1.4 on OpenBSD 3.9.
I have only now discovered sa-update and would like to get it running.
I have read some posts on this list regarding how to do this but they
refer to directory /var/lib which does not exist on my system. I am
also running all
Peter wrote:
I am running amavisd-new 2.4.2 and spamassassin 3.1.4 on OpenBSD 3.9.
I have only now discovered sa-update and would like to get it running.
I have read some posts on this list regarding how to do this but they
refer to directory /var/lib which does not exist on my system. I
24 matches
Mail list logo
