I found their forwarding policy is somewhat strange.
They changed the "to:" header address in the forwarded email to the
destination address.
For example, u...@foo.com writes to t...@5x2.de, this mail will be
forwarded to d...@gmail.com
When gmail receives this email, the "to:" header is d...@gmail
Linkcheck:
> Sorry Wietse, I thought it might be the other way around: postfix
> wasn't picking up the dovecot reference.
There is a real protocol between Postfix and Dovecot. Postfix will
complain when it is unable to speak that protocol with Dovecot, or
when it receives an unexpected response.
Maybe you can ask on the DOVECOT list why DOVECOT isn't providing
Postfix with SASL mechanism names.
Wietse
I am setting up a new postfix/dovecot/etc mail server. Apart from a few
new features, due to new versions, I have copied a similar setup which
has been running well for several years. A few days ago the new server
was working, with just a few tweaks required for dkim/dmarc/etc. At that
stage I
Jos Chrispijn:
> Recently read this in my logfile
>
> midna_domain_to_ascii_create: Problem translating domain
> "?M-^X??M-^X??M-^X??M-^...
>
> Can you tell what is triggering this?
Some domain name contained binary garbage, causing the conversion
from UTF8 domain name to PUNY code (a 7-bit for
Recently read this in my logfile
midna_domain_to_ascii_create: Problem translating domain
"�M-^X§�M-^X®�M-^Xª�M-^...
Can you tell what is triggering this?
Thanks.
-- With both feet on the ground you can't make any step forward
