Bastian Blank:
> On Wed, Aug 29, 2012 at 01:01:52PM +0200, Bernhard Schmidt wrote:
> > ok: 134.130.87.26 -PTR-> domaindnszones.geotechnik.rwth-aachen.de
> > -A-> 134.130.87.26
> > ok: -PTR-> forestdnszones.geotechnik.rwth-aachen.de
> > -A-> 134.130.87.26
> > ok: -PTR-> g
On Wed, Aug 29, 2012 at 01:01:52PM +0200, Bernhard Schmidt wrote:
> ok: 134.130.87.26 -PTR-> domaindnszones.geotechnik.rwth-aachen.de
> -A-> 134.130.87.26
> ok: -PTR-> forestdnszones.geotechnik.rwth-aachen.de
> -A-> 134.130.87.26
> ok: -PTR-> gc._msdcs.geotechnik.rwth-aa
Benny Pedersen:
> Den 2012-08-29 13:18, Bernhard Schmidt skrev:
>
> > gc._msdcs.geotechnik.rwth-aachen.de
>
> _adsp._domainkey.example.org
> foo._domainkey.example.net
These are not HOST NAMES, therefore they are irrelevant to this discussion.
Wietse
Den 2012-08-29 13:18, Bernhard Schmidt skrev:
gc._msdcs.geotechnik.rwth-aachen.de
_adsp._domainkey.example.org
foo._domainkey.example.net
bar._example.org
dont know if the last one is valid, but the 2 first is
Am 29.08.2012 13:34, schrieb Wietse Venema:
> Please run the attached programs ON THE AFFTECTED MACHINE. They
> show what Postfix gets from your libc routines.
>
> ./getnameinfo ipaddr
> ./getaddrinfo hostname (once for each result from getnameinfo).
So it's indeed the system resolver ... see the
Please run the attached programs ON THE AFFTECTED MACHINE. They
show what Postfix gets from your libc routines.
./getnameinfo ipaddr
./getaddrinfo hostname (once for each result from getnameinfo).
Wietse
/*
* getaddrinfo(3) (name->address lookup) tester.
*
* Compile with:
*
Bernhard Schmidt:
> Am 29.08.2012 13:20, schrieb Wietse Venema:
> > Postfix logs a WARNING message if it has a problem with the hostname.
> > Show that logfile message.
>
> I have no warning message about that, that's what is bothering me. Even
Postfix does not refuse to use a name without loggin
Am 29.08.2012 13:20, schrieb Wietse Venema:
> Postfix logs a WARNING message if it has a problem with the hostname.
> Show that logfile message.
I have no warning message about that, that's what is bothering me. Even
with the test client in the debug_peer_list and debug_peer_level = 10
the output
Postfix logs a WARNING message if it has a problem with the hostname.
Show that logfile message.
Wietse
Am 29.08.2012 13:05, schrieb Mike:
> On 12-08-29 08:01 AM, Bernhard Schmidt wrote:
>
>> We suspect (and verified with an internal client with custom rDNS)
>> that the _msdcs entry is at fault. This hostname does not seem to get
>> accepted. As soon as I remove the '_' it works fine.
>>
>
> Have a
On 12-08-29 08:01 AM, Bernhard Schmidt wrote:
We suspect (and verified with an internal client with custom rDNS)
that the _msdcs entry is at fault. This hostname does not seem to get
accepted. As soon as I remove the '_' it works fine.
Have a read:
http://en.wikipedia.org/wiki/Hostname#Res
Hello,
we are running Postfix (2.8.4 on SLES10.4 on that particular box, but I
also verified with 2.9.1 on Debian Squeeze) with
smtpd_client_restrictions =
reject_unknown_reverse_client_hostname,
reject_unknown_client_hostname,
(extensive whitelists of course as well). One sou
12 matches
Mail list logo
