This is the area for a general support questions, discussions and information that you can read and share. Post your experiences, stats and tricks and tips that are not covered elsewhere. Remember, for questions please search the FAQ first, as your question may already be answered.
Moderators: wizard, magicspam
- Posts: 1
- Joined: Mon Jan 22, 2018 12:46 am
Here is the situation:
1. Extension is installed and is working fine:
Code: Select all
# plesk bin extension --enable magicspam
The extension's status was successfully updated.
# service magicspam-daemon status
Loaded: loaded (/etc/systemd/system/magicspam-daemon.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2018-01-22 13:26:00 +07; 1h 26min ago
# service magicspam-milter status
Loaded: loaded (/etc/systemd/system/magicspam-milter.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2018-01-22 13:26:02 +07; 1h 26min ago
2. However, after removal files in /etc/systemd/system/ are left behind:
Code: Select all
# plesk bin extension --uninstall magicspam
The extension was successfully removed.
# ls -l /etc/systemd/system/magicspam*
-rw-r--r-- 1 root root 272 Nov 16 00:42 /etc/systemd/system/magicspam-daemon.service
-rw-r--r-- 1 root root 288 Nov 16 00:42 /etc/systemd/system/magicspam-milter.service
3. Services are in 'enabled' but 'failed' status, so they are generating errors on every reboot because magicspam-daemon and magicspam-milter failed to start, because there is no magicspam installed.
It is actual for systemd-based, all is removed properly from /etc/init.d/.
- Posts: 1188
- Joined: Tue Oct 28, 2008 2:27 pm
Thank you for your post.
We have forwarded the information provided to our development team, and they will be working on fixing the packaging issue for the next release of MagicSpam.
Please let us know if you have any other questions.
-- MagicSpam Support Team --
Who is online
Users browsing this forum: No registered users and 2 guests