[Mailman-Users] web interface bug after restore mailman

[Mark Sapiro]

Cen Gao wrote:
>
>Traceback:
>
>
>Traceback (most recent call last):
>  File "/usr/local/bin/mailman//scripts/driver", line 82, in run_main
>immediate=1)
>  File "/usr/local/bin/mailman//Mailman/Logging/StampedLogger.py",
>line 52, in __init__
>    Logger.__init__(self, category, nofail, immediate)
>  File "/usr/local/bin/mailman//Mailman/Logging/Logger.py", line 50, in __init__
>    self.__get_f()
>  File "/usr/local/bin/mailman//Mailman/Logging/Logger.py", line 68, in __get_f
>    1)
>  File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/codecs.py",
>line 566, in open
>    file = __builtin__.open(filename, mode, buffering)
>IOError: [Errno 13] Permission denied: '/usr/local/bin/mailman/logs/error'
<snip>
>
>
>FYI, the log directory and even all the mailman directory is owned by
>mailman:mailman


The web server cannot write the error log. Are all the wrappers in
$mailman/cgi-bin/ group mailman and do they all have the SETGID bit
set?

E.g., -rwxr-sr-x xxxx mailman


If this is OK, I seem to recall some Apple issue mentioned on this list
a couple of years ago. Search the archives.
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.018.htp>


Was there anything else on the page before this about the initial
problem that it was trying to write to the error log?



>And in /logs/error , it says
>
>
>Aug 01 00:02:04 2007 (432) Uncaught runner exception: multipart message with
> no defined boundary
>Aug 01 00:02:04 2007 (432) Traceback (most recent call last):
>  File "/usr/local/bin/mailman//Mailman/Queue/Runner.py", line 100, in _oneloop
>    msg, msgdata = self._switchboard.dequeue(filebase)
>  File "/usr/local/bin/mailman//Mailman/Queue/Switchboard.py", line 164, in dequ
>eue
>    msg = email.message_from_string(msg, Message.Message)
>  File "/usr/local/bin/mailman/pythonlib/email/__init__.py", line 51, in message
>_from_string
>    return Parser(_class, strict=strict).parsestr(s)
>  File "/usr/local/bin/mailman/pythonlib/email/Parser.py", line 75, in parsestr
>    return self.parse(StringIO(text), headersonly=headersonly)
>  File "/usr/local/bin/mailman/pythonlib/email/Parser.py", line 64, in parse
>    self._parsebody(root, fp, firstbodyline)
>  File "/usr/local/bin/mailman/pythonlib/email/Parser.py", line 246, in _parsebo
>dy
>    raise Errors.BoundaryError(
>BoundaryError: multipart message with no defined boundary
>Aug 01 00:02:04 2007 (432) Ignoring unparseable message: 1181090435.8718021+ee06
>64d951288e0b7e6fb4b4e2b0efdc18362709


This error is from an incoming post that is unparseable - almost
certainly spam. The message was discarded.


>and this error log has only been written twice since I restored this
>directory, although I've accessed the web page tons of times.


The web server can't write the error log.


-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan