• 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.

issues with mailman email address [email protected]

D

dthoward

Guest
Plesk 7.5.2 on Redhat 9 ... GoDaddy ...

Mailman is working but ... noticed that the site mail list "mailman" is not functioning. That is to say, messages sent to [email protected] bounce.

On a domains main mail list web page there is this address reference ... as I said, mail to this address bounces.

"Send questions or comments to [email protected]."

Any ideas !!! Thanks !!! Todd
 
Here's what I have found and what I have sent to GoDaddy

Here's an update ... please let me know what progress has been made on your end ??? THanks

the virtual host entry lists.xxx.yyy.zzz.secureserver.net created by Plesk is not possible in the BlueRazor Hosting environment ... what is the correct setting ???

the Plesk initialization process does not configure the qmail entries to the site list "mailman" ... is there a fix ???

the site list "mailman" does not show up on the list of maillists within the Plesk control panel ... it should, how can I manage this list ??? for example by default it has a public archive and anyone can subscribe, not safe defaults ...

and since mailman is not virtual, what is the proper procedure to correct email address references like "[email protected]" when the "mailman" site list is at [email protected] ??? Plesk should have this configured (or at least documentation to list any manual configuration steps), the admin shouldnt need to do it ...

I realize that a Virtual Hosting account needs to be supported by the purchaser ... but these are bugs, I purchased the Plesk service to deal with a portion of the admin tasks, its broken ...
 
Back
Top