Unable to set autoresponder

[EgonP]

After I upgrade to Plesk 9.2.1 Plesk, when i set an autoresponder i get this error message:


ERROR: PleskUtilException

mailmng failed: Unable to set autoresponder for user@domain.ext.See log for details
Some errors occured. See log for details

0: class.MailManager.php:242
MailManager::execWithException(string 'smart_exec', string 'mailmng', array, array, string 'lst')
1: class.MailManager.php:274
MailManager->callMailManager(string 'set-autoresponder', array)
2: class.MailManager.php:531
MailManager->setAutoresponder(string 'domain.ext', string 'info', array, array)
3: MailNameAutoResponders.php:166
MailNameAutoResponders->_setListStatus(boolean true)
4: MailNameAutoResponders.php:97
MailNameAutoResponders->enable()
5: mail_name_responders.php:75

I have try to execute this command
/usr/local/psa/admin/sbin/mchk --with-spam

==> Checking for: mail_spam_restore... ok
==> Checking for: mailsrv_conf_init... ok
==> Checking for: mail_mailbox_restore... ok
==> Checking for: mailsrv_entities_dump... ok
==> Checking for: mail_admin_aliases... ok
==> Checking for: mail_auth_dump... ok
==> Checking for: mailman_lists_dump... ok
==> Checking for: mail_responder_restore... ok
==> Checking for: mail_drweb_restore... ok
==> Checking for: mail_kav_restore... ok
==> Checking for: mail_spf_restore... ok
==> Checking for: mail_dk_restore... ok
==> Checking for: mail_grey_restore... ok


... but the error message remains and the autoresponder is not executed.

Any ideas how to fis this problem ?

Thank you for help

 

[EgonP]

Hi,
everyone can suggest me how to fix this problem ???

Thank you

 

[EgonP]

with the Plesk Update to 9.2.2 the problem was solved.

 

[morgan.goose]

Something I found

Make sure you have this file with these permissions:

-r-xr-x--- 1 root popuser 33032 Apr 14 09:42 /usr/local/psa/handlers/hooks/autoresponder


It was missing on a plesk 9.3.0 box I have, but I grabbed a copy from a 9.2.3 machine and after restarting qmail, and toggling the autoresponders on the account, for good measure, they were up and running again. All with out the error messages.