-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jason Haar writes:
> I'm the author of the Qmail content filter Qmail-Scanner, and currently
> it calls spamc as "spamc -u [EMAIL PROTECTED]" so as to help out the sites
> doing per-user SA configs.
>
> I've assumed that anyone wanting to do this would be using SQL backends
> (so requiring them to refer to local accounts as "[EMAIL PROTECTED]" is
> fine) - but apparently I presumed too much! Some are just interested in
> standard old /home/$USER/.spamassassin/ style lookups. Now calling
> "spamc -u [EMAIL PROTECTED]" doesn't work for them as there is no local
> username called "[EMAIL PROTECTED]".
>
> So I could add yet another feature to Qmail-Scanner where it will strip
> back to the username - or SpamAssassin could.
>
> I don't mind either way - it's just that I wonder if this is also an
> issue for other SA-integrated MTAs (milter, postfix), so thought I'd
> post it out for comment? Maybe others can suggest another way of doing
> it? [Let's not dwell on the fact that spamd may have to run as root for
> this mode to work...]
Hi Jason!
There's a general problem, though -- which is that SpamAssassin doesn't
have the information to deal with just one of those cases. Take a look.
So there's two items of data:
- RCPT TO address ("[EMAIL PROTECTED]")
- username ("user")
Now, we could add code to SpamAssassin to assume that "[EMAIL PROTECTED]"
translates to the username "user", but in reality *it may not* -- the MTA
configuration could have an alias that translates it to username "jm"
instead of "user".
So in that case, it makes more sense to wait for the MTA to translate it,
and let the MTA pass on the 'real', fully-alias-resolved username instead.
- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFBtlTfMJF5cimLx9ARAlGhAKCykTUGmqJ/Fxey0++0AwCiOyjmoQCguoeK
7sGO4hPDb4QTNTVf+B5Nmw8=
=GmI5
-----END PGP SIGNATURE-----
