Microsoft Outlook is a personal information manager from Microsoft, available as a part of the Microsoft Office suite. The current versions are Microsoft Office Outlook 2013 for Windows and Microsoft Office Outlook 2011 for Mac.
Although often used mainly as an email application, it also includes a calendar, task manager, contact manager, note taking, journal, and web browsing.
We don’t recommend it because it is not Free and Open Source Software (software libre).
We have no tutorial written yet for configuring Outlook with Riseup. You can help by contributing one!
- Don’t enable secure passwords or secure authentication. These are somewhat of a misnomer. These methods of specifying passwords require that the email server keep a cleartext copy of your password. We would consider this a security risk, so we don’t enable “secure passwords.” Because the connection to riseup.net is encrypted anyway, these are not needed.
- Encrypt your mail! For enhanced message security use Encrypted Email.
- The secure connection may be of type TLS or StartTLS. For security reasons, we no longer support SSL. You should not use StartTLS. Instead, it is much better to use regular TLS. For added security, go to your account settings and change your connection type from StartTLS to TLS.
- There are many vulnerabilities with how secure connections work. If you need high security, you should always connect to Riseup services using the Riseup VPN. This will prevent a long list of potential attacks against your communication.
- To enhance connection security you can use Tor to connect to Riseup’s .onion services for IMAP and SMTP. Look for the according
smtp.*.onionaddresses on the linked page and replace
mail.riseup.netfor each server. Note: * SMTP port 465 is often blocked by exit nodes, but port 587 is less frequently blocked. If you have a problem sending mail, try port 587 or configure your client to use Riseup’s email hidden service in place of the regular
mail.riseup.netdomain. This is better than sending traffic through a Tor exit as it is MITM resistant, but it will generate certificate errors on the client side.