I think using procmail might be the best solution, giving me more control
without having to go through support at the hosting company.
--- On Fri, 9/26/08, Jake Maul <[EMAIL PROTECTED]> wrote:
Some common configurations of Exim are set up such that Exim does
*NOT* use the message as provided by Spamassassin. It gives SA a
*copy* of the message, then puts the SA headers from the copy into the
main message. This has the effect of ignoring any SA-modified headers,
like the subject. Notably, Debian's exim4-daemon-heavy is usually
configured this way.
Globally, I've fixed this by having Exim write a X-New-Subject header
if the SA score is high enough, then run a system filter at the end
that replaces Subject with X-New-Subject if it exists.... seems to be
the 'recommended' way to do this sort of thing. IIRC, Debian-Exim's
config files explain all this, if they're using Debian. Heck, it might
be in the main Exim config stuff even.
I would ask the hosting company if they can fix Exim server-side to do
this for you. Otherwise, perhaps make a procmail recipe that does it
for you?
On Fri, Sep 26, 2008 at 8:27 AM, pbr pbr <[EMAIL PROTECTED]> wrote:
> I'm using a domain hosting service that uses exim for mail. I have
little
> control other than through user_prefs file and can't change the
local.cf
> file. In fact, I can't even find it when I look in /etc.
>
>
> spamassassin --lint:
>
> [12158] warn: config: could not find site rules directory
> check: no loaded plugin implements 'check_main': cannot scan! at
> /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 164.
>
>
>
> --- On Fri, 9/26/08, Matt Kettler <[EMAIL PROTECTED]> wrote:
>
> I ask because some integration tools make their own markups, and only
> use SA to generate a list of hits. In those tools, it doesn't matter
> what you set rewrite_header to, SA will ignore you.
>
> Have you
> tried rewrite_header at the local.cf level?
>
> Have you run spamassassin --lint, to make sure it has nothing to say?
>
>
> How do you call SpamAssasin?
>
>
