3
via You must be vouched for by a vouched user to participate.
-
🙃! Great! Thanks for testing
You reply via NNTP (that's why you can login as well).
I found
slrnnot very good to be honest. It doesn't support rfc3977 fully and it fetches each article headers separately instead of doing an OVER because it uses the nonstandard XOVER (the rfc does not specify what to do in this case). Also it POSTs with an empty article to check that posts are allowed instead of reading it from the CAPABILITY response.I built this first to make a base for a mailing list bridge so in the future replying via SMTP/NNTP should both work
EDIT: forgot to mention, you can reply via NNTP by setting
set post_object "nntp"Well, it's not like I'm a great fan of slrn either (and not a great fan of s-lang in general); it's visibly burdened by a significant amount of obsolete features, standards, behaviors, configuration options and overall keeps quite a conservative approach, even at the cost of compromising usability. Nevertheless, it's the only command-line client I'm aware of which support NNTP over SSL, emacs + gnus aside, and that's my main reason for using it. I do most of my mailing / usenet posting remotely, on public shells (namely SDF), so mutt and slrn are tools I slowly became accustomed to, in lack of a better replacement.
Not really a replacement, but my (experimental) email client meli has basic NNTP (over tls) support. I think if it had users other than myself we could get some progress done on fully supporting NNTP. In fact I might implement POSTing now.
BTW I fixed some stuff which hopefully is still rfc3977 compliant and
slrnloads the articles faster, it seems.
I have been unable to load any posts in Hogwasher, despite
sic.allshowing 246 posts.Check for new news failed 9/5/21, 11:06 PM Error Code: 100211 Server: sic.pm Subscription: sic.all Newsgroup: sic.all The server returned bad data from the GROUP command. Try again later. --Maybe I should say: I am not tied to Hogwasher. I don't mind paying money for a good reader- (as opposed to downloader-)friendly NNTP client on MacOS.
Recommendations welcome. I used to use
tinandForté Agentback in the day, if it helps. I am too old and blind for a TUI these days, methinks.Thanks for the report. I have no idea what might be wrong, since the GROUP response the server sends seems correct to me. Then again this is a very young implementation and quirks haven't been ironed out yet.
Have you tried Thunderbird? I understand it has very good NNTP support!
Looks like posting from my Usenet client doesn't work.
I recommended tin, but missed your mention of it in my reader. I guess I'm too old and blind for a GUI these days myself ;)
I looked at the server logs and didn't see any POST commands; could your client be trying to reply via SMTP?
-
I tested following up by NNTP from Gnus, and ended up giving it up. Here's my running commentary:
I'm testing following-up from Gnus. I'm able to read via NNTP, though the only visible group is slc.all. I don't expect posting to work, because the followup buffer is missing a bunch of headers I would generally consider essential (like Newsgroup, References). But we'll see!
First try to send: Message-mode couldn't figure out how to send the message. It does automatically construct a References header now, so that's helpful. I'm adding the Newsgroup header to try again. Following-up to groups not on your primary NNTP server is not always easy in Gnus, so we'll see when I try to send.
Okay, that posting buffer didn't know it was responding to a newsgroup, and changing the headers didn't fix it? Creating a news posting buffer from scratch and copying over headers.
Nope.
Oh! The header is "Newsgroups". Guess it's been a while since I did much NNTP. Okay, now it tries to send via my default news server, which is not good... making it try harder.
(setq gnus-post-method (cons gnus-select-method gnus-secondary-select-methods)) C-u 0 C-c C-cNope, still no good.
Also, you may know this already, but your CSS is asking if the user prefers dark mode, but the dark theme it sends in that case isn't complete — new posts and preformatted text set their backgrounds without setting their foregrounds.
I'm afraid I don't understand most of this post. What buffers are you talking about?
The server supports the latest NNTP rfc which doesn't have any required headers other than Message-ID. You post a reply or a new article by sending a POST command while authenticated to the NNTP server itself, not another one.
Yeah, I think these are more or less all Gnus issues; the buffers in question are Emacs buffers. I think it would work fine if sic.pm was my primary/only NNTP server, but in fact, it's my third. I don't have trouble posting to my other secondary news server (news.orbitalfox.eu), though; Gnus figures out that it's supposed to post there, not my default. There must be something that's tripping Gnus up here, so that it doesn't know where to post, but I'm now at a loss to figure out what it is.
-
this is great!!
NNTP is the way of the future, i think.
Glad you got it working right, well done! I just tested it and can confirm it's working, saved a screenshot here.
I was able to to authenticate using my credentials and verified I was allowed to post. Attempting to follow up on threads resulted in slrn spawning mutt to reply, so I suppose reply-to is the standard method to post comments (via mail, through a smtp -> http gateway)?
I noticed it's a bit slow at getting headers, so being able to download articles to a local spool (e.g. via slrnpull) would be a good option, but I wonder if other users would be ok with that. Cheers!