jim tyler

Hi, I would like to figure out how to have exim use
the local users' spamassassin preferences. My
understanding is that spam filter settings are
individual - one user's spam is another user's ham.
Hence, a site-wide spam filter may be too generic.
Since individual users have no input into site-wide
settings, I need a way to include individual settings.

I want to set up the system so that users get email by
using fetchmail through cron or a script. I figure
that I could speed things up further, from the
end-user perspective, by checking for spam and
transferring it into individual spam directories while
mail is going through the delivery process, instead of
having each user call spamassassin for each email
through a filter in their MUAs. I know I can speed
things up by deleting spam outright, but nobody wants
to lose mail to false positives. So, it seems best to
check for spam, separate it from other mail, and then
let users review their spam and use sa-learn on their
own stuff.

I am currently using the exim4 and spamassassin from
unstable on a home lan. There are five users, who
each download boat-loads of mail from IPs either via
fetchmail or directly through their MUAs. They then
use spamassassin through indivudual MUA filters.
Direct lan emailing also works fine. It may also be
important for any filtering to point out that except
for local lan mail, user names and email addresses
usually do not match.

I have been looking online and through the doc files,
esp.
usr/share/doc/exim4-daemon-heavy/exiscan-acl-examples.txt
and exiscan-acl-spec.txt., but I think I am becoming
more confused than enlightened, so I hoped people here
might share their wisdom and experiences regarding the
following questions.
Exim and its configuration have been debianized, so
are there any recommended debian ways to handle this?
If I use exiscan-acl can I set multiple users or use a
regular expression to indicate the proper user in a
"spam= " line?
Some options I have found include running mail through
exim twice. Is this a bit
complex|wasteful-of-resources|kludgy?
Would setting up a (pop|imap) server help in any way?
Should I use procmail (although, many people on
exim-users seem to find procmail inferior to exim's
filters)?
Can this even be done in exim, maybe in conjunction
with ~/.forward files?
Is my current method best left as is?
Is there something else|better that I am missing?
Thanks,
Jim

__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

nate duehr

<snipped long question...>

I have done this on a box similar to yours with only a few users by
using a procmail recipe that handles sending things to spamassassin.

Doing it that way, spamassassin is using the user's
~/.spamassassin/user_prefs file -- but shouldn't your setup via exim
directly also be doing that?

I use procmail to filter things into IMAP folders, so it was already in
place for all the users, and I just added SA to it...

Nate


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

jim tyler

Unless I'm mistaken, since exim doesn't run as the
individual users, neither would spamassassin when
called by exim. Spamassassin would, therefore, use
prefs from /etc/spamassassin instead of
~/.spamassassin, or so I thought.


So far, this looks like the best way to go.
Thanks,
Jim

__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

scruloose

By default, this is true, but if you have exim call spamassassin (or
spamc) with the -u option, it'll use the prefs for the specified user.

Using -u $local_part will supply the username of the local user the mail
is being delivered to.
Cheers! -- ,-------------------------------------------------------------------------.

`-------------------------------------------------------------------------'

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/vVHZGW5/T9+iw4kRAnaMAJ4iGIm5ETa+BOz2rLClhPSgB8duNACeNM1d
gDPt8P0J+TkYvX8dvUQO/18=
=kO1+
-----END PGP SIGNATURE-----