http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4645
------- Additional Comments From [EMAIL PROTECTED] 2005-10-28 16:27 ------- (In reply to comment #1) > Normally one doesn't run spamassassin with no parameters and no input. Can > you try That is true. I was just providing the simplest cast that failed. Each incoming msg caused a core file in my home directory meaning each procmail invocation of spamassassin crashed. > Q: Why do you flag this as a critical SA item, if SA does not fail on its own, > but only if you insist on using snoopylogger? I would think you would at least > open a snoopylogger bug so it would be worked on from that end also, no? You have a valid point. I flagged SA because no other application I am running has shown a problem. It seems specific to SA / snoopylogger interaction and it causes the filesystem to fill up with core files. > Also, reading > http://sourceforge.net/tracker/index.php?func=detail&aid=612504&group_id=9226&atid=109226 > suggests that this may very well be a problem within snoopylogger, since the > symptom (segmentation failure) seems the same. Thank you for pointing this out. I will examine the snoopylogger code in detail and see if I can fix that myself. Perhaps the segfault is within a subsequent exec call with corrupted argument sizes. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
