BluepointATM Email Setup Investigation — 2025-11-07

Overview

During the ^[1], Mark and Melissa investigated the existing wade@bluepointatm.co email configuration in order to replicate it for a new mike@bluepointatm.co address. The new address is needed to support ^[2] HubSpot outreach sequences without risking blacklisting of Wade's primary .com address.

The investigation was inconclusive during the call — the existing setup does not match Mark's standard AWS SES workflow and requires further offline investigation before the new address can be created.

Background

Bluepoint previously needed a dedicated sending address (wade@bluepointatm.co) for HubSpot email sequences so that Wade's real @bluepointatm.com address would not be flagged or blacklisted by spam filters. Mark set up the .co address at some earlier point, but the exact method used was not immediately recalled during this call.

The new request is to create mike@bluepointatm.co with forwarding to mike@bluepointatm.com, following the same pattern.

DNS Findings

Mark pulled up the bluepointatm.co domain in Cloudflare during the call and noted the following:

Key observation: The MX record pointing to Google is inconsistent with Mark's standard AWS SES setup (which he has used for clients like Big Believe, King Company, and American Extractions). This means the wade@bluepointatm.co address was likely set up via Google Workspace, not AWS SES.

Neither Mark nor Melissa has confirmed credentials for a Google Workspace account on bluepointatm.co. Wade likely does not know the details either.

Standard AWS SES Workflow (for reference)

For other clients, Mark's typical process is:

1. Create an AWS organization for the client
2. Add the sending domain (e.g., letsbakebelieve.co) to AWS SES
3. Create a user/email address within SES
4. Configure forwarding so no one actually monitors the SES inbox — all replies route to the client's real address
5. Provide HubSpot with the SES SMTP credentials for sending

This workflow does not appear to have been used for Bluepoint, based on the Google MX record.

Open Questions

• Does a Google Workspace account exist for bluepointatm.co? If so, who owns/manages it?
• Was wade@bluepointatm.co created in Google Workspace, Cloudflare Email Routing, or another service?
• Does Asymmetric have admin access to whatever system manages this domain's email?

Action Items

• [ ] Mark — Investigate the existing wade@bluepointatm.co configuration offline; determine whether it was set up via Google Workspace, AWS SES, or Cloudflare Email Routing (@Mark Hope)
• [ ] Mark — Create mike@bluepointatm.co and configure forwarding to mike@bluepointatm.com; confirm completion with Melissa (@Mark Hope)
• [ ] Melissa — Email Bluepoint re: next HubSpot automation; note that sending can proceed from wade@bluepointatm.co now, and mike@bluepointatm.co is pending creation (@Melissa Cusumano)
• [ ] Isalia — Email Bluepoint re: payment terms for Blueprint project (separate but noted in same call) (@Isalia Ramirez)

Related

• ^[3]
• ^[4]
• ^[5] (if exists)