OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: For each check_ns or each check_mx, the value is not cached?

From: mouss (moussnetoyen.net)
Date: Tue May 06 2008 - 11:29:41 CDT

Justin Piszcz wrote:
>
>
> On Tue, 6 May 2008, Justin Piszcz wrote:
>
>> I have multiple check_ns and check_mx for different rule sets but it
>> also looks like it tries to lookup the NS or MX per each rule set.
>>
>> It appears I should try and combine all my files into one and use a
>> single check, or is there another way to do it so this does not occur?
>>
>> May 6 07:16:04 l1 postfix/smtpd[8626]: connect from
>> unknown[122.162.120.129]
>> May 6 07:16:05 l1 postfix/smtpd[8626]: warning: Unable to look up NS
>> host for ABTS-NCR-Dynamic-129.120.162.122.airtelbroadband.in: Host
>> not found
>> May 6 07:16:05 l1 postfix/smtpd[8626]: warning: Unable to look up MX
>> host for ABTS-NCR-Dynamic-129.120.162.122.airtelbroadband.in: Host
>> not found
>> May 6 07:16:05 l1 postfix/smtpd[8626]: warning: Unable to look up MX
>> host for ABTS-NCR-Dynamic-129.120.162.122.airtelbroadband.in: Host
>> not found
>> May 6 07:16:05 l1 postfix/smtpd[8626]: warning: Unable to look up NS
>> host for ABTS-NCR-Dynamic-129.120.162.122.airtelbroadband.in: Host
>> not found
>> May 6 07:16:05 l1 postfix/smtpd[8626]: warning: Unable to look up MX
>> host for ABTS-NCR-Dynamic-129.120.162.122.airtelbroadband.in: Host
>> not found
>> May 6 07:16:05 l1 postfix/smtpd[8626]: warning: Unable to look up NS
>> host for ABTS-NCR-Dynamic-129.120.162.122.airtelbroadband.in: Host
>> not found
>>
>> Example:
>> check_client_access
>> cidr:/etc/postfix/sbl_drop_peer_list.cidr,
>> check_helo_mx_access
>> cidr:/etc/postfix/sbl_drop_peer_list.cidr,
>> check_helo_ns_access
>> cidr:/etc/postfix/sbl_drop_peer_list.cidr,
>> check_sender_mx_access
>> cidr:/etc/postfix/sbl_drop_peer_list.cidr,
>> check_sender_ns_access
>> cidr:/etc/postfix/sbl_drop_peer_list.cidr

what are
    check_helo_mx_access
    check_helo_ns_access
    check_sender_ns_access
?

I don't see what you're trying to achieve anyway.
>>
>> Thanks,
>>
>> Justin.
>>
>
> The other checks/different rules I was mentioning:
>
> check_client_access cidr:/etc/postfix/spam_check_mxaccess.cidr,
> check_client_access
> pcre:/etc/postfix/spam_check_clients.pcre,
> check_helo_access pcre:/etc/postfix/spam_check_helos.pcre,
> check_helo_mx_access
> cidr:/etc/postfix/spam_check_mxaccess.cidr,
> check_sender_access
> pcre:/etc/postfix/spam_check_senders.pcre,
> check_sender_mx_access
> cidr:/etc/postfix/spam_check_mxaccess.cidr,
> warn_if_reject check_helo_ns_access
> cidr:/etc/postfix/spam_check_mxaccess.cidr,
> warn_if_reject check_sender_ns_access
> cidr:/etc/postfix/spam_check_mxaccess.cidr
>