Issue #948: Surface spam-folder hint on Login page, drop email-body redundancy#952
Open
bjagg wants to merge 1 commit into
Open
Issue #948: Surface spam-folder hint on Login page, drop email-body redundancy#952bjagg wants to merge 1 commit into
bjagg wants to merge 1 commit into
Conversation
…p email-body redundancy @cbeach47's review of LIF-Initiative#946 pointed out the spam-folder hint in the verification email body sits in the wrong surface area: if recipients can read the email they don't need the hint; if it's in spam they won't see it. The right place is the SPA at the moment the user is about to register and start waiting for the code. Add a small `<Text size="1" color="gray">` block under the Sign In / Register button (Cognito branch only — the legacy username/ password flow doesn't email codes), and drop the now-redundant parenthetical from the email body in `cognito-selfserve.yml`. The verification email sender (`no-reply@verificationemail.com`) is still Cognito's default — the proper fix is SES with a verified sender domain, which needs AWS production-access approval and is tracked under LIF-Initiative#941. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@cbeach47's review of #946 noted the spam-folder hint in the verification email body is in the wrong surface area:
Move the hint to the SPA Login page — the moment the user is about to bounce to Cognito to sign up, and is about to start waiting for the code.
Closes #948.
Changes
frontends/mdr-frontend/src/pages/Login.tsx— under the Cognito Sign In / Register button (only whenisCognitoEnabled, since the legacy username/password flow doesn't email codes):cloudformation/cognito-selfserve.yml— drop the now-redundant(If you don't see this in your inbox, please check Spam / Junk.)line from the email body. With the SPA hint in place, the email-body version is duplicative.Out of scope
The actual sender-address change (
no-reply@verificationemail.com→noreply@unicon.netvia SES with DKIM/SPF) is the proper fix — but it needs AWS to grant SES production access (multi-day process). Tracked under #941.Verification
npx tsc --noEmit -p tsconfig.app.jsoncleannpx vite buildclean/login, confirm the hint renders under the Sign In / Register button (Cognito mode); not visible in legacy username/password modeThe frontend portion deploys to dev on merge via
lif_mdr_frontend.yml. The cognito-selfserve.yml change needs an explicit stack deploy for dev (and for demo when promoting); the new SPA hint is the user-visible value either way, so the cognito change can wait if needed.🤖 Generated with Claude Code