Mark Sapiro [EMAIL PROTECTED] probably said:
Peter Radcliffe wrote:
Utils.get_site_email() with no hostname which goes through
get_domain() to get where it's looking for... which pulls the hostname
out of mm_cfg.DEFAULT_URL_HOST.
Yes, but then it looks that up in VIRTUAL_HOSTS
I've got what
Peter Radcliffe wrote:
If it shouldn't be necessary then I'm missing something since I can't
get that chunk of code to output the right answer... admittedly my
python is a bit rusty, though.
Try the following tests:
$ bin/withlist -i
No list name supplied.
Python info ...
(InteractiveConsole)
Mark Sapiro [EMAIL PROTECTED] probably said:
Try the following tests:
Utils.get_domain()
(should return 'www.pir.net')
Utils.get_site_email()
(should return '[EMAIL PROTECTED]')
mm_cfg.VIRTUAL_HOSTS
(should return {'www.pir.net': 'list.pir.net'}
All return as they should. Even this
Peter Radcliffe wrote:
Makes me really puzzled.
Me too.
My best guess is I changed the mm_cfg.py file
from when I had the bad entries in, post-upgrade, and afterwards only
processes not in the mailman group that couldn't write to
Mailman/mm_cfg.pyc were run until I was done testing...
This
Peter Radcliffe wrote:
I checked I had gotten rid of all the old variables, had run
add_virtualhost() properly in mm_cfg.py, ran fix_url, restarted the
qrunners, etc, everything I could find about it until I ran
across;
http://mail.python.org/pipermail/mailman-users/2006-April/050706.html
It
I recently upgraded from mailman 2.0.x to 2.1.x finally (yeah, I've
been kinda busy moving countries again) and was bitten by what seems to
me to be a change in behaviour.
Mail sent to listname-owner was appearing with an SMTP envelope
sender of listname-bounces@DEFAULT_URL_HOST which isn't a
