Hi Wietse and others *I found the root cause of the problem..*
I grepped through the dict and found out that utf8 module is changing the dict settings, so I wondered if anything would change if I would comment out smtputf8_enable = yes And a new test has revealed that the problem is fixed without this configuration! See below: # postmap -v -q "SRS0=xxxx=YY=domain.com=i...@otherdomain.com" tcp:localhost:10001 postmap: name_mask: ipv4 postmap: inet_addr_local: configured 5 IPv4 addresses postmap: dict_open: tcp:localhost:10001 postmap: dict_tcp_lookup: key *SRS0=xxxx=YY=domain.com <http://domain.com>=i...@otherdomain.com <i...@otherdomain.com>* postmap: trying... [127.0.0.1] postmap: dict_tcp_lookup: send: get SRS0=xxxx=YY=domain.com= i...@otherdomain.com postmap: dict_tcp_lookup: recv: 200 SRS1=Ftpn=otherdomain.com==xxxx=YY= domain.com=i...@synio.be postmap: dict_tcp_lookup: found: SRS1=Ftpn=otherdomain.com==xxxx=YY= domain.com=i...@synio.be SRS1=Ftpn=otherdomain.com==xxxx=YY=domain.com=i...@synio.be But... I do want full UTF8 support.. *So what is going wrong with the combination of UTF8 + dict_tcp_lookup?* Any ideas how to fix this in my configuration? Or is this a bug? Kind regards Wesley S. Op do 27 dec. 2018 om 23:28 schreef Wietse Venema <wie...@porcupine.org>: > Wesley van Synio: > > Is this DICT_FLAG_FOLD_MUL something that I should configure in another > > way..? > > This is the flag that according to my searches is not set anywhere > in Postfix. That's why I was asking for verbose logs as a last resort. > > Wietse > -- *Synio* *Ilgatlaan 9* *3500 Hasselt* *0477 71 79 25*
