Re: Making Spamass-Milt respect virtusertable and aliases (fwd)

[Cassandra Lynette Brockett]

Using sendmail -bv should expand the virtusertable entries correctly.

I currently have modified spamd on my system to provide the same
functionality, and using sendmail -bv to do so, and that has been working
well for about six months now.

Oh, if anyone needs the patch for the short run (until Dan can get the
milter functionality running), I'd be happy to provide the patch to spamd
for you.  Of course, remember this is a source patch, so you would need to
reapply the patch to every version of spamd that comes out... and the
authors of spamassassin don't see the current functionality they have as a
problem - so they won't be using my patch (I asked in case anyone is
interested).

Regards,
    Cassandra

PS - I guess it's time to update my copy of spamass-milter locally then... I
need to give this new code tree a test - and see how it functions with my
patch in spamd.

----- Original Message ----- 
From: "Dan Nelson" <address@hidden>
To: "Tony Shadwick" <address@hidden>
Cc: <address@hidden>
Sent: Monday, August 11, 2003 3:16 PM
Subject: Re: Making Spamass-Milt respect virtusertable and aliases (fwd)


> In the last episode (Aug 11), Tony Shadwick said:
> > We have a mail host, @tseinc.com.  I create the user 'limited'.  Their
> > e-mail address is now address@hidden
> >
> > On an external mail exchanger (not the same system) there is a
> > virtusertable entry stating that  address@hidden is actually
> > address@hidden
> >
> > Said user HATES spamassassin, and is demanding that it be taken off of
> > his account.  Okay, so I go into his user_prefs and set his threshhold
to
> > 100.  His mail is still getting tagged as spam because spamassassin is
> > looking for the user 'bob' to read his prefs, isn't finding that user,
so
> > it's using the global defaults instead of ever thinking to look at
> > 'limited'.
> >
> > I have one workaround in mind, but it's a real kludge.  In my first
> > example, it would be to create the user bob, symlink his ~/.spamassassin
> > directory to limited's home, set a .forward in bob's home directory to
> > address@hidden
> >
> > Okay, so wishful thinking is something that checks /etc(/mail)/aliases
and
> > /etc/mail/virtusertable and uses the correct user_prefs.  Is there a way
I
> > can manually set this up on a per-user basis so I don't have users
wanting
> > to rip my head off?
>
> I just started adding code to expand usernames;  if you want to see
> whether it'll do what you want, try build the current CVS (or 0.2.0+cvs
> tarball from teh website) and run with the -d rcpt flag.  It'll log
> something like this for each recipient:
>
> Aug 11 17:05:34 gatekeeper spamass-milter[24972]: calling
/usr/sbin/sendmail -bv "<address@hidden>"
> Aug 11 17:05:34 gatekeeper spamass-milter[24972]: sendmail output:
address@hidden deliverable: mailer esmtp, host dan.emsphone.com.,
user address@hidden
> Aug 11 17:05:34 gatekeeper spamass-milter[24972]: user:
address@hidden
> Aug 11 17:05:34 gatekeeper spamass-milter[24972]: Expanded to 1 recipients
> Aug 11 17:05:34 gatekeeper spamass-milter[24972]: remembering recipient
<address@hidden>
>
> Currently all it does it log.  The final code will call spamc with the
> expanded username (the one on the third line in the above output), only
> if it expanded to one recipient.  If it expands to more than one,
> you'll get the "defaultuser" value just like if the mail was addressed
> to two recipients originally.
>
> Let me know if it's logging correctly-expanded virtusertable users; I
> don't have any so I have just been testing with /etc/aliases expansion.
>
> -- 
> Dan Nelson
> address@hidden
>
>
> _______________________________________________
> Spamass-milt-list mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/spamass-milt-list
>