Skip to main content

6 posts tagged with "dashboard"

View All Tags

Reputation scores count the bounces your sending can influence (rolling out)

  • Every bounce still shows as bounced. Logs, totals and message outcomes are unchanged. What changes is the counted figure that feeds a score.
  • Counted: an address or domain that does not exist, policy blocks (reputation, content, authentication) and anything that cannot be classified. Not counted: a full recipient mailbox, a network failure, and blocks on Motorical's own sending network.
  • New response fields on GET /motor-blocks/{id}/reputation (and the overview's reputation): totals.bouncedCounted, totals.bouncedExcluded, and lowVolume with a note. They appear where the rule is active for your account; nothing is removed or renamed.
  • Small Motor Blocks. With fewer than 50 sends in the window, bounces are not scored yet (lowVolume: true); complaints and failures still are.
  • Dashboard. The Health chip keeps the raw bounce rate; its tooltip gains a line saying how many bounces counted and why.
  • Rolling out. Active per account as the rollout reaches it. See which bounces count.

Documentation changed

Domains: reliable DKIM checks, clearer delete

DKIM verification is more reliable. Some correctly published DKIM records failed to verify, or failed for up to half an hour after you deleted and re-added a domain. We fixed three causes: long DKIM keys are now compared consistently across DNS providers, a stale cached record can no longer hide the current one (we ask your domain's own nameservers), and we now re-check by ourselves: every 10 minutes for the first two hours after a domain is verified, then hourly, for up to 48 hours. When your DNS is right, the domain becomes send-ready without you pressing anything.

Documentation changed

Backup codes: regenerate any time

One set of backup codes covers every way you sign in, whether you use a passkey, an authenticator app, or both.

  • Regenerate backup codes is now available in Settings → Security, including for accounts that only use a passkey. Replacing the set invalidates the old codes immediately and needs a fresh confirmation from you.
  • Adding an authenticator app no longer replaces your codes. If your account already has backup codes, they stay valid and the setup screen says so. Before this change, enabling an authenticator app generated a new set and silently invalidated the one you had saved.

One password rule everywhere

Every place that sets a password now applies the same rule: at least 8 characters, including a lowercase letter, an uppercase letter and a number. A symbol is welcome but does not replace a number.

  • The sign-up, set-password, reset-password and change-password forms all check the rule before you submit, so a password the server would refuse can no longer look acceptable.
  • The API returns a single message for every violation: "Password must be at least 8 characters and include a lowercase letter, an uppercase letter and a number".
  • If setting the password fails after your verification code was accepted, you can retry without requesting a new code.
  • The sign-up password form now includes your email as the username, so your browser's save-password prompt stores a complete login.

Sign-in: passkey first, codes as a second choice

If your account has both a passkey and an authenticator app, signing in now offers the passkey first. Your browser's passkey prompt opens by itself; if you dismiss it you can try again, or choose Use a code instead to enter an authenticator or backup code.

  • Passkey only: the code box asks for a backup code, and says why.
  • Authenticator app only: nothing changes.
  • Settings → Security: you can now rename a passkey, so you can tell your devices apart.

Also fixed: signing out after the page had been idle for a while could leave you signed in. Logout now ends the session reliably.