On 06/10/06, Mark Sapiro [EMAIL PROTECTED] wrote:
Chris Puttick wrote:
Ok, the problem:
http://lists.openarchaeology.net/mailman/listinfo
compared with
http://lists.openarchaeology.net/mailman/listinfo/mailman
mm_cfg:
from Defaults import *
Chris Puttick wrote:
On 06/10/06, Mark Sapiro [EMAIL PROTECTED] wrote:
I suspect that adding
VIRTUAL_HOST_OVERVIEW = Off
to the above will fix the symptom. If it does, the underlying problem
is that your web server is setting HTTP_HOST (or if HTTP_HOST is
unset, SERVER_NAME) to
I have a private list set up that requires moderator approval. List
members are approved based upon who they are. Their email is not enough
to determine their identity. How can I get the name of those requesting
subscription approval to show up in the moderator emails?
Jerry Win
Please copy your replise to the list.
Noah wrote:
Mark Sapiro wrote:
Where are the messages ('ls -lR /usr/local/mailman/qfiles/')?
yes
# ls -lR /usr/local/mailman/qfiles/ | wc -l
14430
# ls /usr/local/mailman/qfiles/
archive bounces in out shunt
Jerry Hole wrote:
I have a private list set up that requires moderator approval. List
members are approved based upon who they are. Their email is not enough
to determine their identity. How can I get the name of those requesting
subscription approval to show up in the moderator emails?
You
At 11:59 PM -0700 10/6/06, Mark Sapiro wrote:
I think that normally, it should pass the name
of the host in the URL that accessed the page, at least in a virtual
hosts configuration, but here it is passing '10.0.10.18'. This is a
web server configuration issue.
Take a look at this. I ran bin/unshunt
now i have a ton of 'SHUNT' errors in the /usr/local/mailman/logs/error
so it looks like there are some python errors here. please look below.
I am not sure where to go from here.
# pkg_info | grep python
python-2.3.5_1 An interpreted
I am puzzled. As I read the code, it is not possible to create the
shunt queue entry without also logging the error and the SHUNTING
message. Ordinarily, I would suggest that you might be logging to a
different set of log files in a different directory, but an earlier
post showed error log
Noah wrote:
Take a look at this. I ran bin/unshunt
now i have a ton of 'SHUNT' errors in the /usr/local/mailman/logs/error
so it looks like there are some python errors here. please look below.
I am not sure where to go from here.
# pkg_info | grep python
python-2.3.5_1 An
Noah wrote:
I can see that only one installation is running.
But is it the same Mailman from the same directory as the one that was
running when the messages were shunted on Oct 6 21:33?
# /usr/local/bin/python -V
Python 2.4.3
after running bin/unshunt there are tons of SHUNT errors messages
Mark Sapiro wrote:
Noah wrote:
Take a look at this. I ran bin/unshunt
now i have a ton of 'SHUNT' errors in the /usr/local/mailman/logs/error
so it looks like there are some python errors here. please look below.
I am not sure where to go from here.
# pkg_info | grep python
Mark Sapiro wrote:
Noah wrote:
I can see that only one installation is running.
But is it the same Mailman from the same directory as the one that was
running when the messages were shunted on Oct 6 21:33?
# /usr/local/bin/python -V
Python 2.4.3
after running bin/unshunt
Noah wrote:
okay well there were no relevant SHUNT messages in logs/error . how
else could I have figure this out from bin/dumpdb ?
You can't. In general, there may be nothing at all wrong with the
message that was shunted. It may be shunted due to a software error or
some other condition not
I also agree. In our environment users want to be able to create a
list without the involvement/delay of the mailman administrator.
Would very much like to see this as a feature of Mailman.
Thank you.
(Sorry if this does not meet up under the original thread. Have
included the reference text
14 matches
Mail list logo
