headers
Javi Pardo | 3 Feb 2008 20:41

problem sending message to INN

I have big problem with INN
into log show this error : timeout short  and Outlook Express/windows 
mail show this message

RECEIVING

Su carpeta 'cotopaxi.publico.cafe_nocturno' no se sondeó para el 
recuento de elementos no leídos. Cuenta: 'Dakota Publicos', Servidor: 
'news.dakotabcn.net', Protocolo: NNTP, Puerto: 119, Seguridad (SSL): No, 
Número de error: 0x800CCC0F

Su carpeta 'cotopaxi.publico.cafe_nocturno.binarios' no se sondeó para 
el recuento de elementos no leídos. Cuenta: 'Dakota Publicos', Servidor: 
'news.dakotabcn.net', Protocolo: NNTP, Puerto: 119, Seguridad (SSL): No, 
Número de error: 0x800CCC0F

Su carpeta 'dakota.publico.amigos' no se sondeó para el recuento de 
elementos no leídos. Cuenta: 'Dakota Publicos', Servidor: 
'news.dakotabcn.net', Protocolo: NNTP, Puerto: 119, Seguridad (SSL): No, 
Número de error: 0x800CCC0F

No finalizó la descarga de encabezados de la carpeta 
'cotopaxi.publico.cafe_nocturno'. Cuenta: 'Dakota Publicos', Servidor: 
'news.dakotabcn.net', Protocolo: NNTP, Puerto: 119, Seguridad (SSL): No, 
Número de error: 0x800CCC0F

No finalizó la descarga de encabezados de la carpeta 
'cotopaxi.publico.cafe_nocturno.binarios'. Cuenta: 'Dakota Publicos', 
Servidor: 'news.dakotabcn.net', Protocolo: NNTP, Puerto: 119, Seguridad 
(SSL): No, Número de error: 0x800CCC0F
(Continue reading)

Permalink | Reply | 4 comments |
headers
Javi Pardo | 3 Feb 2008 23:13

Timeout Short Re: problem sending message to INN

hello!

in local network have the same error!!!

Feb  3 23:04:42 dakota nnrpd[10804]: portatil.dakotabcn.net timeout short
Feb  3 23:04:42 dakota nnrpd[10804]: portatil.dakotabcn.net times user 
0.000 system 0.000 idle 0.000 elapsed 12.535

i have changed in inn.conf

clienttimeout:          600
initialtimeout:         80   -> original 10
is possible the cause of timeout short this parameters?

regards

Javi Pardo escribió:
> I have big problem with INN
>
Permalink | Reply | 3 comments |
headers
Jeffrey M. Vinocur | 4 Feb 2008 02:22

Re: Timeout Short Re: problem sending message to INN

On Sun, 3 Feb 2008, Javi Pardo wrote:

> Feb  3 23:04:42 dakota nnrpd[10804]: portatil.dakotabcn.net timeout short

I'm not sure, but I think this is a problem with your client.

Can you try a different newsreader and see if you have the same issue?

> clienttimeout:          600
> initialtimeout:         80   -> original 10
> is possible the cause of timeout short this parameters?

This is related, but not the cause.

--

-- 
Jeffrey M. Vinocur
jeff <at> litech.org
Permalink | Reply | 2 comments |
headers
Javi Pardo | 4 Feb 2008 07:47

Re: Timeout Short Re: problem sending message to INN

the problem are gneral, not only 1-2 users, all users with diferente 
newsreaders have the same problem
is possible cause my isp?¿ all others protocols no have problem, only 
nntp protocol... :(

regards

Jeffrey M. Vinocur escribió:
> On Sun, 3 Feb 2008, Javi Pardo wrote:
>
>   
>> Feb  3 23:04:42 dakota nnrpd[10804]: portatil.dakotabcn.net timeout short
>>     
>
> I'm not sure, but I think this is a problem with your client.
>
> Can you try a different newsreader and see if you have the same issue?
>
>
>   
>> clienttimeout:          600
>> initialtimeout:         80   -> original 10
>> is possible the cause of timeout short this parameters?
>>     
>
> This is related, but not the cause.
>
>
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jeffrey M. Vinocur | 4 Feb 2008 13:30

Re: Timeout Short Re: problem sending message to INN

On Mon, 4 Feb 2008, Javi Pardo wrote:

> the problem are gneral, not only 1-2 users, all users with diferente 
> newsreaders have the same problem
> is possible cause my isp?¿ all others protocols no have problem, only 
> nntp protocol... :(

I doubt it's your ISP.

What happens if you try manually, then?  Telnet to port 119 of the news 
server, type DATE and press ENTER.  

--

-- 
Jeffrey M. Vinocur
jeff <at> litech.org
Permalink | Reply | 0 comments |
headers
David Hláčik | 4 Feb 2008 16:35
Picon
Favicon

newsgroups with mailinglist support

Hi to all , i am looking for a solution to provide :
News Groups (local) mirrored with mailinglists
Best solution i see is INN + mailman.

What i am looking for is some script which will make my life easier.

I want to be able to automatically create News Group with same Mailinglist
name .
I want to be able to have a user -based access to a particular news groups.

Thanks in advance!

David
Permalink | Reply | 1 comment |
headers
Kathryn Hemness | 4 Feb 2008 21:30
Picon

buffindexed: overview data too large

Greetings,

I've been running an inn 2.4.2 usenet news server on a Solaris 9
system since 2004 without any issues.  I'm using cnfs and buffindexed
for the article storage and the overview.

For a little over a week now, I've been seeing the following errors in
my news_daily logs:

Unknown entries from news log file:
First 7 / 7 lines (100.0%)
Feb  3 00:02:40 news innd: [ID 584949 news.error] buffindexed: overview data is
too large 12733

The ID is always 584949 (this isn't a PID and couldn't find it in any the
other logs).

I've plenty of space for my overview.

Overview Buffer usage (inndf -o and inndf -n) :
12% overview space used
6731696 overview records stored

Can someone tell me what the error means and if there are any configuration
changes I can make so that innd will stop complaining.

Any help is greatly appreciated.

--Kathy
(Continue reading)

Permalink | Reply | 0 comments |
headers
Russ Allbery | 5 Feb 2008 19:58
Picon
Favicon
Gravatar

INN maintenance and facing reality

I really should have sent this message about a year ago, but I kept hoping
I would discover more free time.  However, this is looking increasingly
unlikely.

As everyone has noticed, there has not been a new release of INN in quite
some time, and I have not been doing any active development.  Due to a
combination of significantly load in my paying job (that isn't related to
Usenet) and other volunteer work, I've had essentially no time to work on
INN for quite a while now.  It doesn't look like this is going to change
in the near future.  As a result, I'm really not doing INN justice.  At a
minimum, a new INN STABLE release is overdue and INN 2.5 probably should
just be released as-is without all the other things that I wanted to put
in it.

Realistically, I don't have the time to continue as lead maintainer or
release manager, and haven't been filling either role for quite some time.
If someone else is willing to pick up the release management role, please
speak up.  I'm happy to help as I can find the time and will try to make
time to do a clean handoff.  I'm also happy to continue to provide
infrastructure, or ISC I'm sure is also willing to do so.

I'm hopefully not disappearing entirely, and I will continue to try to
comment on the list and do things for INN when I can, but I'll feel less
guilty and more realistic if I don't expect myself to maintain the level
of contribution that I have in the past.

Peter, please let whoever needs to know at ISC about this as well.

--

-- 
Russ Allbery (rra <at> stanford.edu)             <http://www.eyrie.org/~eagle/>
(Continue reading)

Permalink | Reply | 627 comments |
headers
Katsuhiro Kondou | 5 Feb 2008 22:31

Re: INN maintenance and facing reality

In article <87bq6v1b90.fsf <at> windlord.stanford.edu>,
	Russ Allbery <rra <at> stanford.edu> wrote,
	on "Tue, 05 Feb 2008 10:58:19 -0800";

} Realistically, I don't have the time to continue as lead maintainer or
} release manager, and haven't been filling either role for quite some time.

I have been at the same standpoint like Russ for over years
since I left my previous job.  I know not a few queries related
to buffindexed which I originally wrote were seen on the list,
but actually I did not have enough time to spare for that.
--

-- 
Katsuhiro Kondou
Permalink | Reply | 0 comments |
headers
Julien ÉLIE | 6 Feb 2008 00:02
Favicon

Re: INN maintenance and facing reality

Hi Russ,

> I really should have sent this message about a year ago

Do not worry about that.

> INN 2.5 probably should just be released as-is without all the
> other things that I wanted to put in it.

Would it be possible to wait a little for that, at least until
some pending stuff has been stabilized?  For instance, correctly handling
checkgroups (updating the active and the newsgroups files accordingly,
if wanted) and allowing to specify the encoding of the newsgroups
file, as we already discussed here.  It would need some new options
to control.ctl, as well as a control.ctl.local file.  Therefore, if
INN 2.5 is not shipped with that, we would have to wait for INN 2.6,
wouldn't we?  Regarding internationalization, it is not very good...

The SSL implementation within nnrpd should also be looked at because
it is broken with Thunderbird and it is very annoying.  See
<https://bugzilla.mozilla.org/show_bug.cgi?id=247226> for more details.
Fortunately, there is a patch from Kachun Lee which could be applied
but it is not a perfect solution.

There are probably other things to check.  But it is up to the release
manager to decide what he wishes to wait for.

I also have more work to do on documentation but I assume it can be
done after.  I also have to provide documentation about the setting up
of a UUCP feed, which we managed to do with Jeffrey some time ago.
(Continue reading)

Permalink | Reply | 5 comments |

Gmane