[Pkg-exim4-users] Exim configuration values not accepted

[Haines Brown]

> On Sat, Jun 23, 2007 at 08:56:26PM -0400, Haines Brown wrote:

> > I don't understand. If a message is assigned a spam score, must it
> > not have been scanned?
> 
> How do you see that the message is assigned a score?

For example, your message to this list had a spam score of 0:

  X-SA-Exim-Connect-IP: 127.0.0.1
  X-SA-Exim-Mail-From: pkg-exim4-users-bounces+brownh=hartford-hwp.com at lists.alioth.debian.org
  X-SA-Exim-Scanned: No (on alioth.debian.org); SAEximRunCond expanded to false
  X-SpamScore: 0

However, I don't understand the line above the spam score, which might
imply it was not scanned. And yet, if my incoming messages are not
scanned, how do they get a score? And I worrry about "SAEximRunCond
expanded to false". I don't know what it means, but it has an ominous
sound.

> > # reject spam at high scores (> 6)
> > deny  message = This message scored $spam_score spam points.
> >       spam = nobody:true
> >       condition = ${if >{$spam_score_int}{120}{1}{0}}
> > 
> > But messages over a score of 6 are not rejected.
> 
> Your code rejects messages over a score of 12. I don't see any "6"
> outside of the comments.

True. However, I don't understand the code itself either. This sounds
more like a way to compose a message about rejection than actually
setting rejection itself.

Let me take a step back. Spamassassin is an application that basically
runs out of the box. One installs it and it works. The same is true of
exim except for the configuration dialog that pops up when it is
installed. This configuration dialog said nothing about filters such
as SA or ClamAV, and so presumeably one need only make a simple change
in a configuration file such as to SAEximRunCond = 1. In all my
stumbling about in the documents and FAQ, I've yet to see a statement
such as: to enable exim's use of filters at SMTP time, do...  And yet
everyone else seems to have no problem.

> > > Exiscan has exactly nothing to do with a system filter.
> > 
> > I didn't mention Exiscan. I thought it had been replaced by
> > EximContentScanning. The document you directed me to seems largely
> > to do with Exiscan.
> 
> Exim Content Scanning _IS_ exiscan. The only difference is that it
> does not need to be patched in any more. Can the package description
> of exim4-daemon-heavy be clarified in this direction?

The package description says: "the content scanning extension
(formerly known as "exiscan-acl")..." While this phrase could imply it
was the same thing with simply a new name, there's also a possible
implication that there is a new entity to carry out the same function,
and this is the reason for the name change. The capitalization of
"Exim Content Scanning" tends to reinforce the misimpression that it
is an entity. Entities are often capitalized; functions are not (I am
probably inventing this rule here, so don't take it too seriously).

-- 
 
       Haines Brown, KB1GRM