Develop GSuite services for the AniNIX #8

New Issue

DarkFeather · 2020-10-20T14:40:21-05:00

DarkFeather commented

2020-10-20 14:40:21 -05:00

The AniNIX does not use an SMTP relay or email server for communciation -- we only use the Anope MemoServ and Gitea threads for long-term messages. The reason for this is the state of email security as noted by 32c3 -- SMTP does not guarantee end-to-end security through the relay network. For all the compromises in SMTP and for the difficulty managing spam, we will only use a closed communication network that requires internal authentication and encryption on all categories.

However, most of the rest of the world is still dependent on email, and some OSINT is only accessible with a proper business email address. In order to keep current, we will need an MX record for aninix.net, which heretofore we have not supported.

Since email is still used by the rest of the world, however, we still need email presence. There are a number of services where in order to engage with the rest of the world we connect data to cloud providers, such as our Discord bridge and GitHub repo mirrors.

When we first filed for our trademark, we were issued a GMX account that we will need to migrate all references from.

The AniNIX does not use an SMTP relay or email server for communciation -- we only use the Anope MemoServ and Gitea threads for long-term messages. The reason for this is the [state of email security as noted by 32c3](https://www.youtube.com/watch?v=_aogXeTbERs) -- SMTP does not guarantee end-to-end security through the relay network. For all the compromises in SMTP and for the difficulty managing spam, we will only use a closed communication network that requires internal authentication and encryption on all categories. However, most of the rest of the world is still dependent on email, and some OSINT is only accessible with a proper business email address. In order to keep current, we will need an MX record for aninix.net, which heretofore we have not supported. Since email is still used by the rest of the world, however, we still need email presence. There are a number of services where in order to engage with the rest of the world we connect data to cloud providers, such as our Discord bridge and GitHub repo mirrors. When we first filed for our trademark, we were issued [a GMX account](mailto:aninix@gmx.com) that we will need to migrate all references from.

DarkFeather referenced this issue

2020-10-28 15:48:32 -05:00

Develop GSuite services for the AniNIX #7

DarkFeather commented

2022-01-31 23:09:08 -06:00

We opened a https://workspace.google.com account, which will carry an annual cost of $72 in addition to our domain registry of $20.

What this brings us:

A domain brand for SMTP, which is sometimes needed for registering for webinars and other cybersec content.
Complete GSuite services for interacting with other businesses, including document sharing & calendar
DKIM / SPF DNS records for our domain, which may be used to give us validation and credibility.

I do have a free Gmail account, but I don't always want to immediately expose my IRL identity during initial conversations with folks. Providing a domain contact email offers a little protection.

In order to close this issue, we need to accept this cost, transition all our cloud accounts that use the GMX account onto the new Workspace account, and set up email forwarding from GMX to the Workspace address.

We opened a https://workspace.google.com account, which will carry an annual cost of $72 in addition to our domain registry of $20. What this brings us: * A domain brand for SMTP, which is sometimes needed for registering for webinars and other cybersec content. * Complete GSuite services for interacting with other businesses, including document sharing & calendar * DKIM / SPF DNS records for our domain, which may be used to give us validation and credibility. I do have a free Gmail account, but I don't always want to immediately expose my IRL identity during initial conversations with folks. Providing a domain contact email offers a little protection. In order to close this issue, we need to accept this cost, transition all our cloud accounts that use the GMX account onto the new Workspace account, and set up email forwarding from GMX to the Workspace address.

DarkFeather added the

In-progress

label 2022-03-03 10:14:17 -06:00

DarkFeather commented

2022-03-03 10:15:12 -06:00

I think we are going to accept this cost. The benefits are worth the cost, especially for the access to cybersec networking. I'll be working the transition from GMX to Workspace shortly.