> Two months ago when we tried upgrading one of our production
mailservers
> to
> SA v3 we had a complete disaster - numerous processes spawning, heavy
load
> factors, high memory usage. I was wondering whether now that SA 3.02
has
> been released whether it is now time to try the upgrade again.
You just decided to upgrade a production mailserver without testing the
software? I assume you just maybe re-pointed your MX records and rolled
back to the working version? I don't see how much of a disaster a
rolling upgrade could be, assuming it was done properly.
The moral of this story is don't upgrade production servers without
proper testing.
> What are the opinions of those running heavily used mailservers? Any
> suggestions or words of wisdom on the proper settings to keep things
under
> control.
Well, first off, as we saw a week or two ago, there are people
processing hundreds of thousands of messages a day with spamassassin
without a problem, so I'm sure one of them could chime in.
In what configuration are you using spamassassin? Are you using a
milter interface for scanning at the MTA, or maybe procmail? There are
countless people (myself included) running SA 3.0 without any problem
what-so-ever, so me thinks you've munged up your configuration somehow.
.jon
__
"The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential, proprietary, and/or
privileged material. Any review, retransmission, dissemination or other
use of, or taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is prohibited.
If you received this in error, please contact the sender and delete
the material from all computers."
