In message <8154118f-d266-aec3-4a6d-fb9e59af3...@pccc.com>, "Kevin A. McGrail" <kmcgr...@pccc.com> wrote:
>Well, first, my firm's commercial Raptor anti-pam solution supports >smarthosting for outbound and inbound on an alternate port. Add any >dynamic DNS solution and you are good to go. Plus you get the best >business anti-spam solution. Happy to chat more about pricing. Thank you, but I need to be frank. VM slices are less expensive than water these days. And also, I'm the world's biggest cheapskate. So I do believe that I will be rolling my own solution in this instance. But thanks anyway. >But that leads to my answer. You can just setup a box on a VM with a >static IP and do smtp authentication for smarthosting through that box >and use it as a relay for your domain on an alternate port using Dynamic >DNS. No need for fetchmail or anything like that. I believe that I understand fully how to handle my outbound email traffic, i.e. treating my (soon to be) cloud VM running Postfix as a "smarthost" for outbound. That part is the easy part, and also the simple part. The harder part is handing the inbound email traffic for my several domains. I *think* that I *may* perhaps understand your suggestion with regards to that, but I'll have to think about it awhile longer before I can be sure. I wish that I had an example to look at, or some slightly-more-detailed write-up to refer to that would show me how to configure this exact approach with Postfix. But if worse comes to worse, I can probably puzzle it all out, starting from just what you said, above. One part that I'm sure that I -do not- understand is why you suggeted an alternative port number. Can you explain? Also, I've never set up any Postfix instance to be a relay before, ever, so I'm hoping that there is a README available on that specific topic (and I'll be googling for that any second now.) The only other thing I can say for now is that although I understand how MXs and their priorities work, I'm really still not too clear on how I would get mail to go to the (static IP) cloud VM Postfix instance most or all of the time, in the first instance, and -then- get all of that stuff to flow, afterwards, to the (secondary) Postfix that I have running out at the dynamic FQDN... when that machine is actually online. Regards, rfg
