Develop GSuite services for the AniNIX #7
Labels
No Label
Blocked
Duplicate
In-progress
On-hold
Peer-review
RFC
Wontfix
Blocked
Duplicate
In-progress
On-hold
Peer-review
RFC
Wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: AniNIX/Wiki#7
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
Duplicate of #8