After logging in with the "Save Password" checkbox set, your password will be saved locally on your machine using a 'cookie'. This means the next time you go to http://www.fastmail.fm, you will automatically bypass the login screen and be logged in. This is useful if you use FastMail regularly from the same machine, are not worried about other people using that machine, and don't want to be prompted with a login screen every time you go to http://www.fastmail.fm.
For this to work, you must have cookies enabled on your machine. Also, when you're finished using FastMail, don't click 'Logout', just close the browser window.
Passwords can be stored in your browser using cookies, or the browser can store the password using the 'Auto complete' feature.
To clear the password saved in cookies, click on the 'Logout' button in your mailbox screen.
To clear the password saved for the 'Auto complete' feature of your browser (Internet Explorer), go to 'Tools' -> 'Internet Options' -> 'Content' -> 'Auto Complete' and click on the 'Clear Passwords' button. If you do not want to save the usernames/passwords, uncheck the 'User names and passwords on Forms'.
When you login to your account, a new "session" is created. This is what lets you click around between pages and always just see your account, but no one else can see your account.
A session has an "inactivity timeout" period. This means if you don't click a link or button on a page within a certain amount of time, the session will expire, and you'll have to login again to continue.
Users can select the session timeout from the drop down menu in the login screen. They can do this by clicking on the "More +" link beside the "Login" button in the login page.
For a "Regular" login we default the session timeout to 2 hours but for "Long term (auto login)" we default it to 8hrs. For "Public terminal" the default value is "30 mins", to make it more secure.
If you would like to change the session timeout, just click on the "More +" link and use the "Session time" drop down to choose value of your choice.
FastMail supports secure sessions using Secure Sockets Layer (SSL). Click here for more information on SSL. When you click 'Secure Login', all communication between your computer and FastMail will be done using a secure channel. This means that you can read and write emails without others on the internet being able to spy on what is happening between your browser and the FastMail server. Note though, that once an email is sent from the FastMail server, it is transported using SMTP, a standard internet mail transfer protocol that is not guaranteed to be secure.
What does this really mean? When using FastMail from an internet cafe or your work, no one at the cafe or at your work will be able to see what you are reading or sending via FastMail. Once the email is sent, it's on the internet like any other system.
Using SSL does not slow down webpage activity, so if your browser supports it (and most modern ones do), we recommend that you use it.
One extra thing to be aware of. When you do a Secure Login, we always redirect you to https://something.fastmail.fm. This is because our SSL certificate is for *.fastmail.fm, so to avoid a security warning we have to do this, and it would be prohibitively expensive to buy and SSL certificate for every domain we have.
For some users, this can be an issue because their work bans websites with "mail" anywhere in the hostname. To work around this, you can add a parameter ?UStickSSL=1 onto your login URL to force sticking to your incoming domain when you do a Secure Login. For instance, if you go to <https://www.rushpost.com/?UStickSSL=1> and do a Secure Login, the URL will stay as https://www.rushpost.com. Your browser will report a security problem (URL and certificate don't match) that you have to accept, but the connection will still be encrypted.
When you use a web browser, the software used for viewing web pages automatically saves all pages you view on the local computer. This saves time because if you view those pages again, the browser simply displays the local copy (i.e., the "cache") instead of downloading the page content again from scratch. However, this is not a good idea if you are reading private messages on a public computer, since another user may look at a page in the cache and see your private data, without needing your password. Checking "Using a public terminal" tells FastMail that you are on a public computer, and causes it to turn off the cache for FastMail pages. When you are finished, be sure to Logout, in order to close your session.
FastMail has many different domains to choose from. To login to your account, you can go to any of the domains listed on that page in your web browser, and login using your full username "firstname.lastname@example.org".
However to login with only your "username" part, you have to go to the url in your browser that corresponds to the @yourdomain.com part of your username.
So if your username is "email@example.com", you can go to http://www.airpost.net and just login with "someusername". But if you go to http://www.myfastmail.com, you'll need to login with your full "firstname.lastname@example.org".
To add a bit of complication, this also interacts with "Secure Login" functionality.
When you do a "Secure Login", we set a cookie on your browser so that next time you go to FastMail, you're automatically redirected to the secure https:// version of the website. Because our SSL security certificate is for www.fastmail.fm (SSL certificates cost money, and it would be expensive to buy separate certificates for every domain we own). This means you'll be redirected to https://www.fastmail.fm, however the login is still treated the same as the original domain you went to in your browser before the redirect occurred.
For example, if the user email@example.com goes to http://www.airpost.net and they are redirected to https://www.fastmail.fm (because their previous login was a "Secure Login"), even though the url would show https://www.fastmail.fm, they would still be able to login by specifying just "someusername" in the "Username" field.