Hi John,
I was able to figure out and running Postfix AND Dovecot Multinstancing.
The Dovecot Multiinstance Features works fine, but
Postfix-Multiinstancing (at least under CentOS 7.1 + SELinux enabled)
has some problems with IPv6 port bindings but IPv4 was ok, even if i was
using smtpd_bind_address6 for
the IPv6 Port bindings. But the same config with IPv4
(smtpd_bind_address) was ok - strange. If i run Postfix in
single Instance mode all IPv6 Ports are binding well. As far as i can
see in the SELinux audit log, there was no
denied messages. Anyhow, i dont use this config right now, so it doesnt
bother me.
Postfix Single instance + Dovecot Multiinstances works fine and any
master.cf smtpd -o lmtp:inet:127.0.0.1 2201 / 2 / 3 ect was connected
correctly to its pee the Dovecot Instance (dovecot -c
/etc/dovecot/domain01.tld.conf / dovecot -c
/etc/dovecot/domain02.tld.conf ect)
I was not able to solve the unwanted "Received: from xxx.xxxxx.tld by
mail.xxxx.tld" E-Mail Header entries.
I noticed (if i run multi smtpd -o per each smtp.domain01.tld domain)
some external EMailservers
cannot connect at all, so i had to confirgure a secondary fallback IPv4
listener in master.cf smtpd -o then the
external EMail was able reach my server. Unfortently i have many IPv6
Addresses but only 1 IPv4 Address.
As far as i know, maybe something like /etc/postfix/headerchecks is my
best bet to filter out some
unwandted email received header entries.
cheers,
Dravion
Am 27.08.2015 um 09:18 schrieb John Fawcett:
for each mta per
domains smtp.mydomain01.com smtp.mydomain02.com
ect. But unfortently the Received from: Header in Thunderbird and
other Mailclients sill is pointing to smtp.mydomain01.com
also if it was sended to smtp.mydomain02.com.
You are using lmtp not smtp to connect to dovecot. If you've set up new
smtp entries in master.cf that will affect only email you're sending out
to other mail servers, not the email you're delivering to dovecot. Also
you would need per domain transport table entries.
Maybe its an IPv6 to IPv4 translation problem and the mta falling back
to my secondary ipv4 mx entry because a lot of mail companys thems
to support IPv4 only and not accepting IPv6.
