noffle-users

Re[4]: [Noffle-users] fetch and import questions..

[Michal <mi...@hu...>]

Hello Jim,


JH> When you say 'multiserver-capable', I presume you mean 'able to fetch news for
JH> the same group from multiple servers'

yes, this and user authorisation are two most needed features in
Noffle (IMHO)

JH>  I must get round to
JH> implementing the former for Noffle.

would be fantastic, please, please do :-)


P.S.
I'm reposting this because I've had a problem with posting that
before... so I'm sorry, if you get it twice.


-- 
Best regards,
 michal

Re: [Noffle-users] noffle&pan

[Jim H. <jim...@ac...>]

On 24-Feb-2003 Tomislav Ivan Flis wrote:
>> Since you already have an entry for noffle in your /etc/hosts.deny, I
>> suggest that you simple remove the 'localhost' line from /etc/hosts.allow,
>> and leave it blank except for comments.
>>
>> Let's see if that works...
> 
> I tried it and it's the same :
> [root@localhost tompa]# telnet localhost nntp
> Trying 127.0.0.1...
> Connected to localhost.localdomain (127.0.0.1).
> Escape character is '^]'.
> Connection closed by foreign host.

Is there anything in the log files about hosts.deny or hosts.allow?

-- 
Jim Hague - jim...@in... (Work), ji...@be... (Play)
Never trust a computer you can't lift or you don't control.

Re: [Noffle-users] Pan

[Mirko L. <mir...@we...>]

Tomislav Ivan Flis wrote:
> I'm trying to use noffle but I ran into troubles. Im a newbie conserning Linux
> 
> I can fetch froups and posts, but my newsreader don't see them. Why? How to 
> fix that?

I'm not convinced that you are able to fetch groups from your
/etc/ppp/ip-up file like that.


> ip-up:
> 
> #!/bin/bash
> # This file should not be modified -- make local changes to
> # /etc/ppp/ip-up.local instead
> 
> PATH=/sbin:/usr/sbin:/bin:/usr/bin
> export PATH
> 
> LOGDEVICE=$6
> REALDEVICE=$1
> /usr/bin/noffle --fetch
> /usr/bin/noffle --online

You are starting noffle too early. Your computer still doesn't know
about the names of other computers. It has yet to know how to use the
domain name service (aka dns) to resolve names like 'news.example.org'
to a numeric address like '127.0.0.1'. The necessary steps are already
present in your ip-up file:

[..snip..]
> if [ -n "$PPP_TEMP_ENTRY" ]; then
>     [ -n "$DNS1" ] && \
> 	echo -e "nameserver $DNS1 $PPP_TEMP_ENTRY" >> /etc/resolv.conf
>     [ -n "$DNS2" ] && \
> 	echo -e "nameserver $DNS2 $PPP_TEMP_ENTRY" >> /etc/resolv.conf
> fi

Why don't you start 'noffle --fetch' from the file /etc/ppp/ip-up.local
like your distribution suggests? Just make sure that /etc/ppp/ip-up.local
has the same owner.group and the same rwx-permissions as /etc/ppp/ip-up.


regards,

Mirko

Re: [Noffle-users] noffle&pan

[Mirko L. <mir...@we...>]

Jim Hague wrote:
> On 23-Feb-2003 Tomislav Ivan Flis wrote:
> ># hosts.deny    This file describes the names of the hosts which are
> >#               *not* allowed to use the local INET services, as decided
> >#               by the '/usr/sbin/tcpd' server.
> >#
> ># The portmap line is redundant, but it is left to remind you that
> ># the new secure portmap uses hosts.deny and hosts.allow.  In particular
> ># you should know that NFS uses portmap!
> > 
> > 
> > noffle: ALL EXCEPT LOCAL
> > 
> > Is the ptopblem maybe in that?
> 
> No, that's fine. It's just saying 'prohibit access to Noffle from all hosts
> *except* localhost'. So 'telnet localhost nntp' should work.

It prohibits access to Noffle from all hosts except those from the same
domain, aka hosts whichout any dots in them. Possibly, that may be
exploited. Better be paranoid and replace the line in /etc/hosts.deny
with:

    noffle: ALL EXCEPT localhost

Further details via 'man 5 hosts_access'.


Sorry for the delay, there's still a lot of work waiting for me.

Mirko

Re: [Noffle-users] noffle&pan

[Jim H. <jim...@ac...>]

On 24-Feb-2003 Tomislav Ivan Flis wrote:
> On Monday 24 February 2003 10:23, you wrote:
>> On 23-Feb-2003 Tomislav Ivan Flis wrote:
>> > YES, I was running xinetd
>>
>> OK, good.
> 
> so it's nota a problem?

Not a problem. Well, it shouldn't be. Noffle definitely works properly with
xinetd. But I don't use xinetd on any of my systems, so I'm not as familiar
with it as I might be. So please be patient; I'm groping my way here. :-)

> Feb 24 17:50:59 localhost xinetd[2243]: warning: /etc/hosts.allow, line 6: 
> missing newline or line too long
> Feb 24 17:50:59 localhost xinetd[2243]: libwrap refused connection to nntp 
> from 127.0.0.1

Ah! This looks a clue as to what exactly is causing the problem. libwrap is the
code that implements the 'hosts.allow' and 'hosts.deny' functionality. So it
looks like xinetd is configured properly, and we need to inspect these.

The first warning looks like it thinks something is wrong with
/etc/hosts.allow. I wonder if that it causing the problem.

'man 5 hosts_access' for the details of what you can put in those files.

Your /etc/hosts.allow file looks a bit suspect to me. I think the line saying
just

localhost

is wrong. The format for hosts.allow is 'daemon name: client_list', e.g.

noffle: localhost

Since you already have an entry for noffle in your /etc/hosts.deny, I suggest
that you simple remove the 'localhost' line from /etc/hosts.allow, and leave it
blank except for comments.

Let's see if that works...

-- 
Jim Hague - jim...@in... (Work), ji...@be... (Play)
Never trust a computer you can't lift.

Re: Re[2]: [Noffle-users] fetch and import questions..

[Jim H. <jim...@ac...>]

On 24-Feb-2003 Michal wrote:
> JH> Are you trying to use an external fetcher simply to import the archives,
> or do
> JH> you have fetching requirements that Noffle can't handle?
> 
> I tried to kill two bird with one stone, importing archives is the first,
> and external fetcher, like newsstar or msuck (IIRC the name) lets me
> make Noffle multiserwer-capable...

When you say 'multiserver-capable', I presume you mean 'able to fetch news for
the same group from multiple servers' rather than 'fetch different groups from
different servers', which Noffle can already do. I must get round to
implementing the former for Noffle.

-- 
Jim Hague - jim...@in... (Work), ji...@be... (Play)
Never trust a computer you can't lift.

Re: [Noffle-users] noffle&pan

[Jim H. <jim...@ac...>]

On 23-Feb-2003 Tomislav Ivan Flis wrote:
> YES, I was running xinetd

OK, good.

> I did that and I restarted xinetd with: /etc/init.d/xinetd restart
> 
> when I try next:
> [root@localhost xinetd.d]# /etc/init.d/xinetd restart
> Stopping xinetd:                                                [ OK ]
> Starting xinetd:                                                [  OK  ]
> [root@localhost xinetd.d]# telnet localhost nntp
> Trying 127.0.0.1...
> Connected to localhost.localdomain (127.0.0.1).
> Escape character is '^]'.
> Connection closed by foreign host.

Oops. I've just noticed this line in what I sent you to put in
/etc/xinetd.d/noffle:

>         disable         = yes

Make that 'disable = no', restart xinetd.d and see if that works. Don't forget
to see if there are any messages in /var/log/messages if it doesn't.

-- 
Jim Hague - jim...@in... (Work), ji...@be... (Play)
Never trust a computer you can't lift.

Re[2]: [Noffle-users] fetch and import questions..

[Michal <mi...@hu...>]

Hello Jim,

Sunday, February 23, 2003, 9:12:36 PM, you wrote:

JH> Are you trying to use an external fetcher simply to import the archives, or do
JH> you have fetching requirements that Noffle can't handle?

I tried to kill two bird with one stone, importing archives is the first,
and external fetcher, like newsstar or msuck (IIRC the name) lets me
make Noffle multiserwer-capable...

JH> You can post an article from the command line with the '--post' option, or by
JH> invoking Noffle as 'inews'.

Running noffle as inews works fine, thanks for that tip.
Now I have to do some scripting... :-)


-- 
Best regards,
 Michal                            

Re: [Noffle-users] groups without any dots in the name don't show up

[Jim H. <jim...@ac...>]

On 23-Feb-2003 Miernik wrote:
> It's probably uncommon to have groups without any dot in the name, but 
> here is an example:
> 
> miernik@tarnica:~$ telnet news.linuxfromscratch.org 119
> Trying 66.11.168.23...
> Connected to linuxfromscratch.org.
> Escape character is '^]'.
> 200 quasar.highos.com InterNetNews NNRP server INN 2.3.3 ready (posting ok).
> list active
> 215 Newsgroups in form "group high low flags".
> control 0000000000 0000000001 n
> control.cancel 0000000045 0000000045 n
> control.checkgroups 0000000000 0000000001 n
> control.newgroup 0000000000 0000000001 n
> control.rmgroup 0000000000 0000000001 n
> junk 0000000000 0000000001 n

All these groups are INN 'internal use' groups.

> cgroup 0000000138 0000000138 y

Not sure about this one.

> links-list 0000002462 0000002445 y

Or this, but it looks possibly legitimate. Re-reading the relevant section of
the latest version of the IEFT draft intended to replace RFC1036, it says:

5.5.1.  Forbidden newsgroup-names
                                                                                
   The following forms of newsgroup-name MUST NOT be used except for the
   specific purposes indicated:
                                                                                
     o Newsgroup-names having only one component. These are reserved for
       newsgroups whose propagation is restricted to a single host or
       local network, and for pseudo-newsgroups such as "poster" (which
       has special meaning in the Followup-To-header - see section 6.7),
       "junk" (often used by serving agents), and "control" (likewise);
     o Any newsgroup-name beginning with "control." (used as pseudo-
       newsgroups by many serving agents);
     o Any newsgroup-name containing the component "ctl" (likewise);
     o "to" or any newsgroup-name beginning with "to." (reserved for the
       ihave/sendme protocol described in section 7.4, and for test
       messages sent on an essentially point-to-point basis);
     o Any newsgroup-name beginning with "example." (reserved for
       examples in this and other standards);
     o Any newsgroup-name containing the component "all" (because this
       is used as a wildcard in some implementations).
                                                                                
   A newsgroup-name SHOULD NOT appear more than once in the Newsgroups-
   header.  The order of newsgroup-names in the Newsgroups-header is not
   significant, except for determining which moderator to send the
   article to if more than one of the groups is moderated (see 8.2).

I think Noffle *should* allow you to create a single-component newsgroup
locally, but shouldn't allow you to retrieve a single-component newsgroup from
another server. I'll try and get round to doing this in CVS.

-- 
Jim Hague - jim...@in... (Work), ji...@be... (Play)
Never trust a computer you can't lift or you don't control.

Re: [Noffle-users] fetch and import questions..

[Jim H. <jim...@ac...>]

On 23-Feb-2003 Michal wrote:
>   Is it possible to use any external fetcher (as suck or newsstar or
>   others) with noffle? Or is it possible to import news from file to
>   the serwer? I have some mbox archives and I'd like to add them to
>   local groups served by Noffle...
>   any ideas?

If I remember rightly (and it's years since I used it last), suck uses NNTP to
post articles into the news server. If it does, it should work with Noffle.

Are you trying to use an external fetcher simply to import the archives, or do
you have fetching requirements that Noffle can't handle?

You can post an article from the command line with the '--post' option, or by
invoking Noffle as 'inews'. So it wouldn't take much
Perl/Python/Ruby/Awk/<insert favourite scripting language here> to extract the
messages from the archives and inject them into Noffle. Or perhaps one of
the mail-to-news gateways would have a tool. Maybe Google would have some
suggestions.

-- 
Jim Hague - jim...@in... (Work), ji...@be... (Play)
Never trust a computer you can't lift or you don't control.

Re: [Noffle-users] noffle&pan

[Jim H. <jim...@ac...>]

On 23-Feb-2003 Tomislav Ivan Flis wrote:
>>2. If you 'telnet localhost nntp', do you see
> 
>    Trying 127.0.0.1...
>    Connected to localhost.
>    Escape character is '^]'.
>    200 NNTP server NOFFLE 1.1.4
> 
> No. I get:
> [tompa@localhost xinetd.d]$ telnet localhost nntp
> Trying 127.0.0.1...
> telnet: Unable to connect to remote host: Connection refused

OK, this is the problem. To function as a NNTP server (which is how Pan access
it), Noffle needs to be run by a 'super-server'. Depending on your system, this
will be either 'inetd', which takes its configuration from /etc/inetd.conf, or
'xinetd', which takes its configuration from files in the /etc/xinetd.d
directory. This is easier to manage, as you just have to add or remove files
from the directory when installing/removing packages, rather than edit a file
(xinetd has other improvements too, but they aren't relevant here).

Since you said:

> /etc/inetd.conf:
> 
> nntp stream tcp nowait news /usr/sbin/tcpd /usr/bin/noffle -r

which looks completely correct, maybe you're running xinetd. Do a 'ps ax'
and see if you see 'xinetd' in the list of running processes.

If you see 'xinetd', you need a file /etc/xinetd.d/noffle with this in it:

# default: off
# description: Usenet newsserver for small sites
 
service nntp
{
        disable         = yes
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = news
        group           = news
        only_from       = 127.0.0.1
        server          = /usr/bin/noffle
        server_args     = -r
}

If you see 'inetd' and NOT 'xinetd', then something else is going wrong. Try
doing the telnet again, and them immediately look in /var/log/messages or
/var/log/syslog to see if any errors were logged by Noffle.

> [tompa@localhost xinetd.d]$ cat /etc/hosts.deny
>#
># hosts.deny    This file describes the names of the hosts which are
>#               *not* allowed to use the local INET services, as decided
>#               by the '/usr/sbin/tcpd' server.
>#
># The portmap line is redundant, but it is left to remind you that
># the new secure portmap uses hosts.deny and hosts.allow.  In particular
># you should know that NFS uses portmap!
> 
> 
> noffle: ALL EXCEPT LOCAL
> 
> Is the ptopblem maybe in that?

No, that's fine. It's just saying 'prohibit access to Noffle from all hosts
*except* localhost'. So 'telnet localhost nntp' should work.

-- 
Jim Hague - jim...@in... (Work), ji...@be... (Play)
Never trust a computer you can't lift or you don't control.

[Noffle-users] fetch and import questions..

[Michal <mi...@hu...>]

Hello noffle-users,

  Is it possible to use any external fetcher (as suck or newsstar or
  others) with noffle? Or is it possible to import news from file to
  the serwer? I have some mbox archives and I'd like to add them to
  local groups served by Noffle...
  any ideas?

  Thx in advance

-- 
Best regards,
 Michal                          

[Noffle-users] noffle&pan

[Tomislav I. F. <tom...@in...>]

Thanks for answering me!
I still haven't found the solution.

>On Sat, Feb 22, 2003 at 09:52:39PM +0000, Tomislav Ivan Flis wrote:
>> I can fetch froups and posts, but my newsreader don't see them. Why? H=
ow to
>> fix that?

>Simple things first.

>1. Have you done a 'noffle --query groups'? If you haven't, noffle
   won't know about any groups.

I did that.

>2. If you 'telnet localhost nntp', do you see

   Trying 127.0.0.1...
   Connected to localhost.
   Escape character is '^]'.
   200 NNTP server NOFFLE 1.1.4

No. I get:
[tompa@localhost xinetd.d]$ telnet localhost nntp
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused

>   If you don't, Noffle isn't set up properly. It needs to have
>   an entry in /etc/inetd.conf or /etc/xinetd.d/. Or you may have
>   denied access in /etc/hosts.deny.

/etc/inetd.conf:

nntp stream tcp nowait news /usr/sbin/tcpd /usr/bin/noffle -r
------------
/etc/xinetd.d/ ->I don't understand. Which file? /etc/xinetd.d/servers:

# default: off
# description: An internal xinetd service, listing active servers.

service services
{
=09type=09=09=3D INTERNAL UNLISTED
=09port=09=09=3D 9098
=09socket_type=09=3D stream
=09protocol=09=3D tcp
=09wait=09=09=3D no
=09disable=09=09=3D yes
=09only_from=09=3D 127.0.0.1
}
--------------------
[tompa@localhost xinetd.d]$ cat /etc/hosts.deny
#
# hosts.deny    This file describes the names of the hosts which are
#               *not* allowed to use the local INET services, as decided
#               by the '/usr/sbin/tcpd' server.
#
# The portmap line is redundant, but it is left to remind you that
# the new secure portmap uses hosts.deny and hosts.allow.  In particular
# you should know that NFS uses portmap!


noffle: ALL EXCEPT LOCAL

Is the ptopblem maybe in that?

[Noffle-users] groups without any dots in the name don't show up

[Miernik <mi...@ct...>]

It's probably uncommon to have groups without any dot in the name, but 
here is an example:

miernik@tarnica:~$ telnet news.linuxfromscratch.org 119
Trying 66.11.168.23...
Connected to linuxfromscratch.org.
Escape character is '^]'.
200 quasar.highos.com InterNetNews NNRP server INN 2.3.3 ready (posting ok).
list active
215 Newsgroups in form "group high low flags".
control 0000000000 0000000001 n
control.cancel 0000000045 0000000045 n
control.checkgroups 0000000000 0000000001 n
control.newgroup 0000000000 0000000001 n
control.rmgroup 0000000000 0000000001 n
junk 0000000000 0000000001 n
lfs.test 0000000417 0000000399 y
lfs.dev 0000011587 0000010949 y
lfs.support 0000014185 0000013837 y
alfs.discuss 0000001445 0000001420 y
blfs.support 0000023724 0000022968 y
lfs.traducfr 0000001182 0000001151 y
lfs.security 0000000449 0000000448 y
lfs.hints 0000001297 0000001258 y
lfs.book 0000004203 0000003969 y
cgroup 0000000138 0000000138 y
blfs.book 0000003163 0000002997 y
blfs.dev 0000002308 0000002198 y
links-list 0000002462 0000002445 y
links.discuss 0000001224 0000001212 y
lfs.chat 0000006779 0000005787 y
unishell.announce 0000000000 0000000001 =
unishell.discuss 0000000000 0000000001 =

Re: [Noffle-users] Pan

[Jim H. <ji...@be...>]

On Sat, Feb 22, 2003 at 09:52:39PM +0000, Tomislav Ivan Flis wrote:
> I can fetch froups and posts, but my newsreader don't see them. Why? How to 
> fix that?

Simple things first.

1. Have you done a 'noffle --query groups'? If you haven't, noffle
   won't know about any groups.

2. If you 'telnet localhost nntp', do you see

   Trying 127.0.0.1...
   Connected to localhost.
   Escape character is '^]'.
   200 NNTP server NOFFLE 1.1.4

   If you don't, Noffle isn't set up properly. It needs to have
   an entry in /etc/inetd.conf or /etc/xinetd.d/. Or you may have
   denied access in /etc/hosts.deny.

[Noffle-users] Pan

[Tomislav I. F. <tom...@in...>]

Hi!
I'm trying to use noffle but I ran into troubles. Im a newbie conserning =
Linux

I can fetch froups and posts, but my newsreader don't see them. Why? How =
to=20
fix that?
ip-up:

#!/bin/bash
# This file should not be modified -- make local changes to
# /etc/ppp/ip-up.local instead

PATH=3D/sbin:/usr/sbin:/bin:/usr/bin
export PATH

LOGDEVICE=3D$6
REALDEVICE=3D$1
/usr/bin/noffle --fetch
/usr/bin/noffle --online

export PATH=3D/sbin:/usr/sbin:/bin:/usr/bin

if [ -x /usr/sbin/sendmail ];then
    /usr/sbin/sendmail -q 2>/dev/null >/dev/null &
fi

# for dynamic DNS support with gnome-ppp and kppp and draknet
if grep -i '#.*ppp temp entry' /etc/resolv.conf >& /dev/null ; then
    PPP_TEMP_ENTRY=3D`grep '#.*ppp temp entry' /etc/resolv.conf | \
       tail -1 | sed 's/.*ppp temp entry/# ppp temp entry/' `
else
    unset PPP_TEMP_ENTRY
fi
if [ -n "$PPP_TEMP_ENTRY" ]; then
    [ -n "$DNS1" ] && \
=09echo -e "nameserver $DNS1 $PPP_TEMP_ENTRY" >> /etc/resolv.conf
    [ -n "$DNS2" ] && \
=09echo -e "nameserver $DNS2 $PPP_TEMP_ENTRY" >> /etc/resolv.conf
fi

[ -f /etc/sysconfig/network-scripts/ifcfg-${LOGDEVICE} ] &&=20
/etc/sysconfig/network-scripts/ifup-post ifcfg-${LOGDEVICE}

[ -x /etc/ppp/ip-up.local ] && /etc/ppp/ip-up.local "$@"

exit 0
-----------------------------------
ip-down:

#!/bin/bash
# This file should not be modified -- make local changes to
# /etc/ppp/ip-down.local instead

PATH=3D/sbin:/usr/sbin:/bin:/usr/bin
export PATH

LOGDEVICE=3D$6
REALDEVICE=3D$1

export PATH=3D/sbin:/usr/sbin:/bin:/usr/bin

mv -f /etc/resolv.conf /etc/resolv.conf.tmp
cat /etc/resolv.conf.tmp | awk '{if(!/nameserver .* # ppp temp entry.*/) =
print=20
$0}' > /etc/resolv.conf
chmod 0644 /etc/resolv.conf
rm -f /etc/resolv.conf.tmp

[ -x /etc/ppp/ip-down.local ] && /etc/ppp/ip-down.local "$@"

/etc/sysconfig/network-scripts/ifdown-post ifcfg-${LOGDEVICE}
/usr/bin/noffle --offline

exit 0


in /etc/inetd.conf already was:

nntp stream tcp nowait news /usr/sbin/tcpd usr/bin/noffle -r


Help me please!

Re: [Noffle-users] feature request: split --fetch to --post-queued --fetch-overview --fetch-selected-bodies

[Mirko L. <mir...@we...>]

Miernik wrote:
> On Tue, Feb 11, 2003 at 04:20:18AM +0100, Mirko Liss wrote:
> > What do you think about a fetch mode that does actually avoid
> > downloading overviews of new articles? You won't be able to filter
> > articles and you won't get articles from groups that have been
> > subscribed in 'over' or in 'thread' mode.
> 
> Because downloading the overviews takes much more time then 
> downloading the selected articles. What I do is I download the 
> overviews during the night.

So you don't need a new fetch mode like I suggested? Well, all right.


Mirko

Re: [Noffle-users] feature request: split --fetch to --post-queued --fetch-overview --fetch-selected-bodies

[Miernik <mi...@ct...>]

On Tue, Feb 11, 2003 at 04:20:18AM +0100, Mirko Liss wrote:
> Please look at noffle/src/noffle.c, at the procedures doFetch()
> and main(). It is _very_ easy to implement, indeed.
>=20
> Just copy doFetch() and delete some of the 'connOk =3D connOk &&'-lines.
> The command line options will be parsed using a switch()-case-structure
> in the main()-procedure. It's easy to insert a new option.

OK, I'll take a look at it then. Tomorow :) , it's really late here ...=20

> What do you think about a fetch mode that does actually avoid
> downloading overviews of new articles? You won't be able to filter
> articles and you won't get articles from groups that have been
> subscribed in 'over' or in 'thread' mode.

Because downloading the overviews takes much more time then=20
downloading the selected articles. What I do is I download the=20
overviews during the night. And when I come to the computer I just=20
select articles which have subjects that interest me. I'd then want to=20
just fetch the selected bodies to read those articles, and then write=20
some replies an then post these replies. I don't want downloading new=20
article overviews this day - that will be done next night. I think it=20
will be useful for people with slow links, who do newsreading this way=20
like me - download only overviews only once daily duging the night,=20
but want just the selected bodies to be downloaded right now, so they=20
can reply, and go on doing different things.

--=20
    Miernik          ____________________________________________________
___ ICQ: 4004001 ___/___ tel.: +48608233394 ___/  mailto:mi...@ct...
Bush "won" 2000 elections with 537 Florida votes. More people where illegal=
y=20
prevented to vote:  http://www.observer.co.uk/Print/0,3858,4103063,00.html

Re: [Noffle-users] feature request: split --fetch to --post-queued --fetch-overview --fetch-selected-bodies

[Mirko L. <mir...@we...>]

Miernik wrote:
[..fetch less, fetch faster..]
> I think that would be very simple for someone who knows Noffle 
> internals.

Please look at noffle/src/noffle.c, at the procedures doFetch()
and main(). It is _very_ easy to implement, indeed.

Just copy doFetch() and delete some of the 'connOk = connOk &&'-lines.
The command line options will be parsed using a switch()-case-structure
in the main()-procedure. It's easy to insert a new option.


However, I'm not convinced that such a patch is actually useful. This
way, you can't avoid downloading the overviews, you'll just delay it.


What do you think about a fetch mode that does actually avoid
downloading overviews of new articles? You won't be able to filter
articles and you won't get articles from groups that have been
subscribed in 'over' or in 'thread' mode.

Instead of getting overviews with 'XOVER number-number', noffle sends
'XHDR Message-Id number-number' to find out the Message-Ids of the new
articles. That's still a waste of bandwidth, but I suppose it's a bit
more efficient than getting the whole overviews.


Well, if noffle was able to download articles by number instead of by
Msg-Id, the aforementioned 'XOVER' could be skipped without the
replacement 'XHDR Message-Id'. That would be even faster. But it's a
lot of work to code this, and there are some problems without trivial
solutions. Avoiding multiple download of crossposts, for example.


regards,

Mirko

[Noffle-users] feature request: split --fetch to --post-queued --fetch-overview --fetch-selected-bodies

[Miernik <mi...@ct...>]

I'd love to have separate options for the three actions which --fetch 
does. For example: 

--post-queued 
--fetch-overview 
--fetch-selected-bodies

Fetching the overview takes very long for me, and very often I need 
only to fetch the article bodies that I have selected, and/or post 
articles I have written.

I think that would be very simple for someone who knows Noffle 
internals.

-- 
    Miernik          ____________________________________________________
___ ICQ: 4004001 ___/___ tel.: +48608233394 ___/  mailto:mi...@ct...
No Iraq war http://www.globalexchange.org/campaigns/iraq/invadeIraq082702.html
Please call the White House +1-202-456-1111 or fax +1-202-456-2461 and say no!

Re: [Noffle-users] AUTHINFO SIMPLE with noffle ?

[Jim H. <jim...@ac...>]

On 10-Feb-2003 Dominique Dumont wrote:
> With noffle v 1.1.3, I want to connect to a news server with
> authentification. But it looks like this server cannot accept
> AUTHINFO:
> 
>   [S] AUTHINFO USER dumont
>   [S FLUSH]
>   [R] 381 PASS required
>   Username rejected. Server stat: 381 PASS required
> 
> According to this server's doc, I should use the 'authinfo simple
> USERNAME PASSWORD'
> 
> So is there a way to setp up noffle so that a 'authinfo simple'
> command is used instead of 'AUTHINFO USER' ?

Unfortunately, not at the moment. It would be simple to implement, but I
haven't done so for 2 reasons:

1. Nobody ever asked :-)
2. The latest IETF recommendations say that this should not be implemented.
   However, since we're talking here about a client, not a server, I think
   it would be OK to implement. 

However, looking at the above, I'm confused. The upstream server does seem to
be returning '381' to the AUTHINFO USER. '381' is the correct 'send me the
password' response, so Noffle *should* have then sent AUTHINFO PASS. But it
didn't, for some reason. Hang on, I'll check the code...

<Blink>

Aarrgghh! There's a horrid cockup in client.c! And, to my shame, I also now see
there's a patch waiting on SourceForge for it.

The fix is to change STAT_AUTH_REQUIRED on line 169 of client.c to
STAT_MORE_AUTH_REQUIRED.

I've now done this in CVS. This is, I think, sufficient breakage to justify a
1.1.4 release as soon as I can get round to it.

-- 
Jim Hague - jim...@in... (Work), ji...@be... (Play)
Never trust a computer you can't lift.

[Noffle-users] AUTHINFO SIMPLE with noffle ?

[Dominique D. <do...@ko...>]

Hello

With noffle v 1.1.3, I want to connect to a news server with
authentification. But it looks like this server cannot accept
AUTHINFO:

  [S] AUTHINFO USER dumont
  [S FLUSH]
  [R] 381 PASS required
  Username rejected. Server stat: 381 PASS required

According to this server's doc, I should use the 'authinfo simple
USERNAME PASSWORD'

So is there a way to setp up noffle so that a 'authinfo simple'
command is used instead of 'AUTHINFO USER' ?

Thanks

-- 
dom...@hp...

Bug#168128: Info received (was [Noffle-users] noffle 1.1.2: Received SIGSEGV. Please submit a bug report)

[<ow...@bu...>]

Thank you for the additional information you have supplied regarding
this problem report.  It has been forwarded to the developer(s) and
to the developers mailing list to accompany the original report.

As you requested using X-Debbugs-CC, your message was also forwarded to
   Miernik <mi...@ct...>, nof...@li...
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
 go...@tc... (Martin A. Godisch)

If you wish to continue to submit further information on your problem,
please send it to 16...@bu..., as before.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the Bug-tracking system.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Re: [Noffle-users] noffle 1.1.2: Received SIGSEGV. Please submit a bug report

[Jim H. <jim...@ac...>]

On 07-Feb-2003 Miernik wrote:
> I got this today in my log:
> 
> Feb  7 03:52:52 tarnica noffle[2750]: Received SIGSEGV. Please submit a bug
> report

Is there a file named 'core' in /var/spool/noffle? If there is, can you send it
to me?

-- 
Jim Hague - jim...@in... (Work), ji...@be... (Play)
Never trust a computer you can't lift or you don't control.

[Noffle-users] noffle 1.1.2: Received SIGSEGV. Please submit a bug report

[Miernik <mi...@ct...>]

Hi, 

I got this today in my log:

Feb  7 03:52:52 tarnica noffle[2750]: Received SIGSEGV. Please submit a bug report

I am running noffle 1.1.2 from http://packages.debian.org/unstable/news/noffle.html

It wasn't at the computer while it did that, so I'm not sure what 
happened. But you ask to report, so I report :)

-- 
    Miernik          ____________________________________________________
___ ICQ: 4004001 ___/___ tel.: +48608233394 ___/  mailto:mi...@ct...
No Iraq war http://www.globalexchange.org/campaigns/iraq/invadeIraq082702.html
Please call the White House +1-202-456-1111 or fax +1-202-456-2461 and say no!