Hi
More fooling around with postfix,
Using in main.cf
smtpd_sender_restrictions = reject_unknown_reverse_client_hostname
did not do what I expected:
from the /var/log/mail/info file:
Jul 12 09:12:48 rap postfix/smtpd[6597]: NOQUEUE: reject: RCPT from
unknown[92.45.179.70]: 450 4.7.1 Client h
2009/7/12 Keld Jørn Simonsen :
> from the /var/log/mail/info file:
>
> Jul 12 09:12:48 rap postfix/smtpd[6597]: NOQUEUE: reject: RCPT from
> unknown[92.45.179.70]: 450 4.7.1 Client host rejected: cannot find your
> reverse hostname , [92.45.179.70]; from=
> to= proto=ESMTP helo=
>
> I then used
On Sun, Jul 12, 2009 at 11:55:36AM +0200, Ole Tange wrote:
> 2009/7/12 Keld Jørn Simonsen :
>
> > from the /var/log/mail/info file:
> >
> > Jul 12 09:12:48 rap postfix/smtpd[6597]: NOQUEUE: reject: RCPT from
> > unknown[92.45.179.70]: 450 4.7.1 Client host rejected: cannot find your
> > reverse
On Sunday, July 12, 2009 at 12:07 CEST,
Keld Jørn Simonsen wrote:
> On Sun, Jul 12, 2009 at 11:55:36AM +0200, Ole Tange wrote:
>
> > Notice how you get a 4xx error code. It may simply be your
> > nameserver did not get an answer quickly enough.
Indeed, but 450 is on the other hand the defau
Magnus Bäck wrote:
Anyway asy70.asy179.tellcom.com.tr is a NXdomain. So maybe postfix
tries to look up the name it got from the PTR.
reject_unknown_reverse_client_hostname only checks that the PTR
lookups succeeds, it doesn't care about the lookup result like
reject_unknown_client_hostname doe
Keld J?rn Simonsen:
> Hi
>
> More fooling around with postfix,
>
> Using in main.cf
>
> smtpd_sender_restrictions = reject_unknown_reverse_client_hostname
>
> did not do what I expected:
>
> from the /var/log/mail/info file:
>
> Jul 12 09:12:48 rap postfix/smtpd[6597]: NOQUEUE: reject: RCPT f
On Sun, Jul 12, 2009 at 08:15:11AM -0400, Wietse Venema wrote:
> Keld Jørn Simonsen:
> > Hi
> >
> > More fooling around with postfix,
> >
> > Using in main.cf
> >
> > smtpd_sender_restrictions = reject_unknown_reverse_client_hostname
> >
> > did not do what I expected:
> >
> > from the /var/lo
On Sun, July 12, 2009 11:48, Keld Jørn Simonsen wrote:
> 70.179.45.92.in-addr.arpa domain name pointer asy70.asy179.tellcom.com.tr
> And this means that there is a PTR RR.
correct
dig asy70.asy179.tellcom.com.tr
gives the reverse ip ? :) (92.45.179.70)
> Can it be something about postfix not s
Keld Jørn Simonsen wrote:
Is it true that if a PTR was found, then this name would be displayed in
the above log message, and not the IP number?
No, the name will still be "unknown" if the hostname->IP
lookup fails.
Anyway, can you confirm that there is no check on availablilty of the
dom
On Sun, Jul 12, 2009 at 03:20:21PM -0500, Noel Jones wrote:
> Keld Jørn Simonsen wrote:
>>
>> Is it true that if a PTR was found, then this name would be displayed in
>> the above log message, and not the IP number?
>
> No, the name will still be "unknown" if the hostname->IP lookup fails.
OK.
>
>
On Sun, 12 Jul 2009, Keld Jørn Simonsen wrote:
> >> Anyway if it is a name server timeout, then I think this is always
> >> handled by a 450 response. In my case the mail was rejected.
> >
> > Yes, temporary errors always get a 450 response.
>
> Then I do not understand why the message was reject
On Sun, July 12, 2009 22:47, Sahil Tandon wrote:
> On Sun, 12 Jul 2009, Keld Jørn Simonsen wrote:
>
>> >> Anyway if it is a name server timeout, then I think this is always
>> >> handled by a 450 response. In my case the mail was rejected.
>> >
>> > Yes, temporary errors always get a 450 response.
On Mon, 13 Jul 2009, Benny Pedersen wrote:
> On Sun, July 12, 2009 22:47, Sahil Tandon wrote:
> > On Sun, 12 Jul 2009, Keld Jørn Simonsen wrote:
> >
> >> >> Anyway if it is a name server timeout, then I think this is always
> >> >> handled by a 450 response. In my case the mail was rejected.
> >>
13 matches
Mail list logo
