We run an email service called Nullhex.
Nullhex is currently invite-only. An account must be manually created for you before you can log in.
In order to useth nullhex, thee wilt agree to the following:
1. i shall treat nullhex as a beta service that could disappear
We do our best to support nullhex, but we're volunteers and
email is tricky. If nullhex takes up too much time, we could choose
to disable the service.
This is why we support custom domains only - you get to take your
addresses with you if we ever shut down. We would also ship you an
archive of all of your mail. And by ship, I mean send you a tarball.
2. my email could wind up in spam folders
New domains are often treated with suspicion by mail providers - there's
not a lot we can do about that. Sometimes your mail will wind up in other
peoples spam folders (Gmail in particular is obnoxious about this).
Anecdotally, this problem goes away in time. I use nullhex for one of my
personal accounts, and I have no deliverability issues at all.
3. i understand that nullhex development follows plaintext email philosophy
Nullhex has an opinionated design that is suitable for sending plaintext
email. See useplaintext.email for more info. The webmail interface
is designed with this in mind, and other decisions are made with this in mind.
There is nothing stopping you from sending HTML email, but it isn't treated as
a first-class citizen in the nullhex world.
email email@example.com when you're ready for us to turn
your domain on. follow the instructions under "setup" at nullhex.com
to enable a new domain:
to create a new email account:
In order for the user to be able to set thier password, they will have to provide you with a linux "crypt3" SHA-512 hash.
These are like the ones linux uses internally for login passwords. I created a silly little web app utility to facilitate the easy creation of such hashes in an inclusive way (does not require terminal usage or require linux to be installed):
The user can either run it from source if they like, or you they can use the version I hosted on my server here:
Once the user provides you with a hash (it should look something like this:)
You can edit the
/etc/mail/passwd file & replace the existing hash for that email address with the new one.
sudo service smtpd restart is required for the password changes to "take".