[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 315
  • Last Modified:

Qmail will not maintain connection.

We have a Qmail server here and it used to autmotically push messages to all IMAP users, but as of 2 nights a go, this feature has stopped our Mac users and our Support System are no longer receiving messages and they must click on Send/Receive to get their messages. On the Macs there's an option to maintain connections and the issue is fixed there, but our Support System doesn't have that feature and the Qmail server must push messages to it. Does anyone know what that feature is called or how to re enable it?

  • 2
1 Solution

It sounds to me like qmail is not "pushing" messages, but is simply delivering to the Maildir folders for each user.  The IMAP daemon is the component that is going to handle any announcement to the users.

Chances are your FAM daemon died and is no longer running.  If you look at your mail logs (check /var/log/mail, /var/log/maillog, /var/log/messages) you'll see a number of errors about "FAM monitoring unavailable" or similar.  You may be able to restart FAM with an init script, e.g. "/etc/rc.d/init.d/fam restart" (may be famd vs. fam), or it may be called from xinetd in which case xinetd is probably dead or having problems.
jumper4000Author Commented:
Well there was something in init.d called imapd and once i started that everything started working. But Thanks for your help. I'll acceept the answer.
If IMAP wasn't running at all, then your Mac clients must've been falling back to POP3.  This is an unusual but convenient feature.

For RedHat, you may wish to "chkconfig --list imapd"; use the command "/sbin/runlevel" to determine your current runlevel (second number is current, first number is previous).  The current runlevel should show an ON status for imapd.  E.g.:

imapd           0:off   1:off   2:on    3:on    4:on    5:on    6:off

This would mean that imapd will turn on in runlevels 2, 3, 4 and 5.  If your current runlevel is any of those, you're fine.  Standard runlevels are 3 and 5 for network-enabled systems.

If it shows as being on, but stopped working, this indicates the IMAP daemon crashed.  There may be clues about why in the logs... try:
grep imapd /var/log/* | grep -v -e Login -e Logout -e "imap service init"

That may yield an error message which would indicate what failed.  If the problem occurs again in the future, a more thorough investigation is warranted, and upgrading imapd as a corrective measure.

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now