Jim,
And I'm sorry for making you waste your time investigating that. I didn't check
the archive, I searched my local mailbox on the subject ("gnucash_user:
rounding errors and significant digits") and turned up only Bruces most recent
two posts. Armed with the date from your 108251 link I looked in my mailbox on
that date and found your posts.
Regards,
John Ralls
> On Sep 9, 2023, at 2:10 PM, Jim DeLaHunt <list+gnuc...@jdlh.com> wrote:
>
> I'm sorry, I made a mistake in my message below.
>
> The Jim message which Bruce was quoting, in the Bruce message to which John
> replied, did in fact make it to the gnucash-user list archive[4], but in
> August, so of course it was not in the September archive[1].
>
> Thus, the list archive is not evidence for intermittent delivery of my
> gnucash-user posts. Maybe there is in fact no delivery problem.
>
> Sorry for the confusion,
> —Jim "Jim" DeLaHunt
>
> [1]
> <https://lists.gnucash.org/pipermail/gnucash-user/2023-September/thread.html>
> [4] <https://lists.gnucash.org/pipermail/gnucash-user/2023-August/108521.html>
>
> On 2023-09-09 13:25, Jim DeLaHunt wrote:
>> On 2023-09-09 12:36, john wrote:
>>> I don't know who this "Jim" is, their replies are not making it to the
>>> list....
>> Oh dear. I spend time writing my messages to Bruce McCoy. It would be a pity
>> if they didn't make it to the list.
>>
>> This "Jim" is me, Jim DeLaHunt <list+gnuc...@jdlh.com>.
>>
>> The Jim message which Bruce was quoting, in the Bruce message to which John
>> replied, did not make it to the gnucash-user list archive[1]. However, I
>> did receive a copy of my reply via the gnucash-user email list[2] at the
>> time. The reply which I sent to the Bruce message today did in fact get to
>> the archive[3]. So maybe my messages are intermittently failing to reach
>> some gnucash-user recipients?
>>
>> Looking at the other headers, I wonder if maybe some spam detection services
>> (ARC? SPF?) are intermittently raising false positives on some of my
>> gnucash-user posts. I don't know how to interpret the headers of my
>> gnucash-user replies to investigate that.
>>
>> Best regards,
>> —Jim "Jim" DeLaHunt
>>
>> [1]
>> <https://lists.gnucash.org/pipermail/gnucash-user/2023-September/thread.html>
>> [2] Some of the mail headers of the copy of my reply which I received from
>> gnucash-user:
>>
>>> ...
>>> Received: from inbound-trex-4 (unknown [127.0.0.6])
>>> by postfix-inbound-v2-8.inbound.mailchannels.net (Postfix) with ESMTP
>>> id C524B600069
>>> for
>>> <list+gnuc...@jdlh.com>
>>> ; Mon, 21 Aug 2023 21:01:05 +0000 (UTC)
>>> ...
>>> Received: from code.gnucash.org (code.gnucash.org [204.107.200.65])
>>> (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384)
>>> by 100.112.2.51 (trex/6.7.2);
>>> Mon, 21 Aug 2023 21:01:05 +0000
>>> ...
>>> Received: from seahorse.cherry.relay.mailchannels.net
>>> (seahorse.cherry.relay.mailchannels.net [23.83.223.161])
>>> (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
>>> key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest
>>> SHA256)
>>> (No client certificate requested)
>>> by code.gnucash.org (Postfix) with ESMTPS id 2FEE14B342
>>> for
>>> <gnucash-user@gnucash.org>
>>> ; Mon, 21 Aug 2023 17:00:08 -0400 (EDT)
>>> ...
>>>
>>
>> [3]
>> <https://lists.gnucash.org/pipermail/gnucash-user/2023-September/108723.html>
>>
>>
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
