From: Luc Pardon (lucpskopos.be)
Date: Thu Feb 02 2006 - 10:08:59 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Wietse Venema wrote:
> Patrick Ben Koetter:
>
>>> 2. Could it be that 2.3 is using $myhostname whereas 2.2 was using
>>>gethostbyname for the SASL realm ?
>
>
> Redhat added a gethostbyname() call to to the code that looks up
> the myhostname value. However, their code was broken, causing every
> Postfix program to dump core when the hostname could not be found.
>
> The unmodified Postfix expressly avoids gethostbyname() for myhostname
> lookup, so that it will not hang when the network is down.
>
> Wietse--

    OK, but that can't be the reason. My previous install, 2.2-20040829,
was also compiled straight from the official sources, no patches applied.

    However, with gethostbyname() out of the picture, I double-checked
for other ocurrences of the hostname gida.skopos.be:

> $ postconf | grep gida
> mydestination = $mydomain, gida.$mydomain, smtp.$mydomain, localhost.$mydomain, www.$mydomain, ns.$mydomain

    To recap:

        mydomain = skopos.be
        myhostname = smtp.skopos.be
        lmtp_lhlo_name = $myhostname

    The question becomes:

  2. Could it be that 2.3 is using $myhostname whereas 2.2 was using
$mydestination for the SASL realm ? Or any other reason why 2.3 uses a
different realm than 2.2?

   Maybe even a different user? Running sasldblistusers on a pre-upgrade
backup of sasldb does not even list the MYUSER that Postfix is now
trying to authenticate with ???

   Maybe I should call it a day and go reboot my brain. Meanwhile, ideas
are welcome...

    Luc

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]