-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
This time, I am avoiding UTF-8.
I have a funny feeling this is the crux of the matter.
Also verified ok...
This time, I am avoiding UTF-8.
I have a funny feeling this is the crux of the matter.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 25/01/2020 9:29 p.m., August Abolins : All wrote:
This time, I am avoiding UTF-8.
I have a funny feeling this is the crux of the matter.
YEP. That one processed without errors. .: must avoid utf-8 encoding
when using signed clear-text. TB must be munging/substituting the
space char with the utf-8 equivalent AFTER generating the block.
Thank you. Looks like clear-signed messages MUST be posted in
plain ASCII only. Or, at least that is the situation with
TB/Enigmail.
Thank you. Looks like clear-signed messages MUST be posted in
plain ASCII only. Or, at least that is the situation with
TB/Enigmail.
Also the combination "JamNNTPd + UTF-8" may be the reason...
Origin: nntp point (2:221/360.8110)
Also the combination "JamNNTPd + UTF-8" may be the reason...
---
* Origin: nntp point (2:221/360.8110)
Sysop: | Psi-Jack |
---|---|
Location: | Gainesville, FL |
Users: | 47 |
Nodes: | 8 (0 / 8) |
Uptime: | 40:47:17 |
Calls: | 1,168 |
Files: | 7,441 |
Messages: | 68,812 |