Email Verification (Reoon)
Overview
The contact form uses the Reoon Email Verifier API (reoon.com) to validate email addresses before accepting submissions. Reoon runs after the nonce, honeypot, Turnstile, and regular field checks, and before CSV storage.
Configuration
| Setting | Detail |
|---|---|
| API Endpoint | https://emailverifier.reoon.com/api/v1/verify |
| API Key | Stored as WordPress option opshell_reoon_api_key |
| Verification Mode | power (deep verification) |
| Timeout | 90 seconds |
Verification Flow
Submit email to Reoon API in power mode
→ Parse response JSON
→ Check `is_safe_to_send` flag
→ true: proceed to CSV storage
→ false: log to failed-verifications.csv, show error
Response Handling
| Condition | Action |
|---|---|
| API key missing | Return WP_Error: "not configured" |
| API request fails | Return WP_Error: "verification failed" |
| Non-200 response | Log failed verification, show generic error |
is_safe_to_send === true | Accept submission |
is_safe_to_send === false | Reject with "valid, deliverable email" message |
Failed Verification Logging
Failed verifications are stored in failed-verifications.csv with:
- Timestamp, IP, Name, Email, Subject, Message (including the URL prefix when supplied)
- Verification status,
is_safe_to_send, mode, overall score - Error message