Um-m-m-m... I'll start of with "I'm not a qpopper developer, but...",
and I'm not picking on you, but...
I've always found that, when testing software, one should test software
in the mode it was designed for... Ie: if the software is designed to
receive lines, to send it lines. If it designed to recognize character
at a time inputs AND line at a time, to test both. If designed for only
'character input', send only character inputs...
Qpopper is designed for software that sends "line" at a time input. Why
not test it in that mode? Most telnet implementations that I have seen
have a switch that allows line transmissions instead of character
transmissions...
Regards,
Gregory Hicks
---------------------------------------------------------------------
Gregory Hicks | Principal Systems Engineer
Cadence Design Systems | Direct: 408.576.3609
555 River Oaks Pkwy M/S 6B1 | Fax: 408.894.3479
San Jose, CA 95134 | Internet: [EMAIL PROTECTED]
> From: Carles Xavier Munyoz Bald� <[EMAIL PROTECTED]>
> Date: Mon, 28 May 2001 11:56:00 +0200
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
> Some days ago I send you this bug report.
> Have you seen something about it ?
>
> [...]
> Hi,
> I'm using Qpopper 4.0.2 and I have found a bug in the module
'popper.c',
> function 'getline()'.
>
> The bug is in the line:
> 425: if ( pPOP->pcInEnd != pPOP->pcInStart && *p == '\n' ) {
>
> The solution is modify the line this way:
> OLD 425: if ( pPOP->pcInEnd != pPOP->pcInStart && *p == '\n' ) {
> NEW 425: if ( p != pPOP->pcInEnd && *p == '\n' ) {
>
>
> I'm going to explain the bug.
> Its something hard to explain, but I'll do my best :-)
>
> The problem appears when I try to test one of my pop users accounts
> using the telnet client from Windows.
> This telnet client sends one TCP packet for every keystroke.
[...snip rest of explanation...]
