hermes-skills/skills/email/email-workflows/references/apex-wpforms-contact-mail-scope.md

Apex WPForms contact mailbox verification and scope discipline

Context

Apex Track Experience WPForms submissions need verification against the actual contact@apextrackexperience.com mailbox when the user asks whether a completed form notification was received.

Verification pattern

1. Query recent WPForms entries from the Apex database.
2. Identify form IDs:
   • 268 — Apex Predators Track Experience Waiver
   • 270 — NASA Top Speed Event
3. Parse latest entry fields for participant name/email/date.
4. Check the contact@apextrackexperience.com inbox directly over IMAP.
5. Search for the participant email/name/form subject on the submission date.
6. Report only the evidence needed: UID, Date, From, To, Subject.

Example verified evidence:

UID: 656
Date: Tue, 14 Jul 2026 14:54:13 +0000
From: Apex Track Experience <info@itpropartner.com>
To: contact@apextrackexperience.com
Subject: Apex Liability Waiver Form - xi liu

Scope discipline

Do not infer that every WordPress or WooCommerce site-level address containing info@itpropartner.com is drift or must be changed. The user explicitly corrected that those settings had not been addressed and should not be treated as a fix target without request.

For Apex mail tasks:

• Use contact@apextrackexperience.com credentials for sending/receiving Apex-specific mail.
• Do not send Apex messages from info@itpropartner.com unless explicitly directed.
• If the user asks why a message appears from another address, inspect and present evidence first; do not label unrelated site settings as wrong.
• Make no settings changes unless the user explicitly asks for a fix.

Useful commands/patterns

Direct IMAP proof is stronger than WP debug logs. WP Mail SMTP debug tables may not include every current successful send and schemas vary by plugin version.

Potential tables:

wp_wpforms_entries
wp_wpforms_entry_meta
wp_wpmailsmtp_debug_events
wp_wpmailsmtp_emails_queue
wp_wpforms_logs

WP Mail SMTP debug table columns observed:

id, content, initiator, event_type, created_at

Do not assume columns named subject or message exist.