• The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Qmail up but does not respond!

RH uw-imap ?

I am wondering if the default RH pop service (uw-imap) got installed, that would explain the ipop3

From the shell prompt, do the following command:

rpm -q uw-imap

If that produces nothing, then try:

rpm -qa |grep 'imap'

Please post both results here.

In any case, Plesk should not need that ipop3 service, so you can try disabling it:

To disable POP3, edit the file

/etc/xinetd.d/ipop3

and make sure it reads something like this:

service pop3
{
disable = yes
socket_type = stream
wait = no
user = root
server = /usr/sbin/ipop3d
log_on_success += USERID
log_on_failure += USERID
}

In particular, make sure that "disable" is set to "yes".

Save your changes, exit your editor, and run:

/etc/rc.d/init.d/xinetd restart

Congratulations! You have just disabled POP3.
Then you will have to make sure that the plesk preferred IMAP is working and/or installed. The rpm listing should show something like:

courier-imap-3.0.8-rh7.build75050506.13

or something similar
 
Re: RH uw-imap ?

Originally posted by jamesyeeoc
I am wondering if the default RH pop service (uw-imap) got installed, that would explain the ipop3

From the shell prompt, do the following command:

rpm -q uw-imap

If that produces nothing, then try:

rpm -qa |grep 'imap'

Please post both results here.

In any case, Plesk should not need that ipop3 service, so you can try disabling it:

Then you will have to make sure that the plesk preferred IMAP is working and/or installed. The rpm listing should show something like:

courier-imap-3.0.8-rh7.build75050506.13

or something similar

Ok there is no UW-IMAP at all. I am sure courier-imap for Plesk is installed because I keep reinstalling it :)

rpm -q uw-imap
package uw-imap is not installed

rpm -q *imap*
package *imap* is not installed

Courier IMAP installed:

courier-imap-3.0.8-rh7.3.build75050128.10

I know IMAP is working right because password changes are reflected and Horde webmail has always been fine.

I disabled ipop3 and restarted xinetd with no luck still
 
rpm -q *imap*
This is not a valid rpm command.

Please do:

rpm -qa |grep 'imap'

to see a complete list of all rpm's containing 'imap' in the name.
 
Originally posted by jamesyeeoc
This is not a valid rpm command.

Please do:

rpm -qa |grep 'imap'

to see a complete list of all rpm's containing 'imap' in the name.

courier-imap-3.0.8-rh7.3.build75050128.10
psa-courier-imap-add-7.5.2-rh7.3.build75050128.10
imap-2001a-10
 
imap-2001a-10
Ok, this is the one which is not *normally* on a Plesk server. Did you install this at some point in the past??

If not, then try removing it and restarting the server just to be sure. I don't know if you may have to do (yet) another re-install of:

courier-imap-3.0.8-rh7.3.build75050128.10
psa-courier-imap-add-7.5.2-rh7.3.build75050128.10

After getting rid of the other one, you may have to reinstall these again.
 
Originally posted by jamesyeeoc
Is your server a Cobalt (or used to be Cobalt Raq) server?

Not at all.

Any idea exactly what services in xinetd should be enabled for mail to work properly?
 
See if you have /etc/xinetd.d/smtp_psa

[root@ns2 xinetd.d]# cat smtp_psa

service smtp
{
socket_type = stream
protocol = tcp
wait = no
disable = no
user = root
instances = UNLIMITED
server = /var/qmail/bin/tcp-env
server_args = -Rt0 /usr/sbin/rblsmtpd -r sbl-xbl.spamhaus.org /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
}
Note: the sbl-xbl.spamhous.org is an optional RBL which I have on this particular server.

Then make sure qmail is running:

ps -ax |grep 'qmail'
(do not use *qmail*)
Mine shows:

[root@ns2 root]# ps -ax |grep 'qmail'
4520 ? S 0:00 qmail-send
4524 ? S 0:00 splogger qmail
4525 ? S 0:00 qmail-lspawn ./Maildir/
4526 ? S 0:00 qmail-rspawn
4527 ? S 0:00 qmail-clean
26900 pts/0 S 0:00 grep qmail
 
Originally posted by jamesyeeoc
See if you have /etc/xinetd.d/smtp_psa

[root@ns2 xinetd.d]# cat smtp_psa

service smtp
{
socket_type = stream
protocol = tcp
wait = no
disable = no
user = root
instances = UNLIMITED
server = /var/qmail/bin/tcp-env
server_args = -Rt0 /usr/sbin/rblsmtpd -r sbl-xbl.spamhaus.org /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
}
Note: the sbl-xbl.spamhous.org is an optional RBL which I have on this particular server.

Then make sure qmail is running:

ps -ax |grep 'qmail'
(do not use *qmail*)
Mine shows:

[root@ns2 root]# ps -ax |grep 'qmail'
4520 ? S 0:00 qmail-send
4524 ? S 0:00 splogger qmail
4525 ? S 0:00 qmail-lspawn ./Maildir/
4526 ? S 0:00 qmail-rspawn
4527 ? S 0:00 qmail-clean
26900 pts/0 S 0:00 grep qmail

My smtp_psa looks good as yours

2164 pts/1 S 0:00 qmail-send
2166 pts/1 S 0:00 splogger qmail
2167 pts/1 S 0:00 qmail-lspawn ./Maildir/
2168 pts/1 S 0:00 qmail-rspawn
2169 pts/1 S 0:00 qmail-clean
18514 pts/2 S 0:00 grep qmail


service smtp
{
socket_type = stream
protocol = tcp
wait = no
disable = no
user = root
instances = UNLIMITED
server = /var/qmail/bin/tcp-env
server_args = /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
 
Excellent

Thank you very much jamesyeeoc
The trick was to disable all the stupid ipop services which I didn't know shouldn't be there.

Even though courier-imap and qmail was shown as started, I did another xinetd reset and then started qmail and courier-imap and now I can send and receive mail just fine.

This has been a really annoying issue and let's say the patience of those paying me was wearing thin

thanks!
 
I too am glad that it is now working, I was about at the end of my rope as well.... :D (but I do love a challenge)
 
Originally posted by jamesyeeoc
I too am glad that it is now working, I was about at the end of my rope as well.... :D (but I do love a challenge)

The moral of the story is apt-get is not very friendly and I should have paid closer attention to what it was doing!

The other one is that jamesyeeoc will help fix anything if you do enough digging :):D
 
Yes, and remember, if you give enough details about your server, then the process would go faster... :D
 
Originally posted by jamesyeeoc
Yes, and remember, if you give enough details about your server, then the process would go faster... :D

Yes, that kind of helps :rolleyes: :D
 
Back
Top