This problem seems to be a little more serious then I thought. It
appears that no HTML attachments are getting through mailman. In
addition to the unparsable error I am also getting a non-text
attachment was scrubbed error and one message went into a black hole
(no message distributed and
At 8:24 AM -0400 2005-06-27, Dennis Putnam wrote:
How can I debug this when there is nothing in the logs?
Good question.
Is
there a verbose mode switch I can turn on? TIA.
Nope, no verbose
Hm.. Shunt queue? Maybe that would at least let me know what Mailman
is looking that it can't parse, just in case something unexpected is
being inserted along the way. Where is that directory? I see nothing in
the /var/mailman path that looks like a shunt queue.
I'm not a Python programmer so
At 9:01 AM -0400 2005-06-27, Dennis Putnam wrote:
Hm.. Shunt queue? Maybe that would at least let me know what Mailman
is looking that it can't parse, just in case something unexpected is
being inserted along the way. Where is that directory? I see nothing in
the /var/mailman path that
Thanks. It is in /var/mailman/qfiles but the shunt directory is empty.
Rats!
On Jun 27, 2005, at 9:07 AM, Brad Knowles wrote:
Normally, it would be located under /usr/local/mailman/qfiles/shunt,
but it appears that the version of Mailman you're using on your
platform has put that
Dennis Putnam wrote:
Thanks. It is in /var/mailman/qfiles but the shunt directory is empty.
Rats!
Not surprising since normally there is a message in the 'error' log
when a message is shunted.
On the original question, have you looked at your list's Content
filtering Section? I suggest that
After some research I have concluded that the errors I am getting from
Mailman are because of a malformed MIME content. Since I am creating
the message myself with a php page I am not surprised (my first time).
Since this probably is a MIME issue I know this is not the correct
forum.
Hi,
Dennis Putnam wrote:
After some research I have concluded that the errors I am getting from
Mailman are because of a malformed MIME content. Since I am creating
the message myself with a php page I am not surprised (my first time).
Since this probably is a MIME issue I know this
I am having a problem with some message not being distributed. When I
look at the error file I can see this:
Jun 23 11:34:34 2005 (3512) message is unparsable:
1119540873.457257+d314fcd9d886c11a670875a479fab98a5fdbde1e
Jun 23 11:34:34 2005 (3512) lost data files for filebase:
