Mail server changes
Updated May 8, 2023: I have updated pile.org to use email server authentication and authorization (see below). If you send email from an @pile.org email address, you now need to use the correct mail servers to help keep your messages from bouncing or being flagged as spam. Please get in touch with me, and I’ll help you get set up!
(Original post follows. After that, for the super-nerds, are some mail headers demonstrating that this all works. At some point, I might set up some kind of DMARC policy, but not tonight.)
Do you send email from an @pile.org email address? Do we know each other, and have we quite possibly had beers together? Get in touch with me before Monday evening Pacific time, May 8, 2023, at my four-letter nickname @pile.org (or however you normally reach me).
I’ve had a few too many emails rejected or dropped into spam folders because I haven’t implemented SPF or DKIM for the domain. It’s long past time to change this, and my current plan is to do it the evening of Monday, May 8. You and I will each need to make a couple changes, so reach out and we’ll get it all sorted — it should be pretty simple.
If you try to send from an @pile.org address after I make the change, without having gotten in touch with me and sorted things out, your emails will have a higher chance of getting rejected as spam by the recipient’s email server (and getting bounced back to you) and/or possibly client (and silently dropping into their spam folder).
(On the back end, I’ll need to make some DNS changes, and will need to set you up with an account that lets you authenticate to the SMTP server for pile.org. You’ll need to change your mail client to send mail via that server.)
Here are some mail headers from Gmail’s receipt of a message sent with the new SPF and DKIM configuration.
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:dkim-signature; bh=Nu+1dXkJIdCjtLlsvKs2R1NYjS/yUvazBiI84+LiFR4=; b=NaXmJOB0QrprcicmvTAvIp6E8+7nUNHq5dtaP4Mqzmh7UrJPbw9xZV9mw40E6fquf4 LPAJDauqlZTAejmqhW2xECkegC3Y+zukaxoCmG9KYRu0BVEIJaBnDTpVUiQcZfj6Tu2e CwxuKSTCCWx+gk0mcC33jJF43Xo6jGIaLgojsJuNa/zwYoJanl4Wn7mJ44r5o8QQuLhm Q3Fogs7/eVPG7NxbEhl11Eyl3qCXqa/M2o2RLr1MgaYlzTOgPE9mYEjA2w2UWX6P1aQl VEiXqUfZ/LGCITBREEii4JZxAekhSawGmqGjnhiNtnKErcCxpbFoYatEbKL65zAC1t9Z 7vrw== ARC-Authentication-Results: i=2; mx.google.com; dkim=pass firstname.lastname@example.org header.s=dreamhost header.b=EUI5mKpK; arc=pass (i=1); spf=pass (google.com: domain of email@example.com designates 220.127.116.11 as permitted sender) Received-SPF: pass (google.com: domain of firstname.lastname@example.org designates 18.104.22.168 as permitted sender) client-ip=22.214.171.124; Authentication-Results: mx.google.com; dkim=pass email@example.com header.s=dreamhost header.b=EUI5mKpK; arc=pass (i=1); spf=pass (google.com: domain of firstname.lastname@example.org designates 126.96.36.199 as permitted sender) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1683606060; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding:dkim-signature; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pile.org; s=dreamhost; t=1683606060; bh=Nu+1dXkJIdCjtLlsvKs2R1NYjS/yUvazBiI84+LiFR4=; h=From:Content-Type:Content-Transfer-Encoding:Subject:Date:To; b=EUI5mKpKNpRlnI0NchGUohFrf14O7aRCJ/Kg3wObnCpO44vPOy913xAei/qk/M/F3 RxS4DbwRQJxd6MWDCf40XoF2JUqZkvqDESRrsJYOKI40oDS+1ClSg8ieMnPhOILM6X fp2WnAmVa+qII1AZy5Igs1qt4lLC38Tzc4iEWmB9jUqDUoSMvI+GtM5CS2DUkcZkXd hTuJxPaO43LGxSKtQSQMwVLJduw6CaNS5RfadlHEUMV+WHUwftr1gJ/S3DlXNXnd64 14SkTpCZqZsbAS8lUmGegfCLGzqAurUNZ+YwV/8KhuxnqmCYxyI+Gx2ABlSl6rspdR RmWI6b8IBqEoA==