On 08/01/2019 10:07, Murray Crane wrote: If I recall, in Exchange it is possible to set up an address that all mail sent to an account is forwarded to.  After a short search, wWhile not what I remember (I was working with a much older version of Exchange), this article (https://www.bursky.net/index.php/2012/03/copy-emails-on-exchange-to-another…) appears to cover a version of that scenario (I presume that it will allow sending to an address outside the organisation). If using Exim in front of an Exchange server, you could create a custom router to handle this (using "unseen deliver [email address to copy to]") - see https://serverfault.com/questions/299349/exim-how-to-deliver-locally-and-se….  I presume there is a way to do so with Postfix, but I'm less familiar with that. I'd say doing it on Exchange would be the easier of the two options.  Try it with a test mailbox first, the last thing you want is a Director on your back because something went wrong and they didn't get an important email while you were trying to get it working... Thanks Gavin

Hi Murray, Στις 8/1/2019 12:07, ο Murray Crane έγραψε: I'd start with this cause it all starts here. So this is the boss not trusting your business' internet connection? How about a synced IMAP mailbox that allows offline access while you're down? Or how about he gets you a backup uplink via GSM or something? Then all of this would not be required. OR maybe he connected once from a hotel with a firewalled hotspot and couldn't get to your exchange servers and decided "this doesn't work"? Do you provide webmail access? If you are currently supporting a mail server on their home network, consider how many "homes" you need to add mail servers to once this gets out as a solution. Bob the CEO tells Jim the CFO and then Jim tells sales and you're screwed cause now 20 Jonathans want it, too. Just don't do it (tm). Say no up front rather than down the line. And why docker, they already have a server at home? Who's supporting that? It would have some issues with bounces but it would work. The question is, why would you do this at all and set yourself up for a tech support nightmare? As for being a 'solutions provider' let them know that creating an unnecessary problem and solving it is like putting holes in your water bucket and finding a way to handle the spillage instead of plugging the freakin' holes. Mention Hillary and her "home server". From the top of my head I see 2 options: 1 VPN is good but you'll need to setup all their personal machines for it, including mobiles (yes). Depending on what OS they're using you could be in for a bit of a permanent support job. If it's just windows maybe set up a simple self extracting rar file or installer they can run that sets up openvpn for them with a bundled config file to just route your corporate IPs. I would not do VPN in general cause unless you set up careful routing to allow access only to the mail server you'll be bringing their home machine/phone into your network (yikes). So lots of work on both sides. 2 Opening IMAP access to exchange from outside would mean you need to setup their mail clients for it, which is also a permanent support job, but easier. This is what I'd do since you can secure it via TLS and a decent password policy (ie you set their passwords for them) and surely Exchange can handle IMAP. If you have a postfix server you can do this: http://pjrlost.blogspot.com/2012/11/smtp-delivery-to-two-mail-servers-via.h… But again, why? --GM

On 08/01/2019 11:07, Murray Crane wrote: I have no doubt you are but they are busy defining the solution not the problem. I am reminded of this: https://www.youtube.com/watch?v=BKorP55Aqvg FWIW I do "split" one of my incoming emails - I let the registrar deal with the email forwarding, hence foo(a)domain.com goes to foo-domain(a)personal.org and foo(a)another.com. My main desktop machine collects from both accounts, but will set the reply-to etc accordingly.