Re: [Mailman-Users] virtual domains problem

2006-01-03 Thread John W. Baxter
On 1/3/06 9:29 AM, Sean Roe [EMAIL PROTECTED] wrote:

The macro
 MM_LISTCHK=MM_HOME/lists/${lc::$local_part}/config.pck
is later used in a list context
 require_files = MM_LISTCHK

So I to would expect the : in $(lc:$local_part) to have to be doubled.  But
what seems to be happening is that the second of the pair of colons is being
picked up as part of the string to be lower-cased.

You could make certain that the colon *doesn't* need to be doubled by
changing the list separator character in the require_files option:
require_files = ; MM_LISTCHK

If you do that, then for sure you only need a single : in the MM_LISTCHK
macro.  (You need to do the same magic other places the macro is used in
list context.)

  --John


--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] virtual domains problem

2006-01-03 Thread Sean Roe
Hi All,

The changes I made were to exim's list_macrodefs:
from:
MM_LISTCHK=MM_HOME/lists/${lc::$local_part}/config.pck
to:
MM_LISTCHK=MM_HOME/lists/${lc:$local_part}/config.pck

and mailman_router:
from:
require_files = MM_LISTCHK
to:
require_files = ; MM_LISTCHK

I made the changes above, but now exim4 says the addresses are unroutable:
#exim4 -bt [EMAIL PROTECTED]
R: system_aliases for [EMAIL PROTECTED]
[EMAIL PROTECTED] is undeliverable:
  Unrouteable address

I reverted the changes and get this:
#exim4 -bt [EMAIL PROTECTED]
[EMAIL PROTECTED]
  router = mailman_router, transport = mailman_transport

Is there anything else I need to do to make this work?  I didn't see any 
other reference to MM_LISTCHK

Thanks,
Sean

John W. Baxter wrote:
 On 1/3/06 9:29 AM, Sean Roe [EMAIL PROTECTED] wrote:

 The macro
   
 MM_LISTCHK=MM_HOME/lists/${lc::$local_part}/config.pck
 
 is later used in a list context
   
 require_files = MM_LISTCHK
 

 So I to would expect the : in $(lc:$local_part) to have to be doubled.  But
 what seems to be happening is that the second of the pair of colons is being
 picked up as part of the string to be lower-cased.

 You could make certain that the colon *doesn't* need to be doubled by
 changing the list separator character in the require_files option:
 require_files = ; MM_LISTCHK

 If you do that, then for sure you only need a single : in the MM_LISTCHK
 macro.  (You need to do the same magic other places the macro is used in
 list context.)

   --John

   

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] virtual domains problem

2006-01-03 Thread Mark Sapiro
Sean Roe wrote:

2006-01-03 09:42:52 1EtpFL-0003iz-RY == [EMAIL PROTECTED] 
R=mailman_router T=mailman_transport defer (2): No such file or 
directory: failed to chdir to /data/mailman/:adoptionweek.com


I believe the problem is the colon at the begining of sub directory 
name.  I cant seem to find where that is coming from.  Below are the 
changes I made to exim to deal with the virt domains:

in 01_exim4-config_listmacrosdefs:

MM_HOME=/data/mailman/${lc::$domain}

Where does this come from? Normally it would just be something like

MM_HOME=/data/mailman/

and not include any reference to $domain. It is the path to but not
including the lists/ directory in the Mailman installation.

-- 
Mark Sapiro [EMAIL PROTECTED]   The 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://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] virtual domains problem

2006-01-03 Thread Sean Roe
Mark Sapiro wrote:
 Sean Roe wrote:
   
 2006-01-03 09:42:52 1EtpFL-0003iz-RY == [EMAIL PROTECTED] 
 R=mailman_router T=mailman_transport defer (2): No such file or 
 directory: failed to chdir to /data/mailman/:adoptionweek.com


 I believe the problem is the colon at the begining of sub directory 
 name.  I cant seem to find where that is coming from.  Below are the 
 changes I made to exim to deal with the virt domains:

 in 01_exim4-config_listmacrosdefs:

 MM_HOME=/data/mailman/${lc::$domain}
 

 Where does this come from? Normally it would just be something like

 MM_HOME=/data/mailman/

 and not include any reference to $domain. It is the path to but not
 including the lists/ directory in the Mailman installation.

   
this is a virtual domain installation.  /data/mailman/{domain} refers 
different mailman installations:

/data/mailman/adoptionlists.com
/data/mailman/adoptionweek.com
ect.

Sean
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] virtual domains problem

2006-01-03 Thread Mark Sapiro
Sean Roe wrote:

this is a virtual domain installation.  /data/mailman/{domain} refers 
different mailman installations:

/data/mailman/adoptionlists.com
/data/mailman/adoptionweek.com
ect.


Sorry, I misunderstood. I thought you were using Mailman virtual
domains, not separate Mailman instances.

-- 
Mark Sapiro [EMAIL PROTECTED]   The 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://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] virtual domains problem

2006-01-03 Thread Sean Roe
Mark Sapiro wrote:
 Sean Roe wrote:

   
 this is a virtual domain installation.  /data/mailman/{domain} refers 
 different mailman installations:

 /data/mailman/adoptionlists.com
 /data/mailman/adoptionweek.com
 ect.
 


 Sorry, I misunderstood. I thought you were using Mailman virtual
 domains, not separate Mailman instances.

   
Unfortunately, I have to do it this way, with multiple instances, as one 
group of lists are using the mysql adapter and one group isn't.  Getting 
back to the original posting, do you know why I am picking up that colon 
on the beguining of the domainname?

Sean
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] virtual domains problem

2006-01-03 Thread Mark Sapiro
Sean Roe wrote:

Unfortunately, I have to do it this way, with multiple instances, as one 
group of lists are using the mysql adapter and one group isn't.  


If you use the extend.py mechanism to specify the MysqlMemberships.py
MemberAdaptor rather than patching MailList.py, you can use
MysqlMemberships.py for only a subset of lists. It is not quite
automatic as you would have to manually copy an extend.py file to the
lists/listname/ directory following creation of a list that would use
MysqlMemberships.py, but it can be done.
 

Getting 
back to the original posting, do you know why I am picking up that colon 
on the beguining of the domainname?


It is not clear to me from the prior posts in this thread exactly what
you've tried. You said in a prior post -

The changes I made were to exim's list_macrodefs:
from:
MM_LISTCHK=MM_HOME/lists/${lc::$local_part}/config.pck
to:
MM_LISTCHK=MM_HOME/lists/${lc:$local_part}/config.pck

and mailman_router:
from:
require_files = MM_LISTCHK
to:
require_files = ; MM_LISTCHK

but it is not clear if you also changed MM_HOME. There is possibly
confusion over whether or not a doubled colon is required in MM_HOME
for

MM_LISTCHK=MM_HOME/lists/${lc::$local_part}/config.pck

but the several other places where MM_HOME is used definitely do not
want the colon to be doubled.

Thus it seems to me you want

MM_HOME=/data/mailman/${lc:$domain}

and

MM_LISTCHK=MM_HOME/lists/${lc:$local_part}/config.pck

and to be sure you don't need doubled colons in MM_LISTCHK,

require_files = ; MM_LISTCHK


-- 
Mark Sapiro [EMAIL PROTECTED]   The 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://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] virtual domains problem

2006-01-03 Thread Brad Knowles
At 3:09 PM -0700 2006-01-03, Sean Roe wrote:

  Is there anything else I need to do to make this work?  I didn't see any
  other reference to MM_LISTCHK

This is really an Exim problem, and I suspect that you're more 
likely to get useful assistance by going to their documentation, 
reading their FAQs, posting to their mailing lists, etc

-- 
Brad Knowles, [EMAIL PROTECTED]

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.

 -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
 Assembly to the Governor, November 11, 1755

  LOPSA member since December 2005.  See http://www.lopsa.org/.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp