• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.

Forwarded to devs Mailman list migration: It notifies everyone even if list settings say "do not notify"

tkalfaoglu

Silver Pleskian
Username: tkalfaoglu

TITLE

Mailman list migration: It notifies everyone even if list settings say "do not notify"

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

centos 8 obsidian latest

PROBLEM DESCRIPTION

When the migration tool is used, it migrates the lists from one server to the other..
From the looks of it, it does not migrate the settings of the list before starting adding users to it.

This causes newsletter-type mailing lists with thousands of users to get "you have been added to the list" emails, EVEN if the mailmanlist settings at the old server says "do not notify users when added/removed".

This causes massive unnecessary email load that upsets users.

STEPS TO REPRODUCE

migrate a mailman list from one server to another.. both plesk..

ACTUAL RESULT

each user gets an email saying they are added

EXPECTED RESULT

NO emails should be sent.. PLESK first should migrate the list settings, THEN it should start adding users.. Preferably in BULK, not one by one as it does not.

ANY ADDITIONAL INFORMATION

This bug exists for many years now. I was burned by it during my PREVIOUS migration as well, about 5 years ago

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Back
Top