Hi Karsten,
On 7/23/2009 10:00 AM, Karsten Bräckelmann wrote:
On Thu, 2009-07-23 at 09:22 -0700, Mike Cappella wrote:
Just as an FYI. I have had (only) one experience where a positive
download contained a corrupted SOUGHT rule file, and an amavis restart
failed.
What exactly do you mean by "corrupt rule file"? Sounds to me like lint
testing should have failed already.
I didn't take the time to ascertain exactly what was wrong with the
file. I recall looking at my logs to determine what events took place
at the time amavis failed. Only the sought rule files were updated. I
attempted to start amavis, but it failed. I removed the sought file(s),
and amavis started.
Also, how exactly do you restart amavis after an sa-update? Are you
listening to the exit codes?
Yes, only on exit code 0. On exit code 1, 2, and others, I output a
diagnostic.
http://marc.info/?l=amavis-user&m=116189238122548&w=2
Hmm, the advice in the first post is wrong. I don't use amavis myself,
but AFAIK you actually do need to restart amavis after any rule changes,
contrary to what the post claims. Same with spamd, FWIW.
This is correct - amavis absolutely does need to be restarted for any SA
changes (eg. rules, code, configuration changes). I read the poster's
response "AFAIK, no." as a response to the statement:
According to << the wiki URL >>,
SA will use them "automatically".
I didn't judge that script to be complete, or the only script acting
upon the problem (there could be another, that evaluates the output).
Regardless, the general idea was there.
Also, one does not need to call 'spamassassin' to lint check. sa-update
does this. (Any lint check is not strictly necessary anyway, but a very
sensible safety measure.)
http://marc.info/?l=amavis-user&m=116213281631150&w=2
And here someone mixes up the dirs. sa-update does not use the site-
config dir for its channels -- that is, not unless one specifically
tells it to, which isn't a good idea.
I recall at that time there being much confusion on the amavis list by
many people as to exact what happened with sa-update, regarding new
rules and which directories were used various platforms, and what needed
to occur for amavis to pick up the changes. Eventually, it was sorted out.
Mike
