Ok Folks, first of all - give me a bit of humility. I certainly didn't
need the private tongue lashing I got from a few of you, I simply wanted
help - I did not request an email reprimand. I'm quite surprised at the
level of hostility on this list when 1) the archives for redundant questions
as mine are down and 2) the process I use are good - the terminology may be
different.. you _should_ be adult enough to adapt.
Having said all of that, I'll try again to answer the main questions and
perhaps someone will be willing to assist again, and at the same time try
not to be lengthy.
>I'm currently running qPopper 4.0.3 under Redhat 7.2 and xinetd.
>What options did you set when you compiled qpopper.
I compiled with --enable-chunky-writes=1 (i.e. ./configure
--enable-chunky-writes=1)
>HTTP side of WHAT?
>
>Qpopper isn't a web server, and neither is xinetd.
All true, but there IS the httpd interface used, otherwise what's the use of
a POP account? When I use a web browser to connect to the POP account, it
errors.
>Look into whatever package (not xinetd or qpopper) which is
>providing you with service.
I'm using MailMan (www.endymion.com) which worked just peachy until I
upgraded to 7.1 and xinetd. I checked the endymion issues, and nothing
indicates that it is this service.
>There is no pop4.
There is if you decide to create your service called 'pop4'. I could have
easily used pop3, this is a terminology issue. telnet <servicename> 110 is
probably what I should have used. Regardless, the service is valid on my
system.
>where'd you get the xinetd config for popper? What's it look like?
Here's part of my xinetd.conf file that pertains to popper:
# default: on
# description: Start the POP service for e-mail
service pop4
{
# disable = no
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/local/sbin/popper
server_args = popper -s
port = 110
}
I got this from the qpopper.com website; FAQ's.
>What examples from where?
see www.qpopper.com/qpopper/faq.html and the RedHat 7.1 newsgroups
pertaining to qpopper, POP3 and xinetd services.
>What does HTTP have to do with this? And how are you
>browsing mail folders or sending mail from an HTTP connection?
HTTP has everything to do with it - if you're using a web browser to view
the emails for the POP account. I suppose there's a number of ways to read
the POP account mail, http is one way. Haven't you ever heard of Hotmail?
>> ROOT side:
>What's that supposed to mean?
Meaning the root account on the system (the god-mode account).
>What HTML error messages? HTML shouldn't come into the
>picture at all.
The HTML error message is this:
Error: Could not connect to server <servername>
I realize html shouldn't come into the picture. The reason I included it
was because of the conflicting message the html returned via what is being
logged in the maillog as an error:
maillog: May 14 15:55:56 <server> popper[16196]: I/O error flushing
output
to client <account> at <server> [IPAddress]: Operation not permitted (1)
>Can you make a connection to the server on the
>pop3 port (110)? Does it work?
Yes and Yes.
>Is this where your popper binary is located? What is the ownership and
>permissions on the file? In other words, what does
>"ls -l /usr/qpopper4.0.4/popper" show?
My binary is at /usr/local/sbin (I have since re-installed it again since
/usr/qpopper4.0.4/popper - so translate the location in your head)
ls -l /usr/local/sbin/popper shows:
-rwxr-xr-x 1 root root 441239 May 14 15:48
/usr/local/sbin/popper
I have added popper:ALL to my /etc/hosts.allow file with no apparent
success.
If you want to help, ok - please don't verbally bash me.
Thanks again.
-Tony
-----Original Message-----
From: Alston, Tony [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 14, 2002 4:22 PM
To: Subscribers of Qpopper
Subject: RH7.1 and QPopper 4.0.4
Has anyone resolved the error with xinetd and qpopper 4? I have followed
the examples to excruciating detail, have backtracked up versions and down
to the current version, reinstalled xinetd from www.xinetd.org and followed
a host of different sources recommending what I should do.
I am getting confusing errors from the html side, and what is being logged
in the maillog file.
HTTP side:
I can get logged in and browse my mail folders, but I cannot receive new
mail or send mail, or move mails between established folders. When sending
new e-mail, I get the following error:
Send Error: Could not connect to server <servername>
ROOT side:
I can 'telnet <servername> pop4' and get the pop server to respond, log in
and out, view the inbox..etc, but that's about it.
LOG files:
My log files do not correspond with the HTML error messages. I know these
are not uncommon errors, I just can't find anything specific on them.
maillog: May 14 15:55:56 <server> popper[16196]: Stats: <account> 0 0 0 0
<servername> <IPAddress>
maillog: May 14 15:55:56 <server> popper[16196]: I/O error flushing output
to client <account> at <server> [IPAddress]: Operation not permitted (1)
messages: May 14 15:56:30 <server> xinetd[16120]: execv
(/usr/qpopper4.0.4/popper ) failed: Permission denied (errno = 13)
I have tried locating the popper executable in the /usr/sbin/popper
directory, but that doesn't seem to matter, the same error applies no matter
where the file is at.
I've read/sweated/frustrated on the FAQ's from qpopper. My xinetd.conf
reflects the currect consensus configuration for running the POP services.
Any takers on helping out?
Thanks in advance....
-Tony
