[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Re: Block email TO one user in a domain on RaQ4
- Subject: Re: [cobalt-users] Re: Block email TO one user in a domain on RaQ4
- From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
- Date: Wed Dec 11 11:33:01 2002
- Organization: nobaloney.net
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
Charlie Summers wrote:
> where it more reasonably belongs and is somewhat easier to
> impliment and maintain. See www.sendmail.org for info on
> FEATURE(blacklist_recipients), and the archives for working with the
> redhat.mc/cobalt.mc file.
Thanks for showing us another way to do it, Charlie.
It's good that we can differ <smile>. I believe that userlevel stuff
for virtual users logically belongs in virtusertable, so that's where I
put it.
I believe domain level stuff belongs in access, and that's where I put
it.
> I prefer not to muck with the virtusertable, frankly, keeping the
> blacklisted records (both in and out) in the same access database for simple
> reference and management. (FWIW, my access file is ~257k in size, with the
> hashed access.db file being considerably larger. I block a _lot._ ;)
As I see it, "mucking" with virtusertable is no more or less likely to
impact your system than is "mucking" with access; both are converted to
hash databases.
Jeff
--
Jeff Lasman, nobaloney.net, P. O. Box 52672, Riverside, CA 92517 US
Internet & Unix/Linux/Sun/Cobalt Consulting +1 909 778-9980
Our jblists address used on lists is for list email only
To contact us offlist: "http://www.nobaloney.net/contactus.html"