Payal Rathod wrote: > Hi, > I use SA 2.61, I want to upgrade next week. How safe is it? It is our > client's server and they have given it to us to use so we cannot disturb > it cos' they too have 2 domains of theirs on it. It is a RH ES 3.0 > Also what is the best way to upgrade safely and to which version is it > recommended? Please ask if you need more info. > > >
Upgrading to 2.64: simple, straightforward, no changes. However, this is a pretty stale version and you're not going to get a lot of the new features. Upgrading to 3.0.5 or 3.1.0. This is fairly easy as long as you have perl 5.6.1 or higher. However, some options have changed. Read the UPGRADE file for full details: http://svn.apache.org/repos/asf/spamassassin/branches/3.1/UPGRADE Read the upgrading to 3.1.0 and upgrading to 3.0.x sections. Important highlights: 1) shut down SA and run sa-learn --rebuild before upgrade. After upgrade run sa-learn --sync. 2) "rewrite_subject" and "subject_tag" have been replaced by the "rewrite_header" command. 3) the -a command line parameter has been replaced by the "use_auto_whitelist" config option. 4) two new config files will be placed in your /etc/mail/spamassassin directory. init.pre and v310.pre. These are important as they control what plugins get loaded. Do not try to copy their contents to local.cf, as the need to be parsed early in order to work. Hence the ".pre" extension. Feel free to read these files and enable or disable various plugins.
