Subj : Test Reply
To   : deon
From : Accession
Date : Sun Dec 24 2023 08:04 am

Hello deon,

On Sun, 24 Dec 2023 13:52:04 +1100, you wrote:

 >> 12 minutes is still an oddly enough long time, probably just due to
 >> someone in the path holding mail for pickup rather than crashing it.
 >> But definitely better than 7+ hours.

 d> It is one of the longer times.

 d> Another consideration is your PC clock time?

Possibly. I don't think it matters enough to dig much further into it. 12 minutes isn't going to make or break an FTN message network. Heck, 7+ hours wouldn't either. ;)

 >> Are you using anything to translate charsets? Or did it just send out
 >> the original CP437 message with a UTF-8 CHRS kludge to match mine?

 d> I dont translate anything. If the message comes with a CHRS kludge line,
 d> then I re-use the original CHRS with the reply, otherwise, I add "CP437
 d> 2". In this case, I'm guessing because it was a NNTP post, your endpoint
 d> added the "UTF-8 4" (or your SmapiNNTPd did?)

You may not want to re-use the original message's CHRS kludge with the reply unless you're actually going to translate it. Your automated message is CP437, and if not translated, should probably stay that way.

And yes, I have Smapinntpd setup to read incoming messages as CP437 (translated to UTF-8 - which is why I can read properly posted CP437 messages here), but anything leaving here is UTF-8 (which covers ASCII if my message doesn't actually contain any UTF-8 characters). I have Golded setup that way as well. Just seems to be the best way for me to see/read *most* things correctly. I usually don't try to quote anything I translate so I don't mess up the original post, but I was trying to figure out why that automated reply didn't look like any of the others I've seen. ;)

Regards,
Nick

.... "Take my advice, I don't use it anyway."
--- Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32)
 * Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0)

.