Path: ...!news.mixmin.net!news2.arglkargh.de!news.in-chemnitz.de!3.eu.feeder.erje.net!feeder.erje.net!newsfeed.bofh.team!paganini.bofh.team!not-for-mail
From: Anton Shepelev <ant@tilde.culb>
Newsgroups: news.software.readers
Subject: Re: tin: Posing not allowed
Date: Thu, 19 Sep 2024 11:58:23 -0000 (UTC)
Organization: To protect and to server
Sender: 9dIQLXBM7WM9KzA+yjdR4A
Message-ID: <vch3kv$1akke$1@paganini.bofh.team>
References: <vcf40t$12gum$1@paganini.bofh.team> <vcf495$12gum$2@paganini.bofh.team> <vcf7on$905$1@nntp.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 19 Sep 2024 11:58:23 -0000 (UTC)
Injection-Info: paganini.bofh.team; logging-data="1397390"; posting-host="RuGtXskjILadxbC+FS6/9w.user.paganini.bofh.team"; mail-complaints-to="usenet@bofh.team"; posting-account="9dIQLXBM7WM9KzA+yjdR4A";
User-Agent: tin/2.6.3-20231224 ("Banff") (FreeBSD/14.1-RELEASE (amd64))
X-Notice: Filtered by postfilter v. 0.9.3
Bytes: 2735
Lines: 42

In news.software.readers Urs Janßen <urs@buil.tin.org> wrote:
> Anton Shepelev wrote:
>>> Why can `tin' be printing:
>>> 
>>>   Can't get a (fully qualified) domain-name!
>>> 
>>> to STDERR at startup? Can it be the cause of it showing the following
>>> message:
>>> 
>>>  *** Posting not allowed ***
>>> 
>>> at the bottom of the screen every time I press `w' to
>>> post an article to any newsgroup on any server (anonymous or not)
>>> even though at startup tin wrote:
>>> 
>>>   (posting ok)
> 
> [<http://bzr.tin.org/README>]
> [...]
> | Note that tin requires a valid fully qualified domain name for the host
> | you are running tin on. IF YOU DON'T HAVE A HOST NAME WITH A VALID DOMAIN
> | GO AND GET ONE AND CONFIGURE YOUR HOST -- NOW! (This will prevent problems
> ! with other software, too.) Otherwise users may get "Invalid Sender" error
> ! messages and won't be able to post using the internal inews.

Thank you.  I searched both the man pages, but neglected the README.
I think such an important requirement should be documented in the 
man pages.  Also, it was by sheer luck that I even saw the message

   Can't get a (fully qualified) domain-name!

because it does not appear if I start tin the usual way, e.g.:

   >rtin -g <server>

And only when I decided to compare the version of tin between
machines with and without this problem, did I notice it; and it is
not at all obvious that the "Posting not allowed" message inside
tin is caused by the absnece of an FQDN.  Can you please make the
startup message more conspicuous, and/or imporove the other message,
e.g. thus:

   *** Cannot post: no FQDN configured ***