I have recently implemented spam assassin in my organisation. It seems like working fine so far by tagging all suspicious mails as SPAM HEADER.
But my main intention is to forward all SPAM mails to separate account instead before reaching to mailbox of employees,
So, our system admin can monitor them and validate accordingly from that separate account .

I have recently implemented spam assassin in my organisation. It seems like working fine so far by tagging all suspicious mails as SPAM HEADER.
But my main intention is to forward all SPAM mails to separate account instead before reaching to mailbox of employees,
So, our system admin can monitor them and validate accordingly from that separate account .

Sorry for Type error/spelling mistakes & thanks in advance

A better strategy possibly. Set your spam delete threshold vey high, like 1000, then use rules to sort delete.

Then the user gets to decide grey area stuff AND admin gets to see and act on all incoming spam. This is what i do. This makes sure i can sort spam from ham. Even if the user ignores the spam (leaves it in the inbox) i can still make sure bayes picks it up. Make sure to change the subject so the user is notified on potential spam.

Once you build up a spam corpus for bayes and get your system running well, you can play with the number. I have my "rule delete threshold" set at 6. Since i can see all spam, I'm confident in the threshold.