Date: Sun, 23 Jun 2002 11:16:20 +0200 From: Cyrille Lefevre <cyrille.lefevre@laposte.net> To: Gregory Neil Shapiro <gshapiro@FreeBSD.ORG> Cc: security@FreeBSD.ORG Subject: Re: Possible security liability: Filling disks with junk or spam Message-ID: <20020623091620.GB95941@gits.dyndns.org> In-Reply-To: <15637.11607.813966.761277@horsey.gshapiro.net> References: <3D13FFB2.39A80570@pantherdragon.org> <200206221716.g5MHGmJZ082170@orthanc.ab.ca> <20020623015353.GB14530@gits.dyndns.org> <15637.11607.813966.761277@horsey.gshapiro.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 22, 2002 at 07:07:19PM -0700, Gregory Neil Shapiro wrote: > cyrille.lefevre> the access seems to be only for domains, not users... > > It can be used for usernames and complete addresses as well. However, for > blocking incoming addresses, you need: > > FEATURE(`blacklist_recipients') > Turns on the ability to block incoming mail for certain > recipient usernames, hostnames, or addresses. For > example, you can block incoming mail to user nobody, > host foo.mydomain.com, or guest@bar.mydomain.com. > These specifications are put in the access db as > described in the anti-spam configuration control section > later in this document. ok, so, we should have both features access_db and blacklist_recipients to block delivery to local users. not seen that before. thanks. Cyrille. -- Cyrille Lefevre mailto:cyrille.lefevre@laposte.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020623091620.GB95941>