Problem translating domain to UTF8 form

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Problem translating domain to UTF8 form

Mark Raynsford
Hello.

I'm using a fresh install of Postfix 3.2.2 and am seeing strange
warning messages in the log when mail bounces:

Jul  1 19:15:16 mail postfix/bounce[88353]: warning: midna_domain_to_utf8_create: Problem translating domain "mail.io7m.com" to UTF8 form: U_FILE_ACCESS_ERROR
Jul  1 19:15:16 mail postfix/bounce[88353]: warning: [built-in]:
conversion "myhostname" failed: input value: "mail.io7m.com"

Here's the output of postconf -Mf and postconf -n:

http://ataxia.io7m.com/2017/07/01/postconf.txt

I've been using this same configuration for over a year, and
this problem appears to have appeared when I migrated to a new
VPS (with different operating system and Postfix package
versions).

The only thing I can think of, from searching for the
U_FILE_ACCESS_ERROR code online, is that the library code
doing the conversion (libicu?) is failing to load its own
internal resource files. Perhaps this is because "bounce"
is running in a chroot? That doesn't really explain why this
configuration has worked for so long, though...

My system is:

$ uname -a
FreeBSD mail.io7m.com 11.0-RELEASE-p9 FreeBSD 11.0-RELEASE-p9 #0: Tue
Apr 11 08:48:40 UTC 2017
[hidden email]:/usr/obj/usr/src/sys/GENERIC  amd64

I'm using the binary packages distributed as part of the ports
system.

Any ideas?

M

attachment0 (871 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problem translating domain to UTF8 form

Wietse Venema
You could try without chroot, that would help identifying the
problem. If the problem is that ICU library does file lookups after
process initialization, then we don't have much choice - either
duplicate the files until eternity, or don't run the process chrooted.

I am on vacation, so this is not a good time to fetch a DVD imaage
and build a VM for testing.

        Wietse
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problem translating domain to UTF8 form

Viktor Dukhovni
In reply to this post by Mark Raynsford
On Sat, Jul 01, 2017 at 09:41:32PM +0000, Mark Raynsford wrote:

> Jul  1 19:15:16 mail postfix/bounce[88353]: warning: midna_domain_to_utf8_create: Problem translating domain "mail.io7m.com" to UTF8 form: U_FILE_ACCESS_ERROR
> Jul  1 19:15:16 mail postfix/bounce[88353]: warning: [built-in]:
> conversion "myhostname" failed: input value: "mail.io7m.com"

> The only thing I can think of, from searching for the
> U_FILE_ACCESS_ERROR code online, is that the library code
> doing the conversion (libicu?) is failing to load its own
> internal resource files. Perhaps this is because "bounce"
> is running in a chroot?

That's the most likely cause.

> My system is:
>
> $ uname -a
> FreeBSD mail.io7m.com 11.0-RELEASE-p9 FreeBSD 11.0-RELEASE-p9 #0: Tue
> Apr 11 08:48:40 UTC 2017
> [hidden email]:/usr/obj/usr/src/sys/GENERIC  amd64

On my FreeBSD system:

    $ uname -sr
    FreeBSD 11.0-RELEASE-p8

tracing "posttls-finger" shows:

    stat("/usr/local/share/icu/58.2/icudt58l.dat",{ mode=-rwxr-xr-x ,inode=220126,size=26213232,blksize=131072 }) = 0 (0x0)
    openat(AT_FDCWD,"/usr/local/share/icu/58.2/icudt58l.dat",O_RDONLY,00) = 3 (0x3)

Quite likely this file is needed in the chroot jail, or avoid chroot.

--
        Viktor.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problem translating domain to UTF8 form

Mark Raynsford
On 2017-07-01T22:33:16 +0000
Viktor Dukhovni <[hidden email]> wrote:
> > Perhaps this is because "bounce"
> > is running in a chroot?  
>
> That's the most likely cause.

Thanks, all. The chroot was the issue. I've no idea why it has suddenly
become a problem, but I can live without running bounce chrooted.

M

attachment0 (871 bytes) Download Attachment
Loading...