Do not even bother with your 2.55 local installation. It's a waste of
effort and time to try to make it work.
Besides, "can't be done" from within SpamAssassin. If you get REALLY
imaginative you might be able to do it with procmail. But that falls
back to the "why bother?" If the employer runs an older version or an
ineffective version install a copy in a personal set of directories.
With some imagination I bet it can be done. You'll have to run spamd
on a different TCP address or else run straight spamassassin, though.
{^_^}
----- Original Message -----
From: <[EMAIL PROTECTED]>
My (large) employer runs SpamAssassin on all incoming mail. My local UNIX
account, managed by a separate technical support group, is on a machine which
also has spamassassin available. Running the local version removes the
headers added by the central version. While I can see good reasons for this,
I would really like to be able to filter on both sets of headers.
Is there a way to tell SpamAssassin to either leave the old headers intact, or
(ideally) to rename them, rather than deleting them?
No version info available for the central instance. Local version is 2.55 --
sorry, I have no control over this. I normally run spamc from my .forward
file, but am willing to consider other options, possibly including my own copy
of spamassassin, although I do not have superuser priviliges on this machine.
Thanks.
