derek at computinginnovations.com
Wed Feb 22 12:15:02 PST 2006
As you said you have just upgraded, did you use the port to upgrade? If
you did it will use the configuration setting to build qpopper. Otherwise,
if you downloaded qpopper's source and built it yourself, you need to check
the configuration settings.
You should verify qpopper is built and executable:
ls -l /usr/local/libexec/qpopper
If you are using tcp wrappers disable them to test qpopper by uncommenting
#ALL : ALL : allow
as a last check, it never hurts to reboot the box, so you are sure there
are no issues from old processes or sockets.
If you are still having problems connecting check the log add the option:
-t [some log file location and file name]
Then you can see what the problems are.
Hope this helps.
At 12:51 PM 2/22/2006, michaela wrote:
>I was running an older version of Qpopper on my mailserver and had NO
>problems whatsoever. Everything was going great. However, I just recently
>upgraded to Qpopper v4.0.8 and now all of a sudden I can't access my mail
>I'm running Qpopper via INETd and my /etc/inetd.conf file looks like this....
>pop3 stream tcp nowait root /usr/local/libexec/qpopper qpopper -
>s -T 600
>However, when I try telnetting to localhost 110, I get the
>dreaded, "CONNECTION CLOSED BY FOREIGN HOST" message. NETSTAT shows that
>Qpopper is listening on Port 110/TCP so I don't know what's wrong.
>My /etc/hosts.allow file is set to allow ALL so that shouldn't be an issue.
>I even executed KILLALL -HUP inetd numerous times and still no go.
>I've poured through the Qpopper FAQs and documentation to see if I'm doing
>anything wrong, or missing something, but I just can't seem to pinpoint it.
>Any suggestions or details as to what I might be missing???
>Any help is much appreciated.
>freebsd-questions at freebsd.org mailing list
>To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions