• Activity
  • Votes
  • Comments
  • New
  • All activity
  • Showing only topics in ~tech with the tag "fqdn". Back to normal view / Search all groups
    1. Setting up own email FQDN (and maybe service?)

      after the latest round of reporting from 404 media on Andy Chen's very un-leader-like and hostile attitude, I would like to start exploring my options for a way to have an email service that is...

      after the latest round of reporting from 404 media on Andy Chen's very un-leader-like and hostile attitude, I would like to start exploring my options for a way to have an email service that is not to beholden to other services.

      my current mindset is:

      1. I have to either be OK with the fact that a service I use starts out with good aspirations but that can all change in the blink of an eye depending entirely upon the current moods of the C-level executives of the company
        OR
      2. I have to be OK with changing my email address every-time a service I use goes a bit nuts. In my view, this is unsustainable and will confuse the fuck out of anyone who likes to keep in contact with me.

      so I view "better" the third option as:

      1. get my own email FQDN [probably something like everyone_is_beautiful.net or something] and that way, I can solve 2 birds with 1 stone
        1. I can make my inbox even more organized, i.e. connect amazon account to amazon@everyone_is_beautiful.net and counseling services to counselling@everyone_is_beautiful.net AND
        2. even setup joint accounts that forward to any number of people and my personal email [which would be joe@everyone_is_beautiful.net for example] (thereby solving this issue too) and everything can be very organized.

      However, it's not like I am going to host my own email hosting service, or at least I imagine that's not advisable probably and I will need to hook my FQDN to some other service that manages all that for me.

      Which gets me back to square 1 of being stuck on some external services, but I imagine, it's better to be dependent at that level cause switching email hosting service is much easier to maintain cause the my email address itself wont change

      But I don't pretend to know what's full involved and was wondering if

      1. if there's faulty logic in my mindset AND
      2. what are the common irritants/nuances of getting down my FQDN and connecting it to an email hosting service and ensure everything works as expected and any emails I send don't wind up going to people's spam
      3. if I do wind up going the third route, I imagine it wont be possible to migrate all my emails with me when I have to do a migration cause a service is starting to go down the drain? Is there a way around that? I'd like to have access to all my emails in 1 places.
      14 votes