Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

MailMan Migration Problem

Discussion in 'E-mail Discussion' started by webr00t, Dec 8, 2007.

  1. webr00t

    webr00t Member

    Joined:
    Aug 15, 2007
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    51
    I just migrated a client site from a dedicated Plesk server to an account on my WHM/cPanel server. I'll spare you the gory details, except the one remaining chunk of gore: some minor problems with the client's mailman list.

    In migrating the list, I set up a new mailing list via cPanel's "Mailing Lists" feature. I gave it an identical name and let it establish. Of course, cPanel's Mailman modifications forced the list directory and other references to be renamed original_listname_domain.com (where it had previously just been original_listname).

    Next, I simply copied the configuration files (config.pck) from the client's server to the /usr/local/cpanel/3rdparty/mailman/lists/original_listname_domain.com directory on my server.

    This seems to have re-established all configurations settings properly. But now when I try to subscribe an address to my client's mailing list, I get a confirmation email with a link such as:

    http://lists.domain.com/mailman/confirm/original_listname_domain.com/ffa2444ac2cdaee10b4f746688edd9c8e18524cf

    If I use that link, Mailman responds:

    Bad confirmation string
    No such list original_listname_domain.com


    if I remove _domain.com from that string, I get:

    Bad confirmation string
    Invalid confirmation string: ffa2444ac2cdaee10b4f746688edd9c8e18524cf.
    Note that confirmation strings expire approximately 3 days after the initial subscription request. If your confirmation has expired, please try to re-submit your subscription. Otherwise, re-enter your confirmation string.


    Meanwhile, if I follow the alternative confirmation instructions in the email, and I send an email to the confirmation address with the confirm
    Code:
    [/I] line in it, I get a "mailformed address" response from the MAIL SERVER, indicating that [email]original_listname@domain.com[/email] doesn't exist (as an email address, nevermind as a mailman list). Of course, that address does not exist in my cPanel email addresses or forwarders list, but it should have been created in exim, I believe, when I created the list.
    
    Anyway, I'm hoping others have figured out solutions to these problems. I know the normal Mailman support community is less than eager to help with problems related to cPanel's modifications of Mailman.
    
    Thanks in advance!
     
  2. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,216
    Likes Received:
    10
    Trophy Points:
    313
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
  3. webr00t

    webr00t Member

    Joined:
    Aug 15, 2007
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    51
    Oh, man

    I wish I knew about that weeks ago. Sounds like you guys could have saved me lots of hassle.

    I did figure out these problems, and seemingly all others related to the migration, as well. Pretty proud of myself :cool:

    This actually turned out to be something freakish. After I switched nameservers at my client's registrar, domain.com was resolving to my server, but lists.domain.com was still pointing to his for about a day. Meanwhile, I assumed that cPanel mailman installer had created a lists. subdomain, but it was his list config that was pointing confirm links to that address. So, unbeknownst to me, for a whole day I was trying to confirm subscriptions to a list called listname_domain.com on a Plesk server that had no use for _domain.com and thus did not recognize it!

    The email problem is stranger still, but easier to explain. The confirmation email includes this line:

    Or include the following line -- and only the following line -- in a
    message to listname-request@domain.com:


    My Mozilla Thunderbird client inexplicably tries to include the trailing : in the outgoing email address, but of course it's nearly invisible in the SMTP error message calling it mailformed. I found that one before I lost too much hair, though.
     
Loading...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice