Stewart,
You get the big reward for coming up with the solution to "most" of my
pop-3d problems. What I don't understand is this. If the Memphis RPM
automatically places in the directory /etc/rc3.d/ as K<n>qmail-pop3d.init
instead of S<a>qmail-pop3d.init, how is it that the Memphis install works on
any system? Is it random chance? For me the effect is clear. If I switch to
S, reboot, I can get my mail through Pop (from my windows computer on my
network using outlook). If I switch back to K, reboot, it fails. So your
solution clearly works, but why is it apparently not necessary on most
systems, since people do get the Memphis RPM to work without doing that.
With the memphis rpm, to start qmail-pop3d, just do
install checkpassword (rpm is in my ftp dir)
/etc/rc.d/init.d/qmail-pop3d.init start
and to start it automatically at boot up, do
chkconfig qmail-pop3d.init on
If you decide not to run qmail-pop3d anymore, do
/etc/rc.d/init.d/qmail-pop3d.init stop
chkconfig qmail-pop3d.init off
I will change the README in my ftp dir to make the staff about pop
clearer.
Now, I have a wierder problem with Pop3, which I really don't understand. I
can get my mail fine now using outlook on a computer on my network using pop
(due to your solution). However, when I go to work and attempt to get my
mail, using the same settings in MS Outlook, I get a failure to connect to
the server!
The only difference is wether I am coming from the outside, or I'm using my
own network. Am I missing something?
Yes, please give us much more details. For example, how did you set
up the tcprules for qmail-pop3d on the server?
What do you get when, on mail.cybergood.net, you telnet to port 110
(copy the whole session except passwd, of course).
Mate
