Hey Birt!
Your email to the list did correctly add a DKIM signature, but it can't be
authenticated because the "selector" given in the email header doesn't
exist. That means your message cannot be authenticated.
DKIM-Signature: v=1; a=rsa-sha256; d=soigeneris.com;
s=*8DA87A45BE3E8E3*; c=relaxed/relaxed;
t=1718800242;
h=from:to:references:in-reply-to:subject:date:message-id:mime-version:
x-mailer:thread-index;
bh=PiIveX6pivAqJBj204nccsUS3EE1LJ80RfSxSB3kz0s=;
b=C3GLo2avqOI2hwNJflXhUYGJHmGwOkUA5e+t891MxfEKDjDMN7NsaadgJf4kp4pbYi85hybiD59
ZCAaB1Y+RRWRnR1XSgbCvnsHWxhLMWwSa4p/OQsyayYWiCon2mv273yjiErU6RbkhqmCRmnRZs2Iy
NVE+wS223x0l7ZkCYMtiRnQT/80SUD4cKC2CjyaRHs3fSv13XrFHw+QrU239YyPTcms7e0B9CxnQE
+W3EAzowMmjaZtF0SaDSkgE+aIKCVvhYM+4GI2CM69c8UU5IFJu9lsVYMskK4GNUK1jsaHETm6Gij
cuPldjouA5H2puYcKNq/y25ya+dEHGXIGCOQ==
As you can see, the selector is set to *8DA87A45BE3E8E3* (which is kind of
weird to me since I've usually seen them named things like "k1", but my
ignorance on this subject is vast.) Looking up that selector using the
*host* command finds nothing:
$ *host -t txt 8DA87A45BE3E8E3._domainkey.soigeneris.com
<http://domainkey.soigeneris.com>*
Host 8DA87A45BE3E8E3._domainkey.soigeneris.com not found: 3(NXDOMAIN)
I'd expect to see the public half of the encryption key, which would look
something like this:
$ *host -t txt arc._domainkey.internetmailserver.net
<http://domainkey.internetmailserver.net>*
arc._domainkey.internetmailserver.net descriptive text "v=DKIM1; k=rsa;
p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDSYjJGE0/J0gUPO516aDStFtciIXw3Ypb7
8mWFVv/nrDo04m52ROtLVqsAocclcXaAAt43o+oxEmNjKp/joemnBsLK7CTKNhDqjvS3ECmA
qI8WFLK6ChaJFODYkICmbqbFXcQ77XWVbu0oDqr3nB8B10t4Lr66ltqaUbM1rLxDmQIDAQAB"
By the way, once you have DKIM set up, I believe you'll also want to add a
DMARC record so that you'll get emailed when there is a problem. (I see you
have CloudFlare for DNS. They have a button that makes adding a DMARC
record easy and they'll even keep track of the failures for you so you
don't get swamped in your normal email address if, for example, a spammer
decides to fake messages as coming from your domain.)
—b9
P.S. Obligatory On-Topic: There's an issue of Portable 100 magazine (June
1985) that I want to read as it appears to be exactly the Rosetta stone I
need that tells me just the diffs between then 200 and 100. Unfortunately,
the scan on whtech <https://ftp.whtech.com/club100/doc/p100-8506.pdf> is
missing page 18 which appears to be the beginning of the "Face to Face"
article. Does anyone have this issue or know where I could find a good
copy? Thanks!
On Wed, Jun 19, 2024 at 5:39 AM <[email protected]> wrote:
> I went through this about 18 months ago configuring my email server to use
> authentication to prevent Gmail from silently eating random emails. This
> helps but I still have random problems communicating to Gmail accounts. In
> one case a friend and I had exchanged ~10 emails in a thread and Gmail
> randomly start blocking them. Sent same exact text from my Gmail account
> and it was fine. Very frustrating for Google to silently block. They seem
> to be the worst at actually blocking spam while not blocking legit emails.
>
>
>
> Jeff Birt
>
>
>
> *From:* M100 <[email protected]> *On Behalf Of *B 9
> *Sent:* Tuesday, June 18, 2024 11:33 PM
> *To:* [email protected]
> *Subject:* Re: [M100] M100 list getting sent to SPAM folder?
>
>
>
> Turns out Dreamhost hasn't figured out yet how to wrap or chain mailing
> list messages properly using encrypted authentication. That's a bit
> disappointing, but it sounds like it's been a major problem for many
> mailing lists. (See:
> https://www.ietf.org/archive/id/draft-levine-dmarc-listugh-01.html)
> Dreamhost currently has the following documentation about DMARC and mailing
> lists:
>
>
>
>
> https://help.dreamhost.com/hc/en-us/articles/215029308-Manage-a-Discussion-List
>
>
>
> In the "from_is_list setting" section, they say that you can get around
> the DMARC problem by selecting the "Munge From" radio button under General
> Settings.
>
> [image: Image removed by sender.]
>
> While "Wrap Message" sounds like what you want, they have a big warning
> that you should under no circumstances click the "Wrap Message" button as
> it is currently broken! I expect eventually they'll get wrapping or ARC
> chaining working.
>
>
>
> I think Munging is probably the best you can do with Dreamhost for now,
> but it does have potential downsides, such as making it hard for certain
> mail readers to show who a message is truly from.
>
>
>
> —b9
>
>
>
> P.S. Obligatory on-topic message: I was trying to figure out how
> Compuserve's Backgammon game worked on the Model 100 since I was curious
> how it sent the graphics. I stumbled across Brian K. White's nifty M100SIG
> archive of Compuserve circa 1996
> <https://github.com/LivingM100SIG/Living_M100SIG> which is a treasure
> trove of historical artifacts. Unfortunately, other than Backgammon being
> mentioned in some forum discussions, it is not available in that archive.
>
>
>
>
>
> On Mon, Jun 17, 2024 at 12:31 PM John R. Hogerhuis <[email protected]>
> wrote:
>
> Didn't mean to ignore this thread, but I have shinier rabbit holes to
> descend.
>
>
>
> If someone can tell me exactly what to do to get this working on Dreamhost
> I am happy to do it.
>
> Barring that... if you're getting this message, always click the "Looks
> Safe" and whitelist the list. I don't think we're getting bounced so much
> as foldered :-) Maybe the AIs will eventually figure it out.
>
>
>
> -- John.
>
>
