Package: spamassassin Version: 3.1.4-1 Severity: normal Hi,
I just wanted to report that it's problematic spamd is started before nscd, this produces failed getpwnam calls for some users (which are stored in ldap) on my system, if I restart spamd afterwards, everything is fine. Greetings, Thomas Jahns -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (900, 'unstable'), (500, 'stable'), (200, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-mercury Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages spamassassin depends on: ii libarchive-tar-perl 1.30-1 Archive::Tar - manipulate tar file ii libdigest-sha1-perl 2.11-1 NIST SHA-1 message digest algorith ii libhtml-parser-perl 3.55-1 A collection of modules that parse ii libsocket6-perl 0.19-1 Perl extensions for IPv6 ii libwww-perl 5.805-1 WWW client/server library for Perl ii perl 5.8.8-6.1 Larry Wall's Practical Extraction Versions of packages spamassassin recommends: pn libmail-spf-query-perl <none> (no description available) ii libnet-dns-perl 0.59-1 Perform DNS queries from a Perl sc ii perl [libmime-base64-perl] 5.8.8-6.1 Larry Wall's Practical Extraction ii spamc 3.1.4-1 Client for SpamAssassin spam filte -- debconf information: spamassassin/upgrade/2.40: spamassassin/upgrade/2.40w: spamassassin/upgrade/cancel: Continue spamassassin/upgrade/2.42m: No spamassassin/upgrade/2.42u: No -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
