Mark,

All I did was follow the instructions in UPGRADE included with 2.1.8.  
There is a Defaults.py at /path/to/mailman/Mailman/Defaults.py with the 
line OLD_STYLE_PREFIXING = Yes in it.  So, unless the instructions in 
UPGRADE (basically, to run ./configure with the same options as the 
previous install and then execute a make install) are flawed, there 
shouldn't be any reason why I got that error.  Nevertheless,  I seem to 
get no errors in any of Mailman's logs or Exim's logs after I made that 
change.  Not sure why it wouldn't pick up the line in Defaults.py....

Best,
Ryan

Mark Sapiro wrote:
> Ryan Steele wrote:
>   
>> Solved my problem by putting the following in mm_cfg.py:
>>
>> OLD_STYLE_PREFIXING = No
>>     
>
>
> But you still have a problem because either you don't have a 2.1.8
> Defaults.py which contains
>
> OLD_STYLE_PREFIXING = Yes
>
> or your mm_cfg.py is missing the stuff near the beginning that says
>
> ###############################################
> # Here's where we get the distributed defaults.
>
> from Defaults import *
>
> ##################################################
> # Put YOUR site-specific settings below this line.
>
>
> If it's the latter, there would be lots of problems like you reported
> in the original post, so I'm guessing there's more likely a problem
> with your Defaults.py. If you compare it to the distribution
> Defaults.py.in, they should be the same except for those variable
> settings which are expanded by configure.
>
>   

------------------------------------------------------
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=show&file=faq01.027.htp

Reply via email to