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