Re: multiple instances of SpamAssassin

[ci...@comcast.net]

>>>>> jdow  writes:

> 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.

I have no evidence that the central version is either old or ineffective.  But
I also want to be able to add spam/ham messages of my own, which can only be
done on the local system.  At the same time, I am not eager to give up the
advantage gained due to the large number of messages processed centrally.
This is a problem regardless of what version is running locally -- unless
there is a way to retain the original headers.

I note in passing that my original submission to this list arrived back with
both an X-Spam-Status and an X-Old-Spam-Status header.  No idea how or why,
although my reading is that this was done at apache.org.  This is exactly the
behavior I'm looking for.


>>>>> cilantro05 writes:

> > 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 co py of spamassassin, although I do not have superuser
> > priviliges on this machine .  Thanks.