Aller au contenu principal

Sender Email Setup

This guide explains how to configure the email sender used by Aaperture. The application can deliver messages either through its own trusted no-reply@aaperture.com address or via your custom Gmail (app password) / custom SMTP credentials.

When to use the default sender​

If you do not configure anything, Aaperture sends all emails with the default address. This is the safest choice because:

  • It works out of the box; no credentials are required.
  • Deliverability is managed centrally (SPF / DKIM / DMARC already aligned).
  • There is no risk of hitting Gmail sensitive scopes that would trigger CASA Tier 2 review.

Keep the default sender if you only need notifications to carry the platform branding or if your own SMTP provider forbids third-party access.

Switching to a custom sender​

Visit Settings → Google to manage sender credentials. The legacy dropdown from Application settings has been replaced with this dedicated page so all Google / SMTP related controls live in the same place. The page gives you:

  • Connection status (green check when a password/token is stored).
  • The form to connect your Gmail app password or a custom SMTP account.
  • A delete button to revoke credentials and fall back to the default sender.
  • A test recipient input so you can trigger a quick email and verify deliverability.

You can switch back to the default sender at any time by removing the stored credentials; Aaperture automatically reverts to the platform address.

Gmail app password​

  1. Enable 2‑Step Verification in your Google account.
  2. Visit Security → App passwords, generate a new 16-character password.
  3. In Aaperture, pick the Gmail option and paste the app password. The UI shows a green badge once the password is stored.
  4. Send a test email to ensure everything works.

Because we rely on SMTP AUTH with an app password, we do not request Gmail scopes via OAuth. This keeps the integration out of CASA Tier 2 requirements.

Custom SMTP server​

If you prefer another mailbox provider, use the SMTP fields on the same page:

  • Email – the mailbox that should appear as the sender.
  • Password – the password or token provided by your mail host.

Ensure the account allows SMTP connections from third-party apps and that you configured SPF/DKIM records for your domain. After saving, send a test email to validate the setup.

Troubleshooting​

  • 404 errors on /api/users/me/email-credentials – confirm the backend is running with the latest migrations; the route lives under the Users module.
  • “Sender Email” showing “Not configured” – credentials have been removed or failed to decrypt. Re-enter the app password or SMTP credentials.
  • Google verification feedback about calendar scopes – unrelated to email sending; the calendar integration only needs https://www.googleapis.com/auth/calendar.events.owned.

For further assistance, reach out through the support channel with the timestamp of the failing request and we’ll inspect the logs.***