Package: spamassassin Version: 3.1.0a-1bpo1 Followup-For: Bug #194686 Hi.
I never had a pre-Sarge version installed (well, actually: I started installing the system with Sarge while Sarge was still Testing), but I still get the following error message in my logs: auto-whitelist: open of auto-whitelist file failed: auto-whitelist: cannot open auto_whitelist_path /etc/spamassassin/locks/awl: Inappropriate ioctl for device My local.cf contains: use_auto_whitelist 1 auto_whitelist_factory Mail::SpamAssassin::SQLBasedAddrList auto_whitelist_factor 0.3 auto_whitelist_path /etc/spamassassin/locks/awl auto_whitelist_file_mode 0775 user_awl_dsn DBI:mysql:spamassassin:localhost user_awl_sql_username spamassassin user_awl_sql_password ******** user_awl_sql_override_username nobody Can you please give me a hint how to get rid of that error message? I must admit, that SA seems to work well even with that error message, but getting it once per email in my logs isn't exactly nice. It seems to be from /usr/share/perl5/Mail/SpamAssassin/DBBasedAddrList.pm, lines 72ff. I could avoid setting auto_whitelist_path, but if I do, I get: auto-whitelist: open of auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile /root/.spamassassin/auto-whitelist.lock.mail1.incase.de.790 for /root/.spamassassin/auto-whitelist.lock: Permission denied when spamassassin is used in spampd (running as user spampd). So this is not exactly what could help here. The ioctl error occures independently of the version of perl installed (tried both the version from stable as well as the version from stable/updates). It is also independent of the filesystem in use (I tried ext3, xfs and tmpfs). I'm however unable to track this problem down any further than to the location named above since I don't know SpamAssassin itself or Perl well enough to do that. A quick web search however seems to indicate that this error _might_ result from the use of improper header files while compiling gcc or perl. So if you are able to track that down, you might need to reassign the bug to perl or gcc. Regards, Sven -- System Information: Debian Release: 3.1 APT prefers stable APT policy: (990, 'stable'), (400, 'experimental'), (90, 'testing'), (50, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11.12-incase Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages spamassassin depends on: ii libdigest-sha1-perl 2.10-1 NIST SHA-1 message digest algorith ii libhtml-parser-perl 3.45-2 A collection of modules that parse ii libnet-dns-perl 0.48-1 Perform DNS queries from a Perl sc ii libsocket6-perl 0.17-1 Perl extensions for IPv6 ii perl 5.8.4-8 Larry Wall's Practical Extraction Versions of packages spamassassin recommends: ii libmail-spf-query-perl 1.997-2 Query SPF (Sender Permitted From) ii perl [libmime-base64-perl] 5.8.4-8 Larry Wall's Practical Extraction ii spamc 3.1.0a-1bpo1 Client for SpamAssassin spam filte -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
