Maybe something like I'm doing? I have 3 instances of postfix running (because I travel) but this can work with 2. 1 server in the cloud, 2 locally one home one office.
The 2 local postfix instances only accept public email from the cloud VM, but they accept local email (ipcam's, for example on the LAN). The MX record points to the cloud VM, should it pass the spam test then the 'clean' email is relayed to 1 of the 2 local postfix servers. The local servers then deliver to a local Dovecot, where I access my email from a local private IP on the LAN. Think of the flow like this. public email > Cloud VM (postscreen/rspamd test passes) > local Postfix > local Dovecot. Whichever local Dovecot received the message with replicate to the other site. I think of it this way, the email is coming from the public internet, so scan it while it's out on the public internet. If it passes the test, then it's considered 'good enough' to be delivered to one of the local servers. Internal email like ipcam's, server emails never leave the local LAN (except to be replicated to the other local site). Hope that makes sense. Chris. On 09/06/2019 23:00, Antonio Leding wrote: > AHHH - yes, thank you Paul - I did mean “cloud” based Postfix… > > > >> On Jun 9, 2019, at 2:53 PM, Pau Amma <paua...@gundo.com> wrote: >> >> On Sun, June 9, 2019 9:29 pm, Ronald F. Guilmette wrote: >>> In message >>> <0100016b3e069855-f95cf3e2-9649-4a55-8290-24a9d44f80cc-000000@email. >>> amazonses.com>, Antonio Leding <t...@leding.net> wrote: >>> >>>> Just curious any reason to not use use the could-based Postfix >>>> server + something like Dovecot and then have your clients access that >>>> directly? I have this now for at least 20 domains and it works awesome. >>> Firstly, I have no idea what you mean by "could-based Postfix". Was that >>> a typo? What did you mean, actually? >> I'm guessing "could" is a typo (or perhaps autocorrection) for "cloud". >>
