[Mailman-Users] More Vitual Domain Blues

[Sergio Murillo]

I'm getting the folowing message when I try to confirm my list 
registration.

The original message was received at Fri, 10 Mar 2000 18:21:16 -0600
from IDENT:root at lenz.unah.hondunet.net [200.3.227.43]

  ----- The following addresses had permanent fatal errors -----
<dev-request at hacsc.net>

  ----- Transcript of session follows -----
550 <dev-request at hacsc.net>... User unknown


------------------------------------------------------------------------
--------
Reporting-MTA: dns; ns.marrder.org
Received-From-MTA: DNS; lenz.unah.hondunet.net
Arrival-Date: Fri, 10 Mar 2000 18:21:16 -0600

Final-Recipient: RFC822; <dev-request at hacsc.net>
Action: failed
Status: 5.1.1
Last-Attempt-Date: Fri, 10 Mar 2000 18:21:25 -0600


Any Ideas?

I'm using linux RH6.1 and added the virtual users first using linuxconf.
This added the file aliases.domain.com

dev-request:       list-dev-request
etc...

Nothing

Then I edited /etc/mail/virtualmailuser
dev-request at domain.com:    list-dev-request
etc...

I did this with and without the trailing ':'... as your example didn;t 
have it.

Of course I have the aliases
list-dev-request: "|/usr/share/mailman/mail/wrapper mailcmd dev"



I've done the 'newaliases' command and the '/etc/rc.d/init.d/sendmail 
restart'

Still nothing...

Any ideas?

Sergio



-----Original Message-----
From: David Sexton <david.sexton at sapphire.net>
Date: Wed, 08 Mar 2000 14:02:23 +0000
Subject: Re: [Mailman-Users] Virtual Domains

>"Sergio A. Murillo" wrote:
>> 
>> I've been trying to configure Mailman to work with a virtual domain
>on a web
>> server with serveral virtual domains. I read  William R. Dickson
>sugestion
>> of installing a copy of mailman for each of the virtual domains.
>> How do i do this?/?? I've been traying all week now and still no
>luck...
>
>	This is the way I have it done (I'm not 100% certain of the
>security/reliability of this but it has worked so far):
>
>	I have one user set-up purely for mailman and mailman is 
installed in
>that user's directory & web space. All the administration for the
>lists
>are done through this one URL (although it may be possible to put
>wrappers around this).
>
>	Onto the 'meat'...
>
>	I'm assuming that you have set up the mail aliases and virtual 
user
>table in the following manner:-
>
>	virtusertable:
>
>	<list-name>@<domain>		list-<list-name>
>	<list-name>-admin@<domain>  	list-<list-name>-admin
>	<list-name>-request@<domain>    list-<list-name>-request
>	<list-name>-owner@<domain>  	list-<list-name>-admin
>
>	aliases:
>
>	list-<list-name>:		"|wrapper post <list-name>"
>	list-<list-name>-admin:		"|wrapper mailowner <list-name>"
>	list-<list-name>-request:	"|wrapper mailcmd <list-name>"
>
>	To change the domain of the list, you would go into the admin 
screen
>and change the host name of the list. This will allow you to
>successfully set-up & use list1 at domain1.com & list2 at domain2.com.
>
>	Is this perfect? No.
>
>	This would work until you needed two lists of the same 'name' 
eg:
>		announce at domain1.com and announce at domain2.com
>
>	A workaround for this is to embed the domain name into the list 
name
>and create lists like the following:-
>		domain1-com-announce  & domain2-com-announce
>
>	This now looks really clunky as the list would be at
>domain1-com-announce at domain1.com etc.
>
>	But .. if you mangle the entries in virtusertable, incoming mail
>works
>....
>
>	virtusertable
>	announce at domain1.com		list-domain1-com-announce
>	announce at domain2.com		list-domain2-com-announce
>		.. do a similar thing for the request & admin etc. 
addresses.
>
>	aliases
>	list-domain1-com-announce:	"|wrapper post domain1-com-
announce"
>	list-domain2-com-announce:	"|wrapper post domain2-com-
announce"
>		<etc. etc>
>
>	Now we're *almost* there. The addresses that mailman puts into
>messages
>it sends out will contain the full list name
>(domain2-com-announce at domain2) , not the short version you want. Back
>in
>the mailman admin screens, there is a field that in the public name of
>a
>list. It seems to indicate that mailman will use this name when
>generating addresses but changing this only does half the job.
>
>	I've hacked around a bit with MailList.py and got much better 
reults.
>If you apply the attached patch and change the 'public name' for the
>lists, it should work.
>
>	** NOTE ** I have very little experience of Python (I'm a 
perler at
>heart) and almost no appreciation of the structure of Mailman so I
>cannot guarrantee that these changes will not foul everything up. The
>docs say that you should not change the public name of a list and,
>although it is working so far, I am not totally sure of the
>implications
>of this.
>
>	Hope this helps,
>
>	Dave
>
>-- 
>David Sexton
>
>Network Technician
>Sapphire Technologies Ltd.
>Tel: +44 (0) 1642 702100
>Fax: +44 (0) 1642 702119
>
>-----------------------------------------------
>Any opinions expressed in this message are those of the individual and
>not necessarily the company.  This message and any files transmitted
>with it are confidential and solely for the use of the intended
>recipient.  If you are not the intended recipient or the person
>responsible for delivering to the intended recipient, be advised that
>you have received this message in error and that any use is strictly
>prohibited.
>
>Sapphire Technologies Ltd
>http://www.sapphire.net
>