Received-SPF: pass (gmail.com ... _spf.google.com: 209.85.210.43 is authorized to use 'jordan.lyall@gmail.com' in 'mfrom' identity (mechanism 'ip4:209.85.128.0/17' matched)) receiver=p-pm-inboundg03a-aws-useast1a; identity=mailfrom; envelope-from="jordan.lyall@gmail.com"; helo=mail-ot1-f43.google.com; client-ip=209.85.210.43
MIME-Version: 1.0
From: Jordan Lyall <jordan.lyall@gmail.com>
Date: Tue, 18 Aug 2026 20:21:59 -0700
Message-ID: <CAKC_OngEpkZ_uv9H0O_tmV2aeg8BtMx5Wc4kEbNdu+oXY5hYUA@mail.gmail.com>
Subject: First one to the real address
To: keep@jordanlyall.com
Content-Type: multipart/alternative; boundary="00000000000002b69706595de82b"

--00000000000002b69706595de82b
Content-Type: text/plain; charset="UTF-8"

Testing keep@jordanlyall.com instead of the 32 character hash.

If this arrives and comes back verified, the demo has a front door someone
could actually remember.

--00000000000002b69706595de82b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><body><div dir=3D"auto">Testing <a href=3D"mailto:keep@jordanlyall.co=
m">keep@jordanlyall.com</a> instead of the 32 character hash.<br><br>If thi=
s arrives and comes back verified, the demo has a front door someone could =
actually remember.</div></body></html>

--00000000000002b69706595de82b--