Newsgroup: tilde.services

Back to Article List


Warning: Undefined array key 1 in /home/deepend/public_html/netnews/view_article.php on line 26

ant  wrote:
>The Free Thinker  wrote:
>>
>>There's also the frequent issue of Tin not wanting to send posts
>>unless it has a Fuly Qualified Domain Name for the computer it's
>>sending from.  The official line in the Tin documentation and
>>mailing list is effectively "No FQDN?  Well go and get one then!",  
>>which isn't terribly practical for most home users (though fine
>>if running Tin at tilde.club or another tilde).  Another solution,  
>>which I use,  is setting "disable_sender=ON" in the
>>/etc/tin/tin.defaults file.  
>
>I seems that setting HOST an arbitrary correct-looking FQDN
>also avoid the problem: tin starts without complains and
>and even posts:
>
>    $ HOST=neigh.say tin ...  
>
>Can you please test this on your side and confirm,  please?  

Well it seems my build of Tin 2.6.5 on my PCs doesn't care any more
whether there's "disable_sender=ON" set or not,  even with the HOST
variable unset (with "unset HOST" run to be sure) and Tin's
configuration reset to defaults.  Neither posting to here,  or to
Usenet from the Paganini server which doesn't require user
accounts.  

Tin certainly needed "disable_sender=ON" in the past,  so I'm
guessing this has been changed in a fairly recent version.  I
compiled Tin myself,  but it doesn't look like any of my build
settings would have affected this behaviour.  

>I never had a clear understanding why tin may need a working,  
>resolvable FQDN.   In this test,  I don't see my fake FQDN
>in any headers...  

I think the "Sender" header sent by Tin might be automatically
overriden by this news server?  Some Usenet servers don't seem to
set it themselves,  but they don't mind if it's missing.  The
standard seems to say it's optional (RFC5536 sect.  3.2 "Optional
Header Fields").  

Maybe it's an interpretation of RFC5537 sect.  3.10.1 "Duties of
an Outgoing Gateway":

  An incoming gateway MUST add a Sender header field to the news
  article it forms by containing the  of the administrator of
  the gateway.   Problems with the gateway may be reported to this
  .   The  portion of this  SHOULD
  indicate that the entity responsible for injection of the message is
  a gateway.   If the original message already had a Sender header
  field,  it SHOULD be renamed to Original-Sender so that its contents
  can be preserved.   See Section 3.10.3 for the specification of that
  header field.  

I don't think posting via NNTP should be considered using a gateway
though.  

The Paganini Usenet news server puts an apparantly-random string in
the "Sender" header.  Well for me now anyway,  I see it hasn't done
that for other users in the past.  

http://www.karlsruhe.org/rfc/rfc5536.txt
http://www.karlsruhe.org/rfc/rfc5537.txt
--

- The Free Thinker      |      gopher://aussies.space/1/%7efreet/