-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Mark,

let me summarize/clarify the problem before the chaos wins:

IMO the code in nntpd.c around line 1200 causes a problem:

            if (!havepath) {
                if (fputs("Path: ", out) == EOF)
                    err = 1;
                if (fputs(fqdn, out) == EOF)
                    err = 1;
                if (fprintf(out, "!%s\r\n", NEWS_USER) < 0)
                    err = 1;
            }

and should be replaced by

            if (!havepath) {
                if (fprintf(out, "Path: %s!not-for-mail\r\n", fqdn) < 0)
                    err = 1;
            }

or alternatively (if leafnode is considered as a client):

            if (!havepath) {
                if (fputs("Path: not-for-mail\r\n", out) == EOF)
                    err = 1;
            }

Explantation:

1. the value of the "hostname" configuration variable must not contain
the fqdn of the upstream news-server. If it does, the article is
accepted by the upstream news-server and available on it -- but not
delivered further because of a duplicate entry in the Path header. =>
"hostname" should contain a resolvable fqdn of the client.

2. Message-IDs are in no case a problem. Leafnode uses the STAT comment
in order to check if an article with an identical Message-ID exists.
Example (real chat recorded with wireshark after executing "fetchnews -P"):

GROUP de.test
211 29017 19807 48857 de.test selected
STAT <[EMAIL PROTECTED]>
430 no such article found
POST
340 Ok, recommended ID <[EMAIL PROTECTED]>
[clients sends data]

The only constraint is that the string after @ is a resolvable domain name.

3. Articles with a Path header containing "news" as a suffix are
rejected by the news-servers upstream to my news-server
news.uni-siegen.de. I made four tests:

a.) hostname=news.uni-siegen.de: Path: not-for-mail
    => success
b.) hostname=pc228.simtec.mb.uni-siegen.de, Path: not-for-mail
    => success
c.) hostname=pc228.simtec.mb.uni-siegen.de,
    Path: pc228.simtec.mb.uni-siegen.de!news
    (equivalent to the unpatched nntpd.c)
    => no success
d.) hostname=news.uni-siegen.de, Path: news.uni-siegen.de!news
    => no success

Furthermore two tests using Path: [fqdn]!not-for-mail

e.) hostname=news.uni-siegen.de
    Path: news.uni-siegen.de!not-for-mail
    => no success
f.) hostname=pc228.simtec.mb.uni-siegen.de
    Path: pc228.simtec.mb.uni-siegen.de!not-for-mail
    => success

success := article successfully delivered and available in the usenet
        I get several answers from these autoresponder-scripts listening
        to de.test.
no success := article successfully delivered but only available on my
        upstream news-server news.uni-siegen.de

Cheers,
- --
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHiJSt2AeXPDkfIYIRArc9AJ9fypU71+49zrIAzfAEqfVHVqe8JQCfSAxb
C7qX9CBPm3OH8KOkGoLa6p4=
=pdVd
-----END PGP SIGNATURE-----



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to