• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Issue Migration taking exponentially long because of listmng

tkalfaoglu

Silver Pleskian
Today I am migrating an Onyx server to another new Onyx Server.

The main holdup is the listmng processing. Mailman lists with thousands of members are being added to the new server one by one.
# ps ax|grep listmng
33004 ? S 0:00 /usr/local/psa/admin/bin/listmng add-member bla_bla bla.info [email protected]

two seconds later, same list, another user.
No wonder the migration has been going on for 8 hours now!

This needs to be done in bulk -- not one user at a time. This might be alright for small mailman installations but I have many lists with TENS OF THOUSANDS users.
 
Furthermore, it sends a "[email protected] was added to the list" to the admin, AND "welcome to the list!" to [email protected] to EACH member.
I don't think these are necessary/useful during a migration.

Finally, the THIRD glitch with mailman: NOQUEUE: reject: RCPT from localhost[::1]: 454 4.7.1 <[email protected]>: Relay access denied;
for every mail being sent out. Apparently 127.0.0.1 does not get automatically whitelisted when PLESK is installed.
 
What I did, is that I hacked into add_members program of mailman and DISABLED both mails from getting sent out..
I will restore it when the migration is complete.. I am also going to whitelist 127.0.0.1 now using the PLESK interface. I didn't do that before because I did not want tens of thousands of "welcome to the list" emails being sent out.
 
Last edited:
Followup: the lists migration never went correctly. So I followed PLESK guides to manually copy the lists over.
Likewise DNS migration also caused problems, and it was not until I clicked on APPLY TEMPLATE at the new server for each domain that those domains started working..
 
Back
Top