On Aug 8, 2025, at 09:15, Philip Borkholder plborker@netzero.net wrote:

I am not receiving emails anymore from the list since the end of July. Ed, could you let me know what I need to do? I re-subscribed with my email: plborker@netzero.net and also tried with: plborker@gmail.com

Neither one of them are receiving list emails for FoxPro Dev.

First off, I recognize the irony is responding to a email delivery problem with another email 😂. I'm hoping you can see this via the archives.

I'm seeing 2 different errors for the different addresses. For the netzero, I see:

Aug 4 09:50:19 mail postfix/smtp[402821]: EC5B61200DF: to=plborker@netzero.net, relay=mx.dca.untd.com[64.136.44.37]:25, delay=432920, delays=432918/0.23/2.3/0, d sn=4.7.4, status=deferred (TLS is required, but was not offered by host mx.dca.untd.com[64.136.44.37])

That looks like a problem with the email provider `untd.com`. You could enquirer about why TLS isn't offered; that's pretty standard for email for many, many years now.

For the gmail, I see the same error I see for all gmail users:

20463:Aug 4 12:04:03 mail postfix/smtp[406281]: C8CC9120184: to=plborker@gmail.com, relay=alt1.gmail-smtp-in.l.google.com[172.253.116.26]:25, delay=34, delays=0.11/0.9 /32/0.92, dsn=4.7.30, status=deferred (host alt1.gmail-smtp-in.l.google.com[172.253.116.26] said: 421-4.7.30 Your email has been rate limited because DKIM authentication didn't 421-4.7.30 pass for this message. Gmail requires all bulk email senders to 421-4.7.30 authenticate with DKIM. 421-4.7.30 421-4.7.30 Authentication results: 421-4 .7.30 DKIM = did not pass 421-4.7.30 To set up DKIM for your sending domains, visit 421-4.7.30 https://support.google.com/a?p=turn-on-dkim 421-4.7.30 To learn more ab out Gmail requirements for bulk senders, visit 421 4.7.30 https://support.google.com/a?p=sender-guidelines. a640c23a62f3a-af91a1f29c1si789064266b.554 - gsmtp (in reply t o end of DATA command))

It boils down to the email says it's from the domain of the person who posted the message, but it's actually being sent by my server, so that results in a DKIM match failure.

-- Ed Leafe