Re: [Mailman-Users] Help! Digest went nuts!

2001-06-05 Thread Barry A. Warsaw


 CVR == Chuq Von Rospach [EMAIL PROTECTED] writes:

 Who's file I/O routines?  Is the MTA mistaking the NUL for an
 EOF?

CVR AFAIKT, it's Python's, and mailman. my archives of the raw
CVR input shows that sendmail was passing it along to mailman,
CVR and mailman was doing the truncation.

This does ring a bell.  I thought we had dealt with some NUL problems
a while ago.  I guess I'll have to troll through the log messages and
archives to see if I can recall the details.

-Barry


--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users



Re: [Mailman-Users] Help! Digest went nuts!

2001-06-04 Thread Barry A. Warsaw


 S == Steph  [EMAIL PROTECTED] writes:

S Here are some facts: * The digest came out incomplete -- it
S broke off in the middle of one of the messages.

Take a look at Mailman's error log file, $prefix/logs/error to see if
you're getting any Python tracebacks.  Could be as you suspect, a
rogue character or some other bogosity is crashing the digesting code,
but for some reason still getting sent out with the partial digest.  A
traceback would help track this down.

Also, you don't say what version of Mailman you're running.  When
encountering problems, please always say what OS you're using, the
version of Python and the version of Mailman (at a minimum)!

-Barry

--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users



Re: [Mailman-Users] Help! Digest went nuts!

2001-06-04 Thread Chuq Von Rospach


On Monday, June 4, 2001, at 10:21 PM, Barry A. Warsaw wrote:


 S == Steph  [EMAIL PROTECTED] writes:

 S Here are some facts: * The digest came out incomplete -- it
 S broke off in the middle of one of the messages.

 Take a look at Mailman's error log file, $prefix/logs/error to see if
 you're getting any Python tracebacks.

if the log shows nothing, I've seen this before. turns out a user had an 
embedded NUL character (ascii 0), and it caused the file I/O routines to 
see a premature EOF. Mailman needs to protect itself from this by 
stripping weird ascii characters as the messages enter the system...


--
Chuq Von Rospach, Internet Gnome http://www.chuqui.com
[[EMAIL PROTECTED] = [EMAIL PROTECTED] = [EMAIL PROTECTED]]
Yes, yes, I've finally finished my home page. Lucky you.

   To the optimist, the glass is half full.
   To the pessimist, the glass is half empty.
   To the engineer, the glass is twice as big as it needs to be.



--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users



Re: [Mailman-Users] Help! Digest went nuts!

2001-06-04 Thread Barry A. Warsaw


 CVR == Chuq Von Rospach [EMAIL PROTECTED] writes:

CVR if the log shows nothing, I've seen this before. turns out a
CVR user had an embedded NUL character (ascii 0), and it caused
CVR the file I/O routines to see a premature EOF. Mailman needs
CVR to protect itself from this by stripping weird ascii
CVR characters as the messages enter the system...

Who's file I/O routines?  Is the MTA mistaking the NUL for an EOF?  If
so, what MTA are you using Steph?  It should be easy to strip out the
NUL's by adding one line to SMTPDirect.py.  At the top of the function
deliver(), add something like the following (untested!):

msgtext = string.replace(msgtext, '\0', '')

or, if you're using Python 2.x

msgtext = msgtext.replace('\0', '')

-Barry

--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users



Re: [Mailman-Users] Help! Digest went nuts!

2001-06-04 Thread Steph

thanks again for the suggestions! I'll have to forward them on to the folks 
who are allowed to get at the Python code. Unfortunately, I don't know 
which version of Python they're using -- but this sounds like it *might* be 
the key we need!

Cheers,
Steph

At 01:43 AM 6/5/01 -0400, Barry wrote:

  CVR == Chuq Von Rospach [EMAIL PROTECTED] writes:

 CVR if the log shows nothing, I've seen this before. turns out a
 CVR user had an embedded NUL character (ascii 0), and it caused
 CVR the file I/O routines to see a premature EOF. Mailman needs
 CVR to protect itself from this by stripping weird ascii
 CVR characters as the messages enter the system...

Who's file I/O routines?  Is the MTA mistaking the NUL for an EOF?  If
so, what MTA are you using Steph?  It should be easy to strip out the
NUL's by adding one line to SMTPDirect.py.  At the top of the function
deliver(), add something like the following (untested!):

 msgtext = string.replace(msgtext, '\0', '')

or, if you're using Python 2.x

 msgtext = msgtext.replace('\0', '')

-Barry


--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users



Re: [Mailman-Users] Help! Digest went nuts!

2001-06-04 Thread Chuq Von Rospach


On Monday, June 4, 2001, at 10:43 PM, Barry A. Warsaw wrote:

 Who's file I/O routines?  Is the MTA mistaking the NUL for an EOF?

AFAIKT, it's Python's, and mailman. my archives of the raw input shows 
that sendmail was passing it along to mailman, and mailman was doing the 
truncation.


--
Chuq Von Rospach, Internet Gnome http://www.chuqui.com
[[EMAIL PROTECTED] = [EMAIL PROTECTED] = [EMAIL PROTECTED]]
Yes, yes, I've finally finished my home page. Lucky you.

Stress is when you wake up screaming and you realize you haven't fallen 
asleep yet.




--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users