[shai-almog]

The backend can now send email, and the security package uses it for the three flows every application ends up writing by hand.

Sending

mail.send(Mail.to("ada@example.com")
        .subject("Your receipt")
        .template("mail/receipt", model)
        .attach("receipt.pdf", "application/pdf", pdf)
        .build());

• One class where Spring has four. Mail is immutable and validated in build(); MailSender is injected by constructor type.
• Transports by URL. cn1.mail.url=smtp://…, smtps://…, ses://eu-west-1, log: for development and memory: for tests. The build reads the property and links only that transport.
• SMTP in pure Java over the runtime's own sockets: STARTTLS (required unless switched off, and a password never crosses a clear connection), PLAIN / LOGIN / XOAUTH2, pipelining, SMTPUTF8, a small connection pool. SendGrid, Mailgun, Postmark and Gmail are all reached this way.
• SES by its API, signed with the machine's own credentials.
• MIME encoded once: quoted-printable text, wrapped Base64, RFC 2047 headers, RFC 2231 file names, multipart/alternative, related and mixed nested as needed.
• Templates under templates/mail render through the generated views; a .txt beside the .html becomes the plain alternative, otherwise it is derived.

Delivery

With a data source, send stages the mail in cn1_mail_outbox inside the caller's transaction: a rolled back order mails no receipt, and a committed one is sent even if the server stops before the transport answers. Failures retry with back-off; a final refusal moves the mail to cn1_mail_dead. Several servers share the table without sending a mail twice.

Counters, a span per send (recipient count, never an address) and a health entry come with it.

Security flows

• Password reset: http.passwordReset(...). The request page answers the same whether or not the account exists; the link is single use and only its hash is stored. The generated login page gains a "Forgot your password?" link whenever a reset page is configured.
• Email verification: a mailed link, confirmed by a button rather than by opening the link (mail scanners open links), and .verifiedEmail() as an authorization rule.
• Mailed sign-in code as a second factor beside TOTP: six digits, ten minutes, five tries.

Testing

@BackendTest captures mail in memory; MailSender.sent() exposes it. MailCheck runs one body on the JVM and natively against an in-process SMTP server that asserts on the bytes received, on SQLite, PostgreSQL and MySQL. BackendMailTest runs it in CI.

Docs

A new Mail chapter in the developer guide, and password reset, verification and mailed codes in the Security chapter.

🤖 Generated with Claude Code

[github-actions]

Cloudflare Preview

• URL: https://pr-6215-website-preview.codenameone.pages.dev
• Branch: pr-6215-website-preview

[github-actions]

Developer Guide build artifacts are available for download from this workflow run:

• Developer Guide HTML package
• Developer Guide PDF
• AsciiDoc linter report
• Vale report
• Unused image report
• Paragraph capitalization report
• LanguageTool report

Developer Guide quality checks:

• AsciiDoc linter: No issues found (report)
• Vale: No alerts found (report)
• Paragraph capitalization: No paragraph capitalization issues (report)
• LanguageTool: No grammar matches (report)
• Image references: No unused images detected (report)

[github-actions]

✅ Continuous Quality Report

Test & Coverage

• ✅ Tests: 15176 total, 0 failed, 170 skipped
• 📊 Line coverage: 65.70% [HTML preview] [Download]
  • Lowest covered classes
    • com.codename1.io.zip.ZipArchiveOutputStream – 0.00%
    • com.codename1.gaming.level.GameSceneView – 0.00%
    • com.codename1.security.NativeCryptoEngine – 0.00%
    • com.codename1.crash.CrashProtection – 0.00%
    • com.codename1.mapping.JsonValues – 0.00%
    • com.codename1.payment.CommerceManager – 0.00%
    • com.codename1.io.outbox.Outbox – 0.00%
    • com.codename1.ai.LocalLlmClient – 0.00%
    • com.codename1.security.CertificateRequest – 0.00%
    • com.codename1.wearable.WearableMessage – 0.00%

Static Analysis

• SpotBugs [Report archive]
  • ✅ ByteCodeTranslator: 0 findings (no issues)
  • ✅ android: 0 findings (no issues)
  • ✅ android-compat: 0 findings (no issues)
  • ✅ android-res-compiler: 0 findings (no issues)
  • ✅ backend: 0 findings (no issues)
  • ✅ backend-test: 0 findings (no issues)
  • ✅ build-engine: 0 findings (no issues)
  • ✅ build-hint-catalog: 0 findings (no issues)
  • ✅ build-hint-tools: 0 findings (no issues)
  • ✅ codenameone-gradle-plugin: 0 findings (no issues)
  • ✅ codenameone-maven-plugin: 0 findings (no issues)
  • ✅ compose-compat: 0 findings (no issues)
  • ✅ core-unittests: 0 findings (no issues)
  • ✅ desktop-compat-runtime: 0 findings (no issues)
  • ✅ fxml-compiler: 0 findings (no issues)
  • ✅ ios: 0 findings (no issues)
  • ✅ javac: 0 findings (no issues)
  • ✅ javafx-compat: 0 findings (no issues)
  • ✅ project-model: 0 findings (no issues)
  • ✅ python-runtime: 0 findings (no issues)
  • ✅ python-transpiler: 0 findings (no issues)
  • ✅ swing-compat: 0 findings (no issues)
• ✅ PMD: 0 findings (no issues) [Report archive]
• ✅ Checkstyle: 0 findings (no issues) [Report archive]

Generated automatically by the PR CI workflow.

[shai-almog]

Compared 231 screenshots: 231 matched.
✅ JavaScript-port screenshot tests passed.