• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Mailman error?

R

rbhaydon

Guest
Here's a challenge for all you Mailman/Python experts:

When a domain customer goes in to click on the web interface for modifying the mailing list (that little gear icon listed to the right of each mailing list), they get the error at the bottom of this message.

Is it a "lock file" problem?

Any help would be appreciated.

Thanks,
Bruce


----------------------------------------------------------------------------------
Bug in Mailman version 2.1.5

We're sorry, we hit a bug!

If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks!
Traceback:

Traceback (most recent call last):
File "/var/mailman/scripts/driver", line 87, in run_main
main()
File "/var/mailman/Mailman/Cgi/admin.py", line 72, in main
mlist = MailList.MailList(listname, lock=0)
File "/var/mailman/Mailman/MailList.py", line 128, in __init__
self.Load()
File "/var/mailman/Mailman/MailList.py", line 593, in Load
dict, e = self.__load(file)
File "/var/mailman/Mailman/MailList.py", line 559, in __load
fp = open(dbfile)
IOError: [Errno 13] Permission denied: '/var/mailman/lists/tableofficers/config.pck'



Python information:

Variable Value
sys.version 2.2.3 (#1, Oct 26 2004, 17:11:32) [GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-47)]
sys.executable /usr/bin/python
sys.prefix /usr
sys.exec_prefix /usr
sys.path /usr
sys.platform linux2
 
Thank-you for the fix...I must admit, that would take a fair bit of digging for me to figure that out!

What would cause the permissions to corrupt? Was it doing a "Red Hat Update" that updated the package?

Thanks again :)

Bruce
 
Back
Top