If you trust all your users that they know what they do ..., you could give them write privileges to their own mailbox directory at the server share. Pmail/Mercury are managing the autoreply function by a simple text file AREPLY / AREPLY.PM. In case the autoreply function is switched off, the placed file reads AREPLY. And in case you activate the autoreply in Pegasus Mail, the file will be renamed in AREPLY.PM.
The file itself contains the autoreply text of the user (I'm out of office until ... bla bla bla), and could be edited by simple text editors like wordpad or notepad.
Your users could simply rename this file to activate or deactivate the autoreply function. Mercury would immediately recognize and read out this file without any restarts.
Is not a smart solution but a workaround.
In the meantime we are (20 users) mostly using Thunderbird, connected by IMAP to Mercury, but have Pmail still installed for such reasons, activating of autoreplies, bouncing of spam messages to spamhalter account, etc.
If you trust all your users that they know what they do ..., you could give them write privileges to their own mailbox directory at the server share. Pmail/Mercury are managing the autoreply function by a simple text file AREPLY / AREPLY.PM. In case the autoreply function is switched off, the placed file reads AREPLY. And in case you activate the autoreply in Pegasus Mail, the file will be renamed in AREPLY.PM.
The file itself contains the autoreply text of the user (I'm out of office until ... bla bla bla), and could be edited by simple text editors like wordpad or notepad.
Your users could simply rename this file to activate or deactivate the autoreply function. Mercury would immediately recognize and read out this file without any restarts.
Is not a smart solution but a workaround.
In the meantime we are (20 users) mostly using Thunderbird, connected by IMAP to Mercury, but have Pmail still installed for such reasons, activating of autoreplies, bouncing of spam messages to spamhalter account, etc.