No Double Email Guard

No-double-email guard

Sending twice to the same person looks like spam and burns the lead. Guard every send.

Keep one permanent contact record

A small SQLite table works: email (primary key), profile, person, status (reserved, sent, unknown, do_not_contact), reserved_at, data (JSON). Never delete rows.

Before each run

1. Import every recipient from the mailbox's Sent folder (To, Cc, Bcc) as status: sent. Read every page. A mailbox error or partial page is NOT an empty result - stop.
2. Check the inbox for replies, opt-outs, and bounces. Mark opt-outs and bounces do_not_contact. Do not cold-email anyone who already has a conversation going.

Before each send

1. Normalize the email (lowercase; for Gmail remove dots and +tags).
2. Block if the email, the LinkedIn profile, or the same person at the same company already exists.
3. Enforce a daily send limit.
4. Write the reservation to the database before the network call. A crash then cannot cause a second send.
5. Send once. On confirmed success, set status: sent with the provider message ID.
6. On any error or unclear result, set status: unknown, stop all sends for the run, and ask the user. Never retry automatically.