Security & sessions and the Administration dashboard name what's off when only some of IMAP, POP3 and ManageSieve are (from the session's new legacyAllowed); an organization's sheet names them and points to the console. Nothing changes against a server that doesn't send legacyAllowed.
3 new strings in all nine catalogs, unreviewed.
Tested: unit tests, typecheck, full suite (1475), and headless Chrome against a local server with POP3 off.
Security & sessions and the Administration dashboard name what's off when only some of IMAP, POP3 and ManageSieve are (from the session's new `legacyAllowed`); an organization's sheet names them and points to the console. Nothing changes against a server that doesn't send `legacyAllowed`.
3 new strings in all nine catalogs, unreviewed.
Tested: unit tests, typecheck, full suite (1475), and headless Chrome against a local server with POP3 off.
inbuxa can now switch IMAP, POP3 and ManageSieve off one at a time,
server-wide and per organization, and the session lists what is still
allowed for the account (legacyAllowed). Where the webmail said
"legacy protocols are off", it now also covers the case where only
some are:
- Security & sessions, above app passwords: "Your organization has
turned off POP3 for mail apps. Mail apps that use it can't connect
to this account; others still can."
- The Administration dashboard: "Some legacy mail protocols are off for
your organization: POP3."
- An organization's sheet in Administration: its switch stays the
all-or-nothing one; when only some are off it names them and points
to the console, where they're switched one at a time, and "Turn
legacy protocols back on" turns them all back on.
With every protocol off, the existing wording shows, as before. From a
server that doesn't send legacyAllowed nothing new appears.
3 new strings in all nine catalogs, unreviewed.
Tested: unit tests for reading the session and a tenant's switches;
the existing tests updated for the new field; typecheck; the whole
suite (1475 tests); and in headless Chrome against a local server with
POP3 off, where Security & sessions showed the new note.
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.
Security & sessions and the Administration dashboard name what's off when only some of IMAP, POP3 and ManageSieve are (from the session's new
legacyAllowed); an organization's sheet names them and points to the console. Nothing changes against a server that doesn't sendlegacyAllowed.3 new strings in all nine catalogs, unreviewed.
Tested: unit tests, typecheck, full suite (1475), and headless Chrome against a local server with POP3 off.