selfpost

311 Commits 1 Branch 3 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
mixandClaude Opus 5.5	2f5f5b2b93	design: password-reset - a confirmed e-mail, then a link to reset Agreed 2026-10-13 ("the e-mail must be confirmed"); his choice of 2026-10-17 for notifications: "Без подтверждения слать" - they go to the address confirmed or not; only a reset link needs it confirmed. Sign-in gets "Forgot your password?" (login.html). login-reset.html asks for the username and says what will happen; login-reset-sent.html is the sign-in page after it, the same answer for any name ("If that account has a confirmed e-mail, the link is on its way"); login-reset-set.html sets the new password from the link and says that every session ends. confirm-email.html is where the confirmation link lands: a button, not a GET that changes state, as a mail scanner opens links. Account: the e-mail's tag (confirmed / not confirmed), what a new address is sent, the current password asked only to change the e-mail (roadmap, 2.0 security review: the e-mail becomes where a reset link goes), and "Send the link again" while it is unconfirmed. The user form shows the tag too. Help #account says it all. The user form loses "The same form, empty, creates a new user" (panel-words: a new user has its own head). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-17 11:02:07 +03:00
mixandClaude Opus 5.5	c5edbd84c7	design: panel-words - the mockups and the panel say the same The owner's "проверь, что документация актуальна с кодом" (2026-10-16): the words the mockups put on screen against what the panel renders and does, page by page (docs-audit, 2026-10-17). Where the code is right about behaviour the mockup follows it; where the mockup is right the code follows in the next commit. The mockups now say: "Refreshes automatically" / "refreshes on its own" instead of "every 10 s" (panel.js polls at 5 s, 30 s, up to 60 s) on Health, Overview, System log and both queues; System log points at the Outbound log, the one with a page per message; the Spam filter facts are what the panel knows without the quarantine (Applies to, Filter, If the filter is down), and Valid recipients takes one per line or comma; a DMARC report's title has no year, as its own title line; the "same form, empty" sentences go (a new application and a new user have their own heads); an application's login is fixed; the auto limit's multiplier is 1.5-5, default 2.5 (store/ratelimits.go); the user form's e-mail is for notifications (no reset link yet) and All makes the single domains ignored (nothing greys them); a user's deletion says "(outbound)"; a message's history is the panel's own steps, with the queue's wait after a deferral; the footer is the panel's, "Copyright © 2026 Mikhail Yenuchenko". Help, true to the code: an application's password is kept by the server (sasldb2) so an export can carry it; a refusal for From:/Sender: is one row of the Outbound log; every password check of a backup counts, right or wrong, ten in 15 minutes; a password set on the user form signs that user out everywhere, but your own keeps your session; the limit mail is daily per sending domain (notify.go, "limit:"+domain). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-17 02:10:29 +03:00
mix	7ef7f75246	release: 1.9.2: Review pass: port-25 milters, DMARC validation, rate-limit fix Review pass over `1.4.0`…`1.9.1`: port 25 no longer shares the submission milter chain, DMARC reports are validated before they are stored, and the auto rate limit is correct for a non-default level-1 window. Schema migration `0010` (index only). Upgrading is a tag bump. Added: - SQLite migration `0010_send_log_app_login_index.sql` — - DMARC aggregate reports are accepted as zip as well as gzip or plain XML - e2e: `checkPort25ConfigCombinations` regenerates the Postfix configuration Changed: - README hero line and a Positioning block in `docs/product.md` record the Fixed: - The setup account's password is hashed at bcrypt cost `12` like every other - Login/setup rate limiter: protecting blocked buckets from eviction is now - `postqueue -p` output is bounded to 4 MiB (the timeout alone left the size of - [schema-migrations.md](docs/schema-migrations.md): the schema section was - postqueue reader is now time-bounded: `postqueue -p` runs under a 5-second … (11 more in CHANGELOG) Changed: - [roadmap.md](docs/roadmap.md) now carries everything the 2026-08-19 code - Extracted `internal/configsafe` — the empty-value and forbidden-character - Build, deploy and migration comments no longer cite the archived - Dropped the `parseDomainRateLimitForm` / `parseAppRateLimitForm` pass-through - Extracted shared helpers: `internal/atomicfile` (atomic temp-write+rename) and … (7 more in CHANGELOG) Removed: - Unused legacy asset `docs/assets/icon.png` (superseded by the four brand SVGs - Plan documents for already-shipped features: `domain-stats-auto-ratelimit`, Full detail: CHANGELOG.md (1.9.2).	2026-09-22 15:24:53 +03:00

Author

SHA1

Message

Date

mixandClaude Opus 5.5

2f5f5b2b93

design: password-reset - a confirmed e-mail, then a link to reset

Agreed 2026-10-13 ("the e-mail must be confirmed"); his choice of
2026-10-17 for notifications: "Без подтверждения слать" - they go to the
address confirmed or not; only a reset link needs it confirmed.

Sign-in gets "Forgot your password?" (login.html). login-reset.html asks
for the username and says what will happen; login-reset-sent.html is the
sign-in page after it, the same answer for any name ("If that account has
a confirmed e-mail, the link is on its way"); login-reset-set.html sets
the new password from the link and says that every session ends.
confirm-email.html is where the confirmation link lands: a button, not a
GET that changes state, as a mail scanner opens links.

Account: the e-mail's tag (confirmed / not confirmed), what a new address
is sent, the current password asked only to change the e-mail (roadmap,
2.0 security review: the e-mail becomes where a reset link goes), and
"Send the link again" while it is unconfirmed. The user form shows the
tag too. Help #account says it all. The user form loses "The same form,
empty, creates a new user" (panel-words: a new user has its own head).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-17 11:02:07 +03:00

mixandClaude Opus 5.5

c5edbd84c7

design: panel-words - the mockups and the panel say the same

The owner's "проверь, что документация актуальна с кодом" (2026-10-16):
the words the mockups put on screen against what the panel renders and
does, page by page (docs-audit, 2026-10-17). Where the code is right about
behaviour the mockup follows it; where the mockup is right the code
follows in the next commit.

The mockups now say: "Refreshes automatically" / "refreshes on its own"
instead of "every 10 s" (panel.js polls at 5 s, 30 s, up to 60 s) on
Health, Overview, System log and both queues; System log points at the
Outbound log, the one with a page per message; the Spam filter facts are
what the panel knows without the quarantine (Applies to, Filter, If the
filter is down), and Valid recipients takes one per line or comma; a DMARC
report's title has no year, as its own title line; the "same form, empty"
sentences go (a new application and a new user have their own heads); an
application's login is fixed; the auto limit's multiplier is 1.5-5,
default 2.5 (store/ratelimits.go); the user form's e-mail is for
notifications (no reset link yet) and All makes the single domains
ignored (nothing greys them); a user's deletion says "(outbound)"; a
message's history is the panel's own steps, with the queue's wait after
a deferral; the footer is the panel's, "Copyright © 2026 Mikhail
Yenuchenko".

Help, true to the code: an application's password is kept by the server
(sasldb2) so an export can carry it; a refusal for From:/Sender: is one
row of the Outbound log; every password check of a backup counts, right
or wrong, ten in 15 minutes; a password set on the user form signs that
user out everywhere, but your own keeps your session; the limit mail is
daily per sending domain (notify.go, "limit:"+domain).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-17 02:10:29 +03:00

mix

7ef7f75246

release: 1.9.2: Review pass: port-25 milters, DMARC validation, rate-limit fix

Review pass over `1.4.0`…`1.9.1`: port 25 no longer shares the submission milter chain, DMARC reports are validated before they are stored, and the auto rate limit is correct for a non-default level-1 window. Schema migration `0010` (index only). Upgrading is a tag bump.
Added:
  - SQLite migration `0010_send_log_app_login_index.sql` —
  - DMARC aggregate reports are accepted as **zip** as well as gzip or plain XML
  - e2e: `checkPort25ConfigCombinations` regenerates the Postfix configuration
Changed:
  - README hero line and a **Positioning** block in `docs/product.md` record the
Fixed:
  - The setup account's password is hashed at bcrypt cost `12` like every other
  - Login/setup rate limiter: protecting blocked buckets from eviction is now
  - `postqueue -p` output is bounded to 4 MiB (the timeout alone left the size of
  - [schema-migrations.md](docs/schema-migrations.md): the schema section was
  - postqueue reader is now time-bounded: `postqueue -p` runs under a 5-second
  … (11 more in CHANGELOG)
Changed:
  - [roadmap.md](docs/roadmap.md) now carries everything the 2026-08-19 code
  - Extracted `internal/configsafe` — the empty-value and forbidden-character
  - Build, deploy and migration comments no longer cite the archived
  - Dropped the `parseDomainRateLimitForm` / `parseAppRateLimitForm` pass-through
  - Extracted shared helpers: `internal/atomicfile` (atomic temp-write+rename) and
  … (7 more in CHANGELOG)
Removed:
  - Unused legacy asset `docs/assets/icon.png` (superseded by the four brand SVGs
  - Plan documents for already-shipped features: `domain-stats-auto-ratelimit`,

Full detail: CHANGELOG.md (1.9.2).

2026-09-22 15:24:53 +03:00