Thomas Trepper:
> One public ip is an official MX-record and I need postfix to accept
> eMails for certain domains (usually incoming mail) and relay them to
> another dyndns-ip postfix installation, which will only accept those
> domains for local storage. Then I am running a webserver on the same
> machine where the official mx-postfix installation is (with the other
> public ip) and I need the same postfix to accept all eMails (usually
> external outgoing mail) from the webserver and relay them (auth) to a
> provider-mailer (wp180.webpack.hosteurope.de)
>
> Basically postfix should answer for the incoming eMails with "postfix
> 2.5 for abc.com" and for the outgoing with "postfix 2.5 xyz.com", so
> that it is impossible to determine which official mx has accepted which
> virtual domains...
The first function just shuttles bits between the Internet and the
dyndns-ip installation. You don't need an MTA for that. It seems
to me that an ngnix proxy would do the job just fine.
Only the web application function would benefit from having an MTA.
The MTA can retry deliveries so that the web application won't have
to wait.
Wieste
