xxx.org

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.