Andrew J S Hamilton <[EMAIL PROTECTED]> writes:
> Dear Dan Harkless,
>
> At a guess you may be the person to email.
No, [EMAIL PROTECTED] is the right address to use for bug reports. This
address is moderated and forwards to [EMAIL PROTECTED] -- I'm cc'ing
this reply there. I don't have time at the moment to look into your
problem, but perhaps someone on the list will get to it before I do.
> inc does not work for me in recent issues of nmh, e.g. nmh-1.0.4.
> The last version that works is nmh-0.27.
>
> Here is the description of the bug
> ----------------------------------
> I use pop3 with my password stored in ~/.netrc.
> With 0.27:
>
> ajsh@dusk ~% inc -host glow.colorado.edu -snoop
> <--- +OK QPOP (version 2.53) at glow starting. <26822.981413531@glow>
> ---> USER ajsh
> <--- +OK Password required for ajsh.
> ---> PASS ********
> <--- +OK ajsh has 0 messages (0 octets).
> ---> STAT
> <--- +OK 0 0
> ---> QUIT
> <--- +OK Pop server at glow signing off.
> inc: no mail to incorporate
>
> With 1.0.4:
>
> ajsh@dusk ~% inc -host glow.colorado.edu -snoop
> <--- +OK QPOP (version 2.53) at glow starting. <26845.981414173@glow>
> ---> USER ajsh
> <--- +OK Password required for ajsh.
> ---> PASS ********
> <--- -ERR Password supplied for "ajsh" is incorrect.
> ---> QUIT
> connection closed by foreign host
> -ERR Password supplied for "ajsh" is incorrect.
> inc: -ERR Password supplied for "ajsh" is incorrect.
>
> Where the bug is in the code
> ----------------------------
>
> The bug is where inc.c calls
> ruserpass (host, &user, &pass);
> ruserpass is `undocumented', so it is hard to see the problem.
>
> In nmh-0.27, ruserpass returns 0;
> in nmh-1.0.4, ruserpass returns -1.
>
> The inputs going into rusperpass are identical, namely (host, null, null),
> but while 0.27 returns the correct user and password,
> 1.0.4 returns a correct user but null password.
>
> I have checked that uid and gid are identical in both 0.27 and 1.0.4.
>
> Any ideas?
>
> Thanks, Andrew Hamilton
> http://casa.colorado.edu/~ajsh/
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
[EMAIL PROTECTED] | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.