ITSH Documentation

English

Deutsch

English

Deutsch

Appearance

Connecting a mail client ​

One hostname serves everything, and your username is always the full email address. Most clients need nothing but the address and the password.

Server settings ​

ServerPortEncryption
Incoming (IMAP)mail.itsh.dev993SSL/TLS
Incoming (IMAP)mail.itsh.dev143STARTTLS
Outgoing (SMTP)mail.itsh.dev587STARTTLS
  • Username: the full address, you@example.com, not the part before the @
  • Password: the mailbox password you set when creating it
  • Authentication is required on the outgoing server too, with the same credentials

465 is not served, and neither is POP3

A client that defaults to "SSL/TLS on 465" for outgoing mail will sit there timing out. Submission is 587 with STARTTLS, and that is the only outgoing port. There is no POP3 on any port; use IMAP.

Let the client configure itself ​

Enter the address and password and stop there. Thunderbird, Outlook, Apple Mail and the common Android clients all discover these settings on their own, as long as the autoconfig, autodiscover and _tcp records from Setting up a domain are in place.

Two things worth knowing before they surprise someone:

  • Outlook asks for permission once. On first setup it shows "Allow this website to configure server settings? https://autodiscover.itsh.dev". Click Allow.
  • Apple devices warn that the profile is not signed. The mailbox Overview page offers a downloadable Apple Mail profile. Opened in Safari on iPhone, iPad or Mac it installs the account in one step, and iOS and macOS show a "Not Signed" warning while it does. That warning is expected.

The same Overview page shows these settings per mailbox with a copy button, which is usually easier than reading them off this page.

Mailbox self-service ​

Someone who has a mailbox but no customer account can still manage it. They sign in at itsh.dev/webmail with the mailbox address and password and get a page with Overview, Vacation, Identities and Login History, plus a password change.

This is not a webmail client. It has no message list and cannot send mail. It exists so a colleague can set their own vacation reply and change their own password without going through you.

Sending from an application ​

An application that sends mail authenticates as a mailbox and submits on 587, exactly like a desktop client. Give it its own mailbox rather than sharing a person's.

Port 25 is blocked for workloads on our Kubernetes platform

Outbound port 25 is denied cluster-wide, on every plan, so a container that tries to deliver mail directly to a recipient's mail server hangs and then times out. Submission on 587 is not affected on a paid namespace and works normally.

A free-tier namespace is narrower still: it may only open outbound connections on 80 and 443, so 587 does not leave it either. Mail from a free namespace has to go out over an HTTPS API of some kind, not over SMTP. See Outbound connections fail.

What's next ​