Hi John
Am 26.08.2015 um 18:44 schrieb John Fawcett:
That header is not added by postfix, but by Dovecot. It reports where
Dovecot gets the message from.
You can influence this with postfix configurations (like
lmtp_bind_address and lmtp_bind_address6 and setting up customized lmtp
Hmm, something like this in dovecot
inet_listener lmtp {
# Avoid making LMTP visible for the entire internet
address = 127.0.0.1
port = 24
}
processes and transports for each destination with separate ips or maybe
by changing to a different method of delivering email to dovecot) but
it's a lot of effort to go to. In your situation, I'd evaluate the
complexity of the various solutions against the simplicity of just
setting up a service domain that handles email (and potentially other
services like dns) for all the hosted domains.
John
Right now i use unix_listener but inet_listener on a local loopback
address like 127.0.0.5/port 222 would not
be a big deal. But there are more questions comming up. How can i
establish diffrent lmtp connects to a postfix
single postfix instance?? As far as i understand, i need diffrent config
files on Postfix AND Dovecot side wich leads
to multiinstance hosting of postfix and dovcecot, right?
I tested postfix instances on my CentOS 7.1 box an hour ago, but it
didnt work well because SELinux is blocking write access
to the new created multi instance /var/spoo/postfix/domain01.tld
/var/spoo/postfix/domain02.tld ect. audit log show denied
messages if i try to start systemctl start postfix.serivce. Hmm looks
very tricky...
Dravion
