Bug#989137: cockpit-ws: No sysvinit script
On 5/27/21 1:57 PM, Martin Pitt wrote: Hello Simon, Simon Walter [2021-05-27 10:17 +0900]: I was trying to make it quicker to deploy for those who run it like this anyway, but I understand not wanting to be responsible for partially functioning software. In that case, shall I open a bug to make systemd a dependency? This is already the case, in Debian testing (and thus upcoming Debian 11), cockpit-ws has a Depends: systemd (>= 235). Thanks! Martin Excellent. Thank you so much. Sorry to take your time. Best regards, Simon
Bug#989137: cockpit-ws: No sysvinit script
Package: cockpit-ws
Version: 188-1
Severity: normal
Tags: patch
Dear Maintainer,
Here is a patch for a sysvinit script.
-- System Information:
Debian Release: 10.9
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit
LSM: AppArmor: enabled
Versions of packages cockpit-ws depends on:
ii adduser 3.118
ii glib-networking 2.58.0-2+deb10u2
ii libc6 2.28-10
ii libglib2.0-02.58.3-2+deb10u2
ii libgssapi-krb5-21.17-3+deb10u1
ii libjson-glib-1.0-0 1.4.4-2
ii libkrb5-3 1.17-3+deb10u1
ii libpam0g1.3.1-5
ii libsystemd0 241-7~deb10u7
ii openssl 1.1.1d-0+deb10u6
cockpit-ws recommends no packages.
cockpit-ws suggests no packages.
-- no debconf information
#!/bin/sh
### BEGIN INIT INFO
# Provides: cockpit
# Required-Start:$local_fs $network $named $time $syslog
# Required-Stop: $local_fs $network $named $time $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: cockpit management webserver
# Description: cockpit management webserver
### END INIT INFO
cmd="/usr/sbin/remotectl certificate --ensure --user=root --group=cockpit-ws
--selinux-type="
cmd1="/usr/lib/cockpit/cockpit-ws"
name=$(basename "$0")
pid_file="/var/run/$name.pid"
stdout_log="/var/log/$name.log"
stderr_log="/var/log/$name.err"
test -x "$cmd1" || exit 0
get_pid() {
cat "$pid_file"
}
is_running() {
[ -f "$pid_file" ] && ps -p "$(get_pid)" > /dev/null 2>&1
}
case "$1" in
start) if is_running; then
echo "Already started"
else
echo "Starting $name"
$cmd >> "$stdout_log" 2>> "$stderr_log"
$cmd1 >> "$stdout_log" 2>> "$stderr_log" &
echo $! > "$pid_file"
if ! is_running; then
echo "Unable to start, see $stdout_log and $stderr_log"
exit 1
fi
fi
;;
stop) if is_running; then
echo "Stopping $name.."
kill "$(get_pid)"
i=0
while [ "$i" -lt 10 ]
do
if ! is_running; then
break
fi
echo "."
sleep 1
i=$((i+1))
done
echo
if is_running; then
echo "Not stopped; may still be shutting down or shutdown
may have failed"
exit 1
else
echo "Stopped"
if [ -f "$pid_file" ]; then
rm "$pid_file"
fi
fi
else
echo "Not running"
fi
;;
restart) $0 stop
if is_running; then
echo "Unable to stop, will not attempt to start"
exit 1
fi
$0 start
;;
status) if is_running; then
echo "Running"
else
echo "Stopped"
exit 1
fi
;;
*) echo "Usage: $0 {start|stop|restart|status}"
exit 1
;;
esac
exit 0
Bug#797722: spamassassin cron.daily fails with permission denied for tmp file
On 12.05.2017 00:52, Noah Meyerhans wrote: > On Tue, Sep 01, 2015 at 10:57:57PM +0000, Simon Walter wrote: >> Package: spamassassin >> Version: 3.4.0-6 >> >> cron.daily spamassassin fails because the tmp file can't be created. script >> seems to be executed in /root/ > This bug has been open for ages. I'd like to either figure out what went > wrong, or close it. Has this issue recurred? Have you managed to work > around it locally? I haven't heard any similar reports, so it seems like > it's dependent on something specific to your environment. > > Have you tried the 3.4.1 packages from stretch of jessie-backports? > I'm not sure how it was resolve and don't remember how to reproduce it. Sorry for this bugreport. You can close it. -- Regards Simon signature.asc Description: OpenPGP digital signature
Bug#831638: mysql-server: mysql_install_db in postinst script does not run
Package: mysql-server Severity: important Dear Maintainer, I tried to install mysql-server on a system with no logger. mysql_install_db in postinst script does not run. The offending line is "bash /usr/bin/mysql_install_db --user mysql --rpm 2>&1 | $ERR_LOGGER". I would suggest checking if a logger is present before using it. -- System Information: Architecture: i386 (i686) Kernel: Linux 3.16.0-4-586 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#831639: mariadb-server: mysql_install_db in postinst script does not run
Package: mariadb-server Version: 10.0.25-0+deb8u1 Severity: important Dear Maintainer, I tried to install mariadb-server on a system with no logger. mysql_install_db in postinst script does not run. The offending line is "bash /usr/bin/mysql_install_db --user mysql --rpm 2>&1 | $ERR_LOGGER". I would suggest checking if a logger is present before using it. -- System Information: Architecture: i386 (i686) Kernel: Linux 3.16.0-4-586 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages mariadb-server depends on: ih mariadb-server-10.0 10.0.25-0+deb8u1 mariadb-server recommends no packages. mariadb-server suggests no packages. -- no debconf information
Bug#797722: spamassassin cron.daily fails with permission denied for tmp file
Package: spamassassin Version: 3.4.0-6 cron.daily spamassassin fails because the tmp file can't be created. script seems to be executed in /root/ /etc/cron.daily/spamassassin: util: failed to create a temporary file '/.spamassassin9891RWTlsmtmp': Permission denied at /usr/share/perl5/Mail/SpamAssassin/Util.pm line 1123. sa-update failed for unknown reasons Possible solutions: - cron-script could specifiy /tmp or /var/lib/spamassassin when starting sa-update - Util.pm tries to use Env-Var TMPDIR which doesn't seems to be configured, so it could be set to /tmp or /var/lib/spamassassine for the execution of sa-update -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-0.bpo.1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages spamassassin depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.22 pn libarchive-tar-perl ii libhtml-parser-perl 3.71-1+b3 ii libnet-dns-perl 0.81-2 ii libnetaddr-ip-perl 4.075+dfsg-1+b1 ii libsocket6-perl 0.25-1+b1 ii libsys-hostname-long-perl 1.4-3 ii libwww-perl 6.08-1 ii perl5.20.2-3+deb8u1 ii perl-modules [libio-zlib-perl] 5.20.2-3+deb8u1 Versions of packages spamassassin recommends: ii gnupg 1.4.18-7 ii libio-socket-inet6-perl2.72-1 ii libmail-spf-perl 2.9.0-3 ii perl [libsys-syslog-perl] 5.20.2-3+deb8u1 pn sa-compile ii spamc 3.4.0-6 Versions of packages spamassassin suggests: ii libdbi-perl 1.631-3+b1 ii libio-socket-ssl-perl 2.002-2 pn libmail-dkim-perl ii perl [libcompress-zlib-perl] 5.20.2-3+deb8u1 pn pyzor pn razor -- Configuration Files: /etc/default/spamassassin changed: ENABLED=1 OPTIONS="--create-prefs --max-children 1 --helper-home-dir" PIDFILE="/var/run/spamd.pid" CRON=1 /etc/spamassassin/local.cf changed: report_safe 0 required_score 10.0 clear_report_template report "_TESTSSCORES(, )_" ifplugin Mail::SpamAssassin::Plugin::Shortcircuit endif # Mail::SpamAssassin::Plugin::Shortcircuit -- no debconf information
Bug#737601: nagios-nrpe-plugin does not need dependency checks for nagios oricinga
Package: nagios-nrpe-plugin Version: 2.13-3_i386 I have installed icinga2 from the official repositories from the Icinga project. These packages are for some reason not included on the Debian server. icinga2 needs to use nagios-nrpe-plugin - just as does icinga. However, it's dependencies are on nagios or icinga. However, if I install nagios-nrpe-plugin from the .deb file from the Debian server, it works. So I would like to suggest removing those dependencies, as it seems it is not a binary(libray) dependency. The following works and does not require the use of --force: $ dpkg -i nagios-nrpe-plugin_2.13-3_i386.deb If these dependencies are removed, one can install icinga2 without the need to compile anything. It installs quite well on Wheezy. There may have been some glitches in the db-config part with indexes being created by two different packages causing an error, which is perhaps why it's not in Wheezy yet. In any case, it will help users who want to install icinga2 from the Icinga project's servers. Kind regards, Simon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711147: bug confirmation
Package: lvm2 Version: 2.02.95-7 I want to confirm that there is a bug with the LVM2 init script. Currently # Default-Start: S Should be: # Default-Start: 2 3 4 5 I don't think there is any stopping to be done. With S as the default start runlevel, logical volumes that are mounted on drbd devices fail to start. It seems that for LVs on top of regular or md block devices, this is not needed. I thought of putting drbd as a requirement for lvm2. It was then that I noticed that it was not run on boot at all. # Required-Start:mountdevsubfs drbd The above was needed in my tests, but perhaps that is just my luck. Please look into that line as well. Thank you. Kind regards, Simon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#641495: gnucash: Crashes on Online Action-Get Transactions
~/.aqbanking/settings/accounts % touch uid%3a%3a0007.conf % l total 48 4 drwx-- 2 x 4096 Sep 16 15:04 . 4 drwx-- 7 x 4096 Sep 15 22:09 .. 4 -rw--- 1 x 421 Sep 15 22:10 uid%3a%3a0001.conf 4 -rw--- 1 x 363 Sep 15 22:10 uid%3a%3a0002.conf 4 -rw--- 1 x 368 Sep 15 22:10 uid%3a%3a0004.conf 4 -rw--- 1 x 400 Sep 15 22:10 uid%3a%3a0005.conf 4 -rw--- 1 x 425 Sep 15 22:10 uid%3a%3a0006.conf 0 -rw-r--r-- 1 x0 Sep 16 15:04 uid%3a%3a0007.conf 4 -rw--- 1 x 406 Sep 15 22:10 uid%3a%3a000a.conf 4 -rw--- 1 x 438 Sep 15 22:38 uid%3a%3a000c.conf 4 -rw--- 1 x 373 Sep 15 22:38 uid%3a%3a000e.conf 4 -rw--- 1 x 363 Sep 15 22:38 uid%3a%3a000f.conf 4 -rw--- 1 x2 Sep 15 22:38 uniqueid % aqbanking-cli listaccs 4:2011/09/16 15-04-22:aqbanking(13430):banking_cfg.c: 532: Provider (null) not found, ignoring user [(null)] aqbanking-cli: account.c:61: AB_Account_fromDb: Assertion `pname' failed. zsh: abort (core dumped) aqbanking-cli listaccs % gdb aqbanking-cli core GNU gdb (GDB) 7.3-debian Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/aqbanking-cli...Reading symbols from /usr/lib/debug/usr/bin/aqbanking-cli...done. done. [New LWP 13430] warning: Can't read pathname for load map: Input/output error. [Thread debugging using libthread_db enabled] Core was generated by `aqbanking-cli listaccs'. Program terminated with signal 6, Aborted. #0 0xb77cd424 in __kernel_vsyscall () (gdb) bt #0 0xb77cd424 in __kernel_vsyscall () #1 0xb73e1911 in raise () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 #2 0xb73e4d42 in abort () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 #3 0xb73dab28 in __assert_fail () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 #4 0xb7668d67 in AB_Account_fromDb (ab=0x9f26218, db=0xa05b728) at account.c:61 #5 0xb7672d37 in AB_Banking_LoadAllAccounts (ab=0x9f26218) at banking_cfg.c:641 #6 AB_Banking_LoadConfig (ab=0x9f26218) at banking_cfg.c:725 #7 AB_Banking_OnlineInit (ab=0x9f26218) at banking_init.c:412 #8 0x0804ce1c in listAccs (argv=0xbfd03b88, argc=1, dbArgs=0x9f25628, ab=0x9f26218) at listaccs.c:113 #9 main (argc=1, argv=0xbfd03b88) at main.c:307 (gdb) On 16.09.2011 09:48, Micha Lenk wrote: Hi Simon, On 09/15/2011 10:56 PM CEST +02:00, Simon Walter wrote: i have fixed the problem... after some gdb fiddling it was obvious the problem was in aqbanking and not gnucash. #strace aqbanking-cli listaccs showed aqbank tried to read files from ~/.aqbanking/settings/accounts and crashed, because some of them had zero-length. deleting the files helped. I would nevertheless be interested in a backtrace of your crash, because a crash is never an appropriate reaction to unexpected zero-length files... Regards, Micha
Bug#641495: gnucash: Crashes on Online Action-Get Transactions
Hi Micha, i have fixed the problem... after some gdb fiddling it was obvious the problem was in aqbanking and not gnucash. #strace aqbanking-cli listaccs showed aqbank tried to read files from ~/.aqbanking/settings/accounts and crashed, because some of them had zero-length. deleting the files helped. -- Regards Simon On 14.09.2011 12:47, Micha Lenk wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Simon, thank you for your feedback. Am 13.09.2011 23:40, schrieb Simon Walter: on any online action on an account gnucash crashes with the following message: gnucash: account.c:61: AB_Account_fromDb: Assertion `pname' failed. Can you please provide some more information on the used online action? Additionally a backtrace of your crash would be very helpful. If you're a Gnome user, can you please install the packages gnucash-dbg and bug-buddy and try to reproduce the crash? Bug-buddy should then assist you to generate the needed backtrace. Regards, Micha -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJOcIY4AAoJEOpsprlRuFE5c1kQAI3qXjf2wg06UkdTN4RVRM0n aND30ry9jA2IfloZ3pdJyUVlo7pf3WncjB4GjfLIU8S9qWanzoiQPWcJR3ENQyx5 As5fZVsWU9Ui07+p+fUs8r1tASeWjLtE8ba9/i6ZUVEXVwK6tGtvfvQ4BFtTGPy6 gquBHX+NmDpDIdcHHI6kaiCJrok/6rvRpGMOmALQRsurJbw3SllqslpKFcCLbyJm jYqOeE8O1AdhV3YuoYpVvvmH8/1Ai/9x0jmmxxbUD9BKhaeDJO5FJYn6pYrA0ets qQkf4PuaQh+nFatkj8mU9I/mfNJU+849KJnVUUQ12KccC31zdiqOFAZdyMkfCwQv y+0I0B4V6YkQYqMUIj9Qo6/iKCs94CNmdhs5ZAo+J64m0Ewn9XITS2LX2rfUe6ZK jId0uEzk+xv0AV3FtVS8/bJDCRP3pmSxmLlNV6FZUtl75uAlyN4l4pX3/flcbYXj gViLyeFgJh434HuV5akVGkuU+To5OsbxZwkKMEAlouUaRoXXf1doXQEuyGIIU+CA UjziFSC7F+8lqtEs2fIRuXy5cJoZBG4hqCI45TcX/rb4BMuOsaC0DMJBbdapeR7m bIz9rtWozA7zyd9VpQv2juObLW/geKAcJ31tkrv2lxWdZ4zUQ5oaT/ZlNmi658nC cxl8xPLmLk1qeK9l24DW =S4jL -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#641495: gnucash: Crashes on Online Action-Get Transactions
Package: gnucash Version: 1:2.4.7-1 Severity: important Dear Maintainer, on any online action on an account gnucash crashes with the following message: gnucash: account.c:61: AB_Account_fromDb: Assertion `pname' failed. -- Regards Simon -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (900, 'unstable'), (250, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnucash depends on: ii gnucash-common 1:2.4.7-1 ii guile-1.8 1.8.8+1-6 ii guile-1.8-libs 1.8.8+1-6 ii libaqbanking33 5.0.14-2 ii libart-2.0-2 2.3.21-1 ii libatk1.0-02.0.1-2 ii libbonobo2-0 2.24.3-1 ii libbonoboui2-0 2.24.3-1 ii libc6 2.13-20 ii libcairo2 1.10.2-6.1 ii libcrypt-ssleay-perl 0.57-2+b2 ii libdate-manip-perl 6.25-1 ii libdbi10.8.4-5.1 ii libfinance-quote-perl 1.17-1 ii libfontconfig1 2.8.0-3 ii libfreetype6 2.4.6-2 ii libgconf2-42.32.4-1 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglade2-01:2.6.4-1 ii libglib2.0-0 2.28.6-1 ii libgmp10 2:5.0.2+dfsg-1 ii libgnome-keyring0 3.0.3-1 ii libgnome2-02.32.1-1 ii libgnomecanvas2-0 2.30.3-1 ii libgnomeui-0 2.24.5-2 ii libgnomevfs2-0 1:2.24.4-1 ii libgoffice-0.8-8 0.8.17-1 ii libgtk2.0-02.24.6-1 ii libgwengui-gtk2-0 4.2.1-1 ii libgwenhywfar604.2.1-1 ii libhtml-tableextract-perl 2.11-1 ii libhtml-tree-perl 4.2-1 ii libice62:1.0.7-2 ii libktoblzcheck1c2a 1.34-1 ii libltdl7 2.4-4 ii libofx41:0.9.4-2 ii liborbit2 1:2.14.18-0.2 ii libpango1.0-0 1.28.4-3 ii libpopt0 1.16-1 ii libsm6 2:1.2.0-2 ii libsoup2.4-1 2.34.3-1 ii libwebkitgtk-1.0-0 1.4.2-2 ii libwww-perl6.02-1 ii libx11-6 2:1.4.4-1 ii libxml22.7.8.dfsg-4 ii perl 5.12.4-4 ii slib 3b1-3.1 ii zlib1g 1:1.2.3.4.dfsg-3 Versions of packages gnucash recommends: ii gnucash-docs 2.2.0-3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611947: madfuload: Firmware not loading
Package: madfuload
Version: 1.2-4
Severity: important
*** Please type your report below this line ***
with the current position of the 42-madfuload.rules in /lib/udev/rules.d
$env{DEVNAME} is not always set causing the following error:
Feb 3 23:05:19 tharlab udevd-work[3932]: RUN '/usr/sbin/madfuload -l -3
-f /usr/share/usb/maudio/ma006100.bin -D $env{DEVNAME}'
/lib/udev/rules.d/42-madfuload.rules:15
Feb 3 23:05:19 tharlab udevd-work[3932]: '/usr/sbin/madfuload -l -3 -f
/usr/share/usb/maudio/ma006100.bin -D ' started
Feb 3 23:05:19 tharlab udevd-work[3932]: '/usr/sbin/madfuload' (stderr)
'/usr/sbin/madfuload: option requires an argument -- 'D''
Feb 3 23:05:19 tharlab udevd-work[3932]: '/usr/sbin/madfuload' (stderr)
'Try /usr/sbin/madfuload --help for more information.'
Feb 3 23:05:19 tharlab udevd-work[3932]: '/usr/sbin/madfuload -l -3 -f
/usr/share/usb/maudio/ma006100.bin -D ' returned with exitcode 1
moving 42-madfuload.rules to 76-madfuload.rules right before
78-sound-card.rules fixed the problem for me
also the correct directory for udev.rules is probably
/lib/udev/rules.d
-- System Information:
Debian Release: 6.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages madfuload depends on:
ii libc6 2.11.2-11 Embedded GNU C Library:
Shared lib
ii udev 164-4 /dev/ and hotplug
management daemo
madfuload recommends no packages.
madfuload suggests no packages.
-- Configuration Files:
/etc/udev/rules.d/42-madfuload.rules [Errno 2] No such file or
directory: u'/etc/udev/rules.d/42-madfuload.rules'
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601599: deluge: argument mismatch between rpcserver and client
On 20.01.2011 15:39, Cristian Greco wrote: On Fri, 26 Nov 2010 17:06:43 +0100 Simon Waltersimon.wal...@hp-factory.de wrote: On 26.11.2010 01:20, Cristian Greco wrote: On Thu, 25 Nov 2010 23:29:21 +0100 Simon Waltersimon.wal...@hp-factory.de wrote: On 25.11.2010 19:02, Cristian Greco wrote: which version of deluge are you running on remote machine? 1.3.1 so server and client are the same version Are you using some additional plugins? only blocklist are you still able to reproduce this bug? I still have no idea about how to reproduce and/or track down your problem. Nope can't reproduce it myself with 1.3.1 So yo can close this bug. -- Regards Simon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601599: deluge: argument mismatch between rpcserver and client
On 26.11.2010 01:20, Cristian Greco wrote: On Thu, 25 Nov 2010 23:29:21 +0100 Simon Waltersimon.wal...@hp-factory.de wrote: On 25.11.2010 19:02, Cristian Greco wrote: which version of deluge are you running on remote machine? 1.3.1 so server and client are the same version Are you using some additional plugins? only blocklist -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601599: deluge: argument mismatch between rpcserver and client
On 25.11.2010 19:02, Cristian Greco wrote: which version of deluge are you running on remote machine? 1.3.1 so server and client are the same version -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601599: deluge: argument mismatch between rpcserver and client
Package: deluge Version: 1.3.0-1 Severity: normal When I use a remote connect to deluged I don't see any torrent and can't open Preferences from deluged.log: [ERROR ] 19:07:13 rpcserver:286 Exception calling RPC request: get_torrents_status() takes exactly 3 arguments (4 given) Traceback (most recent call last): File /usr/lib/pymodules/python2.6/deluge/core/rpcserver.py, line 281, in dispatch sendError() TypeError: get_torrents_status() takes exactly 3 arguments (4 given) [ERROR ] 19:07:03 rpcserver:286 Exception calling RPC request: get_free_space() takes exactly 2 arguments (1 given) Traceback (most recent call last): File /usr/lib/pymodules/python2.6/deluge/core/rpcserver.py, line 281, in dispatch sendError() -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596403: mailscanner: NMU diff for 4.79.11-2.1 (Intent to NMU; CVE-2010-3095)
Hi, not maintaining anymore, so go ahead ... -- Regards Simon On 18.10.2010 10:39, jari.aa...@cante.net wrote: Dear maintainer, Here is the NMU diff according to DevRef 5.11.1[1][2] for bug: #596403. See the debian/patches directory for the important fixes. Please let me know if it's ok to proceed with the NMU. Thank you for maintaining the package, Jari Aalto [1] http://www.debian.org/doc/developers-reference/pkgs.html#nmu [2] http://dep.debian.net/deps/dep1.html lsdiff(1) of changes: mailscanner-4.79.11/debian/changelog mailscanner-4.79.11/debian/patches/CVE-2010-3095--bug596403.patch mailscanner-4.79.11/debian/patches/series -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587603: dbmail: new stable upstream release
Package: dbmail Severity: wishlist Please package the lastest stable upstream release (2.2.16) As fare as I understand it's a bugfix release and it would fix problems like this http://code.google.com/p/k9mail/issues/detail?id=1159 which would be very nice. ;) Thanks! -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/4 CPU cores) Locale: lang=de...@euro, lc_ctype=de...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573340: README file missing in conf.d
package mailscanner close 573340 thanks Hi Stephane, README file from conf.d can be found here: /usr/share/doc/mailscanner/examples/conf.d -- Regards Simon On 10.03.2010 18:41, Stephane Leclerc wrote: Package: mailscanner Version: 4.79.11-1 Hi! I've just found that the README file in /etc/Mailscanner/conf.d/ is missing. This file is included in the original tar ball. Sincerely, Stephane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531317: O: mailscanner -- email gateway for virus scanning, spam and fishing detection
Package: wnpp Severity: normal Upload: http://mailscanner.info/ Work in progress: http://thargor.org/mailscanner/ I'm no longer able to maintaine this package. -- Regards Simon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529358: mailscanner: MailScanner dies an ugly death when using perl 5.10.0-22
Hello, # dpkg -l perl ii perl 5.10.0-22 # dpkg -l mailscanner ii mailscanner4.74.16-1 Afterwards, debugging mailscanner showed it dying with the error message Insecure dependency in chown while running with the -T switch in /usr/share/MailScanner//MailScanner/Message.pm on line 2407. It appears to be while calling the perl chown function to set the permissions on an exploded message in the incoming work directory. I have noticed this bug[1] myself some days ago while trying to package 4.76.25-1. I have fixed this bug, but have not tested the bugfix yet. Your solution[3] to this problem is not every generic. Users would have to edit /etc/ini.d/mailscanner depending on the mailserver they are using. There is also a problem when using clamavd, it crash and complains about missing permission for lstat on the unpacked mail, no matter how I configure Incoming Work User/Group/Permission. I currently don't have the time to track down the problem, find a solution and test the -T patch. If anyone else has some spare time, feel free to help out. I have uploaded the current state to mentors[2]. I have added mailscanner-ml to CC because there are probably other debian-users out there... -- Regards Simon Walter [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=+529358 [2] http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=mailscanner [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=+529358#10 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529358: mailscanner: MailScanner dies an ugly death when using perl 5.10.0-22
On Wed, 20 May 2009 16:54:59 +0300 Gerasimos Melissaratos gmeli...@gmail.com wrote: On Wed, May 20, 2009 at 3:35 PM, Simon Walter simon.wal...@hp-factory.de wrote: There is also a problem when using clamavd, it crash and complains about missing permission for lstat on the unpacked mail, no matter how I configure Incoming Work User/Group/Permission. That's an easy one, just change the antivirus from auto to clamav in MailScanner.conf and ... you have disabled clamd usage, using clamav as standalone scanner and lost a considerable amount of processing performance. It's a workaround but not a solution. -- Regards Simon Walter -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#313145: Support for debian-volatile
package mailscanner tags 313145 confirmed thanks will be relevant again if mailscanner makes it into the next stable release -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#418619: Mailscanner dies when shadow: set to ldap on /etc/nsswitch.conf
package mailscanner tags 418619 etch thanks Hello, apparently nothing happen ... I close this bugreport because its not a bug in mailscanner but in libnss-ldap. -- Regards Simon signature.asc Description: PGP signature
Bug#517197: network-manager-gnome: Lost icons
Package: network-manager-gnome Version: 0.7.0.97-1 Followup-For: Bug #517197 I can confirm problems with the icons. I have installed network-manager-gnome on a clean sid installation using xfce with a panel on the right side. The nm-applet area showed up but the icon was only 1x1 pixel. After moving the panle to the top, the icon appared and stayed when moving back to the right but it doesn't scale to the width of the panel. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages network-manager-gnome depends on: ii libc6 2.9-4 GNU C Library: Shared libraries ii libdbus-1-3 1.2.12-1 simple interprocess messaging syst ii libdbus-glib-1-2 0.80-3 simple interprocess messaging syst ii libgconf2-4 2.24.0-7 GNOME configuration database syste ii libglade2-0 1:2.6.3-1 library to load .glade files at ru ii libglib2.0-0 2.18.4-2 The GLib library of C routines ii libgnome-keyring0 2.22.3-2 GNOME keyring services library ii libgtk2.0-0 2.14.7-4 The GTK+ graphical user interface ii libnm-glib-vpn0 0.7.0.97-1 network management framework (GLib ii libnm-glib0 0.7.0.97-1 network management framework (GLib ii libnm-util1 0.7.0.97-1 network management framework (shar ii libnotify1 [libnotify1-gtk2.1 0.4.4-3sends desktop notifications to a n ii libpango1.0-0 1.22.4-2 Layout and rendering of internatio ii libpolkit-gnome0 0.9-2 PolicyKit-gnome library ii libpolkit20.9-3 library for accessing PolicyKit ii network-manager 0.7.0.97-1 network management framework daemo Versions of packages network-manager-gnome recommends: ii libpam-gnome-keyring [libpam- 2.22.3-2 PAM module to unlock the GNOME key ii notification-daemon 0.3.7-1+b1 a daemon that displays passive pop ii policykit-gnome 0.9-2 GNOME dialogs for PolicyKit Versions of packages network-manager-gnome suggests: pn network-manager-openvpn-gnome none (no description available) pn network-manager-pptp-gnomenone (no description available) pn network-manager-vpnc-gnomenone (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516347: debian-installer: guided-with-lvm no longer allows multiple primary partition
Hi,
Looking closer at partman logs, I now doubt that this is a
partman-auto-lvm specific issue.
The disk size as seen by the installer is 10947133440 bytes
The initial preseeded recipe is :
96 128 128 ext3 $primary{ } $bootable { } method{ format } \
format{ } use_filesystem{ } filesystem{ ext3 }
mountpoint{ /boot } . \
100 1000 -1 ext3 $lvmok{ } method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } mountpoint{ / }
Which is transformed by expand_recipe into the following actual scheme
for creating the primary partitions :
128 0 128 ext3 $primary{ } $bootable { } method{ format } \
format{ } use_filesystem{ } filesystem{ ext3
} mountpoint{ /boot } . \
10819 96 -1 ext3 $primary{ } method{ lvm }
This scheme should fit on the disk (10819+128=10947 MiB)
But the partman log extract at the end of this post shows that :
1) when parted_server is asked to create a 128 MiB partition at the
beginning of the disk,
It creates a 131.6 MiB (131604480 bytes) partition beginning at
position 32256, and ending at 131604479.
2) parted_server is then asked to create a 10819 MiB primary partition
to hold the physical volume,
but starting at position 131604480, it can find enough space on the
disk and fails :
How can the gap between what is asked and what is performed by
parted_server be explained ?
- 131572224 B doesn't equal 128 MB, so an International System Units
vs binary Units mismatch doesn't seem to be involved.
- the disk size seems not to be involved either, as having tried a lvm
preseeded recipe on a 70 GB physical hard drive have given the same
result (will try tomorrow with bigger disks)
- is some overhead missing in the partition size calculation by expand_recipe ?
- should the scheme be recomputed with feedback from the parted_server
before creating following partitions ?
On Etch, the same recipe works because the default behavior is to
create the physical volume in a logical partition, using the entire
free space (position parameter set to full).
Any thoughts/questions on the subject are welcome :
- directions to look further
- examples of lvm preseed recipe working with the lenny installer
- requests for precision or execution traces
Regards.
Simon Walter.
Partman log extract :
parted_server: main_loop: iteration 30
parted_server: Opening infifo
/bin/autopartition-lvm: IN: NEW_PARTITION =dev=hda primary ext3
0-10947133439 beginning 12801
parted_server: Read command: NEW_PARTITION
parted_server: command_new_partition()
parted_server: Note =dev=hda as changed
parted_server: Opening outfifo
parted_server: requested partition with type primary
parted_server: requested partition with file system ext3
parted_server: add_primary_partition(disk(21381120),0-25)
parted_server: OUT: OK
parted_server: OUT: 1 32256-131604479 131572224 primary ext3
/dev/hda1
parted_server: Closing infifo and outfifo
parted_server: main_loop: iteration 31
parted_server: Opening infifo
/bin/autopartition-lvm: IN: PARTITIONS =dev=hda
parted_server: Read command: PARTITIONS
parted_server: command_partitions()
parted_server: Opening outfifo
parted_server: OUT: OK
parted_server: OUT: 1 32256-131604479 131572224 primary ext3
/dev/hda1
parted_server: OUT: -1 131604480-10939622399 10808017920
pri/log free/dev/hda-1
parted_server: Partitions printed
parted_server: OUT:
parted_server: Closing infifo and outfifo
parted_server: main_loop: iteration 32
parted_server: Opening infifo
/bin/autopartition-lvm: IN: PARTITION_INFO =dev=hda 131604480-10939622399
parted_server: Read command: PARTITION_INFO
parted_server: command_partition_info()
parted_server: Opening outfifo
parted_server: command_partition_info: info for partition with id
131604480-10939622399
parted_server: partition_with_id(131604480-10939622399)
parted_server: OUT: OK
parted_server: command_partition_info: partition found
parted_server: OUT: -1 131604480-10939622399 10808017920
pri/log free/dev/hda-1
parted_server: Closing infifo and outfifo
parted_server: main_loop: iteration 33
parted_server: Opening infifo
/bin/autopartition-lvm: IN: NEW_PARTITION =dev=hda primary ext3
131604480-10939622399 beginning 1081901
parted_server: Read command: NEW_PARTITION
parted_server: command_new_partition()
parted_server: Note =dev=hda as changed
parted_server: Opening outfifo
parted_server: requested partition with type primary
parted_server: requested partition with file system ext3
parted_server: add_primary_partition(disk(21381120),257040-21387899)
parted_server: OUT: Error
parted_server: OUT: Can't have a partition outside the disk!
parted_server: OUT:
parted_server: OUT: Cancel
parted_server: OUT:
open_dialog NEW_PARTITION primary ext3 0-10947133439 beginning 12801
parted_server: OUT: 1 32256-131604479 131572224 primary ext3
/dev/hda1
/bin/autopartition-lvm: IN: NEW_PARTITION =dev=hda primary ext3
131604480-10939622399
Bug#516347: debian-installer: guided-with-lvm no longer allows multiple primary partition
Hello.
I'm facing the same problem while preseededing partionning recipes in
the lenny amd64 installer on a 10Gb xen virtual hard drive, but it is not lvm
specific, as it appears also in partman-auto with regular recipes.
I don't know more than you if it comes from an incorrect recipe, or some
regression from etch.
Either of the two following recipes exits with a Can't have a partition
outside the disk!/This probably happened because there are too many
(primary) partitions in the partition table. error message.
Recipe 1 fails : /boot + lvm root partition :
d-i partman-auto/method string lvm
d-i partman-auto/expert_recipe string custom :: \
96 128 128 ext3 $primary{ } $bootable { } \
method{ format } format{ } use_filesystem{ } \
filesystem{ ext3 } options/nodev{ nodev } mountpoint{ /boot } \
. \
100 1000 -1 ext3 $lvmok{ } method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } mountpoint{ / } .
/var/log/partman :
parted_server: Opening infifo
/bin/autopartition-lvm: IN: NEW_PARTITION =dev=hda primary ext3
131604480-10939622399 beginning 1081901
parted_server: Read command: NEW_PARTITION
parted_server: command_new_partition()
parted_server: Note =dev=hda as changed
parted_server: Opening outfifo
parted_server: requested partition with type primary
parted_server: requested partition with file system ext3
parted_server: add_primary_partition(disk(21381120),257040-21387899)
parted_server: OUT: Error
parted_server: OUT: Can't have a partition outside the disk!
Recipe 2 fails : /boot + regular primary root partition :
d-i partman-auto/method string regular
d-i partman-auto/expert_recipe string custom :: \
96 128 128 ext3 $primary{ } $bootable { } \
method{ format } format{ } use_filesystem{ } \
filesystem{ ext3 } options/nodev{ nodev } mountpoint{ /boot } \
. \
100 1000 -1 ext3 $primary{ } method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } mountpoint{ / } .
/var/log/partman :
parted_server: Opening infifo
/bin/perform_recipe: IN: NEW_PARTITION =dev=hda primary ext3
131604480-10939622399 beginning 1081901
parted_server: Read command: NEW_PARTITION
parted_server: command_new_partition()
parted_server: Note =dev=hda as changed
parted_server: Opening outfifo
parted_server: requested partition with type primary
parted_server: requested partition with file system ext3
parted_server: add_primary_partition(disk(21381120),257040-21387899)
parted_server: OUT: Error
parted_server: OUT: Can't have a partition outside the disk!
In either case, parted_server is asked to create a primary partition
which goes beyond the disk end :
1081901 (size) + 131604480 (beginning) = 10950604481
Traces in partman-auto and partman-auto-lvm shell scripts shows that
the disk size is correctly :
+ disksize=10947133440
I still got to track back how this improper size value is computed.
Changing recipe 2 to have a logical root partition leads to a
successfull partitionning :
d-i partman-auto/method string regular
d-i partman-auto/expert_recipe string custom :: \
96 128 128 ext3 $primary{ } $bootable { } \
method{ format } format{ } use_filesystem{ } \
filesystem{ ext3 } options/nodev{ nodev } mountpoint{ /boot } \
. \
100 1000 -1 ext3 method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } mountpoint{ / } .
parted_server: Opening infifo
/bin/perform_recipe: IN: NEW_PARTITION =dev=hda logical ext3
131604480-10939622399 full 1081901
parted_server: Read command: NEW_PARTITION
parted_server: command_new_partition()
parted_server: Note =dev=hda as changed
parted_server: Opening outfifo
parted_server: requested partition with type logical
parted_server: requested partition with file system ext3
parted_server: OUT: OK
As the position is full instead of beginning, the given size is
ignored, and the partitionning succeed :
# fdisk -l /dev/hda
Disk /dev/hda: 10.9 GB, 10947133440 bytes
255 heads, 63 sectors/track, 1330 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000c38bd
Device Boot Start End Blocks Id System
/dev/hda1 1 16 128488+ 83 Linux
/dev/hda2 17 1330 10554705 5 Extended
/dev/hda5 17 1330 10554673+ 83 Linux
Regards.
--
Simon Walter
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#313145: Support for debian-volatile
On Mon, Feb 16, 2009 at 10:33:34PM +0100, Simon Walter wrote: Any chance a volatile package can be made available? I don't know. Is it even possible to get a package into volatile if it didn't made it into the last stable release? Acceptance rules says nothing against this... Can someone from the volatile team enlight us? ;) No, sorry. No new packages. It's not new since it was in in etch and even in sarge... So it would be new to fresh lenny installations, but for people using it in etch it would be an update... I don't think this change anything just wanted to mention it. ;) -- Regards Simon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#313145: Support for debian-volatile
Hello George B. i93.b...@gmail.com writes: The mailscanner package was removed from the new Debian Stable release (Lenny). :-( Mailscanner was removed from stable because of #506353[1]. Any chance a volatile package can be made available? I don't know. Is it even possible to get a package into volatile if it didn't made it into the last stable release? Acceptance rules says nothing against this... Can someone from the volatile team enlight us? ;) Thanks! -- Regards Simon Walter [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506353 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#506353: lenny removal requests
Hi
Gabor FUNK funk.ga...@hunetkft.hu writes:
mailscanner #506353
The maintainer Simon Walter writes:
In the current state the package should not be part of
the lenny release.
I'm in no position to fix all this. I'm not familiar enough with
the MailScanner sourcecode and I'm not able to test the changes I
would have to make, in particular to all the virusscanner scripts.
upstream apparently does not seem to, let's say, consider the tempfile
vulnerability a bug and does not seem to want to fix it.
The mailscanner temp vulnerability seems to be fixed in upstream:
Yes, upstream has fixed the vulnerability, but not yet release a
stable (non-beta) version. Next stable release will be on 01.01.09 but
this release will also come with quite some features.
Noah Meyerhans from seacurity-team and I have been working on a
backport of the upstream fixes for mailscanner-4.68.8.
Current state of this work is: It works (MailScanner starts and scans
a simple textmail) but it's not well tested. There still need to be
done some testing with TNEF attachment, virus removal and some other
cases.
I currently don't Know when I will have the time to do this.
I have attached the diff against 4.68.8 debian package.
--
Regards
Simon Walter
diff -Naur mailscanner-4.68.8/debian/changelog mailscanner-4.68.8-1+lenny1-proposed/debian/changelog
--- mailscanner-4.68.8/debian/changelog 2008-12-24 23:29:01.0 +0100
+++ mailscanner-4.68.8-1+lenny1-proposed/debian/changelog 2008-12-24 23:27:44.0 +0100
@@ -1,3 +1,11 @@
+mailscanner (4.68.8-1+lenny1) testing-proposed-updates; urgency=high
+
+ * Security upload to fix CVE-2008-5140, CVE-2008-5312, CVE-2008-5312
+(insecure creation of files in /tmp)
+Thanks Raphael Geisser, Noah Meyerhans
+
+ -- Simon Walter simon.wal...@hp-factory.de Mon, 22 Dec 2008 19:43:05 +0100
+
mailscanner (4.68.8-1) unstable; urgency=low
* New upstream release
diff -Naur mailscanner-4.68.8/debian/mailscanner.install mailscanner-4.68.8-1+lenny1-proposed/debian/mailscanner.install
--- mailscanner-4.68.8/debian/mailscanner.install 2008-12-24 23:29:01.0 +0100
+++ mailscanner-4.68.8-1+lenny1-proposed/debian/mailscanner.install 2008-12-24 23:27:44.0 +0100
@@ -2,6 +2,7 @@
bin/df2mbox usr/sbin/
bin/upgrade_MailScanner_conf usr/sbin/
bin/MailScanner /usr/sbin
+bin/mailscanner_create_locks /usr/sbin
bin/update_virus_scanners /usr/sbin
bin/update_phishing_sites /usr/sbin
lib/MailScanner.pm usr/share/MailScanner/
diff -Naur mailscanner-4.68.8/debian/patches/00list mailscanner-4.68.8-1+lenny1-proposed/debian/patches/00list
--- mailscanner-4.68.8/debian/patches/00list 2008-12-24 23:29:01.0 +0100
+++ mailscanner-4.68.8-1+lenny1-proposed/debian/patches/00list 2008-12-24 23:27:43.0 +0100
@@ -10,3 +10,4 @@
update_virus_scanners.dpatch
upgrade-manpage.dpatch
use_spamassassinprefsconf.dpatch
+CVE-2008-5313.dpatch
diff -Naur mailscanner-4.68.8/debian/patches/CVE-2008-5313.dpatch mailscanner-4.68.8-1+lenny1-proposed/debian/patches/CVE-2008-5313.dpatch
--- mailscanner-4.68.8/debian/patches/CVE-2008-5313.dpatch 1970-01-01 01:00:00.0 +0100
+++ mailscanner-4.68.8-1+lenny1-proposed/debian/patches/CVE-2008-5313.dpatch 2008-12-24 23:27:43.0 +0100
@@ -0,0 +1,1335 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## CVE-2008-5313.dpatch by no...@debian.org
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: No description.
+
+...@dpatch@
+diff -urNad mailscanner-4.68.8~/bin/MailScanner mailscanner-4.68.8/bin/MailScanner
+--- mailscanner-4.68.8~/bin/MailScanner 2008-12-22 22:48:13.0 +0100
mailscanner-4.68.8/bin/MailScanner 2008-12-22 22:48:14.0 +0100
+@@ -61,6 +61,7 @@
+ use FileHandle;
+ use File::Path;
+ use IO::Handle;
++use IO::File;
+ use Getopt::Long;
+ use Time::HiRes qw ( time );
+ use Filesys::Df;
+@@ -362,6 +363,18 @@
+checking configuration...\n;
+ MailScanner::Log::Configure($logbanner, 'stderr');
+
++ # Check -autoupdate lock files
++ my $lockdir = MailScanner::Config::QuickPeek($ConfFile, 'lockfiledir');
++ if ($lockdir eq || $lockdir =~ /tmp$/i) {
++print STDERR Please move your \Lockfile Dir\ setting in MailScanner.conf.\n;
++print STDERR It should point outside /tmp, preferably /var/spool/MailScanner/incoming/Locks\n;
++ }
++ my $cluid = MailScanner::Config::QuickPeek($ConfFile, 'runasuser');
++ my $clgid = MailScanner::Config::QuickPeek($ConfFile, 'runasgroup');
++ my $clr = system(/usr/sbin/mailscanner_create_locks \$lockdir\ \$cluid\ \$clgid\);
++ print STDERR Error: Attempt to create locks in $lockdir failed!\n
++if ($clr8) != 0;
++
+ # Read the directory containing all the custom code
+ MailScanner::Config::initialise(MailScanner::Config::QuickPeek($ConfFile,
+ 'customfunctionsdir'));
+@@ -446,6 +459,12 @@
+}
+ }
+
++ # Check permissions on /tmp
++ if ($WantLintOnly
Bug#506353: mailscanner: many scripts allow local users to overwrite arbitrary files, and more, via symlink attacks
package mailscanner tags 506353 help upstream confirmed thanks Hello, Mark Purcell [EMAIL PROTECTED] writes: On Friday 21 November 2008 08:24:46 Raphael Geissert wrote: I'm using severity grave as this package should definitely not be shipped in any release as is. Simon, This RC bug was reported almost two weeks ago without any comment from you. Are you in a position to investigate and propose a way forward for your package in lenny? I have looked at the code-segments Raphael pointed out and I'm totally agree with him. In the current state the package should not be part of the lenny release. I'm in no position to fix all this. I'm not familiar enough with the MailScanner sourcecode and I'm not able to test the changes I would have to make, in particular to all the virusscanner scripts. I have put Julian Field (upstream author) in CC to inform him about all this. (@Julian: the full bugreport is here [1]) If he is willing and able to fix the problems in a feature release before lenny is released I will try to backport the fixes to the current package in lenny. Otherwise this package should be removed. I'm also wondering why [2] marks CVE-2008-5140 as fixed for sid+lenny. It claims the bug was fix with 4.57.6-1, but there is no difference between 4.55.10-3 and 4.57.6-1. Sorry for the late reply. -- Regards Simon Walter [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506353 [2] http://security-tracker.debian.net/tracker/CVE-2008-5140 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498745: Acknowledgement (audacious: Suddenly puts songs on pause)
Package: audacious Version: 1.5.1-4 *** Please type your report below this line *** Hello, I have a similar problem with audacious. Sometimes while compiling(java), starting jboss or redeploying cpu-usage peaks and the hole system stops responding for a very short time ( 1sec). Audacious stop playing and I have to move the slider or restart the song. I suppose the problem has nothing to do with audacious or any other programm but with the kernel. I experince the described behaviour only with linux-image-2.6.26-1-686-bigmem, if I use 2.6.25-2-686-bigmem instead the problem is gone. -- Regards Simon -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686-bigmem (SMP w/4 CPU cores) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages audacious depends on: ii audacious-plugins 1.5.1-2Base plugins for audacious ii dbus 1.2.1-4simple interprocess messaging syst ii gtk2-engines-pixbuf 2.12.11-4 Pixbuf-based theme for GTK+ 2.x -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498208: mailscanner: directive Max SpamAssassin Size with trackback parameter fails
package mailscanner found 498208 tags 498208 upstream thanks Hello Viktor Matys [EMAIL PROTECTED] writes: Package: mailscanner Version: 4.68.8-1 Severity: normal MailScanner has problem whey I use trackback parameter in directive Max SpamAssassin Size = 200k trackback Without trackback it works correctly. Can't use string (1) as an ARRAY ref while strict refs in use at /usr/share/MailScanner//MailScanner/PFDiskStore.pm line 509. I was able to reproduce this problem with mailscanner 4.68 and postfix. I tried to fix the bug myself but either I wasn't successful or my bugfix produced some errors in the following code-segements. So I will forward this bug to the Upstream-Author. I also looked at the equivalent code for exim and the trackback feature isn't even implemented there... -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498208: mailscanner: directive Max SpamAssassin Size with trackback parameter fails
With a little help I produced a patch to fix the problem, but i don't know if
the code still does what it should do.
So I will still forward this bug to upstream and let him handle it...
but if you like give the following patch a try...
without any warranty .. ;)
--- PFDiskStore.pm~ 2008-03-24 14:07:46.0 +0100
+++ PFDiskStore.pm 2008-10-01 22:28:39.0 +0200
@@ -506,8 +506,8 @@
# Handle trackback -- This is the tricky one
if ($configwords[1] =~ /tr[ua]/i) {
#print STDERR Trackback:\n;
-while ([EMAIL PROTECTED](@{$body})-1] !~ /^\s*$/) {
- print Line is . [EMAIL PROTECTED](@{$body})-1] . \n;
+while ($body-[-1] !~ /^\s*$/) {
+ print Line is . $body-[-1] . \n;
pop @{$body};
#print STDERR .;
}
--
Regards
Simon Walter
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491037: More information on how to reproduce the bug
Hello, sorry for the late answer, I didn't had the time to work an the package lately... Fernando J. Rodríguez [EMAIL PROTECTED] writes: I discovered that if I issue the /etc/init.d/mailscanner stop command while MailScanner is still autodetecting virus scanners (calling in turn the helper scripts in /etc/MailScanner/wrappers), it correctly kills 3 running instances of MailScanner and no other one is spawned. But if I wait until the autodetection ends, the script kills the 2 running instances, but a new one is spawned as I showed in my first message, a new instance that start-stop-daemon does not kill (I think it does not send any signal to that process), but still keeps waiting for it to finish (wich never happens, because there is no reason for it). If I supress the autodetection of available virus scanners, by putting the name of one of them (f-prot in my case) instead of auto, and I run: /etc/init.d/mailscanner start; sleep 5; /etc/init.d/mailscanner stop the bug happens. On the other hand, /etc/init.d/mailscanner start; 5; /etc/init.d/mailscanner stop does not cause the bug to happen. So there is some time window between starting and stopping MailScanner where the bug occurs. Does any of this make any sense to you? Some, yes ;) Could you replace line 129 in the init.d script with start-stop-daemon --stop --retry=TERM/10/TERM/20 --name $NAME and try again? -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491037: #491037 /etc/init.d/mailscanner stop leaves a MailScanner process running
package mailscanner tags 491037 unreproducible thank you Hello, i was not able to reproduce the problem on my system. can you debug the script (sh -x) and send me the output? -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353266: #353266 Mailscanner causing false positive phishing frauds for quoted URLs and some TLDs
package mailscanner tag 353266 unreproducible thank you Hello, i was not able to reproduce the problem. can you provide a simple sample message to reproduce the problem? -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472489: impossible to uninstall/remove/reinstall mailscanner after upgrading
I did make one change to the postrm script: /var/lib/dpkg/info/mailscanner.postrm line 435 # bugfix for #454381 rm -f /etc/cron.d/mailscanner please remove this line and retry uninstall/upgrade. -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472489: impossible to uninstall/remove/reinstall mailscanner after upgrading
Hello, Shams Fantar [EMAIL PROTECTED] writes: Subject: impossible to uninstall mailscanner after upgrading Package: mailscanner Version: 4.58.9-2 Severity: important I can't uninstall the mailscanner package after updating/upgrading. If I try to uninstall, here is the message[1], If I try to reinstall the package, here's the message[2] and if I try to remove it[3]. I think it's a bug in lenny/sid with mailscanner. [1] : http://snurf.info/sfantar/debian/bugs/mailscanner/mailscanner-remove.txt [2] : http://snurf.info/sfantar/debian/bugs/mailscanner/mailscanner-reinstall-.txt [3] : http://snurf.info/sfantar/debian/bugs/mailscanner/mailscanner-remove1.txt I have tried to reproduce your problem by installing an old version and upgrade to the most recent and found not problem. I also can find any usefully information in the output-logs you uploaded. Can you try dpkg -r mailscanner and dpkg -P mailscanner after you backup your config/data and tell me if the problem still exists and what dpkg shows you? -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418619: Mailscanner dies when shadow: set to ldap on /etc/nsswitch.conf
Daniel Estévez Sánchez [EMAIL PROTECTED] writes: El Miércoles, 27 de Febrero de 2008, Simon Walter escribió: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375533 seems like your problem is/was a bug in ldap itself. Thanks for your help! It's surprisingly grateful to discover that someone takes a look at bug reports which were submitted a year ago. The problem was indeed, as stated in that bug report, that /etc/nsswitch.conf had mode 600. Changing permissions to 644 solved the problem. I wonder why a permissions problem would result in an assertion failure. But, anyway, it's fixed now. However, the ldap-nss.c assertion failure, doesn't seem to be fixed yet. I run a fully updated debian stable, and the problem persits when /etc/nsswitch.conf has mode 600 and shadow is set to compat ldap. greendragon:/home/daniel# LANG=C MailScanner --debug In Debugging mode, not forking... perl: ldap-nss.c:1376: do_init: Assertion `cfg-ldc_uris[__session.ls_current_uri] != ((void *)0)' failed. Ldap version in stable is 251 with some security fixes. The bug was fixed by upstream in 255 and testing runs 258. So there never was a specific debian-stable patch for this issue. Can I close this bug? -- Regards Simon Walter
Bug#418619: Mailscanner dies when shadow: set to ldap on /etc/nsswitch.conf
package mailscanner close #418619 thanks Daniel Estévez Sánchez [EMAIL PROTECTED] writes: El Jueves, 28 de Febrero de 2008, Simon Walter escribió: Ldap version in stable is 251 with some security fixes. The bug was fixed by upstream in 255 and testing runs 258. So there never was a specific debian-stable patch for this issue. Can I close this bug? Ok, it's good to know that. Feel free to close the bug, but perhaps a backport of the patch to debian-stable would help, because it seems that bug #418615 is caused by the same problem. Yes, i agree with you. There are probably other bugreports on different packages related to this bug, but I don't know howto propose a patch for stable. Probably we should first contact the maintainer of libnss-ldap and talk to him. The bug should be reopend for the stable version or a new bugreport should be create and tagged as etch related. Yeah, I think the best would be if you report a new bug against libnss-ldap with reportbug from your stable system. Link the bugreport with the patch #375533 and the bugreports for mailscanner #418619 and #418615 in it, attach the patch itself and point out that you want this problem resolved for the stable release. Then lets see what happens. :) -- Regards Simon Walter
Bug#418619: Mailscanner dies when shadow: set to ldap on /etc/nsswitch.conf
Hi Daniel, i have something for you ;) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375533 seems like your problem is/was a bug in ldap itself. -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464317: Looks like there are missing Build-Depends too
Hello, Daniel Schepler [EMAIL PROTECTED] writes: From earlier in my pbuilder build log for mailscanner: ... make -C build man \ MAN_PARAMS=--stringparam man.output.quietly 1 \ --stringparam refentry.meta.get.quietly 1 \ --stringparam man.charmap.enabled 0 I/O error : Attempt to load network entity http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd ../MailScanner.xml:23: warning: failed to load external entity http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd; ] ^ I/O error : Attempt to load network entity http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd ../d2mbox.xml:45: warning: failed to load external entity http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd; ] ^ If I install docbook-xml in addition to the package's Build-Depends, those errors go away, but still the package fails to build. I can see these error messages too, but they don't stop the build-process. dtd's are not required to transform xml to man, as far as I know. With docbook-xml as build-depends the error-messages go away. Can you please send me the output from your pbuilder build. Or try the following patch: --- mailscanner-4.66.5/debian/rules 2008-02-27 12:45:34.0 +0100 +++ ../mailscanner-4.66.5/debian/rules 2008-02-25 10:34:53.0 +0100 @@ -36,7 +36,8 @@ make -C debian/man clean dh_clean debian/ucffiles debian/postinst.ucf debian/postrm.ucf - debconf-updatepo +# unnessasary see #467411 +# debconf-updatepo install: build dh_testdir @@ -84,19 +85,21 @@ dh_installlogcheck dh_installman dh_install -X.old - dh_link dh_compress dh_fixperms : # fix permissions -find $(d)/usr/share/MailScanner/reports -type f | xargs chmod -f a-x -find $(d)/usr/share/doc/mailscanner/examples -type f | xargs chmod -f a-x - chmod -f a-x $(d)/usr/share/MailScanner/MailScanner/ConfigDefs.pl - chmod -f a-x $(d)/usr/share/MailScanner/MailScanner/*.pm - chmod -f a-x $(d)/usr/share/MailScanner/MailScanner.pm - chmod -f a-x $(d)/etc/MailScanner/CustomConfig.pm - chmod -f a-x $(d)/etc/MailScanner/*.conf* - chmod -f a-x $(d)/etc/MailScanner/rules/* + chmod a-x $(d)/usr/share/MailScanner/MailScanner/ConfigDefs.pl + chmod a-x $(d)/usr/share/MailScanner/MailScanner/*.pm + chmod a-x $(d)/usr/share/MailScanner/MailScanner.pm + chmod a-x $(d)/etc/MailScanner/CustomConfig.pm + chmod a-x $(d)/etc/MailScanner/*.conf* + chmod a-x $(d)/etc/MailScanner/rules/* + + : # #464317 install links after fixing permission to avoid chmod: cannot operate on dangling symlink + dh_link : # custom premissions chown -f -R mail:mail $(d)/var/lib/MailScanner -- Regards Simon Walter
Bug#467411: mailscanner: Should drop the upgrade note
package mailscanner tag 467411 + pending tag 467465 + pending thanks Hello Christian, Christian Perrier [EMAIL PROTECTED] writes: Package: mailscanner Severity: normal The versions 3.x of mailscanner were in Debian much before etch. As n+2 upgrades aren't supported, there is no point to keep that debconf template and all the debconf stuff. Please drop the template ASAP before translators notice this and start updating their translations as you even changed the template wording recently. Thanks for this hint. I will remove the template with the next package release. -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#466896: Bug#465095: Same as Bug#466896
reassign #466896 mailscanner 4.58.9-2 forcemerge #465095 #466896 thanks Juergen Kosel [EMAIL PROTECTED] writes: I had reported as Bug#466896 as a bug of libmailtool-perl. Could you please merge it? Sure, no problem. -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465095: mailscanner fails to start with FIELD_NAME not imported
Hi Tom, thanks for this info. From mailscanner Changelog 4.66.5: Updated to handle new MailTools 2.02. This includes the use of several new Perl modules, so you'll have to use the install.sh to install all the requirements of the new MailTools code (unless you are doing clever things with yum repositories). So updating the package to a version 4.66 would probably fix this problem. Problem is, I'm only Maintainer no DD and currently I don't have a sponsor at hand. I had two offers but no reply yet. I will try to build a debian package from the newest upstream version some day next week and upload it to mentors. -- Regards Simon Walter Tom Faska [EMAIL PROTECTED] writes: I have experienced this problem and found that it is caused by upgrading libmailtools-perl from version 1.77-1 to 2.02-1. The problem is fixed when downgrading the libmailtools-perl back to version 1.77-1. This is reproducible as seen from the terminal capture below. Apparently there is some incompatibility between Mailscanner 4.58.9-2 and libmailtools-perl version 2.02-1. I hope this helps. Tom -- Mailscanner version installed monitor:~# dpkg -l mailscanner Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii mailscanner4.58.9-2 email virus scanner and spam tagger Stop and restart Mailscanner with no errors on start monitor:~# /etc/init.d/mailscanner stop Program MailScanner, 1 process(es), refused to die. monitor:~# /etc/init.d/mailscanner stop monitor:~# /etc/init.d/mailscanner start Upgrade libmailtools-perl from version 1.77-1 to 2.02-1 monitor:~# apt-get -u upgrade Reading package lists... Done Building dependency tree... Done The following packages will be upgraded: libmailtools-perl 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/96.6kB of archives. After unpacking 28.7kB disk space will be freed. Do you want to continue [Y/n]? (Reading database ... 38857 files and directories currently installed.) Preparing to replace libmailtools-perl 1.77-1 (using .../libmailtools-perl_2.02-1_all.deb) ... Unpacking replacement libmailtools-perl ... Setting up libmailtools-perl (2.02-1) ... Now stop and restart Mailscanner with the error monitor:~# /etc/init.d/mailscanner stop Program MailScanner, 1 process(es), refused to die. monitor:~# /etc/init.d/mailscanner stop monitor:~# /etc/init.d/mailscanner start Variable $FIELD_NAME is not imported at /usr/share/MailScanner/MailScanner/Message.pm line 6367. Variable $FIELD_NAME is not imported at /usr/share/MailScanner/MailScanner/Message.pm line 6370. Global symbol $FIELD_NAME requires explicit package name at /usr/share/MailScanner/MailScanner/Message.pm line 6367. Global symbol $FIELD_NAME requires explicit package name at /usr/share/MailScanner/MailScanner/Message.pm line 6370. Compilation failed in require at /usr/sbin/MailScanner line 79. BEGIN failed--compilation aborted at /usr/sbin/MailScanner line 79. Mailscanner failed to start monitor:~# /etc/init.d/mailscanner stop No MailScanner found running; none killed. Downgrade libmailtools-perl back to version 1.77 monitor:~# dpkg --force-downgrade -i /var/cache/apt/archives/libmailtools-perl_1.77-1_all.deb dpkg - warning: downgrading libmailtools-perl from 2.02-1 to 1.77-1. (Reading database ... 38855 files and directories currently installed.) Preparing to replace libmailtools-perl 2.02-1 (using .../libmailtools-perl_1.77-1_all.deb) ... Unpacking replacement libmailtools-perl ... Setting up libmailtools-perl (1.77-1) ... Now no errors on start monitor:~# /etc/init.d/mailscanner start Mailscanner processes are running monitor:~# ps aux | grep Mail postfix 24102 0.0 0.9 25160 19468 ?SNs 09:49 0:00 MailScanner: master waiting for children, sleeping postfix 24103 1.8 3.8 101732 80140 ?SN 09:49 0:08 MailScanner: waiting for messages postfix 24110 1.8 3.8 101732 80132 ?SN 09:49 0:08 MailScanner: waiting for messages postfix 24113 1.9 3.8 102312 80848 ?SN 09:50 0:09 MailScanner: waiting for messages postfix 24116 1.9 3.8 101728 80124 ?SN 09:50 0:08 MailScanner: waiting for messages monitor:~# -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465095: mailscanner fails to start with FIELD_NAME not imported
Hello Lukas, did you update an old mailscanner installation? -- Regards Simon Walter Lukas Ruf [EMAIL PROTECTED] writes: Package: mailscanner Version: 4.58.9-2 Severity: grave Justification: renders package unusable The following error is reported when I attempt to start mailscanner: Starting mail spam/virus scanner: MailScannerVariable $FIELD_NAME is not imported at /usr/share/MailScanner/MailScanner/Message.pm line 6367. Variable $FIELD_NAME is not imported at /usr/share/MailScanner/MailScanner/Message.pm line 6370. Global symbol $FIELD_NAME requires explicit package name at /usr/share/MailScanner/MailScanner/Message.pm line 6367. Global symbol $FIELD_NAME requires explicit package name at /usr/share/MailScanner/MailScanner/Message.pm line 6370. Compilation failed in require at /usr/sbin/MailScanner line 79. BEGIN failed--compilation aborted at /usr/sbin/MailScanner line 79. failed! invoke-rc.d: initscript mailscanner, action start failed. Does anybody know how to resolve this problem? Is it related to the following debconf setting? mailscanner/v3_upgrade: Don't upgrade If so, how can I change that? Thanks for any support Kind regards, Lukas -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.23.9-euphrat (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_IE, LC_CTYPE=en_IE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages mailscanner depends on: ii debconf [debconf-2.0] 1.5.19 Debian configuration management sy ii libarchive-zip-perl 1.18-1 Module for manipulation of ZIP arc ii libcompress-zlib-perl 2.008-1 Perl module for creation and manip ii libconvert-binhex-perl 1.119+pristine-2 Perl5 module for extracting data f ii libconvert-tnef-perl0.17-5 Perl module to read TNEF files ii libdbd-sqlite3-perl 1.14-1 Perl DBI driver with a self-contai ii libfilesys-df-perl 0.92-3 Module to obtain filesystem disk s ii libhtml-parser-perl 3.56-1 A collection of modules that parse ii libmime-perl5.425-2 transitional dummy package ii libmime-tools-perl [lib 5.425-2 Perl5 modules for MIME-compliant m ii libnet-cidr-perl0.11-2 Manipulate IPv4/IPv6 netblocks in ii libsys-hostname-long-pe 1.4-1Figure out the long (fully-qualifi ii libsys-syslog-perl 0.24-1 Perl interface to the UNIX syslog( ii perl5.8.8-12 Larry Wall's Practical Extraction ii postfix [mail-transport 2.5.1~rc1-1 High-performance mail transport ag ii spamassassin3.2.3-1 Perl-based spam filter using text ii ucf 3.004Update Configuration File: preserv ii unzip 5.52-10 De-archiver for .zip files Versions of packages mailscanner recommends: pn libnet-cidr-lite-perl none (no description available) ii ncftp 2:3.2.1-1 A user-friendly and well-featured ii tnef 1.4.3-2Tool to unpack MIME application/ms ii wget 1.10.2-3 retrieves files from the web -- debconf information: mailscanner/v3_upgrade: Don't upgrade -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449140: O: mailscanner -- spam/virusfilter
Package: wnpp Severity: normal mailscanner has a high release cycle (once a month). I don't have the time to build a new package this often and honestly I'm not even shure if such a volatile software should be part of debian. Over the last half year I also tried to find a sponsor in mdo without success. I created 3-4 packages and none made it into the offical debian repo. So I orphan this package and suggest to remove it from debian. -- Regards Simon -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22.9 (PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446536: [Pkg-xfce-devel] Bug#446536: Bug#446536: Bug#446536: xfce4-panel: Dies with SIGSEGV on Remove Panel
Hello Yves-Alexis Perez [EMAIL PROTECTED] writes: On sam, 2007-10-13 at 22:25 +0200, Yves-Alexis Perez wrote: On sam, 2007-10-13 at 22:18 +0200, Yves-Alexis Perez wrote: Thanks for this bug report, but I *cant* confirm this. It works flawlessly here. Can you be a little more specific on your config? Is there some logs? Is it 100% reproducible? If you run xfce4-panel from a terminal, is there some output? Ok, really sorry. I can indeed reproduce this (and even worse, the panel is *not* removed). It seems that it's a bug with gtk 2.11, fixed upstream. I'll try to get the patch in our package and report back. Ok the patch is working, upload will follow asap. I can't build on i386 but have amd64 packages if you need it. No problem, removing panels is not an every day task and I have modified my config by hand. Thanks for the quick responce and the fix. -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446536: xfce4-panel: Dies with SIGSEGV on Remove Panel
Package: xfce4-panel Version: 4.4.1-1 Severity: normal If you remove a panel with the Panel Manager xfce4-panel crashs with a segmentation fault afterwards. The panel is removed, but the redraw or what ever the Panel Manager does, fails. If you restart xfce4-panel by hand, the removed panel is gone and everything is fine. -- Regards Simon Walter -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22.9 (PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages xfce4-panel depends on: ii libatk1.0-0 1.20.0-1 The ATK accessibility toolkit ii libc6 2.6.1-5 GNU C Library: Shared libraries ii libcairo2 1.4.10-1 The Cairo 2D vector graphics libra ii libexo-0.3-00.3.2-5 Library with extensions for Xfce ii libfontconfig1 2.4.2-1.2generic font configuration library ii libfreetype62.3.5-1+b1 FreeType 2 font engine, shared lib ii libglib2.0-02.14.1-5 The GLib library of C routines ii libgtk2.0-0 2.12.0-2 The GTK+ graphical user interface ii libice6 2:1.0.4-1X11 Inter-Client Exchange library ii libpango1.0-0 1.18.2-2 Layout and rendering of internatio ii libpng12-0 1.2.15~beta5-2 PNG library - runtime ii libsm6 2:1.0.3-1+b1 X11 Session Management library ii libstartup-notification 0.9-1library for program launch feedbac ii libx11-62:1.0.3-7X11 client-side library ii libxcursor1 1:1.1.9-1X cursor management library ii libxext61:1.0.3-2X11 miscellaneous extension librar ii libxfce4mcs-client3 4.4.1-1 Client library for Xfce4 configure ii libxfce4mcs-manager34.4.1-1 Manager library for Xfce4configur ii libxfce4util4 4.4.1-1 Utility functions library for Xfce ii libxfcegui4-4 4.4.1-1 Basic GUI C functions for Xfce4 ii libxfixes3 1:4.0.3-2X11 miscellaneous 'fixes' extensio ii libxi6 2:1.1.3-1X11 Input extension library ii libxinerama11:1.0.2-1X11 Xinerama extension library ii libxrandr2 2:1.2.2-1X11 RandR extension library ii libxrender1 1:0.9.4-1X Rendering Extension client libra ii zlib1g 1:1.2.3.3.dfsg-6 compression library - runtime xfce4-panel recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#425861: Is this being maintained?
Hello, Jim Barber [EMAIL PROTECTED] writes: Does this package still have an active maintainer? This wish list item is 104 days old now. The current stable version of mailscanner is now at 4.63.7 and has numerous additions, improvements, and fixes over the version that is packaged in Debian. The fight against spam is a constant arms race, so if there is no maintainer to this package there is little point in using it. Not really active. I have got a new job, changed location, moving again in 3 weeks, was on holiday last week and will be on holiday the next two weeks. Over a month ago I tried to upload a new version of this package, but my previous sponsor stopped all his sponsorings. I asked in debian.mentors for a new sponsor but there was little responce and I replied too late to it. The source of my new packaged version was no longer available and the one person responding requested a new package with the lastest source. I still havn't found the time to fullfill this request. Sorry for that. I will be able to create a new package in 3-4 weeks. In the mean time, anyone willing to help or take over the package is welcomed. -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418619: Mailscanner dies when shadow: set to ldap on /etc/nsswitch.conf
package mailscanner tag 418619 help moreinfo thanks Hello Sorry, i don't have time to investigate this sort of setup. Are you currently able to reproduce the problem, run mailscanner in debug-mode and send me the output? If anyone want to invest some work in this or provide a simple solution, i would be glad. Daniel Estévez Sánchez [EMAIL PROTECTED] writes: Package: mailscanner Version: 4.55.10-3 I have recently done the dist-upgrade to etch and I have found that using libnss-ldap when in /etc/nsswitch.conf shadow: is set to compat ldap, mailscanner dies with the following on syslog when it's started via /etc/init.d/mailscanner start Apr 10 22:15:19 greendragon MailScanner: MailScanner setting GID to Debian-exim (109) Apr 10 22:15:19 greendragon MailScanner: MailScanner setting UID to Debian-exim (109) Apr 10 22:15:20 greendragon MailScanner[4776]: MailScanner E-Mail Virus Scanner version 4.55.10 starting... Apr 10 22:15:20 greendragon MailScanner[4776]: Read 748 hostnames from the phishing whitelist Apr 10 22:15:21 greendragon MailScanner[4776]: Using SpamAssassin results cache Apr 10 22:15:21 greendragon MailScanner[4776]: Connected to SpamAssassin cache database Apr 10 22:15:21 greendragon MailScanner[4776]: Enabling SpamAssassin auto-whitelist functionality... Apr 10 22:15:31 greendragon MailScanner: Process did not exit cleanly, returned 0 with signal 6 Apr 10 22:15:31 greendragon MailScanner[4779]: MailScanner E-Mail Virus Scanner version 4.55.10 starting... To solve this problem i have had to set in /etc/nsswitch.conf shadow: to compat only. I am using a default (only minor changes) new mailscanner configuration. -- Linux registered user #327978 since summer 2003 http://greendragon.homelinux.org/~daniel/ -- Regards Simon Walter
Bug#414850: mailscanner: changelogs etc. missing in 4.55.10-4.deb
Hello Anthony Fok [EMAIL PROTECTED] writes: Package: mailscanner Version: 4.55.10-4 Severity: normal Hello! After upgrading mailscanner to 4.55.10-4, I could no longer find the Debian and upstream changelogs, and the following search returns nothing either: $ dpkg -c mailscanner_4.55.10-4_all.deb | grep changelog $ md5sum mailscanner_4.55.10-4_all.deb b263497c370f3704d22a6ed71dbed84a mailscanner_4.55.10-4_all.deb Thanks! When I do this on my local copy, I get the following results: dpkg -c mailscanner_4.55.10-4_all.deb | grep changelog -rw-r--r-- root/root 6222 2006-12-20 21:37 ./usr/share/doc/mailscanner/changelog.Debian.gz md5sum mailscanner_4.55.10-4_all.deb d57a009e21404d9e496f71ac2e2fb3a5 mailscanner_4.55.10-4_all.deb From where did you get the package? Because 4.55.10-4 is neither in testing nor in unstable and the md5sum doesn't match. -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#412883: mailscanner : [INTL:pt] Portuguese translation for debconf messages
package mailscanner tags 412883 + pending thanks Traduz ML [EMAIL PROTECTED] writes: Package: mailscanner Version: 4.58.9-2 Tags: l10n, patch Severity: wishlist Portuguese translation for mailscanner's debconf messages. Translator: Miguel Figueiredo elmig _at_ debianpt.org Feel free to use it. For translation updates please contact 'Last Translator' or the Portuguese Translation Team traduz _at_ debianpt.org. Thanks for the translation, it will be part of the next package version. -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410647: Quarantine and special characters in filename
package mailscanner tags 410647 +confirmed +upstream severity 410647 wishlist thanks Hello, I wasn't able to solve this problem in a reasonable time by myself, so I have forwarded this to mailscanners mailinglist where the mailscanner gurus and developers live. ;) I tag it as upstream. New severity is minor, because its only a problem if quarantine is accessed directly over a webserver in the described specific way. -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410647: Quarantine and special characters in filename
Hi Stephane Leclerc [EMAIL PROTECTED] writes: I tagged this report normal but it's may be a wishlist. We will see. :) When attachments are stored in the quarantine directory, we have a problem with filename containing blank or others special characters. /var/spool/MailScanner/quarantine/20070211/1HGIyC-0003vD-6w/Europ\ 10m\ Deauville.xls\ .xls The problem is, how to access theses files using http? Using the Mailscanner variables to generate a download link do not give the right path and blanks are not well managed. http://server.domain.tld/quarantine/20070211/1HGIyC-0003vD-6w/Europ 10m Deauville.xls .xls Forbidden You don't have permission to access /quarantine/20070211/1HGIyC-0003vD-6w/Europ 10m Deauville.xls .xls on this server. Do this need to be managed in Mailscanner with a better setup, a new feature or using another way? Where/how do you generate the download link? In my setup the reports contain a link to a php-script with parameters of date and messageid. The script shows the content of the specified message on a html-page. This way I don't have any problems with special characters. But I agree with you, if you get this link out of mailscanner there should be a way to get the string url-encoded. -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#333674: #33367 MailScanner: Entity.pm, print_body chokes on undefined parts. Never processes message, jams queue processing.
package mailscanner tags 333674 +unreproducible thanks Hello, I was unable to reproduce this bug in a clean sarge installation with clamav and f-prot enabled. MailScanner.conf: Virus Scanners = clamav f-prot Spam Action = attachment deliver The provided queue-file is scanned, detected as spam and phishing and placed in mqueue without any problems. -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#369356: #369356 mailscanner: 'Multiple Headers = replace' breaks SMTP message
package mailscanner tags 369356 +unreproducible thanks Hello, I have tested this with the following versions and I'm unable to reproduce the error. mailscanner-4.41.3-2 mailscanner-4.55.10-3 and postfix-2.3.7-1 Queue files are okay, mails get delivered and Headers are okay. Everything is fine. Can you give me some more information on this? Perhaps your complete MailScanner.conf or a broken queue file? -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410148: Bug report: Mailscanner 4.57.6 , installer process
package mailscanner
tags 410148 +confirmed
thanks
Hello,
I have decided to change this behaviour to the old one.
I don't want to place a symbolic link into /etc/spamassassin because
this not part of the MailScanner package.
I have patched this in 4.55.10-4, but missed to apply a part of this
patch to 4.57.6.
Please try the following patch. This should enable the usage of
/etc/MailScanner/spamassassin.prefs.conf without the
/etc/spamassassin/mailscanner.cf link.
--- /usr/local/src/debian/mailscanner/upstream/MailScanner-install-4.57.6/perl-tar/MailScanner-4.57.6/lib/MailScanner/SA.pm 2006-06-06 19:03:43.0 +0200
+++ /usr/share/MailScanner/MailScanner/SA.pm 2007-02-08 13:49:40.0 +0100
@@ -94,9 +94,9 @@
unless (MailScanner::Config::IsSimpleValue('usespamassassin')
!MailScanner::Config::Value('usespamassassin')) {
$settings{dont_copy_prefs} = 1; # Removes need for home directory
-# This file is now read directly by SpamAssassin's normal startup code.
-#$prefs = MailScanner::Config::Value('spamassassinprefsfile');
-#$settings{userprefs_filename} = $prefs if defined $prefs;
+# #399424 use /etc/MailScanner/spam.assassin.prefs.conf
+$prefs = MailScanner::Config::Value('spamassassinprefsfile');
+$settings{userprefs_filename} = $prefs if defined $prefs;
$val = $MailScanner::SA::Debug;
$settings{debug} = $val;
# for unusual bayes and auto whitelist database locations
--
Regards
Simon Walter
Bug#346212: mailscanner: Exim spool format error: one_time option treatment
packages mailscanner tags 346212 +pending thanks Hello, I have downloaded exim-testsuite to produce a spoolfile with a one_time router. You misinterpreted a sentence[1] in Exims-spec[2] as of the flag-field has 2 digits (01), but exim only writes 1 digits (1) to the spool-file. old patch: $line =~ s/ (\d+),\d+#01$//; new patch: $line =~ s/ (\d+),\d+#1$//; I have submit the new patch to upstream and it will be part of the next debian release. -- Regards Simon Walter [1] The 01 flag bit indicates the presence of the three other fields that follow the top-level address. [2] http://exim.org/exim-html-4.66/doc/html/spec_html/ch53.html#id2742891 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#326193: 'Incoming Work Group' not honoured for files named with a leading dot
packages mailscanner
tags 326193 +pending
thanks
Hello,
change the line 1729 to
chown $workarea-{uid}, $workarea-{gid}, grep { -f } glob $explodeinto/*
$explodeinto/.*
will fix this problem.
I have submit the patch to upstream and it will be part of the next
debian package.
--
Regards
Simon Walter
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409902: exim4: bad queue+retry handling on 4xx(greylisting)
Package: exim4 Version: 4.63-10 Severity: normal There is an interesting patch in the current exim-upstream version (4.64) which fixes delay-problems if a mailserver returned a 4xx for a mailbox. For a complet description of the problem, see below. In my situation this causes sometimes huge delays for a single mailbox which is quite annoying. I wonder if it's possible to backport this to debians exim version. From the exim ChangeLog: Exim version 4.64 - PH/36 After a 4xx response to a RCPT error, that address was delayed (in queue runs only) independently of the message's sender address. This meant that, if the 4xx error was in fact related to the sender, a different message to the same recipient with a different sender could confuse things. In particualar, this can happen when sending to a greylisting server, but other circumstances could also provoke similar problems. I have changed the default so that the retry time for these errors is now based a combination of the sender and recipient addresses. This change can be overridden by setting address_retry_include_sender=false in the smtp transport. Related discussion: http://www.gossamer-threads.com/lists/exim/users/65173 -- Package-specific info: Exim version 4.63 #1 built 05-Nov-2006 10:41:09 Copyright (c) University of Cambridge 2006 Berkeley DB: Sleepycat Software: Berkeley DB 4.3.29: (September 6, 2005) Support for: crypteq iconv() IPv6 PAM Perl GnuTLS move_frozen_messages Content_Scanning Old_Demime Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql Authenticators: cram_md5 cyrus_sasl plaintext spa Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 Configuration file is /var/lib/exim4/config.autogenerated -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.1 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages exim4 depends on: ii debconf [debconf-2.0] 1.5.8 Debian configuration management sy ii exim4-base4.63-10support files for all exim MTA (v4 ii exim4-daemon-heavy4.63-10exim MTA (v4) daemon with extended exim4 recommends no packages. -- debconf information: exim4/drec: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409790: /etc/cron.daily/mailscanner
package mailscanner tags 409790 +confirmed Hello Stephane Leclerc [EMAIL PROTECTED] writes: Package: mailscanner Version: 4.57.6-2 Severity: normal I upgraded to 4.57.6-2 from -1 The server is using Etch uptodate. Now, I received each morning this message from CRON: /etc/cron.daily/mailscanner: line 41: [: eq: binary operator expected The test is wrong. The result for the exim4 -bP spool_directory is /var/spool/exim4. The test semantic is correct, but the syntax is wrong. Read the comment above it. Replace the line with the following should fix it. if [ $SPOOLDIR != $SPOOLDIRDEFAULT ]; then -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409824: bugzilla: XSS vulnerability in Atom feeds
Package: bugzilla Version: 2.22.1-2 Severity: normal Tags: security A possible cross-site scripting (XSS) vulnerability in Atom feeds produced by Bugzilla. http://www.bugzilla.org/security/2.20.3/ -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (200, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-3-k7-smp Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE) Versions of packages bugzilla depends on: ii apache2-mpm-prefork [htt 2.0.54-5sarge1 traditional model for Apache2 ii dbconfig-common 1.8.29 common framework for packaging dat ii debconf [debconf-2.0]1.4.30.13 Debian configuration management sy ii exim44.50-8sarge2metapackage to ease exim MTA (v4) ii exim4-daemon-heavy [mail 4.50-8sarge2exim MTA (v4) daemon with extended ii libappconfig-perl1.56-2 Perl module for configuration file ii libdbd-mysql-perl2.9006-1A Perl5 database interface to the ii libmailtools-perl1.74-1 Manipulate email in perl programs ii libmime-perl 5.417-1 Perl5 modules for MIME-compliant m ii libtemplate-perl 2.14-1 template processing system written ii libtimedate-perl 1.1600-4Time and date functions for Perl ii mysql-client-4.1 [mysql- 4.1.11a-4sarge7 mysql database client binaries ii patch2.5.9-2 Apply a diff file to an original ii ucf 1.17Update Configuration File: preserv -- debconf information: bugzilla/mysql_user: bugzilla bugzilla/mysql_available: true * bugzilla/dbconfig-install: false bugzilla/mysql/admin-user: bugzilla/remove-error: abort bugzilla/mysql/method: unix socket bugzilla/internal/reconfiguring: false bugzilla/bugzilla_installation_way: Automatic * bugzilla/bugzilla_admin_real_name: Simon Walter bugzilla/mysql_host: localhost bugzilla/upgrade-error: abort bugzilla/dbconfig-reinstall: false bugzilla/db/app-user: bugzilla/internal/skip-preseed: false bugzilla/purge: false * bugzilla/bugzilla_installation_way_single: Later bugzilla/upgrade-backup: true bugzilla/db/dbname: bugzilla/dbconfig-remove: bugzilla/database-type: mysql bugzilla/mysql_need_root: true bugzilla/remote/host: bugzilla/mysql_root_name: root bugzilla/remote/port: bugzilla/index_upgrade1: bugzilla/mysql_name: bugzilla bugzilla/dbconfig-upgrade: true bugzilla/install-error: abort * bugzilla/bugzilla_admin_name: [EMAIL PROTECTED] bugzilla/passwords-do-not-match: bugzilla/remote/newhost: bugzilla/mysql_port: 3306 bugzilla/index_upgrade2: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408161: mailscanner: Option for debconf managed config.
package mailscanner tags 408161 + confirmed thanks Hello [EMAIL PROTECTED] writes: I only ask this because arno-iptables-firewall provides something similar. It would be nice to have debconf driven configuration of mailscanner for the site name, MTA, spool directories, and other standard config tweaks. For those that like to customize the whole thing by hand have a debconf question of Manage mailscanner.conf Yes, this would be nice. It's on my own wishlist too, but this is my first package and I have never worked with debconf before. So i will first have to read some docs and examples. I don't know when I will find the time to do this. -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408135: f-prot-installer: ftp.f-prot.com no longer available -- installation fails
Package: f-prot-installer Severity: important Downloading f-prot from ftp.f-prot.org is no longer possible. See ftp://ftp.f-prot.com/pub/README.TXT http://www.fprot.org/pub/ would be an alternative but they don't provide a md5 file. -- Regards Simon -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages f-prot-installer depends on: ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii debianutils 2.17.5 Miscellaneous utilities specific t ii libwww-perl 5.805-1WWW client/server library for Perl ii unzip 5.52-9 De-archiver for .zip files ii wget 1.10.2-2 retrieves files from the web f-prot-installer recommends no packages. -- debconf information: * f-prot-installer/reinstall: true * f-prot-installer/update_defs: true f-prot-installer/install_later: * f-prot-installer/action: Download and install * f-prot-installer/configured: false f-prot-installer/note_cron: f-prot-installer/where_are_files: /tmp f-prot-installer/failed: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312420: #312420 mailscanner: i/o error when invoking clamav
tags 312420 + moreinfo If this problem is still present, please provide more information like clamav version, otherwise I will close this bug soon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#406814: please check your entropy generator
tags 406814 + pending Since exim-4.63-16 it's possible to override EXIM4_SPOOLDIR in exim4_refresh_gnutls-params from environment (#406989). The new exim/cron.daily.patch does this. -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351650: #351650 Mailscanner Null mime boundary bypass vulnerability
tags 351650 + sarge wontfix confirmed retitle 351650 CVE-2005-1706: Mailscanner Null mime boundary bypass vulnerability thanks I don't want to make a sarge bugfix because etch is on its way. -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407957: move_frozen_messages sometimes fails
Magnus Holmgren [EMAIL PROTECTED] writes: On a mailsystem with ~50k mails per day and the option move_frozen_messages enabled I get 3-5 paniclog lines aday about messages which couldn't be moved to the frozen directory. Does it always fail or are some frozen messages successfully moved? I trust /var/spool/exim4/Finput has the right owner and permission (the code doesn't seem to do anything about it if the directory already exists, even if it could)? It fails in like 0.1% of the messages. ~5k Mails get moved to the frozen directory aday and 3-5 of this fail. exim is configured in a MailScanner setup. So mails go like this: exim_in (smtp_listener) - mailscanner - exim_out (queue runner) But this should not be the problem, because MailScanner uses the correct locking mechanism and mails which are frozen had gone through atleast one delivery attempt... or do i miss something? -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407581: cron.daily/mailscanner has exim4 specific cruft.
tags 407581 + pending thanks [EMAIL PROTECTED] writes: 1) Script is largely exim4 specific. Logic to determine the MTA in use on the system should be run prior to MTA specific code. At current moment, I would suggest adding logic to detect the presence of exim4 before proceeding with the exim specific portion of the cron.daily script. 2) Poor quoting of variables in script. From the script if [ ! $SPOOLDIR eq $SPOOLDIRDEFAULT ]; then # and there is the default spool directory if [ -d $SPOOLDIRDEFAULT ]; then Should be something of the form if [ ! $SPOOLDIR eq $SPOOLDIRDEFAULT ]; then # and there is the default spool directory if [ -d $SPOOLDIRDEFAULT ]; then $SPOOLDIR may be the empty string. Without quoting this will confuse the test builtin ([) in the shell leading to erroneous results. 1) Pending, see #305239 2) Now also pending. These variables should only be empty on very obsure conditions, but this way it's cleaner. -- Regards Simon Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305239: #305239 mailscanner: stops scanning email
I will add a comment to MailScanners README.Debian about this problem and close this bug with the next upload. The related razor bug is gone since upstream version 2.75 and debian version 2.810-1, which has reached testing nearly a year ago. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#406989: need to tell exim4_refresh_gnutls-params to use a different spooldirectory
Package: exim4 Severity: normal Using exim4 with MailScanner modifies the configuration so exim has two spooldirectories. First one for incoming messages (exim4 ...) second one for outgoing (exim4 -DOUTGOING ...). MailScanner takes the messages from incoming, scanns them an places them into outgoing. To run exim_tidydb and generate log-reports in the outgoing spooldirectory I tell the users to copy /etc/cron.daily/exim4-base and patch it to call exim4 with -DOUTGOING. This works except for the refresh of the GnuTLS parameters because this is handeled by /usr/share/exim4/exim4_refresh_gnutls-params which itself calls exim4 to find the spooldirectory. So I need a way to tell exim4_refresh_gnutls-params to deligate the -DOUTGOING to its exim4 call or tell exim4_refresh_gnutls-params directly in which spooldirectory it should work. Related mailscanner bugs is: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406814 Regards Simon -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#406814: please check your entropy generator
Hi Stephane Leclerc [EMAIL PROTECTED] writes: and call this script in your /etc/cron.daily/mailscanner_exim instead of the original exim4_refresh_gnutls-params. Are you sure? In /etc/cron.daily/, I only have exim4-base and exim4-outgoing. I patched exim4-outgoing. The only mailscanner_exim file is located in /etc/logrotate.d/ and is used for log rotate. Sorry, my bad. I meant /etc/cron.daily/exim4-outgoing. -- Regards Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#406814: #406814 please check your entropy generator
Hello, problem is /etc/cron.daily/mailscanner_exim calls /usr/share/exim4/exim4_refresh_gnutls-params which does its own detection of the spooldirectory (exim4 -bP spool_directory). so exim4_refresh_gnutls-params always runs on /var/spool/exim4/ and never on /var/spool/exim4_outgoing. currently there is no way to tell exim4_refresh_gnutls-params to use a different spool_dir so i have opened a bugreport on exim4 to request this. in the meantime you can copy /usr/share/exim4/exim4_refresh_gnutls-params to /usr/local/share/mailscanner/ or something similar, change line 28 to SPOOLDIR=$(/usr/lib/exim4/exim4 -DOUTGOING -bP spool_directory | sed 's/.*=[[:space:]]\(.*\)/\1/') and call this script in your /etc/cron.daily/mailscanner_exim instead of the original exim4_refresh_gnutls-params. -- Regards Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295727: Fixed in 2.810-1
This bug was fixed in upstream 2.75 and should be closed with debian version 2.810-1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401329: Mailscanner logrotate and crondaily scripts
I don't think mailscanners cron.daily or logrotate should do anything MTA specific. A better solution would be to change the exim installation manual, so exim handles /var/spool/exim like it should and another cron.daily script handles the manual created /var/spool/exim_x directory. I have appended a tar.gz file with a new README.exim4 and the necessary files. -- Regards Simon mailscanner_exim.tar.gz Description: Binary data
Bug#401329: new init-script
Here is new version of the init-script which would solve the problems.
#! /bin/sh
### BEGIN INIT INFO
# Provides: MailScanner daemon
# Required-Start:$local_fs $remote_fs
# Required-Stop: $local_fs $remote_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Controls mailscanner instances
# Description: MailScanner is a queue-based spam/virus filter
### END INIT INFO
# Author: Simon Walter [EMAIL PROTECTED]
# Do NOT set -e
# PATH should only include /usr/* if it runs after the mountnfs.sh script
PATH=/usr/sbin:/usr/bin:/bin:/sbin
DESC=mail spam/virus scanner
NAME=MailScanner
PNAME=mailscanner
DAEMON=/usr/sbin/$NAME
STARTAS=MailScanner
SCRIPTNAME=/etc/init.d/$PNAME
CONFFILE=/etc/MailScanner/MailScanner.conf
# Exit if the package is not installed
[ -x $DAEMON ] || exit 0
run_mailscanner=0
run_nice=0
stopped_lockfile=/var/lock/subsys/MailScanner.off
# Read configuration variable file if it is present
[ -r /etc/default/$PNAME ] . /etc/default/$PNAME
# Load the VERBOSE setting and other rcS variables
. /lib/init/vars.sh
# Define LSB log_* functions.
# Depend on lsb-base (= 3.0-6) to ensure that this file is present.
. /lib/lsb/init-functions
# Don't start if MailScanner is not configured
if [ $run_mailscanner = 0 ]; then
if [ -z $satisfy_nitpicking_on_removal ]; then
cat -EOF
Please edit the file /etc/MailScanner/MailScanner.conf according to
your needs. Then configure sendmail or exim for use with mailscanner.
After you are done you will have to edit /etc/default/mailscanner as
well. There you will have to set the variable run_mailscanner to 1,
and then type /etc/init.d/mailscanner start to start the mailscanner
daemon.
EOF
fi
exit 0
fi
# sanity check for permissions
check_dir()
{
if [ ! -d $1 ]; then
echo 2 $0: directory $1: does not exist
exit 1
fi
actual=$(stat -c %U $1)
if [ $actual != $2 ]; then
echo 2 $0: directory $1: wrong owner (expected $2 but is $actual)
exit 1
fi
actual=$(stat -c %G $1)
if [ $actual != $3 ]; then
echo 2 $0: directory $1: wrong group (expected $3 but is $actual)
exit 1
fi
}
user=$(echo $(awk -F= '/^Run As User/ {print $2; exit}' $CONFFILE))
group=$(echo $(awk -F= '/^Run As Group/ {print $2; exit}' $CONFFILE))
check_dir /var/spool/MailScanner ${user:-mail} ${group:-mail}
check_dir /var/lib/MailScanner ${user:-mail} ${group:-mail}
check_dir /var/run/MailScanner ${user:-mail} ${group:-mail}
check_dir /var/lock/subsys/MailScanner ${user:-mail} ${group:-mail}
#
# Function that starts the daemon/service
#
do_start()
{
# Return
# 0 if daemon has been started
# 1 if daemon was already running
# 2 if daemon could not be started
start-stop-daemon --start --quiet --startas $STARTAS --name $NAME --test /dev/null \
|| return 1
start-stop-daemon --start --quiet --nicelevel $run_nice --exec $DAEMON --name $NAME -- $DAEMON_ARGS \
|| return 2
# Add code here, if necessary, that waits for the process to be ready
# to handle requests from services started subsequently which depend
# on this one. As a last resort, sleep for some time.
# Set lockfile to inform cronjobs about the running daemon
RETVAL=$?
if [ $RETVAL -eq 0 ]; then
touch /var/lock/subsys/mailscanner
rm -f $stopped_lockfile
fi
}
#
# Function that stops the daemon/service
#
do_stop()
{
# Return
# 0 if daemon has been stopped
# 1 if daemon was already stopped
# 2 if daemon could not be stopped
# other if a failure occurred
start-stop-daemon --stop --retry=TERM/30 --name $NAME
RETVAL=$?
[ $RETVAL = 2 ] return 2
# Remove lockfile for cronjobs
if [ $RETVAL -eq 0 ]; then
rm -f /var/lock/subsys/mailscanner
touch $stopped_lockfile
fi
}
case $1 in
start)
[ $VERBOSE != no ] log_daemon_msg Starting $DESC $NAME
do_start
case $? in
0|1) [ $VERBOSE != no ] log_end_msg 0 ;;
2) [ $VERBOSE != no ] log_end_msg 1 ;;
esac
;;
stop)
[ $VERBOSE != no ] log_daemon_msg Stopping $DESC $NAME
do_stop
case $? in
0|1) [ $VERBOSE != no ] log_end_msg 0 ;;
2) [ $VERBOSE != no ] log_end_msg 1 ;;
esac
;;
#reload|force-reload)
#
# If do_reload() is not implemented then leave this commented out
# and leave 'force-reload' as an alias for 'restart'.
#
#log_daemon_msg Reloading $DESC $NAME
#do_reload
#log_end_msg $?
#;;
restart|force-reload)
#
# If the reload option is implemented then remove the
# 'force-reload' alias
#
log_daemon_msg Restarting $DESC $NAME
do_stop
case $? in
0|1)
do_start
case $? in
0) log_end_msg 0 ;;
1) log_end_msg 1 ;; # Old process is still running
*) log_end_msg 1 ;; # Failed to start
esac
;;
*)
# Failed to stop
log_end_msg 1
;;
esac
;;
*)
#echo Usage: $SCRIPTNAME {start|stop|restart|reload|force-reload} 2
echo Usage: $SCRIPTNAME {start|stop|restart|force-reload} 2
exit 3
;;
esac
:
Bug#401329: wrong bug id
sorry, i misinterpreted a bts-mail last mail should have gone to the new bug which still has no #id -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402967: mailscanner: init-script doesn't wait reliably for children to die
Package: mailscanner Version: 4.51.5-1.1 Severity: important on heavy load systems the init-script doesn't wait for all children/processes to die. this results in multiple instances of mailscanner running after /etc/init.d/mailscanner restart also the init-script detects editor processes which announce the open file in their process-name as running mailscanner instances like emacs /etc/MailScanner.conf -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402967: fixed init-script
Here is new version of the init-script which would solve the problems.
#! /bin/sh
### BEGIN INIT INFO
# Provides: MailScanner daemon
# Required-Start:$local_fs $remote_fs
# Required-Stop: $local_fs $remote_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Controls mailscanner instances
# Description: MailScanner is a queue-based spam/virus filter
### END INIT INFO
# Author: Simon Walter [EMAIL PROTECTED]
# Do NOT set -e
# PATH should only include /usr/* if it runs after the mountnfs.sh script
PATH=/usr/sbin:/usr/bin:/bin:/sbin
DESC=mail spam/virus scanner
NAME=MailScanner
PNAME=mailscanner
DAEMON=/usr/sbin/$NAME
STARTAS=MailScanner
SCRIPTNAME=/etc/init.d/$PNAME
CONFFILE=/etc/MailScanner/MailScanner.conf
# Exit if the package is not installed
[ -x $DAEMON ] || exit 0
run_mailscanner=0
run_nice=0
stopped_lockfile=/var/lock/subsys/MailScanner.off
# Read configuration variable file if it is present
[ -r /etc/default/$PNAME ] . /etc/default/$PNAME
# Load the VERBOSE setting and other rcS variables
. /lib/init/vars.sh
# Define LSB log_* functions.
# Depend on lsb-base (= 3.0-6) to ensure that this file is present.
. /lib/lsb/init-functions
# Don't start if MailScanner is not configured
if [ $run_mailscanner = 0 ]; then
if [ -z $satisfy_nitpicking_on_removal ]; then
cat -EOF
Please edit the file /etc/MailScanner/MailScanner.conf according to
your needs. Then configure sendmail or exim for use with mailscanner.
After you are done you will have to edit /etc/default/mailscanner as
well. There you will have to set the variable run_mailscanner to 1,
and then type /etc/init.d/mailscanner start to start the mailscanner
daemon.
EOF
fi
exit 0
fi
# sanity check for permissions
check_dir()
{
if [ ! -d $1 ]; then
echo 2 $0: directory $1: does not exist
exit 1
fi
actual=$(stat -c %U $1)
if [ $actual != $2 ]; then
echo 2 $0: directory $1: wrong owner (expected $2 but is $actual)
exit 1
fi
actual=$(stat -c %G $1)
if [ $actual != $3 ]; then
echo 2 $0: directory $1: wrong group (expected $3 but is $actual)
exit 1
fi
}
user=$(echo $(awk -F= '/^Run As User/ {print $2; exit}' $CONFFILE))
group=$(echo $(awk -F= '/^Run As Group/ {print $2; exit}' $CONFFILE))
check_dir /var/spool/MailScanner ${user:-mail} ${group:-mail}
check_dir /var/lib/MailScanner ${user:-mail} ${group:-mail}
check_dir /var/run/MailScanner ${user:-mail} ${group:-mail}
check_dir /var/lock/subsys/MailScanner ${user:-mail} ${group:-mail}
#
# Function that starts the daemon/service
#
do_start()
{
# Return
# 0 if daemon has been started
# 1 if daemon was already running
# 2 if daemon could not be started
start-stop-daemon --start --quiet --startas $STARTAS --name $NAME --test /dev/null \
|| return 1
start-stop-daemon --start --quiet --nicelevel $run_nice --exec $DAEMON --name $NAME -- $DAEMON_ARGS \
|| return 2
# Add code here, if necessary, that waits for the process to be ready
# to handle requests from services started subsequently which depend
# on this one. As a last resort, sleep for some time.
# Set lockfile to inform cronjobs about the running daemon
RETVAL=$?
if [ $RETVAL -eq 0 ]; then
touch /var/lock/subsys/mailscanner
rm -f $stopped_lockfile
fi
}
#
# Function that stops the daemon/service
#
do_stop()
{
# Return
# 0 if daemon has been stopped
# 1 if daemon was already stopped
# 2 if daemon could not be stopped
# other if a failure occurred
start-stop-daemon --stop --retry=TERM/30 --name $NAME
RETVAL=$?
[ $RETVAL = 2 ] return 2
# Remove lockfile for cronjobs
if [ $RETVAL -eq 0 ]; then
rm -f /var/lock/subsys/mailscanner
touch $stopped_lockfile
fi
}
case $1 in
start)
[ $VERBOSE != no ] log_daemon_msg Starting $DESC $NAME
do_start
case $? in
0|1) [ $VERBOSE != no ] log_end_msg 0 ;;
2) [ $VERBOSE != no ] log_end_msg 1 ;;
esac
;;
stop)
[ $VERBOSE != no ] log_daemon_msg Stopping $DESC $NAME
do_stop
case $? in
0|1) [ $VERBOSE != no ] log_end_msg 0 ;;
2) [ $VERBOSE != no ] log_end_msg 1 ;;
esac
;;
#reload|force-reload)
#
# If do_reload() is not implemented then leave this commented out
# and leave 'force-reload' as an alias for 'restart'.
#
#log_daemon_msg Reloading $DESC $NAME
#do_reload
#log_end_msg $?
#;;
restart|force-reload)
#
# If the reload option is implemented then remove the
# 'force-reload' alias
#
log_daemon_msg Restarting $DESC $NAME
do_stop
case $? in
0|1)
do_start
case $? in
0) log_end_msg 0 ;;
1) log_end_msg 1 ;; # Old process is still running
*) log_end_msg 1 ;; # Failed to start
esac
;;
*)
# Failed to stop
log_end_msg 1
;;
esac
;;
*)
#echo Usage: $SCRIPTNAME {start|stop|restart|reload|force-reload} 2
echo Usage: $SCRIPTNAME {start|stop|restart|force-reload} 2
exit 3
;;
esac
:
Bug#346212: Still not fixed
this bug is still not fixed in 4.57.6
suggested patch is present but commented out
see Exim.pm L442:
#BROKEN # strips new special content = 4.10
#BROKEN $line =~ s/ (\d+),\d+#01$//;
#BROKEN if (defined $1) {
#BROKEN $line = substr($line, 0, length($line)-$1-1);
#BROKEN }
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
