I am wanting to know how prior Reflexion.net users handled the migration to Sophos when they had to deal with hundreds/thousands of "address on the fly" (AOTF) addresses and no more smarthost send connectors to port 587.
1) The AOTF addresses can be imported but with no quick and easy method to add aliases, how are users handling this? When you adopted AOTF as a method of account protection, where every company you deal with has their unique alias, so if they get hacked, that email/account is no good anywhere else, no more AOTF is a very significant loss and headache. I personally have over 1500 aliases and REALLY don't want to give my root address out as a sign on.. This means I have to enter my account, my pw, my 2FA, drill into my account for email, drill into the mailbox, drill into the aliases, then add the new alias. This is a HUGE amount of work compared to what we used to have at Reflexion.
How have you and your clients handled this change? Are there any faster methods than what I described to create aliases with Sophos?
2) How are you handling port 25 being blocked by ISPs for clients that have home offices and host their own mail server? Sophos doesn't support 587 or 465; only 25. I've asked and they won't do a firewall redirect/forwarding of 587 to 25. I'm starting to look at hosted VPN as a possible solution but not sure if this is the best solution.