Prompt
smtp mailbox verification
Latest observation
Oct 5, 2026
OpenAI APIWeb search: off
“SMTP mailbox verification” usually means checking whether an email address can receive mail by interacting with the target mail server over SMTP.
Important note: this can be used for legitimate bounce-reduction or account-validation workflows, but it’s also commonly used for email enumeration. If you’re doing this on addresses/domains you don’t own or don’t have permission to test, I can’t help with that.
If your goal is legitimate verification for your own system, here are safe approaches:
-
Send a confirmation email
- Most reliable method.
- User clicks a link or enters a code.
- Confirms both mailbox ownership and deliverability.
-
Use SMTP only for basic deliverability checks
- Check that the domain has MX records.
- Open an SMTP connection and verify the server accepts your mail during normal sending.
- This does not reliably prove the mailbox exists.
-
Use bounce handling
- Send a real message and process DSNs/bounces.
- Mark addresses invalid if they hard-bounce.
-
Validate syntax and domain first
- RFC-ish email format check.
- DNS MX lookup.
- Optional SPF/DKIM/DMARC checks for domain hygiene.
-
Avoid relying on SMTP “VRFY/RCPT TO” probing
- Many servers disable or fake responses.
- Results are often unreliable and can trigger abuse defenses.
If you want, I can help with one of these legitimate options:
- a Python email validation script
- SMTP connection testing for your own domain
- a deliverability workflow design
- bounce processing setup