You just took a step in the right direction. No more tracking by Big Data, no more having your emails scanned for ads. No more limits. However, there are a few things you probably want to know now that you've signed up. I've outlined some basic instructions below, but you can always email email@example.com or head on over to the Keybase team chat if you need anymore help.
Let's begin, shall we?
You have a freedom of choice when it comes to accessing your email. You can always access webmail at https://shrt.email/mail on any browser, but I understand that's not always convenient. If you're using an email client on a desktop computer such as Thunderbird, Windows Mail, or anything else, you'll need to connect using SHRT's IMAP (incoming) and SMTP (outgoing) servers. Here the details on that:
- IMAP server: shrt.email
- IMAP port: 993
- IMAP security: SSL or TLS
- SMTP server: shrt.email
- SMTP port: 587
- SMTP security: STARTTLS (set it to "always" or "required" if your client needs)
- Username for both: Your whole @shrt.email address
- Password for both: Your password set at registration time
As for mobile, the settings differ slightly depening on if you're on Android or iOS. If you're on Android, you'll want to add a new Exchange/ActiveSync account to your device. Simply enter your @shrt.email email address and password and you'll be good to go.
Apple users, you're a bit lucky. Just click or tap this nifty link right here and let the autoconfiguration guide you through the process.
Cloud storage is great, because it helps you keep track of important files and make sure you always have what you need when you need it. If you don't know how to access it, though, what's the point? SHRT.email uses the opensource fork of OwnCloud called NextCloud to power your cloud storage. You can, again, access it through a web-portal at https://shrt.email/cloud. Or, you can download the official clients from the NextCloud website. Access through any method is plain and simple, your username is your whole @shrt.email email address and the password you set when you registered.
Rest assured, your files are safe in this cloud. Server-side encryption has been enabled on all files (except for a special few, we'll get to that later) so that nobody can snoop in on them. Additionally, they are scanned with ClamAV antivirus software to detect any threats to yourself or others. Back-ups are made regularly and stored off-site to prevent data loss. In the case of server failures, we will automatically restore the previous day's back-up. Since your sync client also keeps local files, there should be very little risk of data loss.
If you're looking to host your own online portfolio, just want to share some recipes with the world, or need an outlet to show your fans your awesome corgi art, you can do that at your own subdomain. Managing files is simple and integrated with your cloud storage.
Remember the special exception to server side encryption mentioned earlier? Special rules have been written for the encryption plugin so that any files stored in a folder called just 'html' in your cloud storage are not encrypted. Instead, they're served through a webserver at your own subdomain. If you chose the username 'dkb' (hey, that's me!) for example, your files in the html folder could be accessed at https://dkb.shrt.email by anyone with an internet connection. A Let's Encrypt SSL certificate is automatically provisioned and installed, as well, so there's no hassle there. Pretty neat, eh?
Last but not least, let's talk about your email aliases. Since a subdomain is automatically provisioned for you, why not take advantage of it? Using my own as an example again, I have everything I want @dkb.shrt.email. This makes filtering super easy. Sketchy website asking for an email before you can read an article? Just throw in firstname.lastname@example.org and you'll know exactly if your information was sold by them. You can then create filters either in your webmail settings or your email client to run actions based on what email address a message was sent to. I would suggest creating a filter for email@example.com, for example, so that anything sent to that address goes straight into the bin without me having to look at it. The possibilities are endless (other than what's allowed by the email standards, of course) and entirely in your control.