Marco Moock <mm+usenet-es@dorfdsl.de> wrote:
> Am 02.11.2023 um 16:47:41 Uhr schrieb VanguardLH:
>
>> As for old clients that don't support the latest encryption protocols
>> and/or ciphers, a solution is to add another program as a proxy that
>> does, like sTunnel. Not all NNTP providers have logins (they don't
>> assign accounts to users), so encryption is meaningless.
>
> That is only possible for your own network, but not for public server.
> Wait some time and they are being abused for posting spam and troll
> posts.

As you well know, it is possible, you just don't like it. Anyone,
like me right now, who uses a news server without user
accounts/log-ins wouldn't care to have a password encrypted if they
were posting from a news server that did require free accounts
either, because it would still provide much more protection against
people spoofing them than they feel is required.

--
__ __
#_ < |\| |< _# | Note: I won't see posts made from Google Groups |

On Fri, 3rd Nov 2023 21:11:41 +0000, Retro Guy wrote:

[Parallel new connection with identical settings]
> Interesting, that works.

If you just wanted 40tude Dialog to work and were not interested in
debugging the causes of your problem (see below), you now could move
all articles you want to keep in all subscribed groups from the
group-folders of the old connection to the same ones of the new
connections. (It is important, that no filters or restricted views
are active on the source folders. - To avoid missing articles.)
After this being successful, the old connection could be deleted.

As it is:
>> See, whether the new connection leads to the same read-only status
>> of groups. If so, maybe contact the Usenet provider about it.
>
> Lol, I am the Usenet provider :) I'll dig into it a bit and see what
> might be the problem. I also wrote the nnrp server, so I assume the
> problem is there. (Watching traffic logs, etc.)

I don't think, you'll get much information this way. The problem, IMHO,
was caused during the first retrieval of the server group list (done
by 40tude Dialog). Out of whatever reason (maybe even a transmission
error), 40tude Dialog got the flag "Postingallowed"=FALSE set in its
database for the group(s) in question. I had expected the flag to get
changed when updating the group list. (If the server lists the group
/now/ as writeable.) But as you wrote yesterday, that wasn't the case.
This seems to be an "unwanted feature" (= bug) by 40tude Dialog, which
(because of the abandoned development) will never be rectified...

The world doesn't end because of this, though. Setting up the parallel
connection and moving archived articles over should work. Another way
to solve this, would be to edit groups.idg with a hex-editor. But that
is not recommended, if one wasn't /really/ familiar with the database
file structure of 40tude Dialog. ;-)

Bernd