[Noffle-devel] [ noffle-Bugs-756585 ] Noffle cannot handle @ in the username
Brought to you by:
bears
From: SourceForge.net <no...@so...> - 2003-06-18 15:20:18
|
Bugs item #756585, was opened at 2003-06-18 14:24 Message generated for change (Comment added) made by bears You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=756585&group_id=1044 Category: None Group: None Status: Open Priority: 5 Submitted By: Steve Lamb (greydmiyu) Assigned to: Jim Hague (bears) Summary: Noffle cannot handle @ in the username Initial Comment: My ISP outsources news to Supernews. My login through that route is use...@is... and not just username. Noffle cannot handle that in the configuration file. root@teleute:/etc/news# noffle -q news.foobar.com Unknown argument -q news.foobar.com Fetch from 'news.foobar.com' Connected to 216.168.3.50:119 Fetch from 'news.foobar.com' finished If I place quotes around the username the quotes are sent to the remote side. root@teleute:/etc/news# vim noffle.conf root@teleute:/etc/news# noffle -q news.foobar.com Unknown argument -q news.foobar.com Fetch from 'news.foobar.com' Connected to 216.168.3.50:119 Password rejected. Server status: 502 no permission (no match for 'ex...@fo...') Connection to remote server lost (article numbers could be inconsistent) Fetch from 'news.foobar.com' finished ---------------------------------------------------------------------- >Comment By: Jim Hague (bears) Date: 2003-06-18 16:20 Message: Logged In: YES user_id=184 Thanks for the bug report. I don't see the problem here. Or not the problem you're describing, at any rate. Noffle can't cope if the username contains a space or tab, and if that becomes a problem I'll need to update the config file parser to cope with quoted strings. But in this case your login seems to be working pefectly. The 'Unknown argument -q news.foobar.com' message is because you have the command wrong. It should be either 'noffle -q groups news.foobar.com' or 'noffle -q desc news.foobar.com'. There *is* a bug in the code here; if neither is given Noffle should just stop. But I stuffed up, so in fact it continues after issuing the error and connects to the server, logging in successfully in the first instance, and then disconnects without actually fetching anything. I'll fix this soon. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=756585&group_id=1044 |