Articles in this section

After removing mailman as a Plesk component, services stay up.

Vincent Lauton
Updated
Plesk for Linux kb: technical

Applicable to:

  • Plesk for Linux

Symptoms

After removing mailman3 as a Plesk component, its services mailman3.service and mailman3-web.service stay loaded, active and running

Cause

Plesk bug #PPPM-14815 which will be fixed in a future update.

To check if it has been fixed already, see the Plesk release log: Change Log for Plesk Obsidian

Resolution

As a workaround:

  1. Connect to the server via SSH

  2. Stop and disable mailman services manually:

    # systemctl stop mailman3 mailman3-web && systemctl disable mailman3 mailman3-web

Was this article helpful?

Comments

3 comments
Date Votes
  • Avatar
    Larry Nedry

    After running these commands, mailman3-web still has active cron jobs.

    0
  • Avatar
    stuart broad

    Hi, Vincent

    After removing Mailman 3, its services may remain running. As a workaround, stop and disable them manually: systemctl stop mailman3 mailman3-web && systemctl disable mailman3 mailman3-web.

    0
  • Avatar
    larry mcelwain

    If Mailman has been removed as a Plesk component but its services are still running, it's possible that the service packages or systemd service entries were not fully removed during the uninstall process. I'd recommend checking the active Mailman-related services, reviewing startup configurations, and verifying whether any dependencies are keeping them alive. A restart of Plesk services or the server may also help confirm whether they're still configured to start automatically.

    0

Please sign in to leave a comment.