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

[Giles Coochey]

I would say

all_spam_to address@hidden

i.e. The virtual address that sendmail is forwarding to. Wouldn't do any
harm to put both in there though.

Re: Derek's point: I guess that with some MTAs the Envelope Recipient
may not be correctly understood by spamassassin, I believe it works fine
with sendmail though.


-----Original Message-----
From: Tony Shadwick [mailto:address@hidden 
Sent: 11 August 2003 17:00
To: Giles Coochey
Cc: Derek J. Balling; address@hidden
Subject: RE: Making Spamass-Milt respect virtusertable and aliases (fwd)


So what do I add?

all_spam_to     address@hidden

or

all_spam_to     address@hidden

???

Translation, the actual user on the target system, or the virtual
address
that sendmail is forwarding?

Tony Shadwick
Manager of Internet Services
Strategic Technology Group
314-872-3000 x105

On Mon, 11 Aug 2003, Giles Coochey wrote:

> Actually I've found it to be quite useful and it does seem to detect
the
> envelope recipients that I believe you are refering to.
>
> Quoted from the Documentation:
>
> If the given address appears as a recipient in the message headers
> (Resent-To, To, Cc, obvious envelope recipient, etc,) the mail will be
> whitelisted. Useful if you're deploying SpamAssassin system-wide, and
> don't want some users to have their mail filtered. Same format as
> whitelist_from.
>
> Thanks
>
> G
>
> -----Original Message-----
> From: Derek J. Balling [mailto:address@hidden
> Sent: 11 August 2003 16:40
> To: Giles Coochey
> Cc: Tony Shadwick; address@hidden
> Subject: Re: Making Spamass-Milt respect virtusertable and aliases
(fwd)
>
>
> As has been previously mentioned many times in this long and winding
> thread, that solution only works for *some* cases.
>
> When Bob (in this example) starts getting mail for, say,
> address@hidden, that solution doesn't prevent his
mail
> from being SA-filtered.
>
> D
>
>
> On Monday, August 11, 2003, at 11:31 AM, Giles Coochey wrote:
>
> > Tony,
> >
> > Rather than edit the user_prefs file, why not edit the local.cf
system
> > wide file and put in "all_spam_to" and then the name of the user
that
> > the email is actually being delivered to?
> >
> > Other options are "whitelist_to" and "more_spam_to"
> >
> > Checkout http://www.spamassassin.org/doc/Mail_SpamAssassin_Conf.html
> > for
> > more details.
> >
> > Thanks
> >
> > Giles
> >
> >
> > -----Original Message-----
> > From: Tony Shadwick [mailto:address@hidden
> > Sent: 11 August 2003 15:10
> > To: address@hidden
> > Subject: Making Spamass-Milt respect virtusertable and aliases (fwd)
> >
> >
> > Arrrgh!!!!
> >
> > Okay, no fault of yours, but I'm having serious issues with
> > spamass-milt,
> > serious enough that my boss is considering making me taking it off.
:(
> >
> > We have a few users that are getting e-mails from virtual host
> > addresses
> > delivered locally.  For example:
> >
> > 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 a similar situation going on with my own mail server.  My
> > username
> > is numbski, but I have several virtusertable entries set up, most
> > notably,
> > tony.  I have much mail that is spam showing up addressed to tony
that
> > never reads my prefs file.  In this case, the virtusertable is
local.
> >
> > 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?
> >
> > Tony Shadwick
> > Manager of Internet Services
> > Strategic Technology Group
> > 314-872-3000 x105
> >
> > ---------- Forwarded message ----------
> > Date: Thu, 3 Jul 2003 22:30:24 +0000 (GMT)
> > From: Tony Shadwick <address@hidden>
> > To: address@hidden
> > Subject: Making Spamass-Milt respect virtusertable and aliases
> >
> > This isn't hugely high on my priority list, but I was wondering if
> it's
> > possible to get the milter to look at not just the user name, but to
> > check
> > aliases and virtusertable to use the appropriate user_prefs for
> > filtering?
> > I personally have dozens of aliases and virtusertable entries that
get
> > to
> > me in one form or another, it would be nice for them to all use my
> > user_prefs file.  Any way to do this out of the box, or does it
> require
> > a
> > patch?
> >
> > Tony Shadwick
> > Manager of Internet Services
> > Strategic Technology Group
> >
> >
> >
> > _______________________________________________
> > Spamass-milt-list mailing list
> > address@hidden
> > http://mail.nongnu.org/mailman/listinfo/spamass-milt-list
> >
> >
> >
> > _______________________________________________
> > Spamass-milt-list mailing list
> > address@hidden
> > http://mail.nongnu.org/mailman/listinfo/spamass-milt-list
> > <smime.p7s>_______________________________________________
> > Spamass-milt-list mailing list
> > address@hidden
> > http://mail.nongnu.org/mailman/listinfo/spamass-milt-list
>
>

smime.p7s
Description: S/MIME cryptographic signature