Is there some drama I’m not aware of here?
Is there some drama I’m not aware of here?
OVH because cheap enough for me, europe based and reliable.
Nah, it’s a matter of personnal preferences and use case.
I love CLI mainly because it allows me to sceipt suff, but lots of people don’t mind actually seeing what they are doing and clicking on stuff to achieve it.
It’s a good news there are piracy tools with a CLI, makes it more accessible to more people - and we should rejoice about it.
I might be wrong, but for me OP is not trying to actually run email, rather have a staging ground that pulls all emails from their accounts on actual providers, apply some treatment to said emails and pull them from client-side apps on their devices.
I haven’t tried any of the following, just my 0.02.
The official documentation page about registration states:
When deploying a self managed Rocket.chat >=6.x workspace you are automatically required to register your workspace upon completing the Setup Wizard
According to the same page, for versions below 6.x you have to manually register your instance.
Official documentation page about Air-gapped installs registration
Hope any of this helps. I’m quire surprised (and not in a good way) to see this mandatory requirement from Rocket.chat. Even if kt means functionality loss (access to their push notif framework for example) you should be able to decline it.
Thanks for the info!