[Mailman-Users] Problem creating mailing lists via web interface in 2.1.11
It works just fine if I log in as root and use newlist, but if I try to create a new list via the web admin interface, two things happen. First, I get an error, whose text I do not have in front of me (I know, I know, first rule of error reporting, report the exact error, but you probably won't need it when I finish my explanation), and second, the aliases file is not updated, so if a subscriber tries to send a message to the list, they receive an auto-reply telling them user unknown in virtual mailbox table. My question is, why doesn't the web interface create new list feature update the aliases file? Is this a bug or a feature, or is there something I should put into mm_cfg.py to enable this, similar to owners-may-delete-their-own-lists? Thanks in advance. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem creating mailing lists via web interface in 2.1.11
On Wed, Mar 28, 2012 at 9:34 PM, Steve Matzura sm...@noisynotes.com wrote: user unknown in virtual mailbox table. My question is, why doesn't the web interface create new list feature update the aliases file? What aliases file? Exim, for example, doesn't need one at all. There are many MTAs, there are many different ways to configure them to deliver to lists. Is this a bug or a feature, It's a missing feature in your MTA. :-) As I wrote, there are MTAs that can be configured to automatically deliver to mailing lists (eg, Exim is told to look for a $LIST.cfg file, and if that is found, it delivers to | mailman post $LIST or something like that). or is there something I should put into mm_cfg.py to enable this, similar to owners-may-delete-their-own-lists? We likely can help you, but you'll need to tell us exactly what MTA you use, and how it's currently configured. If you are using a OS-distro-provided Mailman, tell us what distro and the full version number of the Mailman package. If you built from source, tell us that. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem creating mailing lists via web interface in 2.1.11
The MTA is postfix. The file in question is /var/lib/mailman/data/aliases which, according to what I've read, is created from aliases.db. The interesting thing is, virtual-mailman *is* updated correctly from virtual-mailman.db while aliases is not. Mailman was installed long before I got here, but I'm assuming it was installed via the standard package installer when Ubuntu was originally built a few years ago. I also recognize I'm not running the latest Ubuntu or Mailman. Here's the perms on those four files: -rw-rw 1 root list 6725 2012-03-28 19:07 aliases -rw-rw 1 list list 12288 2012-03-28 19:07 aliases.db -rw-rw 1 root list 5830 2012-03-28 19:07 virtual-mailman -rw-r- 1 root list 12288 2012-03-28 19:07 virtual-mailman.db On Thu, 29 Mar 2012 01:52:45 +0900, you wrote: On Wed, Mar 28, 2012 at 9:34 PM, Steve Matzura sm...@noisynotes.com wrote: user unknown in virtual mailbox table. My question is, why doesn't the web interface create new list feature update the aliases file? What aliases file? Exim, for example, doesn't need one at all. There are many MTAs, there are many different ways to configure them to deliver to lists. Is this a bug or a feature, It's a missing feature in your MTA. :-) As I wrote, there are MTAs that can be configured to automatically deliver to mailing lists (eg, Exim is told to look for a $LIST.cfg file, and if that is found, it delivers to | mailman post $LIST or something like that). or is there something I should put into mm_cfg.py to enable this, similar to owners-may-delete-their-own-lists? We likely can help you, but you'll need to tell us exactly what MTA you use, and how it's currently configured. If you are using a OS-distro-provided Mailman, tell us what distro and the full version number of the Mailman package. If you built from source, tell us that. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
