An upstream bug in dspam-3.10.1 causes "invalid byte sequence" errors with PostgreSQL >9.0. This may result in mail getting lost since it is swallowed by dspam. The bug is already fixed in the VCS version of dspam and will be released as part of 3.10.2. From the dspam mailing list: http://sourceforge.net/mailarchive/forum.php?thread_name=4ED4E8C7.3050205%40whyscream.net&forum_name=dspam-user Reproducible: Always
Note that there's simple workaround: setting standard_conforming_strings=off in postgresql.conf (not nice but it works).
dspam-3.10.2 came out today which has this issue fixed.
+*dspam-3.10.2 (24 Apr 2012) + + 24 Apr 2012; Eray Aslan <eras@gentoo.org> +dspam-3.10.2.ebuild: + Version bump. Fixes bug #392407 + For the record, dspam-3.10.2 was released on April 23rd, 2012.
Thanks a bunch! (The update hit the download servers a while before it was announced on the mailing list.)