• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • 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.

Bug in Mailman 2.0.13

kevin@

Basic Pleskian
Hello,

I just upgraded from Plesk 7 to 7.5 on FreeBSD and am now getting the following error with mailman:

Bug in Mailman version 2.0.13

We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs.


I checked the mailman logs, but they did not yield anything too useful. Has anyone else experienced this?

Ideas?

Thanks!

Kevin
 
This thread might help. An excerpt from that thread:

I'm running Plesk 7.5.2 also on FreeBSD 4.9, i''ve had the same problems with the web frontend, but solved that with:
/usrl/local/psa/mailman/check_perms -f

But now I've problems with the mail delivery from mailman, any mail send to a mailinglist doesn't show up, and seems to be dissapeared.

I've got it solved:

chmod +x /usr/local/psa/mailman/cron/*

did the trick...
 
Back
Top