OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: Access.db doesn't seem to filter incoming mail...

From: Magnus Bäck (magnusdsek.lth.se)
Date: Tue Jul 12 2005 - 00:06:20 CDT


On Tuesday, July 12, 2005 at 06:24 CEST,
     Michael & Julie Jones <julemikyahoo.com> wrote:

> Here's the contents of my access file and my current postconf. My goal
> is to block all e-mail coming in from 218.x.x.x . Also attached is the
> internet header of the e-mail from that block that continues to come in
> despite my current configuration (besides 218, I continue to get from
> other blocks for which I've explicitly stated REJECT). YES I DO run
> postmap /etc/postfix/access which generates access.db . Should I be
> using ' hash:/etc/postfix/access.db ' instead of
> 'hash:/etc/postfix/access ' ????

[...]

> smtpd_sender_restrictions = hash:/etc/postfix/access,

This is equivalent to:

smtpd_sender_restrictions = check_sender_access hash:/etc/postfix/access

To reject messages based on the client address, use check_client_access.

> reject_non_fqdn_sender, reject_unknown_sender_domain, reject_rbl_client
> relays.ordb.org, reject_rbl_client blackholes.mail-abuse.org,
> reject_rbl_client relays.mail-abuse.org
> transport_maps = hash:/etc/postfix/transport
> unknown_local_recipient_reject_code = 550
>
> E-MAIL HEADER

Never mind the header. The logs are what's important.

[...]

--
Magnus Bäck
magnusdsek.lth.se