[Mailman-Users] transport-mailman and virtual-mailman not updated with new list

Mark Sapiro mark at msapiro.net
Wed Jan 6 17:42:25 EST 2016

On 01/06/2016 02:24 PM, Eggert Ehmke wrote:
> Am Mittwoch, 6. Januar 2016, 13:28:12 schrieb Mark Sapiro:
>> What is important is that if in mailman's directory, you run
>> for list in `bin/list_lists -b`; do
>>  bin/dumpdb lists/$list/config.pck | grep host_name.:
>> done
>> That every listed host_name be in POSTFIX_STYLE_VIRTUAL_DOMAINS
>> Is that the case?
> When I run this command, it first only showed me the domain of my first mailing 
> list. I then discovered in the web gui, that the hostname for the new list was 
> set to the domain of the old list. I changed that in the web gui (where is the 
> corresponding entry in the mailman config?) After that run above command again, 
> and now both domains are listed.

The web admin General Options setting

Host name this list prefers for email.
(Details for host_name)

Is the list's host_name attribute.

The output from the above command should be one line for each list of
the form

    'host_name': 'example.com',

It doesn't identify the list, but each entry corresponds to the
host_name in the web UI.

>> When you run bin/genaliases, is there any output to the terminal? If so,
>> what?
> No output. After running genaliases, data/aliases and data/virtual-mailman 
> have new time stamps. However, only data/aliases has all mailing lists, 
> data/virtual-mailman has only the old list.

OK. Everything seems to be working correctly. It appears that the issue
is with POSTFIX_STYLE_VIRTUAL_DOMAINS in mm_cfg.py. In order for entries
to be generated in data/virtual-mailman (and data/transport-mailman) for
a list, that list's host_name must be in the

Is that the case?

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

More information about the Mailman-Users mailing list