Skip to main content

transfer tool failed mailman lists

Comments

8 comments

  • 24x7server
    Hello, Can you please let me know what error are you getting with the transfer tool ? Please post here so that we can assist you on this.
    0
  • Goddard
    I figured it out. If you run into this problem just copy the 3rdparty/mailman/archive and /lists folders. This will update cpanel. It is to bad it didn't work in Cpanel.
    0
  • cPanelMichael
    Hello :) I'm happy to see the issue is now resolved. Did you notice any specific error messages when the mailman lists failed to copy over? Thank you.
    0
  • Patricio Anguita
    Hello :) I'm happy to see the issue is now resolved. Did you notice any specific error messages when the mailman lists failed to copy over? Thank you.

    Same thing happened to me. The issue in my case was that when a suspended account is transferred, and then un-suspended on the destination server, mailing lists doesn't become active. I think this is a bug, because the archives did transfer without problems. Regards,
    0
  • Goddard
    I don't remember if I did.
    0
  • cPanelMichael
    The issue in my case was that when a suspended account is transferred, and then un-suspended on the destination server, mailing lists doesn't become active.

    Could you let us know the version of cPanel installed on the destination server when this happens? Thank you.
    0
  • Goddard
    At the time it was the latest version of cpanel with the latest stable version of cent os 7.
    0
  • cPanelMichael
    Same thing happened to me. The issue in my case was that when a suspended account is transferred, and then un-suspended on the destination server, mailing lists doesn't become active. I think this is a bug, because the archives did transfer without problems.

    Internal case CPANEL-3208 is open to address an issue where transferring or restoring a suspended account results in a broken/unsuspended account on the destination server. Suspending and unsuspending the account is the temporary workaround. You can monitor our change log for this case number at:
    0

Please sign in to leave a comment.