> Last November, I submitted a bug report with patches for nmh - it didn't work
> as a POP client properly on Linux systems. But unfortunately, the patches
> didn't get into the 1.0.4 release, so here goes again:
I had the same problems, and fixed them after 1.0.4 came out. I did not
want to commit them prematurely and risk the release version having bugs.
My solution was to completely take out any dependency on system ruserpass,
and use the version packaged with nmh. If you want to take advantage of
this, I recommend you get the latext CVS version.
> 2. For Linux systems, avoid using the glibc version of ruserpass(), and use
> the version supplied with nmh. There's an additional problem here -
> ruserpass() calls getpass(), and in glibc, the getpass() flushes standard input
> before prompting the user for a password. When a program like exmh uses 'inc',
> it feeds in the password as standard input with code like:
>
> exec inc +inbox -truncate -nochangecur -width 100 << password
>
> which fails with the glibc version of getpass(). So a replacement for
> getpass() needs to be provided as well.
I haven't tested this with exmh. I will look into it.
> I'm willing to put together changes to the nmh configure script that will
> use the nmh version of ruserpass(). I have a patch for ruserpass() that works
> with my system (see attached). Would you like me to work on the configure
> portion?
configure is done, as is ruserpass. I will work on incorporating your
getpass().
> So, what would you like to do? Please at least include a note in the MACHINES
> file about the restriction that on Linux systems, ~/.netrc must be used for
> POP login/password info. Thanks!
Hopefully this will not be necessary.
Shantonu
*-------------------------------------------*
|Shantonu Sen * (617)225-6778 * [EMAIL PROTECTED]|
|Electrical Engineering and Computer Science|
|Massachusetts Institute of Technology, 2002|
*-------------------------------------------*
