Good luck…you’ll get it figured... :=)
> On Jun 9, 2019, at 5:03 PM, Ronald F. Guilmette <r...@tristatelogic.com> > wrote: > > > In message <14936220-5b2f-e44a-2f3a-5301e4153...@opendmz.com>, > cvandesa...@opendmz.com wrote: > >> $ cat /etc/postfix/transport_maps >> # Mail to anyone at opendmz.com is sent via SMTP to haproxy >> opendmz.com smtp:haproxy:10025 >> >> The haproxy is an unnecessary layer of complication I added, but it >> could just as easily be your home IP. >> I'm using dynamic DNS in case my home IP changes, but it hasn't changed >> in over 3 years now! >> >> for example: >> >> opendmz.com smtp:my-home-ip.dyndns.org:25 > > Wow! My head is spinning! > > I confess that I didn't "get it" at all when Wietse mentioned > transport maps, but I *think* I am just starting to get it now. > > So, basically, I can do what I want to do without even introducing > the extra layer of complexity of -any- separate TCP proxy, yes? > > Assuming so, this is getting easier and easier by the minute! > > If all I really need to do is to put my own personalized version of > the one-liner you posted (above) into /etc/postfix/transport_maps, > then all I can say is "Thank you Postfix!! Thank you Wietse!!" > > I can't wait to try this. I'm off now to do just that. It'll take > me awhile. I have to buy a fresh new VM, install an OS and Postfix > on it, set up dynamic DNS for my home machine, read up on how get my > SOHO router to do this fancy-schamncy port forwarding thing (for SMTP > traffic), configure and/or reconfigure two sets of Postfix .cf files, > and then reboot everything in sight and run some tests. > > Wish me luck. > > > Regards, > rfg
