On Jun 26, 2010, at 2:44 PM, Terry Barnum wrote: > I noticed this morning that dspam had quit last night, 6/25, and restarted it > but it quit again about 10 minutes later. The last change made to dspam.conf > was on 6/23, turning off ParseToHeader. > > There are 59 messages in the postfix queue and when I try to do a postfix > flush, dspam quits. It seems that there's one or more messages causing dspam > to quit? If this is the case, how can I figure out which one? I thought maybe > to move all deferred mail into the hold queue and then release one by one, > but I can't see how to release just one.
Okay, figured this part out. I missed the postsuper -H <MessageID> in the manpage. I've put all deferred messages into the hold queue and am moving ones out that arrived later the approximate time that dspam quit last night. Those are being delivered by a postfix flush. I hope to be able to narrow it down this way. Thanks, -Terry ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
