>Ok, good find. Now I wonder why I haven't seen this in 2 years of >running it. Surely I must have had some line somewhere that caused the >buffer to overflow---but then again, maybe this just reveals how >uncommon it is for email systems to violate the line length restriction >in emails.
It wouldn't surprise me that a SINGLE byte buffer overflow wouldn't necessarily trigger a crash on all systems. It sounds like what happened here was the malloc pool got corrupted and future allocations stepped over a previously-allocated buffer. If the system malloc() implementation ended up doing something like rounding up some allocations to some alignment-based size, you might not see it. --Ken
