Topic: Mailman contrib?

[EdelingF]

Has anyone tried to install Mailman in SME7 yet?
I used it on my previous SME6 but can't find any info on it.

Freek

[kruhm]

It's in a work-in-progress (WIP) folder in gordon's site.

-create new virtualdomain lists.yourdomain.com
-wget http://www.gormand.com.au/smeserver/WIP/smeserver-mailman/mailman-2.1.5-33.rhel4sme01.i386.rpm
-wget http://www.gormand.com.au/smeserver/WIP/smeserver-mailman/smeserver-mailman-1.3.0-12.noarch.rpm
-rpm -Uvh mailman
-rpm -Uvh smeserver-mailman
-/usr/lib/mailman/bin/mmsitepass (changes password)
-/usr/lib/mailman/bin/check_perms -f (fixes permission problem, should be fixed in newer versions of smeserver-mailman)
-visit http://lists.yourdomain.com/mailman

[jahlewis]

any of you know how these RPM's would address existing mailman lists?

I'm currently running on an SME 7.0 server...
 mailman-2.1.4-2
 e-smith-mailman-1.0-7
which is mostly working...

I'd love to use/test these RPM's, but don't want to do it with live lists...

[kruhm]

UVA, eh?

It shouldn't affect the lists. They live in the /var/lib/mailman dir. You can even copy the dir from one server to another and it will keep everything in tact.

[jahlewis]

Cool, I'll try it.

Only thing is, I've got lists for two different domains.  Based on the instructions, creating a domain called "lists.domain.com" confuses me as "lists" is more of a cname or psuedonym than a domain...

Shad's old version used db/accounts to track which domain a list belonged to.  Does this version?

[kruhm]

I've never tried it using HOSTNAMES so I couldn't say but you could always give it a shot with a fake list and let us know what happens.

I always put in a VIRTUAL DOMAIN and it seems to work.

When you transfer the lists be certain to keep the permissions in tact or MAILMAN will complain.

If you run into problems, check the logs /var/log/mailman and it will point you in the right direction.

Good luck.

[brianr]

I installed the SME7 version of mailman from gordons site some time ago.  The web interface seems to work, but qmail rejects any messages sent to the list:

Hi. This is the qmail-send program at bjsystems.co.uk.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<xxx-announce@bjsserver.bjsystems.co.uk>:
Sorry, no mailbox here by that name. (#5.1.1)


I have hunted around, but have not been able to find the problem.

I posted a bug on bugzilla, but got no response.

http://bugs.contribs.org/show_bug.cgi?id=1438

[kruhm]

Send the email to: <listname>@lists.domain.tld

[brianr]

Send the email to: <listname>@lists.domain.tld

Nope, that didn't work:

Hi. This is the qmail-send program at bjsystems.co.uk.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<xxx-announce@lists.bjsystems.co.uk>:
Sorry, I couldn't find any host named lists.bjsystems.co.uk. (#5.1.2)

[kruhm]

Sorry, I couldn't find any host named lists.bjsystems.co.uk. (#5.1.2)

Do you have a virtualdomain?: lists.yourdomain.tld

Come back with the output of:

Code: [Select]


db domains show


[brianr]

no, the only domains are ones I have created (i.e. not including lists...).

Should the mailman contrib have created one?

I could create it myself from server-manager?

[kruhm]

Yes, follow the instructions above and create it from the server-manager.

[brianr]

ok, created lists.bjsystems.co.uk, and still cannot send to the list.  As a mailbox applies to ALL domains on the server, I can't see that it would make any difference anyway.

I suspect a that some aspect of the qmail structure/configs is not correct, and I worked through everything I could find, but cannot see where the gap is.

[kruhm]

I suspect a that some aspect of the qmail structure/configs is not correct, and I worked through everything I could find, but cannot see where the gap is.

you're looking in the wrong direction. The problem isn't sme, it's mailman. It's very particular in it's python and very unforgiving in it's permissions.

I could go into detail but don't have the time. The easiest thing to do is to uninstall the mailman rpms you have and follow exactly as above. I'll post it agian:

Code: [Select]


-create new virtualdomain lists.yourdomain.com
-wget http://www.gormand.com.au/smeserver/WIP/smeserver-mailman/mailman-2.1.5-33.rhel4sme01.i386.rpm
-wget http://www.gormand.com.au/smeserver/WIP/smeserver-mailman/smeserver-mailman-1.3.0-12.noarch.rpm
-rpm -Uvh mailman*
-rpm -Uvh smeserver-mailman*
-/usr/lib/mailman/bin/mmsitepass (changes password)
-/usr/lib/mailman/bin/check_perms -f (fixes permission problem, should be fixed in newer versions of smeserver-mailman)
-visit http://lists.yourdomain.com/mailman to create or modify


Let me know where it errors out and the error message.

[EdelingF]

Tried to install Mailman and while trying to make a first list I get:
Error: Unknown virtual host: lists.mydomain.eu.org

I did make the virtual host, I even uninstalled Mailman and reinstalled it just to make sure.

I used:
http://www.gormand.com.au/smeserver/WIP/smeserver-mailman/mailman-2.1.5.1-34.rhel4.3sme01.i386.rpm
http://www.gormand.com.au/smeserver/WIP/smeserver-mailman/smeserver-mailman-1.3.0-14.noarch.rpm
http://www.gormand.com.au/smeserver/WIP/smeserver-mailman/mailman-debuginfo-2.1.5.1-34.rhel4.3sme01.i386.rpm

Did I do something wrong? Should I use the previous version instead?
I didn't use the main domain, maybe that's the problem?

Freek

[jahlewis]

I was running into similar problems with a clean 7.0 box (mailman worked in my upgraded 7.0 box using the old 6.0 contribs...).

I've installed
mailman-2.1.5.1-34.rhel4.3sme01
smeserver-mailman-1.3.0-14

I did not create any lists* virtual domains.  Creating lists using the /usr/lib/mailman/bin/addlist script created a list, but did not do all the smeserver related stuff.

What I did do is in a browser, to http://mydomain.com/mailman and used the links to create a list... AND IT WORKED!  So its using the FQDN to process.

Now I just have to figure out how to get it to recognize my old lists....

[brianr]

Now I just have to figure out how to get it to recognize my old lists....

I had to rename my list with "-" in its name, and then copy over the members, using the bulk subscribe facility, then go through and set up the parameters as required.

[jahlewis]

I'm trying desperately to not have to manually recreate my lists.  In the past, the lists were stored in /usr/lib/mailman/lists

Where are they stored now?  I can't seem to find them.

My old lists are in /home/e-smith/db/accounts
They are in /var/qmail/users/assign
I put the old list files in /usr/lib/mailman/lists

When I send mail to an old list, /var/log/mailman/error says:

Code: [Select]

Oct 22 13:06:35 2006 post(4609): post script, list not found: lewis

in /var/log/qmail/current

Code: [Select]

@40000000453ba52332cb0b4c starting delivery 1250: msg 6031282 to local alias-localdelivery-lewis@arachnerd.com
@40000000453ba52338be7f34 info msg 6031231: bytes 2147 from <lewisjo@ntelos.com> qp 4606 uid 400
@40000000453ba523392da83c starting delivery 1251: msg 6031231 to local lewis@gluon.arachnerd.com
@40000000453ba525071fb13c delivery 1251: deferral: post_script,_list_not_found:_lewis/
@40000000453ba5880663c7c4 starting delivery 1252: msg 6031231 to local lewis@gluon.arachnerd.com
@40000000453ba5881283383c delivery 1252: deferral: post_script,_list_not_found:_lewis/


so...
1) where does mailman know about which lists exist?  I'm happy to edit manually if it is not derived from db/accounts
2) is anyone using archiving messages?  the new list I just created, which works for sending and recieving mail, does not keep archives...

And if I have to recreate manually, do I need to remove them from db/accounts first?

Mailman is a great mailing list manager, allowing people to self manage their lists using nicely documented web pages.  I'd really like to get it back and running, and am happy to test etc.

Thanks.

[jahlewis]

Even creating a new list with the same name as an old is not consistent...

Here is an error I get creating a list that used to exist (as in the alias files exist already, and it is already in the db/accounts

Code: [Select]

[root@gluon mailman]# bin/newlist prospace-board
Enter the email of the person running the list: jnlewis@arachnerd.com
Initial prospace-board password:
Invalid list name prospace-board at /usr/lib/mailman/bin/smelist line 25.
Traceback (most recent call last):
  File "bin/newlist", line 219, in ?
    main()
  File "bin/newlist", line 186, in main
    sys.modules[modname].create(mlist)
  File "/usr/lib/mailman/Mailman/MTA/SME.py", line 43, in create
    raise RuntimeError, msg % (acmd, status, errstr)
RuntimeError: command failed: /usr/lib/mailman/bin/smelist addlist prospace-board (status: 255, Unknown error 255)

but it creates the list.  bin/rmlist error's out with the same message, but does not remove the list

Notice this list has a "-" in the name.  When I created a list without the "-", it created fine.

Creating a list via the webpage remembers what domain you created it in.  Creating it from the command line puts it in the default domain.

Oh how I wish I new where mailman stores this information...

-JL

[jahlewis]

I'm back to trying to work with mailman on my 7.1 server.
I'm using: mailman-2.1.5.1-34.rhel4.3sme01 smeserver-mailman-1.3.0-14

When trying to remove a list in /opt/mailman/bin I get:

Code: [Select]

[root@gluon bin]# ./rmlist Prospace-Board
Not removing archives.  Reinvoke with -a to remove them.
Invalid list name prospace-board at /usr/lib/mailman/bin/smelist line 25.
Traceback (most recent call last):
  File "./rmlist", line 153, in ?
    main()
  File "./rmlist", line 121, in main
    sys.modules[modname].remove(mlist)
  File "/usr/lib/mailman/Mailman/MTA/SME.py", line 55, in remove
    raise RuntimeError, msg % (acmd, status, errstr)
RuntimeError: command failed: /usr/lib/mailman/bin/smelist rmlist prospace-board (status: 255, Unknown error 255)

Not sure how do do this manually.  Any ideas?

[jahlewis]

After searching for "mailman" in the bug tracker, then googling "smeserver-mailman-1.3.0-15" in google, I discovered that the updated mailman rpms are in smedev.

So I installed them:

Code: [Select]

yum --enablerepo=smedev update mailman smeserver-mailman

Which upgraded me to:
mailman-2.1.5.1-34.0.el4.sme
smeserver-mailman-1.3.0-15.el4.sme

I am now able to remove lists with hyphens in them.  AWESOME!!!  Thanks Gordon!

PS. I notice there are a bunch of rpms I can upgrade in smedev, most of which have same versions but with el4 as part of the rpm name.  How do I find out what the changes are for these RPM's to decide whether they are worth the risk of applying to a production box?

[stephen noble]

> whether they are worth the risk of applying to a production box?

NO, the smedev repo is almost certain to cause problems

individual rpms may be OK, (if they aren't they don't get release to the testing repo) but even they can pull in updates of dependancies wich will break your server

[william_syd]

PS. I notice there are a bunch of rpms I can upgrade in smedev, most of which have same versions but with el4 as part of the rpm name.  How do I find out what the changes are for these RPM's to decide whether they are worth the risk of applying to a production box?

Go to the repodata directory of the repository your interested in....

Eg.
http://mirror.contribs.org/smeserver/releases/7.1/smedev/i386/repodata/repoview/smeserver-mailman-0-1.3.0-15.el4.sme.html

This will give you a little info.

Note the number after SME: in the changelog. This is the bug entry for that change.

[gordonr]

I am now able to remove lists with hyphens in them.  AWESOME!!!  Thanks Gordon!

No worries. I hope to get smeserver-mailman into the (soon to be created) smeextras repository soonish for all to share. Thanks.

[jahlewis]

Great!  Excellent idea. Looking forward to it.

After looking around the smedev repository, i saw some ones that I'm interested in, and would love yum to manage their updates and dependencies.  Mailman, RT and sme7admin in particular.  Are the RT contribs in smedev ready to roll?  I'm wanting to install a ticket tracker, and have been waiting for RT rather than use some of the PHP versions.

So contribs that are extra, and production ready will be stored in the smeextra's repository, and managed by the contrib owners?

[bmoore]

greetings.  Okay, I installed the latest versions of mailman and smeserver-mailman from the sme-dev archives.  all seems to be working except for the migration of my old lists from my 6.0 production box.
If I run the genaliases command by hand, I get a complete list on screen.  HOwever, I can't figure out how to get the alaises to work. when I try and send a message to an existing list, I get a delivery failure.  Not sure where this stuff is stored now.  If I can avoid recreating 14 lists by hand, I wouldbe really happyy.  This is getting somewhat urgent because the old hardware is starting to go I think and I can not install 6.0 on my new dell poweredge box cause it is using sata drives and 6.0 didn't recognize the new raid card.

I have copied all the list files from the old server /opt/mailman/lists to the new location which seems to be /var/lib/mailman/lists.  Have done the same with archives.  there must be an easy way to migrate old lists but I'm stuck at the moment.

any help would be much appreciated.

thanks.
rian.

[cjensen]

Probably the fastest answer is to search... I found this:

------- Comment #1 From Gordon Rowell 2006-03-08 20:04 [reply] -------

(In reply to comment #0)
> [...]
> This server has an existing mailman installation, which seems to be a problem
> for this package.

Yes. As noted in the changelog of the package, we need to perform a migration
of the data to /var/lib/mailman

It's something like this:

cd /opt
mv mailman mailman.old
cd mailman.old
mkdir /var/lib/mailman
mv archives data lists spam /var/lib/mailman

mkdir /usr/lib/mailman/aliases
mv aliases/.??* /usr/lib/mailman/aliases

from
http://bugs.contribs.org/show_bug.cgi?id=987
Craig

[bmoore]

Greetings.  thanks to Craig's post, I finally have migrated my old lists from my sme 6.0.101 box and have them working.  Whilethere might be an easier way, this worked for me.  I created a tar archive of the mailman folder from my sme 6 box and moved it to a fresh install of 7.1 after recreating all my user accounts.  I then moved the lists, archives, data and spam directories from /opt/mailman to /var/lib/mailman.

Then installed the latest versions of the mailman rpms from the dev repo.  Despite moving the aliases from /opt/mailman/aliases to /usr/lib/mailman/aliases, my lists still did not work.  If I sent a message, got a delivery failure with no such mailbox.  

Here is what I did to get them working again.  By hand, I removed each list including its archive with /usr/lib/mailman/rmlist -a listname and thenre-created the same lists with /usr/lib/mailman/bin/newlist

IN order not to have to replace all the settings, memberships etc, I then copied the old lists directory back and restarted mailman.  NOw, all my lists work again.  

ON the old system, I had added the htdig and mhonarc programs for archiving which create a slightly nicer set of archives than the standard ones generated by pipermail but I haven't worked out yet how to get that bit back in.  I have the rpms which I installed on my sme 6 box but I don't know how to generate the cron jobs correctly and I have to work out where to tell mailman to use an external archiver but that is a project for next week when I have more time.

Brian.

[cjensen]

I'm not sure about the archiving, but the cron jobs should be working from the mailman-2.1.5.1-34.rhel4.3sme01 rpm.  Which set of packages do you have for mailman?

rpm -qa | grep mailman
smeserver-mailman-1.3.0-14
mailman-2.1.5.1-34.rhel4.3sme01

I know there have been several bugs (most I think are resolved) logged in the bug tracker for mailman/sme7.

Craig

[bmoore]

HI craig.  Mailman works correctly.  It was only the archiving bit I wasn't sure about.  I think all the mailman bugs are worked out from what I can tell by reading the bug tracker.  I was trying to figure out how to install htdig and mhonarc and get them to work correctly.  It can be done, will just take a little playing to get it working nicely.  Mailman itself seems to be doing all it should.
Brian.

[bmoore]

Greetings.  Not sure if this is a real bug so I don't want to raise one yet.  Mailman seems to be working well on sme 7.1 with latest rpms from sme-dev.  However, I am getting delivery failures from the bounce processor. I don't think I have mis-configured anything but not sure.  I get lots of  notices to post master that bounce notices are failing with local aliases not existing
I think there may be an error in this latest version but want to be sure I didn't do something before I raise a real bug.

see below
Hi. This is the qmail-send program at screenreview.org.
I tried to deliver a bounce message to this address, but the bounce bounced!
<
buddys-dogscoop-bounces+323401cb6602df68236929ce14ced54e131dc20e@server.screenreview.org
>:
Sorry, no mailbox here by that name. (#5.1.1)
--- Below this line is the original bounce.
Return-Path: <>
Received: (qmail 26013 invoked by alias); 6 Feb 2007 09:55:11 -0000
Delivered-To:
alias-localdelivery-buddys-dogscoop-bounces+323401cb6602df68236929ce14ced54e131dc20e@screenreview.org
Received: (qmail 26010 invoked for bounce); 6 Feb 2007 09:55:11 -0000
Date: 6 Feb 2007 09:55:11 -0000
From:
MAILER-DAEMON@screenreview.org
To:
buddys-dogscoop-bounces+323401cb6602df68236929ce14ced54e131dc20e@screenreview.org
Subject: failure notice
Hi. This is the qmail-send program at screenreview.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<
mcrogers1@verizon.net
>:
206.46.232.11 does not like recipient.
Remote host said: 550 4.2.1 mailbox temporarily disabled:
mcrogers1@verizon.net
Giving up on 206.46.232.11.
--- Below this line is a copy of the message.

[bmoore]

Okay, I will turn this into a bug soon if I can't figure it out.  I have searched the mailman faq the mailman lists and here but haven't gotten much further with this one.

I have the following installed
mailman-2.1.5.1-34.0.el4.sme.i386.rpm
smeserver-mailman-1.3.0-15.el4.sme.noarch.rpm.  I still get delivery failures from the bounce processor.

Code: [Select]


Hi. This is the qmail-send program at screenreview.org.
I tried to deliver a bounce message to this address, but the bounce bounced!
<
juno-l-bounces+7343c8858aefc1102f5c5efbcee8782f1ffff542@server.screenreview.org
>:
Sorry, no mailbox here by that name. (#5.1.1)
--- Below this line is the original bounce.
Return-Path: <>
Received: (qmail 24590 invoked by alias); 8 Mar 2007 13:44:18 -0000
Delivered-To:
alias-localdelivery-juno-l-bounces+7343c8858aefc1102f5c5efbcee8782f1ffff542@screenreview.org
Received: (qmail 24587 invoked for bounce); 8 Mar 2007 13:44:18 -0000
Date: 8 Mar 2007 13:44:18 -0000
From:
MAILER-DAEMON@screenreview.org
To:
juno-l-bounces+7343c8858aefc1102f5c5efbcee8782f1ffff542@screenreview.org
Subject: failure notice
Hi. This is the qmail-send program at screenreview.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<
Luvlabpups@aol.com
>:
205.188.158.121 does not like recipient.
Remote host said: 550 We would love to have gotten this email to
luvlabpups@aim.com
. But, your recipient never logged onto their free AIM Mail account. Please contact
them and let them know that they're missing out on all the super features offered
by AIM Mail. And by the way, they're also missing out on your email. Thanks.
Giving up on 205.188.158.121.
--- Below this line is a copy of the message.
Return-Path: <
juno-l-bounces+7343c8858aefc1102f5c5efbcee8782f1ffff542@screenreview.org
>
Received: (qmail 24584 invoked by uid 453); 8 Mar 2007 13:44:13 -0000
Received: from localhost (HELO server.screenreview.org) (127.0.0.1)
    by screenreview.org (qpsmtpd/0.32) with ESMTP; Thu, 08 Mar 2007 08:44:13 -0500
Subject: Juno-l mailing list probe message
From:
juno-l-bounces+7343c8858aefc1102f5c5efbcee8782f1ffff542@screenreview.org
To:
Luvlabpups@aol.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1729239141=="
Message-ID: <
mailman.6.1173361451.5407.juno-l@screenreview.org
>
Date: Thu, 08 Mar 2007 08:44:11 -0500
Precedence: bulk
X-BeenThere:
juno-l@screenreview.org
X-Mailman-Version: 2.1.5
List-Id: "Juno-l is A supportive communications forum for Guide Dog users,
and Puppy Raisers. Founded and supported by Guiding Eyes for the Blind
Graduates. " <juno-l.screenreview.org>
X-List-Administrivia: yes
Sender:
juno-l-bounces+7343c8858aefc1102f5c5efbcee8782f1ffff542@screenreview.org
Errors-To:
juno-l-bounces+7343c8858aefc1102f5c5efbcee8782f1ffff542@screenreview.org
--===============1729239141==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
This is a probe message.  You can ignore this message.
The Juno-l mailing list has received a number of bounces from you,
indicating that there may be a problem delivering messages to
Luvlabpups@aol.com
. A bounce sample is attached below.  Please examine
this message to make sure there are no problems with your email
address.  You may want to check with your mail administrator for more
help.
If you are reading this, you don't need to do anything to remain an
enabled member of the mailing list.  If this message had bounced, you
would not be reading it, and your membership would have been disabled.
Normally when you are disabled, you receive occasional messages asking
you to re-enable your subscription.
You can also visit your membership page at
http://www.screenreview.org/mailman/options/juno-l/luvlabpups%40aol.com
On your membership page, you can change various delivery options such
as your email address and whether you get digests or not.  As a
reminder, your membership password is
    poceum
If you have any questions or problems, you can contact the list owner
at
juno-l-owner@screenreview.org
--===============1729239141==
Content-Type: message/rfc822
MIME-Version: 1.0
Return-Path: <>
Delivered-To:
juno-l-bounces@server.screenreview.org
Received: (qmail 23737 invoked by alias); 8 Mar 2007 13:37:43 -0000
Delivered-To:
alias-localdelivery-juno-l-bounces@screenreview.org
Received: (qmail 23698 invoked for bounce); 8 Mar 2007 13:37:35 -0000
Date: 8 Mar 2007 13:37:35 -0000
From:
MAILER-DAEMON@screenreview.org
To:
juno-l-bounces@screenreview.org
Subject: failure notice
Hi. This is the qmail-send program at screenreview.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<
Luvlabpups@aol.com
>:
205.188.155.89 does not like recipient.
Remote host said: 550 We would love to have gotten this email to
luvlabpups@aim.com
. But, your recipient never logged onto their free AIM Mail account. Please contact
them and let them know that they're missing out on all the super features offered
by AIM Mail. And by the way, they're also missing out on your email. Thanks.
Giving up on 205.188.155.89.
<
waterloo26@yahoo.com
>:
216.39.53.2 failed after I sent the message.
Remote host said: 554 delivery error: dd Sorry your message to
waterloo26@yahoo.com
 cannot be delivered. This account has been disabled or discontinued [#102]. - mta216.mail.re4.yahoo.com
--- Below this line is a copy of the message.

These messages should increment a bounce score automatically and not be returned to post master but they aren't for some reason. I suspect that the system is not dealing with the temporary aliases correctly but I can't for the life of me figure out how to fix it.

thanks.
Brian.


[dmay]

mailman-2.1.5.1-34.0.el4.sme.i386.rpm

Also note 2.1.5 is circa 2004. The current stable version is 2.1.9, released on 12-Sep-2006. Before you issue bug reports on an old release, I'd suggest you contact Gordon and see if he is contemplating updating the contrib.

Darrell

[kruhm]

Do you have bounce_processing turned on or off?

[bmoore]

HI.  It is on for all lists.  I would attempt to upgrade to the current stable release of mailman but not sure what it might break in smeserver-mailman.
Brian

[tiziano]

hello I have mailman lastest version but

for viewer archive I don't have permision
why ?


http://iw7efc.dyndns.org/mailman/public/hamradio/

[chrismaltby]

I'll post it agian:

Code: [Select]

-create new virtualdomain lists.yourdomain.com


I'm sure there's a simple answer to this question but it's stumping me right now. How do I create a new virtualdomain using smeserver tools. I can make a domain based pseudonym, or put my own custom template in /var/qmail/control/{rcpthosts,virtualdomains}, but nothing in my 7.2 install seems to match the instruction quoted above...

[mmccarn]

I *think* those instructions are telling you to use server-manager::Configuration::Domains::Add domain to create a new "domain".

These were refered to as 'virtual domains' at one point - I think because the main fallout from adding a domain in server-manager was the creation of various 'VirtualHost' sections in /etc/httpd/conf/httpd.conf, modification of qmail's 'virtualdomains' configuration, etc...

[chrismaltby]

Ah.. well I think it's just that it doesn't work the way I expected. Instead of creating a qmail virtualhost entry to forward the entire domain to the mailman account, it creates special mailmanlist account entries, one per list, and uses them to expand qmail user name lookups. That means that list names can't conflict with user names and are accessible from all virtual host names in use for the server. Another way it could be done (better) would be to put listname@listdomain:mailman entries into qmail's virtualhost file to limit the list's email accessibility to its defined virtual host.

<aside>Isn't qmail wonderful... always lots of ways to solve any problem, and never any consensus on which way is best...</aside>