On Tue, Mar 26, 2013 at 1:17 PM, Stan Hoeppner <s...@hardwarefreak.com> wrote:
> On 3/26/2013 7:04 AM, Lima Union wrote:
> ...
>> ok, it seems that for some reason the check is not being triggered
>> (#847) after a postfix reload and 24 hours of operation in a busy
>> server, any ideas?
>
> So when you grep "Please relay via ISP" against your mail log you get
> nothing?  Do you have any warnings or errors related to this parameter?
>  Is this host behind a NAT or proxy that doesn't pass the client rDNS
> name to Postfix?  It may be helpful to post a transaction from your log,
> addresses obfuscated if need be, so we can verify Postfix is seeing
> client rDNS strings.
>
>>    835  smtpd_recipient_restrictions =
> ...
>>    847          check_reverse_client_hostname_access
>> regexp:$config_directory/maps/fqrdns.pcre,
> ...
>
> This parameter is only supported in 2.6 and later.  This is clearly
> stated in the instructions at the top of the fqrdns.pcre file.  What
> version of Postfix are you running?
>
> --
> Stan
>

As suggested by Noel I added at the end of the file the WARN and it's
logging, thus it's using the file (also checked with postconf -n).
Postfix is mail_version 2.7.3. The problem seems to be with the rDNS
resolution as suggested by Stan, what I don't know is why it's not
working. This MTA is behing a firewall, in a DMZ with a bidirectional
mapping (1:1). I issued a grep ': connect from' and everything shown
is 'connect from unknown[ip.add.re.ss]'. I'm using pdnsd for caching
purposes. My resolv.conf points to 127.0.0.1 and seems to be working
fine:

$ dig +short -x 209.85.212.54
mail-vb0-f54.google.com.

Why postfix is not doing the rDNS? what can I check?
Thanks!

Reply via email to