Skip to content

armgit / floci

Public Imported from GitHub
0

Light, fluffy, and always free - The AWS Local Emulator alternative

docs(ses): list the missing MEDIUM IsValid among the insights deviations (#6579)

Kenshin Okinaka1e89ae290879
diff --git a/docs/services/ses.md b/docs/services/ses.md
index 1b6ea3a724..cea7a6d09e 100644
--- a/docs/services/ses.md
+++ b/docs/services/ses.md
@@ -511,7 +511,7 @@ registered Easy DKIM domain do not report this SES-hosted zone.
S/MIME certificate associations are stored per region and never used: Floci does not sign mail. Associating validates the request as SES does (a domain identity needs a `FromAddress` in the domain or one of its subdomains, one certificate per address regardless of case) but, like SES, does not inspect the certificate. `ListEmailIdentityCertificates` reports `ACTIVE` while the association meets the [S/MIME certificate considerations](https://docs.aws.amazon.com/ses/latest/dg/send-email-authentication-smime.html#send-email-authentication-smime-certificate-considerations), plus the requirements a probe found SES also enforces (an end-entity certificate whose key usage includes `digitalSignature` and whose extended key usage includes `emailProtection`), checked against Floci's ACM and identity verification when the list is read, with the certificate's expiry as `CertificateExpiryTime`, and `FAILED` otherwise. There is no `PROVISIONING` phase, `DisassociateEmailIdentityCertificate` removes an association at once, and the certificate is not listed as in use by ACM. As on SES, `DeleteEmailIdentity` refuses an identity that still has a certificate associated, whatever its status. The v1 `DeleteIdentity` and `DeleteVerifiedEmailAddress` share the identities and refuse it too, with the same `BadRequestException` the tenant-association guard returns there; SES's v1 behaviour was not probed.
-[`GetEmailAddressInsights`](https://docs.aws.amazon.com/ses/latest/dg/email-validation-api.html) is answered offline: Floci performs no DNS lookup and no mailbox probe, and charges nothing. As on AWS (probed 2026-10-25), it answers with Virtual Deliverability Manager disabled, a malformed or over-long address returns 200 with every verdict `LOW` rather than an error, an empty `EmailAddress` is a `BadRequestException` (an absent one, which the AWS CLI refuses to send, is assumed to answer the same), and `IsValid` is `LOW` whenever `HasValidSyntax`, `HasValidDnsRecords` or `MailboxExists` is `LOW` and `HIGH` otherwise. The verdicts follow fixed rules:
+[`GetEmailAddressInsights`](https://docs.aws.amazon.com/ses/latest/dg/email-validation-api.html) is answered offline: Floci performs no DNS lookup and no mailbox probe, and charges nothing. As on AWS (probed 2026-10-25), it answers with Virtual Deliverability Manager disabled, a malformed or over-long address returns 200 with every verdict `LOW` rather than an error, an empty `EmailAddress` is a `BadRequestException` (an absent one, which the AWS CLI refuses to send, is assumed to answer the same), and `IsValid` is `LOW` whenever `HasValidSyntax`, `HasValidDnsRecords` or `MailboxExists` is `LOW`. The verdicts follow fixed rules:
| Evaluation | Floci's verdict |
|---|---|
@@ -521,7 +521,7 @@ S/MIME certificate associations are stored per region and never used: Floci does
| `IsRoleAddress` | `HIGH` when the local part, without a `+label`, is a common role name such as `admin`, `info`, `noreply`, `postmaster` or `support`; otherwise `LOW` |
| `IsDisposable`, `IsRandomInput` | Always `LOW` |
-Deviations from AWS: every domain that is not reserved is taken to have valid DNS records, Floci keeps no disposable-domain list and detects no random input, and an address with a non-ASCII character in its domain (an internationalized domain name included) or in an unquoted local part is rated `LOW` everywhere, as a send would reject it, while a quoted local part, which a send does not inspect, is rated like any other; AWS's verdicts for such addresses were not probed.
+Deviations from AWS: `IsValid` is `HIGH` whenever it is not `LOW` and never `MEDIUM`, although AWS documents a `MEDIUM` overall verdict too (no probed address returned one), every domain that is not reserved is taken to have valid DNS records, Floci keeps no disposable-domain list and detects no random input, and an address with a non-ASCII character in its domain (an internationalized domain name included) or in an unquoted local part is rated `LOW` everywhere, as a send would reject it, while a quoted local part, which a send does not inspect, is rated like any other; AWS's verdicts for such addresses were not probed.
### Request member types