By default, Ploi's own SSH logins (workers and site monitors) do not trigger SSH login notifications. As soon as you enter any custom IP in "Excluded IPs", those Ploi logins start triggering notifications. So adding an exclude list results in more notifications than having none.

To get rid of that noise you have to copy Ploi's IPs (the IP addresses page in the docs, or /api/ips) into the excluded list of every server by hand. This is tedious and goes stale whenever Ploi changes its IPs.

Request: keep Ploi's own IPs implicitly excluded when a custom exclude list is set. Optionally show it as a checkbox, "Don't notify for Ploi logins" (on by default), maintained by Ploi.

Related:

• #1611 (global list of custom whitelisted IPs, which would cover team members but not Ploi's own IPs) -> https://roadmap.ploi.io/projects/1-server-level-requests/items/1611-global-list-of-ip-adresses-to-whitelist-in-ssh-login-notifications
• #1639 (spaces after commas in the excluded list) -> https://roadmap.ploi.io/projects/7-bugs/items/1639-ssh-login-notification-still-sent-for-excluded-ips-when-the-list-has-spaces-after-commas