• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

How stop stop mchk

tkalfaoglu

Silver Pleskian
If you accidentally run mchk, your system will be out of commission maybe for hours.
It disables pop3/imap logins and you are stuck. If you ctrl-c it, the logins stay disabled.

So, what is the correct way to get out of this devilish program?

Thanks!
-t
 
Utilities from /psa/admin/(s)bin is internal Plesk utilities and they are not intended for use by clients. Only utilities from /psa/bin/ can be used by clients. Therefore I would like to know why you are using mchk utility so often? What it necessary?
 
I'm using mchk as little as possible - once a year or so. Usually after I forget its major drawback - that it disables IMAP/POP3 while it runs slowly.

This morning when trying to delete a subscription, PLESK 10.4 gave me an error. googling it, I found that someone recommended I ran mchk. Like a fool I ran it around 8:00AM.. After 9AM, it was still running, and I had many angry customers. It finished around 9:45.

Therefore, I was trying to correct a PLESK problem when I created a bigger problem.
Neither was my fault, AFAIC.

Btw, I found a way to speed up parts of "mchk" - just rename spammgr for a while.. It just zips thru the part where it blacklists the same **** for every email address - even if you have personalized spam checking disabled.
 
Maybe it would be better to fix mail problem without mchk running each time? Yes, we know that mchk is very common and effective method, but I believe that many mail problems can be fixed without mchk. Also use options for mchk when it is necessary:

# /usr/local/psa/admin/sbin/mchk --help
Restore settings for all mailboxes.
Usage: /usr/local/psa/admin/sbin/mchk [OPTION]

OPTIONS:
--without-spam restore all settings except for SpamAssassin configuration
--with-spam restore all settings
--spam-only restore only SpamAssassin settings
 
The option I found on the net was something like this:

mchk --domain --domain-name blah.com

which is what I launched. mchk ignored these erroneous parameters, did not display an error message, but instead launched into its work right away. So I was unable to stop it (tried it once - but IMAP/POP3 stayed locked, so I had to-launch it).
These parameters were probably for an older mchk..
 
Back
Top