Here is how to poll messages from one nntp server to another using inn2:

Select a non-root user to use for this part:

Create a file in this user's home directory called '.pullnews' containing:

# Format: (date is epoch seconds)
# hostname [username password]
#         group date high
192.168.0.220 <username> <password>
         rocksolid.admin.admin
         rocksolid.shared.dancingelephants
         rocksolid.shared.entertainment
         rocksolid.shared.freenet
         rocksolid.shared.general
         rocksolid.shared.helpdesk
         rocksolid.shared.i2p
         rocksolid.shared.news
         rocksolid.shared.offtopic
         rocksolid.shared.retrobbs
         rocksolid.shared.test
         rocksolid.shared.tor

username and password are the ones assigned to you when joining the network. Don't use your own personal username/password from any rocksolid forums as that won't work, you will be assigned a specific user/pass just to sync with the nntp server.

To pull DOVE-Net forums, add:
         DOVE-Net.Advertisements
         DOVE-Net.Entertainment
         DOVE-Net.General
         DOVE-Net.HAM_Radio
         DOVE-Net.Hobbies
         DOVE-Net.Internet
         DOVE-Net.Programming
         DOVE-Net.Religion
         DOVE-Net.Synchronet_Discussion

For Freenet (FMS) add:
boards 0 0
         censorship
         fms
         freedom
         freenet
         news
         politics
         privacy
         programming
         public
         security
         shared.test
         sites
         test

For every board you want to sync, you must add it to your inn2 installation:

As root: 'ctlinnd newgroup <name.of.group>

Now, add to crontab of the user you used for pullnews:

*/5 * * * * /usr/lib/news/bin/pullnews

This will poll the remote server every 5 minutes. Please don't poll a server any more often than that, it can create an unnecessary load on someone else's server.

This will pull messages from the other server to yours. To get your messages out to another server, they must poll you.

Retro Guy

On 09/06/2017 01:53 AM, Retro Guy wrote:

Here is how to poll messages from one nntp server to another using inn2:
...
For Freenet (FMS) add:
boards 0 0
        censorship
        fms
        freedom
        freenet
        news
        politics
        privacy
        programming
        public
        security
        shared.test
        sites
        test

I'm tired, so I didn't double check my post. The section above should look like:

For Freenet (FMS) add:
boards
         censorship
         fms
         freedom
         freenet
         news
         politics
         privacy
         programming
         public
         security
         shared.test
         sites
         test

pullnews will add info to the right of each board name after each poll (date and msg number). Don't change these or remove these as this will interfere with the next poll.

Retro Guy

On 09/06/2017 01:53 AM, Retro Guy wrote:

Here is how to poll messages from one nntp server to another using inn2:

Select a non-root user to use for this part:

Create a file in this user's home directory called '.pullnews' containing:

# Format: (date is epoch seconds)
# hostname [username password]
#         group date high
192.168.0.220 <username> <password>
        rocksolid.admin.admin
        rocksolid.shared.dancingelephants
        rocksolid.shared.entertainment
        rocksolid.shared.freenet
        rocksolid.shared.general
        rocksolid.shared.helpdesk
        rocksolid.shared.i2p
        rocksolid.shared.news
        rocksolid.shared.offtopic
        rocksolid.shared.retrobbs
        rocksolid.shared.test
        rocksolid.shared.tor

username and password are the ones assigned to you when joining the
network. Don't use your own personal username/password from any
rocksolid forums as that won't work, you will be assigned a specific
user/pass just to sync with the nntp server.

To pull DOVE-Net forums, add:
        DOVE-Net.Advertisements
        DOVE-Net.Entertainment
        DOVE-Net.General
        DOVE-Net.HAM_Radio
        DOVE-Net.Hobbies
        DOVE-Net.Internet
        DOVE-Net.Programming
        DOVE-Net.Religion
        DOVE-Net.Synchronet_Discussion

For Freenet (FMS) add:
boards 0 0
        censorship
        fms
        freedom
        freenet
        news
        politics
        privacy
        programming
        public
        security
        shared.test
        sites
        test

For every board you want to sync, you must add it to your inn2
installation:

As root: 'ctlinnd newgroup <name.of.group>

Now, add to crontab of the user you used for pullnews:

*/5 * * * * /usr/lib/news/bin/pullnews

This will poll the remote server every 5 minutes. Please don't poll a
server any more often than that, it can create an unnecessary load on
someone else's server.

This will pull messages from the other server to yours. To get your
messages out to another server, they must poll you.

Retro Guy

Oops, replace the '192.168.0.220' with the address of the server you are connecting to. If the port is not 119 then, for example, other.server:2119.

Retro Guy

Everything works so far, but the result is:
-------------------------------------------------------------------------------
/usr/lib/news/bin/pullnews
Fri Sep  8 09:36:14 2017 start

Connecting to downstream host: localhost port: 119 ...done.

Legend: ``.'' is an article the downstream server refused
        ``*'' is an article the downstream server rejected
        ``+'' is an article the downstream server accepted
        ``x'' is an article the upstream server couldn't give out
        ``m'' is an article skipped due to headers (-m or -P)


Saving config

0 articles were offered to server on localhost

Done Fri Sep  8 09:36:14 2017
----------------------------------------------------------------
It seems like pullnews is doing something, but inn2 does not connect further.
Posted by:anonymous <anonymous@def.i2p>

Everything works so far, but the result is:
-------------------------------------------------------------------------------
/usr/lib/news/bin/pullnews
Fri Sep  8 09:36:14 2017 start

Connecting to downstream host: localhost port: 119 ...done.

Legend: ``.'' is an article the downstream server refused
        ``*'' is an article the downstream server rejected
        ``+'' is an article the downstream server accepted
        ``x'' is an article the upstream server couldn't give out
        ``m'' is an article skipped due to headers (-m or -P)


Saving config

0 articles were offered to server on localhost

Done Fri Sep  8 09:36:14 2017
----------------------------------------------------------------
It seems like pullnews is doing something, but inn2 does not connect further.
Posted by:anonymous <anonymous@def.i2p>

On 09/08/2017 02:50 AM, anonymous wrote:

Everything works so far, but the result is:
-------------------------------------------------------------------------------

/usr/lib/news/bin/pullnews
Fri Sep  8 09:36:14 2017 start

Connecting to downstream host: localhost port: 119 ...done.

Legend: ``.'' is an article the downstream server refused
       ``*'' is an article the downstream server rejected
       ``+'' is an article the downstream server accepted
       ``x'' is an article the upstream server couldn't give out
       ``m'' is an article skipped due to headers (-m or -P)


Saving config

0 articles were offered to server on localhost

Done Fri Sep  8 09:36:14 2017
----------------------------------------------------------------
It seems like pullnews is doing something, but inn2 does not connect
further.
Posted by:anonymous <anonymous@def.i2p>

It should say:

connecting to upstream server example.com...done.

right after it displays the legend.

Did you list a server in .pullnews?

<servername:port> <username> <password>
list
of
groups

Retro Guy

On 09/08/2017 03:25 AM, Retro Guy wrote:

On 09/08/2017 02:50 AM, anonymous wrote:

Everything works so far, but the result is:
-------------------------------------------------------------------------------


/usr/lib/news/bin/pullnews
Fri Sep  8 09:36:14 2017 start

Connecting to downstream host: localhost port: 119 ...done.

Legend: ``.'' is an article the downstream server refused
       ``*'' is an article the downstream server rejected
       ``+'' is an article the downstream server accepted
       ``x'' is an article the upstream server couldn't give out
       ``m'' is an article skipped due to headers (-m or -P)


Saving config

0 articles were offered to server on localhost

Done Fri Sep  8 09:36:14 2017
----------------------------------------------------------------
It seems like pullnews is doing something, but inn2 does not connect
further.
Posted by:anonymous <anonymous@def.i2p>

It should say:

connecting to upstream server example.com...done.

right after it displays the legend.

Did you list a server in .pullnews?

<servername:port> <username> <password>
    list
    of
    groups

Retro Guy

The file '.pullnews' (note the dot) should be in a user's home directory.

..pullnews should contain:

<servername:port> <username> <password>
         rocksolid.admin.admin
         rocksolid.shared.dancingelephants
         rocksolid.shared.entertainment
         rocksolid.shared.freenet
         rocksolid.shared.general
         rocksolid.shared.helpdesk
         rocksolid.shared.i2p
         rocksolid.shared.news
         rocksolid.shared.offtopic
         rocksolid.shared.retrobbs
         rocksolid.shared.test
         rocksolid.shared.tor

Then run pullnews as the same user that has .pullnews in their home dir.

You can test username:port with Thunderbird (which I think you are doing) just to make sure it is accessible.

Also, there are no '<' '>' in the actual .pullnews file, just the info.

Retro Guy

On 09/08/2017 03:30 AM, Retro Guy wrote:

On 09/08/2017 03:25 AM, Retro Guy wrote:

On 09/08/2017 02:50 AM, anonymous wrote:

Everything works so far, but the result is:
-------------------------------------------------------------------------------



/usr/lib/news/bin/pullnews
Fri Sep  8 09:36:14 2017 start

Connecting to downstream host: localhost port: 119 ...done.

Legend: ``.'' is an article the downstream server refused
       ``*'' is an article the downstream server rejected
       ``+'' is an article the downstream server accepted
       ``x'' is an article the upstream server couldn't give out
       ``m'' is an article skipped due to headers (-m or -P)


Saving config

0 articles were offered to server on localhost

Done Fri Sep  8 09:36:14 2017
----------------------------------------------------------------
It seems like pullnews is doing something, but inn2 does not connect
further.
Posted by:anonymous <anonymous@def.i2p>

It should say:

connecting to upstream server example.com...done.

right after it displays the legend.

Did you list a server in .pullnews?

<servername:port> <username> <password>
    list
    of
    groups

Retro Guy

The file '.pullnews' (note the dot) should be in a user's home directory.

.pullnews should contain:

<servername:port> <username> <password>
        rocksolid.admin.admin
        rocksolid.shared.dancingelephants
        rocksolid.shared.entertainment
        rocksolid.shared.freenet
        rocksolid.shared.general
        rocksolid.shared.helpdesk
        rocksolid.shared.i2p
        rocksolid.shared.news
        rocksolid.shared.offtopic
        rocksolid.shared.retrobbs
        rocksolid.shared.test
        rocksolid.shared.tor

Then run pullnews as the same user that has .pullnews in their home dir.

You can test username:port with Thunderbird (which I think you are
doing) just to make sure it is accessible.

Also, there are no '<' '>' in the actual .pullnews file, just the info.

Retro Guy

The server you need to connect to is the inn server here:

cm6lpd....3hcq.b32.i2p

Which is the address I previously sent by mail.

Retro Guy

Pullnews is there, the file is with the dot, and the server is accessible. The commandline is run by the user who owns the file.
This is the pullnews file:

# Format: (date is epoch seconds)
# hostname [username password]
#         group date high
ipaddressofi2ptunnel:portnumber username password
rocksolid.shared.test

inn2 does connect to the i2p tunnel, I can see that. It just does not get any messages from the server (in contrast to Thunderbird, which works with the same credentials). Strange...
Posted by:anonymous <anonymous@def.i2p>

I can connect from the same box to your inn server via telnet, so the connection as such works. I cannot authenticat to the server, but that might be due to telnet (I always get a 502). But anyway, the connection is there, and if I use Thunderbird, I can connect and authenticate just fine. Just my inn2 cannot do it.
Do I need to edit some settings beyond readers.conf,.pullnews and inn2.conf ?

Regards

wed
Posted by:anonymous <anonymous@def.i2p>

On 09/08/2017 01:29 PM, anonymous wrote:

I can connect from the same box to your inn server via telnet, so the
connection as such works. I cannot authenticat to the server, but that
might be due to telnet (I always get a 502). But anyway, the connection
is there, and if I use Thunderbird, I can connect and authenticate just
fine. Just my inn2 cannot do it.
Do I need to edit some settings beyond readers.conf,.pullnews and
inn2.conf ?

Regards

wed
Posted by:anonymous <anonymous@def.i2p>

I just modified the i2p tunnel to try to avoid inn2 thinking you're connecting from 127.0.0.1. Don't know if that will help, but we'll see.

I also just sent you a different user/pass via email.

Retro Guy

oh man, finally I figured out why pullnews was not working before. It is so stupid. The manual for pullnews can be found here: https://www.eyrie.org/~eagle/software/inn/docs-2.5/pullnews.html

And it says: --------------------------
 The full syntax is:

    <host> [<username> <password>]
            <group> [<time> <high>]
            <group> [<time> <high>]

where the <host> line must not have leading whitespace and the <group> lines must. --------------------------
Whitespace. Fuck. Otherwise the line is not recognized.
Posted on def.i2p

ok, working now. RTFM. RTFM. Fuck.
Posted on def.i2p