Re: [Mailman-Users] Virtual domain support
Hi Mark, re multiple installs, On Mon, 5 Oct 2009, Mark Sapiro wrote: The post at http://mail.python.org/pipermail/mailman-users/2004-June/037443.html (linked from the FAQ at http://wiki.list.org/pages/viewpage.action?pageId=4030604) has good information. I don't thing there's anything better collected in one place. I'm now working through this and have hit a bit of a problem. The post in question reads as follows: Where thing may get more complicated is setting up your local MTA to support virtual hosts. For instance, aliases generated by the per-host copies of $per-host-prefix/bin/newlist will generate alias definitions that pipe to the correct per-host instance of the Mailman delivery agent script but getting your MTA to recognise the aliases belong to one host rather than another is not something I am familiar with. This would appear to be the sticking point. The aliases file doesn't generate fully-qualified Email addresses, only local parts. How do I ensure that a message to annou...@foo.com doesn't go to annou...@bar.org? This must be doable, because if it's not, then this defeats the whole point of doing this in the first place. Presumably I need to do this in postfix/main.cf somehow but I'm at a loss as to how to do this. Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
Geoff Shang wrote: This would appear to be the sticking point. The aliases file doesn't generate fully-qualified Email addresses, only local parts. How do I ensure that a message to annou...@foo.com doesn't go to annou...@bar.org? This must be doable, because if it's not, then this defeats the whole point of doing this in the first place. Presumably I need to do this in postfix/main.cf somehow but I'm at a loss as to how to do this. Not sure if this will help you or not, but I'll share anywhere ... I have a multi setup for mailman to host multiple domains. All my list domains are configured as 'lists.$domain', for example 'lists.yeehaw.net'. My mailman installations all go under /home/mailman/lists.$domain I don't know how this is done in postfix, but in sendmail I have the following: = /etc/mail/aliases/$domain-aliases mailman-lists.$domain \ |/home/mailman/lists.$domain/mail/$domain-mailman post mailman mailman-admin-lists.$domain:\ |/home/mailman/lists.$domain/mail/$domain-mailman admin mailman mailman-bounces-lists.$domain: \ |/home/mailman/lists.$domain/mail/$domain-mailman bounces mailman mailman-confirm-lists.$domain: \ |/home/mailman/lists.$domain/mail/$domain-mailman confirm mailman = /etc/mail/virtusertable mail...@lists.$domain mailman-lists.$domain mailman-ad...@lists.$domainmailman-admin-lists.$domain mailman-boun...@lists.$domain mailman-bounces-lists.$domain mailman-conf...@lists.$domain mailman-confirm-lists.$domain This ensures that an incoming e-mail to say for example 'mailman-ad...@lists.$domain' gets rerouted to 'mailman-admin-lists.$domain' which the alias then expands in to '|/home/mailman/lists.$domain/mail/$domain-mailman admin mailman' This allows one to have various mailman@'various domains' going to the same server through the same MTA without it going nutso. Now you may be wondering why I renamed the 'mailman' binary to '$domain-mailman'. That's because of permissions within sendmail. Any binary that is going to be sending stuff out needs to be allowed by sendmail, and since I have multiple installations of mailman, in different paths, you can't just tell sendmail it's called 'mailman'. It will get utterly confused when the various lists are trying to send something out. So, by renaming each one to their respective $domain, it keeps sendmail from going bonkers. In my /usr/adm/sm.bin/ I have various symlinks to $domain-mailman which link back to /home/mailman/lists-$domain/mail/$domain-mailman Cheers -- W | It's not a bug - it's an undocumented feature. + Ashley M. Kirchner mailto:ash...@pcraft.com . 303.442.6410 x130 IT Director / SysAdmin / Websmith . 800.441.3873 x130 Photo Craft Imaging . 2901 55th Street http://www.pcraft.com . . .. Boulder, CO 80301, U.S.A. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
On Wed, 7 Oct 2009, Ashley M. Kirchner wrote: Geoff Shang wrote: This would appear to be the sticking point. The aliases file doesn't generate fully-qualified Email addresses, only local parts. How do I ensure that a message to annou...@foo.com doesn't go to annou...@bar.org? [snip] I have a multi setup for mailman to host multiple domains. All my list domains are configured as 'lists.$domain', for example 'lists.yeehaw.net'. My mailman installations all go under /home/mailman/lists.$domain I don't know how this is done in postfix, but in sendmail I have the following: = /etc/mail/aliases/$domain-aliases mailman-lists.$domain \ |/home/mailman/lists.$domain/mail/$domain-mailman post mailman mailman-admin-lists.$domain:\ |/home/mailman/lists.$domain/mail/$domain-mailman admin mailman Ok but how do you get Mailman to produce alias tables that look like that? Or don't you? Mine only have the list address part, not the fully qualified list address. Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] missing list!
Hello guys.. one of my lists is missing !! I'm getting this : ./list_members list1 No such list: list1 0 ./list_members list2 477 ./list_members list3 483 ./list_members list4 442 when running : bin/list_lists I get this error: ./list_lists Traceback (most recent call last): File ./list_lists, line 122, in ? main() File ./list_lists, line 94, in main mlist = MailList.MailList(n, lock=0) File /usr/lib/mailman/Mailman/MailList.py, line 130, in __init__ self.Load() File /usr/lib/mailman/Mailman/MailList.py, line 644, in Load raise Errors.MMCorruptListDatabaseError, e Mailman.Errors.MMCorruptListDatabaseError: [Errno 2] No such file or directory: '/var/lib/mailman/lists/dailymail/config.db.last' HELP!! Thanks _ Windows Live: Keep your friends up to date with what you do online. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_1:092010 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
Geoff Shang wrote:
On Wed, 7 Oct 2009, Ashley M. Kirchner wrote:
I have a multi setup for mailman to host multiple domains. All my list
domains are configured as 'lists.$domain', for example 'lists.yeehaw.net'.
My mailman installations all go under /home/mailman/lists.$domain
I don't know how this is done in postfix, but in sendmail I have the
following:
= /etc/mail/aliases/$domain-aliases
mailman-lists.$domain \
|/home/mailman/lists.$domain/mail/$domain-mailman post mailman
mailman-admin-lists.$domain:\
|/home/mailman/lists.$domain/mail/$domain-mailman admin mailman
Ok but how do you get Mailman to produce alias tables that look like that?
Or don't you? Mine only have the list address part, not the fully
qualified list address.
For Postfix integration, you need to do a few things.
Consider only the one mailman instance for the domain example.com. The
others will be analagous.
in mm_cfg.py, add
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['example.com']
This will cause mailman to also write data/virtual-mailman with entries
like
l...@example.comlist
list-ad...@example.com list-admin
...
in addition to data/aliases with entries like
list: |path/to/wrapper post list
list-admin: |path/to/wrapper admin list
...
for each list. The data/virtual-mailman(.db) is analagous to Ashley's
/etc/mail/virtusertable.
There is still a problem in that there is a potential list name
conflict, so to resolve that, you need to make a patch (see attached
Postfix.patch.txt) to Mailman/MTA/Postfix to make virtual-mailman and
aliases look like
l...@example.comlist.example.com
list-ad...@example.com list-admin.example.com
...
and
list.example.com: |path/to/wrapper post list
list-admin.example.com: |path/to/wrapper admin list
...
Then you need the following in Postfix's main.cf
alias_maps = ...
hash:/path/to/example.com's/data/aliases
virtual_alias_domains ... example.com
virtual_alias_maps = ...
hash:/path/to/example.com's/data/virtual-mailman
And probably also if you don't have them anyway
recipient_delimiter = +
unknown_local_recipient_reject_code = 550
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--- f:/test-mailman-2.1/Mailman/MTA/Postfix.py 2008-08-22 15:18:57.0
-0700
+++ f:/test-mailman/Mailman/MTA/Postfix.py 2009-10-07 17:24:52.21875
-0700
@@ -102,14 +102,16 @@
if mlist is None:
return
listname = mlist.internal_name()
+hostname = mlist.host_name
fieldsz = len(listname) + len('-unsubscribe')
# The text file entries get a little extra info
print fp, '# STANZA START:', listname
print fp, '# CREATED:', time.ctime(time.time())
# Now add all the standard alias entries
for k, v in makealiases(listname):
+qname = '%s.%s:' % (k, hostname)
# Format the text file nicely
-print fp, k + ':', ((fieldsz - len(k)) * ' ') + v
+print fp, qname, ((fieldsz - len(k)) * ' ') + v
# Finish the text file stanza
print fp, '# STANZA END:', listname
print fp
@@ -147,7 +149,7 @@
for k, v in makealiases(listname):
fqdnaddr = '%...@%s' % (k, hostname)
# Format the text file nicely
-print fp, fqdnaddr, ((fieldsz - len(k)) * ' '), k
+print fp, fqdnaddr, ((fieldsz - len(k)) * ' '), k + '.' + hostname
# Finish the text file stanza
print fp, '# STANZA END:', listname
print fp
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
On Wed, 7 Oct 2009, Mark Sapiro wrote:
Geoff Shang wrote:
On Wed, 7 Oct 2009, Ashley M. Kirchner wrote:
= /etc/mail/aliases/$domain-aliases
mailman-lists.$domain \
|/home/mailman/lists.$domain/mail/$domain-mailman post mailman
mailman-admin-lists.$domain:\
|/home/mailman/lists.$domain/mail/$domain-mailman admin mailman
Ok but how do you get Mailman to produce alias tables that look like that?
Or don't you? Mine only have the list address part, not the fully
qualified list address.
{snip}
There is still a problem in that there is a potential list name
conflict, so to resolve that, you need to make a patch (see attached
ah...
I will review your patch, and I used list-domain.tld instead of
list.domain.tld, but I basically came to the same conclusion and just
implemented same. I got the idea from
http://mail.python.org/pipermail/mailman-users/2008-September/063254.html
This really needs to be documented somewhere.
does using a dash vs a dot as a separater make any difference re eventual
upgrade path? I'm still testing at this point but I'll be making a lot of
lists soon, so now's the time to change anything.
Thanks again,
Geoff.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] missing list!
Khalil Abbas wrote: one of my lists is missing !! I'm getting this : ./list_members list1 No such list: list1 So the list isn't there. I.e., there is no lists/list1/ directory containing at least one of config.pck, config.pck.last, config.db or config.db.last. The directory has been renamed or removed or the config.* files have been removed. 0 ./list_members list2 477 ./list_members list3 483 ./list_members list4 442 when running : bin/list_lists I get this error: ./list_lists Traceback (most recent call last): File ./list_lists, line 122, in ? main() File ./list_lists, line 94, in main mlist = MailList.MailList(n, lock=0) File /usr/lib/mailman/Mailman/MailList.py, line 130, in __init__ self.Load() File /usr/lib/mailman/Mailman/MailList.py, line 644, in Load raise Errors.MMCorruptListDatabaseError, e Mailman.Errors.MMCorruptListDatabaseError: [Errno 2] No such file or directory: '/var/lib/mailman/lists/dailymail/config.db.last' There is a lists/dailymail/ directory containing probably a config.pck and config.pck.last, but these are somehow corrupted and can't be unpickled by the list instantiation process. Note that the current (Mailman 2.1.x) files are config.pck*. It is normal to not have config.db* files. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
Geoff Shang wrote: On Wed, 7 Oct 2009, Mark Sapiro wrote: There is still a problem in that there is a potential list name conflict, so to resolve that, you need to make a patch (see attached ah... I will review your patch, and I used list-domain.tld instead of list.domain.tld, but I basically came to the same conclusion and just implemented same. I got the idea from http://mail.python.org/pipermail/mailman-users/2008-September/063254.html This really needs to be documented somewhere. Yes. I'll see about a FAQ. Maybe you could help when you get it all worked through. does using a dash vs a dot as a separater make any difference re eventual upgrade path? I'm still testing at this point but I'll be making a lot of lists soon, so now's the time to change anything. I don't think so. I actually was going to use an underscore, but I went with the dot because Ashley was using a dot. Changing after the fact is not hard. You'd only need to change Mailman/MTA/Postfix.py and run bin/genaliases for each domain. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
