Upgrading Spamassassin from 3.1.0 to 3.1.7

I'm opening this thread for general issues relating to upgrading
Spamassassin (SA) from v3.1.0 to v3.1.7 on Westhost.

With SA v3.1.0, too much SPAM is getting past it, so I'm hoping that
a simple upgrade toi v3.1.7 will detect more SPAM automatically.

WARNING: If you have modified your procmailrc file you better
back it up before upgrading to v3.1.7. I chose the option to
upgrade from v3.1.0 to v3.1.7 and it wiped out my customized
file... etc\procmailrc

Fortunately I had my procmailrc file backedup

I simply uploaded my customized procmailrc file that I was
previouly using with v3.1.0 .

Bad News:
Copying my old procmailrc file caused my email to stop working!
I sent myself an email and it did not get bounced back, it did not
get tagged as SPAM, and I never received it. It got totally lost.

I reverted back to the procmailrc file that installs with SA v3.1.7
and my Email works again but it's not working as it used to where
all ***SPAM*** tagged email was automatically forwarded to
a separate mail box named... spam . I'm now receiving the
***SPAM*** tagged email on my regular email box.

Below is my old procmailrc file that won't work with v3.1.7
but worked perfectly with v3.1.0. What's wrong?

Both:
:0:
and
:0
are valid lines. The first means create a lock file before running the rule, the second means don't bother with a lock file.
I suspect that your edited file was saved in Windows format (guaranteed to kill procmail) and when WH looked at it, they saved it in Unix format. just a guess.

Upgrading SA may make a difference in the amount of spam blocked but usually minor upgrades (such as 3.1.0 to 3.1.7) are either bug fixes or efficiency improvements, it probably won't effect the amount getting caught.
What can have an effect though is your ruleset. You can either write your own rules or use some such as Rules Emporium have. I use rules_du_jour and they have served me well.

Both:
:0:
and
:0
are valid lines. The first means create a lock file before running the rule, the second means don't bother with a lock file.
I suspect that your edited file was saved in Windows format (guaranteed to kill procmail) and when WH looked at it, they saved it in Unix format. just a guess.

Hmmmm, you might be right about the actual problem being the
format I saved the procmailrc file. I used either Notepad or Wordpad.
I've always edited my files on my Windows PC and uploaded them
with no problems. What would you suggest I use, Notepad or Wordpad?