tin: Posing not allowed

[Anton Shepelev]

Hello, all
Can't get a (fully qualified) domain-name!
to STDERR at startup? Can it be the cause of it showing the following
*** Posing 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)
(posting ok)

Wrong newsgroup.

Folowup-To: news.software.readers,alt.comp.software.newsreaders

[Anton Shepelev]

Hello, all
Can't get a (fully qualified) domain-name!
to STDERR at startup? Can it be the cause of it showing the following
*** Posing 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)

*** Posting not allowed ***

[Urs Janßen]

Can't get a (fully qualified) domain-name!
to STDERR at startup? Can it be the cause of it showing the following
*** Posing 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)
(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.
[...]

[Anton Shepelev]

Post by Urs Janßen

Can't get a (fully qualified) domain-name!
to STDERR at startup? Can it be the cause of it showing the following
*** 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)
(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!

Post by Urs Janßen
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 ***

[Urs Janßen]

Post by Anton Shepelev
man pages. Also, it was by sheer luck that I even saw the message
Can't get a (fully qualified) domain-name!

Post by Urs Janßen
rtin -g <server>

It's printed before starting curses, so at leat it shall still be
visible after ending tin. Anyway I fixed the sleep(4) which got lost
and added a no posting hint to that message. With the next version
(2.6.4) there will be a connection info screen ('J') which will also
hold that info.

[Anton Shepelev]

Post by Urs Janßen

Post by Anton Shepelev
man pages. Also, it was by sheer luck that I even saw the message
Can't get a (fully qualified) domain-name!

Post by Urs Janßen
rtin -g <server>

It's printed before starting curses, so at leat it shall still be
visible after ending tin.

I use Tin from the "hardware" TTYs (Ctrl+Alt+F2-F8) with no back
scrolling. Upon exit from Tin, all I see is a blank screen with
the prompt at the bottom. This is why I kept missing this warning.

Post by Urs Janßen
Anyway I fixed the sleep(4) which got lost
and added a no posting hint to that message.

Thank you. I think that forcing the user to read the warning and
press Enter to continue would also be a good option for the those
with slow reactions, e.g.:

# Have user confirm warnings instead of auto-hiding them after
# a delay:
confirm_warnings=YES

Post by Urs Janßen
With the next version (2.6.4) there will be a connection info screen
('J') which will also hold that info.

That sounds useful, and I hope it will look so, too.

[Urs Janßen]

Post by Anton Shepelev
Thank you. I think that forcing the user to read the warning and
press Enter to continue would also be a good option for the those

| Can't get a (fully-qualified) domain-name!
| *** Posting not allowed ***

now stays for 4 secs. that should be enough for those who can't
either configure thier system (set a valid FQDN on the system or
at least HOSTNAME or $HOST) or tin (--with-domain-name).

[Anton Shepelev]

Post by Urs Janßen

Post by Anton Shepelev
Thank you. I think that forcing the user to read the warning and
press Enter to continue would also be a good option for the those

| Can't get a (fully-qualified) domain-name!
| *** Posting not allowed ***
now stays for 4 secs. that should be enough for those who can't
either configure thier system (set a valid FQDN on the system or
at least HOSTNAME or $HOST) or tin (--with-domain-name).

Yes, I think so. As for me, I set an /invalid/ (not pingable) FQDN,
to prevent Tin from... complaining. By the way, which is the preferred
spelling of the name in plain text: `tin', tin, or Tin?

[Urs Janßen]

Post by Anton Shepelev
to prevent Tin from... complaining. By the way, which is the preferred
spelling of the name in plain text: `tin', tin, or Tin?

As I'm not Iain Lea: *shrug* - I'd use tin.