Core Rule Set: Mastodon's email field passes ordinary addresses (closes #273)
check / check (push) Failing after 16m29s

user[email] on /auth and the paths under it skips 930120, 932120 and
932260. They refused signing up, signing in and resetting a password
with addresses such as python3@example.com, powershell@example.com and
jane.profile@example.com. The field keeps 932250 and every other rule.

Recorded from Mastodon 4.7.5: sign-up, sign-in, password reset and an
email change.

Model: opus-5-5
This commit was merged in pull request #277.
This commit is contained in:
clawbot committed 2026-11-10 06:43:23 +01:00
1 parent 20e4b3b080
commit 183a6072d5
5 files changed
+77 -2

No files matched your search

+5
View File
@@ -1170,6 +1170,11 @@ The changes hold in front of every app, and no setting undoes them:
- `user[account_attributes][username]` on `/auth`, the sign-up form's
username.
`user[email]` on `/auth` and the paths under it skips 930120, 932120
and 932260. The sign-up, sign-in, password reset and account settings forms
send an email address there, such as `python3@example.com`. An address holds
no spaces, so it keeps 932250.
On `/api/v1/reports`, the JSON keys `forward` and `forward_to_domains` skip
930120 by their names. A report forwarded to another server lists that
server in `forward_to_domains`. In the Core Rule Set the keys are named: