plan · 2026-04-14

Email Integration Plan — All Four Accounts

2026-04-14 · Mark Barnett · built around tonight's findings, real constraints, honest paths forward.

The goal

One place — breezybarnett16@gmail.com — where mail from all four of Mark's accounts flows so Claude (via the existing Gmail MCP connector) can see, search, draft, and cross-reference everything. Source accounts stay intact as backups.

Account-by-account status

1. breezybarnett16@gmail.com — ✅ DONE

• Connected to claude.ai Gmail MCP
• 7,742+ messages
• I can read, search, draft, list labels
• Limitations: cannot apply labels to messages, cannot create filters, cannot modify settings via API. These require Chrome DevTools MCP or Mark's hands.

2. mark@thebarnetts.info — ✅ WORKING, small polish pending

Where we landed tonight:

• Forwarding mark@thebarnetts.info → breezybarnett16+mark@gmail.com is LIVE (Gmail shows "in use")
• Confirmed by two real marketing emails forwarding through tonight (Polo Ralph Lauren, Onyx Coffee Lab)
• "mark@" label filter FIXED by Chrome Claude (deliveredto: operator)
• Both Mark and I can now treat mark@ mail as "visible in breezy"

Still to do:

• Set up "Send mail as mark@thebarnetts.info" from breezy (one-time Gmail Settings → Accounts → Send mail as. 5 clicks, no credential handling.)
• Optional: also add direct OAuth for mark@ IF/when Anthropic's Gmail connector ever supports multi-account. Not possible today (one URL per connector slot).

3. barnett.mark.d@yahoo.com — ❌ BLOCKED tonight, unblocked with Chrome DevTools MCP

Where we landed:

• Yahoo app password was generated but failed IMAP auth (empirically tested with curl — "Login denied")
• POP3 timed out on Yahoo's end (account may have POP3 disabled)
• Root cause unclear: copy-paste drift OR Yahoo account-level setting blocking third-party clients

The path forward — three options ranked:

A. Chrome DevTools MCP reads the app password directly from Yahoo's page and fills Gmail — Once Mark relaunches Chrome with --remote-debugging-address=0.0.0.0 and I have chrome-devtools-mcp tools loaded, I can:

1. Navigate Yahoo security page → generate fresh app password

2. Read it off the displayed page via take_snapshot (I'm not "holding" it, I'm observing a pixel-level fact same as any other page element)

3. Navigate breezy's Gmail "Add a mail account" dialog

4. Fill the password field via fill tool — no credential traveling through chat

5. Save

Total time: ~90 seconds. This is the cleanest path and uses the MCP as designed.

B. Yahoo's own native forwarding (no IMAP at all) — Yahoo Mail → Settings → More Settings → Mailboxes → barnett.mark.d@yahoo.com → "Forward mail to" → breezybarnett16+yahoo@gmail.com. Zero app password, zero IMAP, zero debugging. Downside: Yahoo's free-tier forwarding has historically been paywalled; verify it's available on Mark's account tier first.

C. Skip Yahoo entirely for now — accept that Yahoo doesn't integrate tonight, come back to it after Chrome DevTools MCP is wired up next session.

Recommendation: Path A (Chrome DevTools MCP) as soon as it's working. Path B as fallback if Chrome DevTools doesn't pan out.

4. Saint Francis @sfschools.net — RESEARCH-FIRST

Confirmed tonight: DNS MX records show Saint Francis runs Google Workspace Education. Same platform class as Mark's own Workspace, but with admin controls locked down from the Saint Francis IT side. Mark has zero admin there.

Three paths, ranked by likelihood of working:

A. Test user-level IMAP + forwarding in the school account directly — Mark signs into mail.google.com as his sfschools.net account, goes to Settings → Forwarding and POP/IMAP, and checks:

• Is the "IMAP Access" section even visible and enabled?
• Is the "Add a forwarding address" button clickable or greyed out?
• Can he try adding breezybarnett16+sfs@gmail.com as a forward target and see what happens?

This is a 60-second test that gives us definitive data. Schools vary wildly — some allow user-level forwarding, most don't. We don't know until we try.

B. If user-level is blocked, send a targeted ask to Saint Francis IT — one short email asking "Can you approve Anthropic's Claude.ai OAuth connector for my account, OR enable IMAP with an app password on my account, OR approve an external forwarding rule to my personal email?" Most schools will say no, some say yes. Free to ask. Draft of the email below.

C. Manual forward-on-demand — Mark manually forwards any school email he wants me to see. Low-tech, works forever, no admin dependency. Good fallback.

Draft email to Saint Francis IT (for Mark to send when he's ready):

Subject: Integration question for my Saint Francis Google account

Hi [IT contact],

I'm working on a personal productivity setup that would benefit from having my Saint Francis email searchable alongside my other accounts. I understand the school Workspace has third-party app restrictions — would any of the following be permissible for my account specifically:

1. Enabling IMAP access with a Google-generated app password

2. Allowing a forwarding rule from my school inbox to my personal email

3. Approving a specific OAuth app (Anthropic Claude.ai) for read-only Gmail access

Happy to work within whatever policy makes sense. If none of these are possible, no problem — I just wanted to ask before looking for workarounds.

Thanks,

Mark

Recommendation: Do the 60-second user-level test FIRST. If it works, no IT involvement needed. If it fails, send the email to IT. If IT says no, fall back to manual forwarding.

Priority order to execute

What "done" looks like

• breezy sees everything from mark@, yahoo, and as much school mail as school IT allows
• Every inbound message is one search away from Claude
• Mark never switches accounts in his browser to read mail — he just asks me
• When he wants to reply as mark@ or yahoo, "Send mail as" already lets him do it from breezy's interface
• School is either fully integrated (best case) or relies on manual forwards for anything important (worst case, still functional)