-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Mark,
Mark Brown wrote:
>> optimal solution (if possible, the suggestion of the news-server should
>> be chosen -- tin seems to work like this).
>
> Could you clarify what you mean by the "the suggestion of the
> news-server", please? Also note that Leafnode may be posting the
> article to multiple upstream servers.
here is some nntp-chat done by DNEWS @ news.uni-siegen.de and tin
(recorded with wireshark):
===
- -> POST
<- 340 Ok, recommended ID <[EMAIL PROTECTED]>
- -> Path: not-for-mail
- -> Message-ID: <[EMAIL PROTECTED]>
- -> From: Michael Weitzel <[EMAIL PROTECTED]>
- -> Subject: test123-8
- -> Newsgroups: de.test
- -> Summary: ignore
- -> Keywords: ignore
- -> User-Agent: tin/1.9.2-20070201 ("Dalaruan") (UNIX) (Linux/2.6.22.1
(i686))
->
- -> testing
- -> --
- -> Michael
- -> .
<- 240 article posted ok
===
Tin adopts the Message-Id suggested by the news-server in the second line.
>
>> However, the header line "Path: <nntp-server-fqdn>!news" causes a
>> problem with the news-servers lying upstream to my provider's news-server
>> and my articles are rejected. I figured out, that the entry "news" is
>> responsible for this and I suggest to use "Path: not-for-mail" in
>
> Could you please explain what it is leads you to believe that this is
> the case? You have provided none of the analysis that either shows the
> problem occurring or explains how the changes you suggest would help
> which makes it difficult to understand your report.
>
> I note that looking at a portion of my news spool it seems that if a
> trailing !news in a Path: were causing problems then something around
> 10% of articles in some groups would experience problems.
I made several tests with different Path: headers and Message-IDs.
Depending on the contents of the Path: header my articles are delivered
or get lost. The news-server responsible for blocking my articles seems
to be news-fra1.dfn.de (the uplink of news.uni-siegen.de). Maybe this
server uses a strict/strange configuration.
Since I have no chance to look into logfiles/configuration of
news-fra1.dfn.de, there is nothing more I can do except testing the
"black box".
>
>> general, since leafnode should (IMO) behave like a news-client, not like
>> a server.
>
> Leafnode is in a very real sense a server to its clients and the
> direction of development is very much towards adding more server
> facilities - for example, development versions support both local groups
> and instantaneous local posting of articles.
>
> Do you experience any problems if you configure the FQDN used by
> Leafnode to be something other than the FQDN of the upstream news server
> you are using?
No. In fact I used a different official fqdn before. I just observed
that posting with tin creates Message-IDs containing the fqdn of the
server (I realized later that these IDs were suggested by the server).
> It is difficult to tell what is happening but based on
> the information you have provided I would guess that what is happening
> is that either the upstream server you are using is rejecting your posts
> or it is also inserting its FQDN into the path, leading to a duplicate
> path entry which causes some other servers to drop the article as
> malformed.
>
In tests where I used "news.uni-siegen.de!not-for-mail" as Path: header
my news-server news.uni-siegen.de (running DNEWS) handled the duplicate
entry "news.uni-siegen.de". In any case, my articles were accepted and
available on news.uni-siegen.de (I connected directly using tin).
Please note that tin uses "not-for-mail" in the above trace.
IMO, in case leafnode behaves like a real news-server the contents of
the Path header sould be resolvable, official fqdns. The entry
"not-for-mail" seems to be a reserved identifier. However, I'm not
really competent here, since I don't know the RFCs in detail.
Thanks & Cheers,
- --
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHhfuK2AeXPDkfIYIRAoKWAJ9vEajWGTFISt70pC31L8g6C5e7xgCeKiMw
GTkYzhJwKYZyDyE5B7gxs30=
=bJ55
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
