exmh and popexmh. Note that the mh binaries on sww seem to
have been setup so that pop won't work. The Solaris binaries are in
/opt/mh/bin
, the SunOS binaries are in /usr/local/mh/bin
It looks like exmh won't work with poper, but it will work with popd.
The trick is to have a ~/.xmhcheck file with the following line
exmh's preferences by mousing on
Preferences -> Incorporate Mail -> multidrop
and then saving your preferences.
We are working on getting kerberos to work, but in the short term,
exmh uses RPOP, which uses
~/.rhosts like the Berkely r* commands
(rsh, rcp etc.). So, to get exmh to work,
you will need to have the machine you are logging in from listed in
your .rhosts file
exmh man page
popper man page.
inc in
/opt/mh/bin, rather than the inc in
/usr/sww/bin. Use which inc to see which
inc binary you running, then adjust your path accordingly.
~/.xmhcheck file
~/.rhosts file.
telnet hostname pop3.
See Testing below for more information.
inc -host hostname from the remote host.
This command should connect to the pop host and get your mail for you.
inc is the command that exmh runs. See for the tcl code that runs the inc command.
/etc/inetd.conf and see where popper
is logging to, then check that file.
truss or
trace on inc might help. Since
inc is setuid root so that it can mess with the mail
spool, truss won't work on it. The solution is to use
which to determine where the inc binary is,
then copy the binary elsewhere and run truss on it.
popperA Working POP3 server for a number of platforms including Solaris
2.x is finally available from QUALCOMM, the company which maintains
Eudora, as ftp://ftp.qualcomm.com/quest/unix/servers/popper/qpop2.1.4-r3.tar.Z
Currently we are using
popper on dewitt.
popperis installed as /usr/local/etc/popper.
ftp://ftp.qualcomm.com/eudora/servers/unix/popper/
./configure --enable-apop=/etc/pop.auth --with-popuid=pop
/etc/inetd.conf
has the following:
popdCurrently we are using popper, but the mh popd daemon was started up on mho in /etc/rc.local:
popd is also running on messier.
The popd we are running is pop3 from the MH distribution. I built the mh distribution by hand, which was no small task.
There is a sol2 popd on sww, but it is readable only by user 18.
Looks to me like popd in mh can be built to support kerberos I have not tried it, but the mh-gen man page says:
imapdimapd might be an alternative /usr/sww/doc/faq/mh.faq
discusses imap
popipopi is a mh program that can be used to connect to a pop host
Unfortunately, the popi on sww is empty, probably for security reasons.
popi is on mho in /usr/local/mh-6.8.3/bin/popi