Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1019
  • Last Modified:

What are the processes Qmail-local.mov and qmail-queue.mov?

What are the processes  Qmail-local.mov and qmail-queue.mov?

Thanks
0
VMWARE
Asked:
VMWARE
1 Solution
 
Daniel McAllisterPresident, IT4SOHO, LLCCommented:
First, understand that QMail is a "multi-threaded" mail system... that means that there isn't one "monolithic" program that "does it all" (like sendmail), instead there are several smaller ("specialized") processes that do the work.

When a message arrives via the SMTP protocol (whether on port 25, 587, 465, or some other port), it has to be "parsed" for recipients -- that is, "where to I deliver this message". The result of this parsing is that the message is QUEUED for delivery -- either to local recipients (domains that are serviced by THIS server), or remote recipients (domains that are serviced by another server -- you'll probably use DNS MX records to discover where that server is and use SMTP to deliver it there). The ACTUAL sending of the message isn't done here, rather it is put into a QUEUE (usually in /var/qmail/queue!) where OTHER processes detect its presence and then process it.

The QMail Queue has several parts, but the MAIN ones are:
  mess  - contains the actual message body (regardless of WHERE the message is going to be delivered -- and especially regardless of how many recipients there are)
  local  - contains the e-mail addresses of local recipients of the message
  remote - contains the e-mail addresses of remote recipients of the message

AGAIN, separate processes monitor the queue for the presence of local- and remote-bound messages. As each message is delivered (local messages are copied into the appropriate user's mailbox, remote messages are delivered via SMTP).  

The two routines you're asking about are the routines the actually move message contents OUT of the queue for local and remote messages (respectively).

The only reason you SHOULD be aware of these processes is if they break... The only time *I* have ever heard of them breaking was in a PLESK distribution that was fixed in 2008 where it didn't allow the process enough RAM to operate, so it would crash repeatedly.

So, if this is the issue, update PLESK!

I hope this explains, and hopefully helps!

Dan
IT4SOHO
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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