At 01:04 AM 3/29/02 -0500, Ron Jarrell wrote: >At 02:45 PM 3/27/02 -0500, Barry A. Warsaw wrote: > >>>>>>> "RJ" == Ron Jarrell <[EMAIL PROTECTED]> writes: >> >> RJ> Now, I'd believe there was something wrong with the header >> RJ> (although mm ought to catch this more elegantly), except the >> RJ> user had just sent it to list1@myserver,list2@myserver, and it >> RJ> made it to *list2*, it just won't go through to list1. I >> RJ> unshunted it, and it failed again the same way. >> >> RJ> So how in heck did it get to list2? >> >> RJ> Barry, I saved the copy I got (I'm on both lists), and the >> RJ> shunt files, if you want them; there's nothing private in the >> RJ> message. >> >>Yes, please do send them to me! >>-Barry > > >Hey, Barry? It's the topic processor causing it. I got a second message to that >same list that generated the same error. I'd tried turning off topics before, since >that was one of the two differences between the working, and non working, list. >But when I did that, I didn't *delete* the topic, I just disabled it. (Although, if >topics are disabled, that really should skip all the topic header scanning... >Apparently >it doesn't.)
Barry, did any of your recent fixes address this one? I've been avoiding putting back topics for now. _______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
