A couple days ago our digests stopped going out automatically. I forced it
to run this morning via a special cron entry and received the following
report. Can anyone give me a clue as to where to go find out what's
happening?Thanks.
Traceback (most recent call last):
File "/usr/home/circle
> "LR" == Luigi Rosa <[EMAIL PROTECTED]> writes:
LR> Mybe I should rephrase my question.
LR> Would'nt it be better if mailman can log either in a logfile
LR> or in a user configurable SysLog facility?
LR> I mean, for each logfile that mm creates, could it be possible
LR>
After playing with this a bit, I've found that it's specificly because of
the Windows-1252 charset not being recognized. The linefeed/tab in the
header didn't make any difference as it choked on another message that
didn't have the linefeed/tab, but was also Windows-1252 charset.
Now... a new pr
saw this on bugtraq, figuried it was a good idea to relay here.
MJM
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 24, 2003 9:35 AM
Subject: [ham] Mailman: cross-site scripting bug
>
>
> Product: Mailman
> Affected Version: 2.1 not other
Hmm,
Looks this is the cause of problem in Cgi/options.py
# Avoid cross-site scripting attacks
safeuser = Utils.websafe(user)
# Sanity check the user, but be careful about leaking membership
# information when we're using private rosters.
if not mlist.isMember(user) and mlist.
VLists.Net Support wrote:
After playing with this a bit, I've found that it's specificly because of
the Windows-1252 charset not being recognized. The linefeed/tab in the
header didn't make any difference as it choked on another message that
didn't have the linefeed/tab, but was also Windows-1252
