Your message dated Fri, 16 Jun 2006 06:47:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#344373: fixed in spampd 2.30-5 has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: spampd Version: 2.30-1 Severity: important Hi, at first I have to thank you for the - so far - well working spampd. Something I've waited for for a long time. After installing there popped two things in my eyes: 1. weird %s in syslog: For every scanned mail spampd generates several lines like Dec 20 04:59:31 one spampd[5490]: %s in the log. After looking through the resolved bugs I think this could probably be a result of the fix introduced in #332259, probably it's unnessessary now due to changes in the perl libraries!? That's only a guess. 2. spamassassin/autolearn uses /root/.spamassassin After checking the output of spampd in the emails I've seen an autolearn=failed entry from spamassassin. Starting spampd in debugging mode showed, that spampd's spammassassin tries to put it's stuff into /root/.spamassassin/: [28638] dbg: config: using "/root/.spamassassin/user_prefs" for user prefs file [28638] dbg: bayes: no dbs present, cannot tie DB R/O: /root/.spamassassin/bayes_toks [28638] dbg: bayes: no dbs present, cannot tie DB R/O: /root/.spamassassin/bayes_toks [28638] dbg: locker: safe_lock: created /root/.spamassassin/auto-whitelist.lock.one.recluse.de.28638 [28638] dbg: locker: safe_lock: trying to get lock on /root/.spamassassin/auto-whitelist with 0 retries [28638] dbg: locker: safe_lock: link to /root/.spamassassin/auto-whitelist.lock: link ok [28638] dbg: auto-whitelist: tie-ing to DB file of type DB_File R/W in /root/.spamassassin/auto-whitelist [28638] dbg: locker: safe_unlock: unlink /root/.spamassassin/auto-whitelist.lock This works while starting the daemon - seems it's still running as root at this time, but as soon as it has given up root rights and it's running as spampd it should be unable to access /root/.spamassassin, at least on a well configured system. [pid 31947] stat("/root/.spamassassin/bayes_toks", 0x508550) = -1 EACCES (Permission denied) [pid 31947] stat("/root/.spamassassin/bayes_toks.db", 0x508550) = -1 EACCES (Permission denied) [pid 31947] stat("/root/.spamassassin", 0x508550) = -1 EACCES (Permission denied) [pid 31947] stat("/root/.spamassassin", 0x508550) = -1 EACCES (Permission denied) [pid 31947] mkdir("/root/.spamassassin", 0700) = -1 EACCES (Permission denied) [pid 31947] stat("/root/.spamassassin", 0x508550) = -1 EACCES (Permission denied) This bug is a bit critical imho, such a daemon should not even try to access stuff in /root. To fix this spampd needs a home-directory (like /var/lib/spampd or something like that) and the spamassassin part should be loaded as the user spampd - or is there any reason to do this before giving up root rights? Unfortunately I can't come up with a path for this - my knowledge of perl is much much too minimal. If you need any more informations or if you have a bugfix to test please let me know. Best regards, Bernd Zeimetz -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14.2-grsec Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages spampd depends on: ii adduser 3.80 Add and remove users and groups ii dpkg 1.13.11 package maintenance system for Deb ii libnet-server-perl 0.89-1 An extensible, general perl server ii perl 5.8.7-7 Larry Wall's Practical Extraction ii spamassassin 3.1.0a-1 Perl-based spam filter using text spampd recommends no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Source: spampd Source-Version: 2.30-5 We believe that the bug you reported is fixed in the latest version of spampd, which is due to be installed in the Debian FTP archive: spampd_2.30-5.diff.gz to pool/main/s/spampd/spampd_2.30-5.diff.gz spampd_2.30-5.dsc to pool/main/s/spampd/spampd_2.30-5.dsc spampd_2.30-5_all.deb to pool/main/s/spampd/spampd_2.30-5_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sven Mueller <[EMAIL PROTECTED]> (supplier of updated spampd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Fri, 16 Jun 2006 15:26:49 +0200 Source: spampd Binary: spampd Architecture: source all Version: 2.30-5 Distribution: unstable Urgency: low Maintainer: Sven Mueller <[EMAIL PROTECTED]> Changed-By: Sven Mueller <[EMAIL PROTECTED]> Description: spampd - spamassassin based SMTP/LMTP proxy daemon Closes: 344373 Changes: spampd (2.30-5) unstable; urgency=low . * Add special "user" configuration file only accessed by spampd's SpamAssassin Instance (closes: #344373) * Revert postinst to use dh_installinit built-in option to call an error handler if the init script fails. * Move dependencies from build-depends-indep to build-depends (since they must also be fulfilled when calling the clean target) Files: 5f095a9888534b8ccd777193ebd479e4 562 mail optional spampd_2.30-5.dsc 8fe6e7796c1b4f5aefb4b8e4c78f8ac0 13155 mail optional spampd_2.30-5.diff.gz dc547096cba98ffdee99d1539b8dec0d 51996 mail optional spampd_2.30-5_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEkrRgDcs5RBTUBgsRAv9FAJ0Q8zgZwriPKkJIexYYKL4/FmWEcgCfTPXY l0TR0oz5b3WqzWwB2CXb89w= =9ZHI -----END PGP SIGNATURE-----
--- End Message ---
