Custom Query (44 matches)
Results (40 - 42 of 44)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#15 | fixed | news log logging wrong source for local postings | ||
Description |
Local postings are logged to the news log as originating from a site from the Path or possibly from elsewhere in memory. I see not-for-mail entries in the news logs, and other people have seen various peer sites. |
|||
#73 | fixed | news2mail's crosspost handling code generates bad To headers | ||
Description |
news2mail uses the following to generate the To header: print SM "To: @a\n\n"; If there are multiple addresses, this generates a broken header since it uses a bare space as a delimiter. sendmail will then turn this into a dot and corrupt the header. It needs to use a comma instead. |
|||
#109 | wontfix | nnrpd doesn't return 420 errors for XOVER | ||
Description |
According to RFC 2980, section 2.8:
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). |