SpamAssassin: SAFE_CODE not filling token

Version 1.60.1


Bug where the lack of exiting custom tags prevented the token from being filled, causing the following in the ~/.spamassasin/user_prefs file: #SAFE AREA start |SAFE_CODE| #SAFE AREA end after updating a re-save will solve the error. ---- Compile time: Jan 27 2020 at ~21:50:08 T23930

Try DirectAdmin with a 30-day money back guarantee!