🚀 go-pugleaf

anybody have a fix for this problem?  sendmail gets to delivering a
bunch of the messages and then dumps core.  the core doesn't tell you
much, since the stack gets all trashed.  chris torek claims it's a
setlmp/longjmp problem and that a timer goes off and restores the wrong
context, thus sending it off into never-never land.  something with
confusion between the two timeouts (each copy vs. the whole message).
of course, the lock files aren't removed and the q files aren't
updated, so it results in multiple copies of messages when the lock
files get removed ... i see this a lot on mailing lists that are long,
including the BIND mailing list on ucbarpa.Berkeley.EDU (which is a
VAX, so it's probably inherent to 5.59 generally).

/jordan