David T-G proclaimed on mutt-users that:
>It boils down to mutt's UNIX-like behavior of expecting other pieces to
>be there; all mutt does is read mail, and it sucks less at that than
>anything else. The biggest problem people often quote is the lack of
>an MTA, since mutt does not talk directly to the MDA on the recipient
>machine via SMTP port 25, as I believe PINE does. It doesn't help that
Correct - but there are several tiny m$-dog based servers like Mercury/32
(the latest version of which has an esmtp module). You can set mercury to
smarthost (relay) through your ISP / office's actual smtp server.
If someone can get mutt compiled and running on windog, a set sendmail
call can be passed to Mercury and it can send the mail out.
>Win doesn't handle subshells gracefully and so things like PGP can be
>tricky as well, as I understand it.
If a barebones version is compiled - to read imap mailboxes instead of the
mail spool - and mutt passes the mail to mercury?
[note - Mercury is freeware but closed source, from David Harris, the
author of Pegasus Mail for Windows. Both Pegasus and Mercury come in
netware versions as well. Both can be downloaded for free from
http://www.pmail.com]
>Bring in your *NIX laptop instead :-) With mutt's IMAP support, you can
>even talk to the MS Exchange server and not have to use LookOut! like the
>rest of your coworkers!
I have access to a sun box via exceed ... that helps, or else I'd have
to use windog mailers like outhouse ;)
--
Suresh Ramasubramanian + [EMAIL PROTECTED]
"I'd love to go out with you, but I'm staying home to work on my
cottage cheese sculpture."