The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact firstname.lastname@example.org.
I now have the *SYSTEM cert store trusting everything built in, and the
two certs I got from Google.
Looking at DCM in a different browser, I was able to figure out how to
remove the cert associations I'd created earlier, with my
local-CA-signed cert. But it didn't make any difference. The results
On the Midrange side, I still typically get:
ID: 004B5A-Q60-002393000000298C20 Time Received: 10/25/22 12:04:00.922
10/25/22 12:04:00 0029 Recipient jamesl@xxxxxxxxxxxxxxxxx transfered
10/25/22 12:04:00 0029 r directly
10/25/22 12:04:00 0029 Recipient jhhl@xxxxxxxxx transfered to server
10/25/22 12:04:02 003B Marking jamesl@xxxxxxxxxxxxxxxxx as WRK
10/25/22 12:04:02 003B Marking jhhl@xxxxxxxxx as WRK
10/25/22 12:04:02 003B Connected to Server
10/25/22 12:04:02 003B ):587
10/25/22 12:04:02 0040 Relay already in processing, skip it
10/25/22 12:04:04 003F Marking jamesl@xxxxxxxxxxxxxxxxx as NDL
10/25/22 12:04:04 003F Marking jhhl@xxxxxxxxx as NDL
and in the Google logs, it shows up as:
Recipient: 0 recipients
Date: Oct 25, 2022 9:07:59 AM
Message ID: <635...SMTPIN_ADDED_REJECT_SESSION_161310@xxxxxxxxxxxx>
Message Size: 0 B
Status: 0/0 Delivered
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: Email sending problem -- any Google Relay experts here?, (continued)
This mailing list archive is Copyright 1997-2023 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.