Custom Query (44 matches)


Show under each result:

Results (1 - 3 of 44)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#87 fixed showtoken should be part of sm eagle eagle

The ability to take apart the class-specific information in a token and display what it means should be added to the storage API and then the capabilities of showtoken included in sm. showtoken is currently a Perl script in contrib

#30 fixed nnrpd doesn't support passwords with spaces eagle eagle

The NNTP protocol uses whitespace as a command and argument separator, which means that passwords containing whitespace don't work. The generic NNTP parser in nnrpd throws away the tail end of the password or produces a syntax error.

However, since the password is the last argument, we can hack around this problem. Here's a patch from Jeffrey M. Vinocur from 2001 that implements that fix, which may require some updating.

#109 wontfix nnrpd doesn't return 420 errors for XOVER eagle Julien ÉLIE

According to RFC 2980, section 2.8:

If no articles are in the range specified, a 420 error response is returned by the server.

nnrpd (from the beginning of the XOVER command) has always returned a 224 response with an empty multiline response instead.

Note that the OVER command properly returns 423 (no articles in that range) when that case occurs. 420 is sent when the current article number is invalid.

Impact: Less information is communicated to the client about why there are no overview records returned. An error response indicating there are no valid articles in that range is possibly more informative.

There is probably no way to fix this now. Changing the reply codes would break a few existing implementations: it may confuse some clients that don't expect to get 420 errors back from overview queries. Clients may be relying on the existing behavior (confirmed with Outlook Express/Windows? Mail for instance).

1 2 3 4 5 6 7 8 9 10 11
Note: See TracQuery for help on using queries.