I have identified the cause of dspam crashing: it occurs when I try to migrate a user .css file from one server to another.
Steps: 1 On new server, delete all data files for a given user under /var/db/dspam/data 2. Start dspam, submit a mail for that user. 3. dspam recreates ../data/ directories and files, such as *.log and *.css. 4. Stop dspam. Copy (scp) .css file from old sever to new server. 5. Restart dspam on new server. Submit new mail. dspam dies. Questions: 1. How does one correctly migrate dpsam data from one server to another? 2. Does machine architecture matter? In my case, old server is 64-bit, new server is 32-bit. Thanks Colin -- View this message in context: http://dspam-users.2290790.n4.nabble.com/dspam-dying-after-connection-tp4641107p4641120.html Sent from the dspam users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
