in daemon mode, dspam occasionally crashes with 'Unable to determine the runtime user'

Binary package hint: dspam

Distribution Information (cat /etc/lsb-release):
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=6.06
DISTRIB_CODENAME=dapper
DISTRIB_DESCRIPTION="Ubuntu 6.06.2 LTS"
---

Package Information (dpkg -l dspam | cat):
ii dspam 3.6.4-4 is a scalable, fast and statistical anti-spam filter
---

An extract from /var/log/mail.log:

Feb 11 02:50:51 xxxxxx dspam[4254]: Unable to determine the runtime user
Feb 11 02:50:51 xxxxxx postfix/virtual[29111]: 4363E1A97FB: to=<xxxxxx@xxxxxx>, relay=virtual, delay=1, status=sent (delivered to maildir)
Feb 11 02:50:51 xxxxxx postfix/lmtp[29113]: 742371A97E8: to=<xxxxxx@xxxxxx>, relay=/var/run/dspam.sock[/var/run/dspam.sock], delay=2, status=deferred (lost connection with /var/run/dspam.sock[/var/run/dspam.sock] while sending end of data -- message may be sent more than once)
Feb 11 02:50:51 xxxxxx postfix/lmtp[29122]: 1364F1A97FA: to=<xxxxxx@xxxxxx>, relay=/var/run/dspam.sock[/var/run/dspam.sock], delay=2, status=deferred (lost connection with /var/run/dspam.sock[/var/run/dspam.sock] while sending MAIL FROM)
Feb 11 02:50:51 xxxxxx postfix/lmtp[29119]: 03FFA1A97F9: to=<xxxxxx@xxxxxx>, relay=/var/run/dspam.sock[/var/run/dspam.sock], delay=2, status=deferred (lost connection with /var/run/dspam.sock[/var/run/dspam.sock] while sending end of data -- message may be sent more than once)
Feb 11 02:50:52 xxxxxx postfix/lmtp[29113]: 742371A97E8: to=<xxxxxx@xxxxxx>, orig_to=<xxxxxx@xxxxxx>, relay=/var/run/dspam.sock[/var/run/dspam.sock], delay=3, status=deferred (lost connection with /var/run/dspam.sock[/var/run/dspam.sock] while sending end of data -- message may be sent more than once)
...(cut)...
Feb 11 02:50:55 xxxxxx postfix/lmtp[29119]: 164D91A97FD: to=<xxxxxx@xxxxxx>, relay=none, delay=1, status=deferred (connect to /var/run/dspam.sock[/var/run/dspam.sock]: Connection refused)

What happened: like what were reported in Debian Bug #385353, fixed with a patch (http://<email address hidden>/msg429574.html)

I tried to patch version 3.6.4 by myself, but patching requires dspam version 3.6.8.
So it would be useful to sync dspam 3.6.8-6 (universe) from Debian unstable (main) as done for bug #186399 also for dapper, maybe putting the package into dapper-backports.