On 7/11/14 6:26 PM, Mark Sapiro wrote:

On 07/10/2014 11:13 AM, Bill Christensen wrote:

...

The setup: Moving from Mac OS 10.8.5 to 10.9.4, on a MAMP setup, everything installed using MacPorts. Upgrading MySQL, PHP, and PostgreSQL in the process. MacPorts hasn't upgraded Mailman beyond 2.1.13 (a separate issue I may want to address later). Right now I'm doing test runs on a backup to make sure all the pieces and parts will work properly when I do the update for real. I have all the other parts in place but I'm now getting the dreaded group mismatch error from Mailman.

When I first installed everything I installed Mailman before PostgreSQL, and the feedback told me that I needed either to compile Mailman as --with-mail-gid=postgresql or change the mail server (standard Mac installation of Postfix) to run as group _mailman. I uninstalled and reinstalled Mailman and now it's telling me that I need to compile Mailman as --with-mail-gid=staff.

I changed the setting in MacPorts' file from --with-mail-gid=_mailman to --with-mail-gid=staff and attempted to reinstall, but I'm getting an error that it's "Unable to open port - invalid command name '--with-mail-gid=staff'".

Anyone have any ideas of where to go from here?

This is really an Apple issue, at least the way you're going about it. Have you asked Apple?

However, you say you (only) changed --with-mail-gid=_mailman to --with-mail-gid=staff, and whereas the install worked with --with-mail-gid=_mailman, after the change it complains "invalid command name '--with-mail-gid=staff'".

I really know nothing about the OS X server Mailman or even where you made that change, but in 'standard' Mailman that would be an option to configure and configure would never make that exact complaint. Are you sure you didn't introduce an extraneous newline or similar that would cause --with-mail-gid=staff to be interpreted as a command rather than an option to a prior command?

Figured it out. It was syntax problems:

First, I had added a comment as a note to myself within the configure_args block, so that if I needed to revert I'd have the exact line. I should have known not to put it in the block.

After I moved the comment to before the block, I left the comment with a trailing "\", as that was at the end of the original line. Unfortunately, that threw things off also. Removing the "\" got the installation working correctly and it's now up and running.

On 07/15/2014 09:55 AM, Sajan Parikh wrote:

What's going to be the best way to configure all the web interfaces to run on a domain like lists.domain.com, but have all the list addresses by domain.com?

I couldn't find anything about this sort of setup in the docs. Maybe I didn't look hard enough?

I'm confused. If you want a single web domain and a single email domain, this is the usual configuration. Just set the following in mm_cfg.py

DEFAULT_URL_HOST = 'lists.domain.com' DEFAULT_EMAIL_HOST = 'domain.com' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

Then run Mailman's

bin/withlist -a -r fix_url

To update the lists' web_page_url and host_name. See the FAQs at <http://wiki.list.org/x/mIA9> and <http://wiki.list.org/x/gIA9>.

I assume, I'll just have to change the aliases and forward the different domains to the lists, but will Mailman actually accept this?

Do you mean that you will have multiple domains of the form lists.domain.com for web access and domain.com for email.

If so, you will need to put additional

add_virtualhost('lists.otherdomain1.com', 'otherdomain1.com') add_virtualhost('lists.otherdomain2.com', 'otherdomain2.com')

lines following the

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

line in mm_cfg.py and run commands like

bin/withlist -r fix_url list1 -u lists.otherdomain1.com

for each list with the appropriate -u web_host option for the list.

In any case, aliases use only the list name and probably don't need to be changed, but if some of these domains are non-local, you may need virtual mappings.

In order to advise you further, I would need to know more about your MTA configuration and how it delivers to Mailman. Your mention of lists.domain.com makes me think you might be using a debian/ubuntu package. If so, and if you are using postfix_to_mailman.py, see the FAQ at <http://wiki.list.org/x/EYDt>.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan