mailman archives bug

[freeranger]

Hi,

I've been chatting to the mailman list and there is a problem that seems to exist only in the CPanel version of mailman 2.1.2.

If you have a mailing list called "test" with private archives set, the mailing list location is, correctly,
http://clientdomain1/mailman/<whatever>/test_clientdomain1/

and the archives are located at:
http://clientdomain1/mailman/private...clientdomain1/

if however, the archives are set to public, the location is:
http://hostingproviderservername/pip...clientdomain1/

As a hosting reseller, this is not good because it exposes the under hosting provider to my client.

One of the mailman guys, Richard, has independently confirmed this behaviour only in the CPanel version.

Richard seem to think that:
"My guess is that the CPanel's own scripts are used by CPanel in place of the standard Mailman scripts to create new lists and that these scripts set the list web_page_url and host_name attributes directly but without adding any matching add_virtualhost() calls to mm_cfg.py to
expand the VIRTUAL_HOSTS dictionary."

The VIRTUAL_HOSTS stuff was added in 2.1.x, so may have been missed when you guys updated your 2.0.x build.

I would appreciate it if you could look into this issue and confirm or deny that this is the problem.

If this is the problem, would you have any idea when you can release a fix for it?

thank you for your kind attention,

Tony

cPanel.net Support Ticket Number:

[freeranger]

Hi,

Has anyone at CPanel picked up on this yet?

Is it a "known" issue that is already been addressed?

thanks.

cPanel.net Support Ticket Number:

[dhost]

Any resolution or additional information regarding this -- we are also having this problem.

cPanel.net Support Ticket Number:

[freeranger]

Well nobody at cpanel has replied, or mailed me privately, so I assume they just don't care.

This is in start contrast to the mailman guys who were very helpful in trying to track the problem....

cPanel.net Support Ticket Number:

[dhost]

In addition to the public archives being located at:
http://hostingproviderservername/pi..._clientdomain1/

The page returns a 404 error unless the viewer manually types "http://clientdomain/pi..._clientdomain1/ [client actual path]. Is there a script available that will not override the standard Mailman script.

cPanel.net Support Ticket Number:

[TechGuy]

Anyone?

[mrjcleaver]

We also want this fixed.

[PeteC]

Originally posted by freeranger
Well nobody at cpanel has replied, or mailed me privately, so I assume they just don't care.

This is in start contrast to the mailman guys who were very helpful in trying to track the problem....

cPanel.net Support Ticket Number:

I am interested in this as well. But you need to put these requests in as support tickets. cPanel staff read all the support tickets but they do not always read and respond to forum posts.

[freeranger]

Not being a "direct" licensee of cpanel, I could not do so - but my provider told me they submitted it, but still nothing...

[Solokron]

I am interested in this as well.

[baohx]

I'm having this problem also. Anyone know where to fix it?

[baohx]

Fixed it myself.

In usr/local/cpanel/3rdparty/mailman/Mailman/Defaults.py
Find:
PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/pipermail/%(listname)s'

Change to:
PUBLIC_ARCHIVE_URL = '/pipermail/%(listname)s'

Then it won't include the box's main hostname. Hopefully this won't cause problems.

[freeranger]

That's great - though unfortunately the next cpanel update will probably replace your modded file, so you have to remember to reapply the change every time

Maybe you could submit it to the cpanel guys and they might actually fix it, since you've done the hard work for them?

cheers.

[casey]

Submit it to bugzilla.cpanel.net

[baohx]

Submitted to bugzilla:
http://bugzilla.cpanel.net/show_bug.cgi?id=646