Meeting
Gardner - Current
Gist
Call with Joel Perkins and Adam (from Gardner's team) about migrating Gardner's hosting and email over to Classic City, prompted by MX record issues after Gardner moved platforms off AWS. Adam suspected the new MX records were causing email delivery failures for vendors trying to reach Gardner. The plan is for Classic City to take over hosting management while future website work is billed hourly ad hoc; the call ended trying to loop in a third person, Mike, who had platform details but couldn't join.
Distilled from the transcript by claude-sonnet-5 · Jul 25
What came out of it
Decisions2
- Gardner's hosting will move to Classic City's management
- Future website work will be billed hourly on an ad hoc basis rather than a retainer
Risks and blockers1
- Gardner's MX records may have changed after their platform migration off AWS, causing vendor emails to bounce
Open questions2
- What are Gardner's new MX records after the platform move?
- Can Mike confirm details of the platform migration and its effect on email/DNS?
Next steps2
- MeSet up a three-way call or connect directly with Mike to get migration details
- MeCheck MX Toolbox to see current published MX records for Gardner's domain
A record of what was agreed, and nothing here was scheduled. Follow-ups reach your list through unconfirmed to-dos, never straight onto it.
From this meeting
No tasks spawned from this meeting.
Notes
No notes on this meeting yet. Use the plus Note button to add one.