Noah just answered in detail but I wanted to follow-up specifically to the questions I asked. :-)
Nigel Horne wrote:
> Bob Proulx wrote:
> > How did you configure it?
>
> I used the supplied Debian configuration to Spamassassin, which is
> why I'm reporting it. But still, any help would be really
> appreciated.
The 'spamassassin' package doesn't include any configuration for
sending email into it. It just supplies the classification engine.
Therefore it can't be an issue either good or bad with the
spamassassin package. Because the spamassassin package doesn't
control what email is sent through it. It is the car engine and not
the road the car drives upon.
> > On Debian systems the most common way is to use procmail to send email
> > through spamassassin and then react to the results of the
> > classification. But there are other possible ways to configure it
> > too. In any case if you have configured it to classify incoming email
> > then it will classify incoming email because that is what it has been
> > configured to do.
>
> I use spamass-milter. Does that have any bearing?
That is absolutely *the* critical part! :-)
apt-cache show spamass-milter
A milter used to filter mail through spamassassin (spamc)
early in the delivery process. Enables site wide filtering through
spamassassin without speed penalties incured by setting up and
tearing down procmail processes for each e-mail.
That is the process you have configured that sends email through
spamassassin. That is the road upon which the car is driving. If you
do or do not want any particular mail to be sent through spamassassin
then it is the spamass-milter package that you have installed that is
controlling that part of the behavior. Spamassassin it self has no
control over it.
I have never use spamass-milter and so don't know anything more about
it. I suggest now that this information is now known that this bug be
closed because it isn't associated with spamassassin.
Neither does this seem like a bug in spamass-milter either. You
previously said:
> Everything I can find on the web says that by default this e-mail
> should not be scanned but it is ...
Sorry but that is not correct. I don't know where you read that
information but it isn't true. Mail is sent to spamassassin and it
scans the messages and makes a classification of them. The process
that sends the messsages to SA is also the process that decides what
to do with the result. There isn't any standard for doing it. There
are many different ways to do it and one must pick one and do it. As
that StartUsing reference link I sent shows there are a number of
different ways to make use of SA.
You are using spamass-milter to integrate spamassassin into your mail
transfer agent (mta). That is perfectly fine. A lot of people do it
that way. But when you set that up that means that it will send all
email that passes through the mta through spamassassin. That is
great. But if you don't want that to happen then it is within the
province of spamass-milter to either do it or to not do it. There is
likely a configuration in spamass-milter to control which email is
sent through SA. Or perhaps there is a configuration in your mail
transport agent to decide which email is sent through the configured
spamass-milter "milter" (aka mail-filter). I suggest investigating
there.
Hope that helps,
Bob
signature.asc
Description: Digital signature
