Hi,I had same situation with the same set up (OpenBSD 4.0-stable, postfix 2.3.x, mysql 5.0, dspam 3.6.8). I found that one message causing dspam to segfault. Look at the postfix queue, are there any messages? If so force them to deliver mailq -q. dspam probably will crash. if so requeue messages by one postsuper -r <message id>, wait about 10-30 sec. postfix will try to deliver this message again, do it with the rest messages while bad message found. This is how I did. Actualy message that caused dspam to crash was from dspam mailing list (this message is attached bad_mail.tgz)
If it is not the same situation as yours then sorry. I wrote to mailing list about this issue but no answer. Also sent the same email to openbsd dspam maintainer, but also no reply.
Dspam wrote:
Hi, I am running dspam on a OpenBSD 4.0-stable. It works not very well. I have many segmentations fault. It run with Postfix like in doc/postfix.txt : postfix delivers to dspam via lmtp socket (/tmp/dspam.sock) Some times i have "connection timeout" so i have added -o lmtp_data_done_timeout=1200 and it work. But i still have many segmentations faults ( ~ 30/day). What can i do ?My dspam version : DSPAM Anti-Spam Suite 3.6.8 (agent/library)Configuration parameters: --with-storage-driver=mysql_drv --with-mysql-libraries=/usr/local/lib/mysql --with-mysql-includes=/usr/local/include/mysql --enable-virtual-users --enable-preferences-extension --enable-domain-scale --with-dspam-owner=_dspam --with-dspam-group=_dspam --with-dspam-home=/var/dspam --enable-daemon Any help would be very appreciated Thanks
bad_mail.tgz
Description: application/compressed
