From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: dn_expand() confuses postfix
Date: Tue, 13 Aug 2013 14:38:17 -0400 [thread overview]
Message-ID: <20130813183816.GF221@brightrain.aerifal.cx> (raw)
In-Reply-To: <20130814021920.7e719d8f@sibserver.ru>
On Wed, Aug 14, 2013 at 02:19:20AM +0800, orc wrote:
> musl's dn_expand() confuses postfix - always returns 0, then postfix's
> libdns.a gets wrong shifts and gives up with something like:
>
> ../test_dns_lookup: lookup yandex.ru type MX flags 2
> ../test_dns_lookup: dns_query: yandex.ru (MX): OK
> ../test_dns_lookup: warning: dns_get_fixed: bad class: 30722
> ../test_dns_lookup: fatal: Name service error for name=yandex.ru type=MX: Malformed or unexpected name server reply
>
> If someone will face same error with postfix & musl, then get portable
> dn_expand.c from
> http://tclsysdns.googlecode.com/svn/trunk/unix/dn_expand.c and put it
> in src/dns (edit Makefile.in to include src & obj).
Cleaning up this code is part of the roadmap for 0.9.13, but I wasn't
aware that it was returning the wrong value. Thanks for bringing that
to my attention.
> (btw running whole LAMP/FTP stack with musl - some issues appear like
> iconv need to be replaced with libiconv to make some CMS happy, so I
> have some compatibility experience here.
Do you know what problems they hit with iconv? It's my intention that
iconv not need to be replaced. My guess is that the issue is failure
to automatically detect UTF-16 endianness via BOM, or missing charset
aliases for some charset strings.
> Musl much more perfect than I
> expected)
Great to hear. :-)
Rich
next prev parent reply other threads:[~2013-08-13 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 18:19 orc
2013-08-13 18:38 ` Rich Felker [this message]
2013-08-13 19:09 ` orc
2013-08-13 20:36 ` Rich Felker
2013-08-14 22:06 ` Rich Felker
2013-08-15 6:14 ` orc
2013-08-15 6:36 ` Rich Felker
2013-08-25 6:43 ` Rich Felker
2013-08-25 8:42 ` orc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130813183816.GF221@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).