Sixth second-wave item from the settings-reorg spec.
Network › Listeners opens with The standard ports: 25, 587, 465, 443, 80, 993, 143, 995, 110 and 4190. Each row has what the port is for ("Receiving mail from other servers", "Sending from mail apps", "Webmail, this console, JMAP apps, automatic setup"…), its encryption (encrypted from the start / STARTTLS / not encrypted), whether it's open, and a switch.
Open adds a listener named after the service on [::]:port, with the service's TLS mode. Close removes the listeners on that port.
Closing 25 or 443 asks first, inline (no browser dialog), saying what stops: Other servers can no longer deliver mail to you / The webmail, this console, JMAP apps and automatic setup stop working.
IMAP, POP3 and ManageSieve rows link to Switched on Hardening. That's where the legacy-protocols switches take listeners away and put them back, so the table never fights them.
The sending ports do the same while legacy mail is off with closeSubmission.
Listeners on other ports are listed as sentences ("name: protocol on port N, encryption.") and left alone.
Reachability: a note says open means the server listens, and that the firewall and hosting provider decide whether the internet can reach it. A real reachability check would need a server call, so it isn't here.
Checked: 4 unit tests for reading ports, sorting listeners into services and building one (491 total), plus typecheck, lint and build. In Chrome against a local server:
opening 587 created submission on [::]:587 (shown in the list below);
opening 25 then closing it asked first, with the message above;
closing both left the server as it was.
English only: about 30 new strings.
Sixth second-wave item from the settings-reorg spec.
Network › Listeners opens with *The standard ports*: 25, 587, 465, 443, 80, 993, 143, 995, 110 and 4190. Each row has what the port is for ("Receiving mail from other servers", "Sending from mail apps", "Webmail, this console, JMAP apps, automatic setup"…), its encryption (encrypted from the start / STARTTLS / not encrypted), whether it's open, and a switch.
- **Open** adds a listener named after the service on `[::]:port`, with the service's TLS mode. **Close** removes the listeners on that port.
- **Closing 25 or 443 asks first, inline** (no browser dialog), saying what stops: *Other servers can no longer deliver mail to you* / *The webmail, this console, JMAP apps and automatic setup stop working*.
- **IMAP, POP3 and ManageSieve rows** link to *Switched on Hardening*. That's where the legacy-protocols switches take listeners away and put them back, so the table never fights them.
- **The sending ports** do the same while legacy mail is off with `closeSubmission`.
- **Listeners on other ports** are listed as sentences ("name: protocol on port N, encryption.") and left alone.
- **Reachability:** a note says *open* means the server listens, and that the firewall and hosting provider decide whether the internet can reach it. A real reachability check would need a server call, so it isn't here.
**Checked:** 4 unit tests for reading ports, sorting listeners into services and building one (491 total), plus typecheck, lint and build. In Chrome against a local server:
- opening 587 created `submission` on `[::]:587` (shown in the list below);
- opening 25 then closing it asked first, with the message above;
- closing both left the server as it was.
English only: about 30 new strings.
Network › Listeners opens with the ports people know: 25 for receiving
mail, 587 and 465 for sending from mail apps, 443 and 80 for the web,
and IMAP, POP3 and ManageSieve. Each row says what it's for, how it's
encrypted and whether it's open, with a switch.
- Opening one adds a listener for it on every address; closing removes
its listeners. Closing 25 or 443 asks first, saying what stops.
- IMAP, POP3 and ManageSieve, and the sending ports while legacy mail
is off, belong to Security › Hardening, whose switches keep and
restore their listeners; their rows link there.
- Listeners on other ports are listed as sentences, and left alone.
- A note says open means listening: the firewall and hosting provider
decide whether the internet can reach it.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Sixth second-wave item from the settings-reorg spec.
Network › Listeners opens with The standard ports: 25, 587, 465, 443, 80, 993, 143, 995, 110 and 4190. Each row has what the port is for ("Receiving mail from other servers", "Sending from mail apps", "Webmail, this console, JMAP apps, automatic setup"…), its encryption (encrypted from the start / STARTTLS / not encrypted), whether it's open, and a switch.
[::]:port, with the service's TLS mode. Close removes the listeners on that port.closeSubmission.Checked: 4 unit tests for reading ports, sorting listeners into services and building one (491 total), plus typecheck, lint and build. In Chrome against a local server:
submissionon[::]:587(shown in the list below);English only: about 30 new strings.