Bug#988078: release-notes: add information regarding exim4 and 'tainted data' issue

Package: release-notes Severity: normal Hi, please add a new paragraph 5.1.13 (and move existing 5.1.14 to .14) regarding exim and the new 'tainted data' issue. Text copied from NEWS.Debian file: --- Please consider exim 4.93/4.94 a *major* exim upgrade. It introduces the concept of

Bug#987133: links to more info

On Exim-users: https://lists.exim.org/lurker/message/20201109.222746.24ea3904.de.html https://lists.exim.org/lurker/message/20210406.161056.f80935f1.en.html On Debian-User-German: Regards, Paul

Bug#987133: exim4: Exim 4.94's new tainting-feature will break many running configs

Package: exim4 Version: 4.94-17 Severity: serious Justification: The tainting-feature that has been introduced with 4.94 by upstream will break many running configurations. Dear Maintainers, the tainting-feature that has been introduced with 4.94 by upstream will break many running

Bug#929937: dovecot-lmtpd: _fully_ support RfC 5233 (Sieve Subaddress Extension) for LMTP transport

Package: dovecot-lmtpd Version: 1:2.2.27-3+deb9u4 Severity: wishlist Tags: upstream Dear Maintainer, Dovecot's LMTP implementation and Pigeonhole Sieve already do support the format. RfC 5233, the Sieve subaddress extension, also offers . Way forward could be like this: 1) Introduce a new

Bug#929936: dovecot-sieve: _fully_ support RfC 5233 (Sieve Subaddress Extension)

Package: dovecot-sieve Version: 1:2.2.27-3+deb9u4 Severity: wishlist Tags: upstream Dear Maintainer, Dovecot's LMTP implementation and Pigeonhole Sieve already do support the format. RfC 5233, the Sieve subaddress extension, also offers . Way forward could be like this: 1) Introduce a new

Bug#772031: Please allow SSL cert and key to be read from different files

Dear Philipp, On 07.11.2015 14:48, Philipp Hübner wrote: > Anyway, I opened an issue with this feature request in the upstream bug > tracker at https://github.com/processone/ejabberd/issues/826 . Many thanks! Greetings, Paul

Bug#804404: libdvd-pkg: dpkg-buildpackage fails on Wheezy

Package: libdvd-pkg Version: 1.3.99-1-1 Severity: normal Dear Maintainer, * What led up to the situation? downloaded .deb and installed with 'dpkg -i ,,,' * What was the outcome of this action? libdvd-pkg: Checking orig.tar integrity... /usr/src/libdvd-pkg/libdvdcss_1.3.99.orig.tar.bz2:

Bug#772031: Please allow SSL cert and key to be read from different files

On 06.11.2015 13:03, Rhonda D'Vine wrote: > * Paul Muster <p...@muster.net> [2015-11-04 21:21:39 CET]: >> It's especially _necessary_ to split key, cert and chain to different >> files to be able to use Let's Encrypt certificates. This mistakable wording has been clarified &

Bug#772031: Please allow SSL cert and key to be read from different files

On 04.11.2015 21:57, Holger Weiß wrote: > * Paul Muster <p...@muster.net> [2015-11-04 21:21]: >> It's especially _necessary_ to split key, cert and chain to different >> files to be able to use Let's Encrypt certificates. > > I haven't played with Let's Encrypt yet,

Bug#772031: Please allow SSL cert and key to be read from different files

Dear Ejabberd-Team, On Thu, 4 Dec 2014 15:11:41 +0100 martin f krafft wrote: > Package: ejabberd > Version: 14.07-3 > Severity: wishlist > Tags: upstream > > SSL cert and key usually are not in the same file. The key usually > has tighter security. Please let me poit ejabberd to a separate >

Bug#671672: openssl s_client -starttls xmpp burn cpu with broken server

Dear OpenSSL-Maintainers, On Wed, 3 Jun 2015 11:25:41 +1000 Brian May wrote: > On Fri, Apr 25, 2014 at 06:03:00PM +0200, gp wrote: > > Attached you'll find a patch that supposedly fixes this issue. It is > > patch 2/4 of this series of patches > >

Bug#793687: rsnapshot: regression fix: --rsh args

tags 793687 patch thanks On Sun, 6 Sep 2015 12:55:32 Jonas Genannt wrote: The patch that is working is backported from upstream to the version in Jessie: Could you please provide a stable update? It would be really great if a fixed package could be provided for

Bug#784070: is it maybe possible to settle dislikings and fix this bug?

Dear Michael, thanks for clarifying the situation. > serverfault solution isn't exactly wrong, it is incomplete, it > does not cover a situation when you have slow-to-appear devices. > This solution, however, fixes the problem in this bugreport, > a problem which I introduced when I tried to

Bug#784823: Regression - mdadm in jessie will not boot degraded raid1 array

severity 784823 critical merge 784070 784823 thanks Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784070 for new information about bug and package status. Greetings, Paul

Bug#780313: [Pkg-owncloud-maintainers] Bug#780313: sabredav: add support for Icedove's Mailing List

Hello there, thank you for the really quick response! Am 2015-03-12 03:19, schrieb David Prévot: Thanks for your interest in the PHP Sabre Debian packages. Well, it... came over me when installing owncloud. ;-) could you please add support for Idedove's feature Mailing List? Maybe this

Bug#780313: sabredav: add support for Icedove's Mailing List

Package: php-sabre-dav Version: 1.8.10-2 Severity: wishlist Dear Maintainer, could you please add support for Idedove's feature Mailing List? Icedove calls Mailing List a set of addressbook entries. One can e.g. write an e-mail to members of this list at once. When synchronizing an addressbook

Bug#779911: mailman: Upstream 2.1.19 available

On 06.03.2015 11:55, Joost van Baal-Ilić wrote: Thanks for your bugreport. Thank *you* for the quick reply! - could you paste upstream NEWS and/or changelog here? It's too long. Please see: https://mail.python.org/pipermail/mailman-announce/2015-February/000202.html Any other urgent

Bug#779911: mailman: Upstream 2.1.19 available

Package: mailman Version: 2.1.18-1+b1 Severity: wishlist Tags: fixed-upstream Hello there, a new version of mailman is available upstream: http://list.org/ | *Current Version* | | The current stable GNU Mailman version is 2.1.19, released | on 28-Feb-2015. Announcement:

Bug#776672: radvd: Add support for dynamic 6rd tunnels

Package: radvd Version: 1:1.9.1-1.3 Severity: wishlist Dear Maintainer, could support for dynamic 6rd tunnels be added? Parameters would be * Base6rdInterface the IPv4-Interface, e.g. ppp0 * 6rdPrefix tunnel provider's prefix, e.g. 2001:55c for Comcast * 6rdPrefixLength tunnel provider's

Bug#774416: RFP: openca-ocspd -- OCSP responder

Package: wnpp Severity: wishlist Actually there is no OCSP responder available in Debian (besides 'openssl ocsp -index ...'). OpenCA's OCSPD seems to be really alive (V.3.1.0 published 13.08.2014) and has interesting features. * Package name: openca-ocspd Version 3.1.0 Upstream Author:

Bug#761925: exim4-config: add OUTGOING_INTERFACE macro to remote_smtp transport

Package: exim4-config Version: 4.80-7 Severity: wishlist Tags: patch Dear Maintainer, could a macro for the outgoing interface be added to conf.d/transport/30_exim4-config_remote_smtp ? .ifdef OUTGOING_INTERFACE interface = OUTGOING_INTERFACE .endif so that one can configure the outgoing

Bug#748302: Add Xen parameters to /etc/default/grub

On 16.05.2014 15:58, Ian Campbell wrote: On Fri, 2014-05-16 at 10:33 +0100, Colin Watson wrote: On Fri, May 16, 2014 at 09:35:48AM +0100, Ian Campbell wrote: On Fri, 2014-05-16 at 00:09 +0100, Colin Watson wrote: On Thu, May 15, 2014 at 11:30:04PM +0200, Paul Muster wrote: Please add

Bug#748302: Add Xen parameters to /etc/default/grub

Package: grub-common Severity: wishlist Please add placeholders/examples for Xen kernel config to /etc/default/grub --- #The values of these options replace the values of #'GRUB_CMDLINE_LINUX' and `GRUB_CMDLINE_LINUX_DEFAULT' #for Linux and Xen menu entries. #GRUB_CMDLINE_LINUX_XEN_REPLACE=

Bug#744018: update for stable is on the way

https://enc.com.au/2014/04/10/wordpress-update-needed-for-stable-too/ | Yesterday I mentioned that wordpress had an important security update | to 3.8.2 The particular security bugs also impact the stable Debian | version of wordpress, so those patches have been backported. I’ve | uploaded

Bug#705860: aptitude: removed (from release) package does not appear in list obsolete ... packages

Package: aptitude Version: 0.6.8.2-1 Severity: normal Dear Maintainers, the system has been upgraded from Squeeze/Stable to Wheezy/Testing some time before Wheezy-Release. Owncloud was available and I installed it. Then owncloud was removed from Wheezy. Even after apt-get update (and aptitude

Bug#705860: Acknowledgement (aptitude: removed (from release) package does not appear in list obsolete ... packages)

Some more information: # apt-cache policy owncloud owncloud: Installed: 4.0.8debian-1.6 Candidate: 4.0.8debian-1.6 Version table: *** 4.0.8debian-1.6 0 100 /var/lib/dpkg/status 4.0.4debian2-3.3 0 500 http://debian/debian/ wheezy-proposed-updates/main i386 Packages #

Bug#680458: fixed before Wheezy release?

Hello, is there something one can do to get this fixed before Wheezy is released? http://www.debian.org/Bugs/Developer.en.html#severities sounds to me like increasing severity to serious should only be done by the package maintainer or the release manager... Thanks, Paul -- To

Bug#702116: exim4-daemon-heavy: LDAP for SMTP auth not working

On 07.03.2013 19:18, Andreas Metzler wrote: On 2013-03-06 Paul Muster p...@muster.dyndns.info wrote: Debug-mode information exim -d -bdf -oX 2525 [...] -d+all might be more helpful. ok, there it is: 19:23:32 29767 SMTP AUTH PLAIN auth_data= 19:23:32 29767 plain_server_ldap authenticator

Bug#702116: exim4-daemon-heavy: LDAP for SMTP auth not working

On 07.03.2013 20:06, Andreas Metzler wrote: Just for debugging, does it work if you specify the IP address of the ldap server instead of its name? That works!!11 Great, after weeks of research - it works! But why? DNS is ok: # su Debian-exim \h:\w$ nslookup ldap Server: 192.168.1.1

Bug#702116: exim4-daemon-heavy: LDAP for SMTP auth not working

On 07.03.2013 20:39, Paul Muster wrote: On 07.03.2013 20:06, Andreas Metzler wrote: Just for debugging, does it work if you specify the IP address of the ldap server instead of its name? That works!!11 Great, after weeks of research - it works! But why? DNS is ok: # su Debian-exim

Bug#702116: exim4-daemon-heavy: resolv.conf not respected when connecting to LDAP server

Hello, please see https://lists.exim.org/lurker/message/20130307.235129.7eabc9f1.en.html where Phil Pennock explains what he thinks about what happens inside of Exim. I don't know if you could and want to change Exim's behaviour for Debian. Thanks greetings, Paul -- To UNSUBSCRIBE, email

Bug#702116: exim4-daemon-heavy: LDAP for SMTP auth not working

Hello, Andreas, thanks for your reply. On 06.03.2013 19:33, Andreas Metzler wrote: your version is a mixture of LOGIN and PLAIN, it identifies itself as as PLAIN and uses auth2/auth3 but specifies nonempty server_prompts. Maybe that's an _additional_ error... I think something like these

Bug#702116: exim4-daemon-heavy: LDAP for SMTP auth not working

Debug-mode information exim -d -bdf -oX 2525 17519 SMTP AUTH PLAIN auth_data= 17519 plain_server_ldap authenticator server_condition: 17519 $auth1 = 17519 $auth2 = paul 17519 $auth3 = password 17519 $1 = 17519 $2 = paul 17519 $3 = password 17519 LDAP parameters:

Bug#702116: exim4-daemon-heavy: LDAP for SMTP auth not working

Hello, some additional information: # exim -d -be '${if ldapauth{user=uid=${quote_ldap_dn:paul},ou=Users,dc=BASIS pass=${quote:geheim} ldap://ldap/}}' shows: * with existing user and wrong password: Mar 4 18:28:06 ldap slapd[9942]: conn=5292 fd=70 ACCEPT from IP=192.168.1.4:37312

Bug#702116: exim4-daemon-heavy: LDAP for SMTP auth not working

Package: exim4-daemon-heavy Version: 4.80-7 Severity: normal Dear Maintainers, I want to use LDAP for SMTP authentication. The second box on http://www.exim.org/exim-html-current/doc/html/spec_html/ch-the_plaintext_authenticator.html#SECID173 shows an example which I customized for my

Bug#614801: USB 3.0 still not working in Wheezy

found 614801 3.6.9-1~experimental.1 thanks As requested I checked older versions - and also found this bug in 3.6.9. # uname -a Linux system 3.6-trunk-686-pae #1 SMP Debian 3.6.9-1~experimental.1 i686 GNU/Linux # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002

Bug#614801: USB 3.0 still not working in Wheezy

fixed 614801 3.7.1-1~experimental.1 thanks With newer Kernel everything is fine: # uname -a Linux system 3.7-trunk-686-pae #1 SMP Debian 3.7.1-1~experimental.1 i686 GNU/Linux # lsusb Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Linux

Bug#614801: USB 3.0 still not working in Wheezy

found 614801 3.2.35-2 severity important thanks Still appears with # uname -a Linux system 3.2.0-4-686-pae #1 SMP Debian 3.2.35-2 i686 GNU/Linux # lspci -nnv -s 00:02.0 00:02.0 USB controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host Controller [1033:0194] (rev 03) (prog-if 30 [XHCI])

Bug#680458: squirrelmail: Q-encoded header issue

tags 680458 + patch Please take a look at http://squirrelmail.org/ : --- ANNOUNCE: PHP 5.4 Compatibility Dec 01, 2012 by Paul Lesniewski With the recent release of PHP version 5.4, some community members have helped identify some small issues which we've fixed and made available in our daily

Bug#695075: logcheck-database: new filter rules for nfs (for Wheezy)

Package: logcheck-database Version: 1.3.15 Severity: normal Tags: patch Dear Maintainer, please change /etc/logcheck/ignore.d.server/nfs: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rpc\.mountd: authenticated (un|)mount request from [._[:alnum:]-]+:[0-9]+ for (/[._[:alnum:]-]*)+

Bug#688339: Acknowledgement (logcheck-database: dhcp: match IPv6-aware records, too)

reassign 688339 logcheck-database 1.3.15 thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#688339: logcheck-database: dhcp: match IPv6-aware records, too

Package: logcheck Version: 1.3.13 Severity: normal Tags: patch Please add following regex ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd: if [._[:alnum:]-]+ IN A rrset doesn't exist and [._[:alnum:]-]+ IN rrset doesn't exist delete [._[:alnum:]-]+ IN TXT [[:alnum:]]+: success\.$ This matches

Bug#687990: logcheck-database: bind: updating zone...PTR and signer...approved

Package: logcheck-database Version: 1.3.15 Severity: wishlist Tags: patch *** Please type your report below this line *** In /etc/logcheck/ignore.d.server/bind (1) please change ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ named\[[[:digit:]]+\]: client [.:[:xdigit:]]+#[[:digit:]]+: updating zone

Bug#687990: logcheck-database: bind: updating zone...PTR and signer...approved

Update: (1) please change ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ named\[[[:digit:]]+\]: client [.:[:xdigit:]]+#[[:digit:]]+: updating zone '[-._[:alnum:]]+/IN': (adding an RR|deleting rrset) at '[._[:alnum:]-]+' A$ to ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ named\[[[:digit:]]+\]:

Bug#485232: RFP: squirrelmail-ldap-common -- a shared library which is required by ldap_abook_backend and ldap_prefs_backend plugins for Squirrelmail

Package: wnpp Severity: wishlist * Package name: squirrelmail-ldap-common Version : 0.5.0 (2006-01-08) Upstream Author : Daniel Marczisovszky * URL : http://daniel.marczisovszky.hu/projects/squirrelmail/ldap_common/ * License : GPL Programming Lang: PHP

Bug#485234: RFP: squirrelmail-ldap-abook-backend -- LDAP abook backend plugin for Squirrelmail makes it possible to store Personal Address Books in LDAP

Package: wnpp Severity: wishlist * Package name: squirrelmail-ldap-abook-backend Version : 0.2.2 Upstream Author : Daniel Marczisovszky * URL : http://daniel.marczisovszky.hu/projects/squirrelmail/ldap_abook_backend/ * License : GPL Programming Lang: PHP

Bug#485238: RFP: squirrelmail-ldap-prefs-backend -- LDAP prefs backend plugin makes it possible to store SquirrelMail user preferences in your LDAP directory

Package: wnpp Severity: wishlist * Package name: squirrelmail-ldap-prefs-backend Version : 0.7.1 Upstream Author : Daniel Marczisovszky * URL : http://daniel.marczisovszky.hu/projects/squirrelmail/ldap_prefs_backend/ * License : GPL Programming Lang: PHP

Bug#485232: RFP: squirrelmail-ldap-common -- a shared library which is required by ldap_abook_backend and ldap_prefs_backend plugins for Squirrelmail

Paul Muster wrote: I.e. Depends: squirrelmail Depends: squirrelmail, php4-ldap | php5-ldap Greetings, Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#485234: RFP: squirrelmail-ldap-abook-backend -- LDAP abook backend plugin for Squirrelmail makes it possible to store Personal Address Books in LDAP

Paul Muster wrote: * Package name: squirrelmail-ldap-abook-backend A patch has to be applied to /usr/share/squirrelmail/functions/addressbook.php I do not know how to implement this in a Debian package. Greetings, Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject

Bug#447783: bacula-sd: fails if no tape loaded in autochanger

Package: bacula-sd Version: 1.38.11-8 Severity: important As discussed in #337376 bacula-sd fails to backup if there is no tape in drive: Start Backup JobId 4, Job=Server.2007-10-23_19.15.00 3301 Issuing autochanger loaded drive 0 command. 3991 Bad autochanger loaded drive 0 command: ERR=Child

Bug#440719: mount: happens in Etch, too

Package: mount Version: 2.12r-19 Followup-For: Bug #440719 I have the same effect in Etch, too. $ grep swap /var/log/boot Sat Sep 8 20:38:19 2007: Activating swap:swapon on /dev/volg1/logv4 Sat Sep 8 20:38:19 2007: Will now activate swapfile swap:swapon on /dev/volg1/logv4 Sat Sep 8

Bug#440719: mount: happens in Etch, too

Package: mount Version: 2.12r-19 Followup-For: Bug #440719 I have the same effect in Etch, too. $ grep swap /var/log/boot Sat Sep 8 20:38:19 2007: Activating swap:swapon on /dev/volg1/logv4 Sat Sep 8 20:38:19 2007: Will now activate swapfile swap:swapon on /dev/volg1/ Sat Sep 8 20:38:19

Bug#435627: bacula-sd: change suggestion for mtx-changer script

Package: bacula-sd Version: 1.38.11-8 Severity: minor In /etc/bacula-sd.conf please replace # Changer Command = /home/kern/bacula/bin/mtx-changer %c %o %S %a %d with # Changer Command = /etc/bacula/scripts/mtx-changer %c %o %S %a %d I spent hours in finding this. Thanks, Paul -- System

Bug#435633: bacula-server: leaves .conf-files in /etc/bacula after purge

Package: bacula-server Version: 1.38.11-8 Severity: normal Also after a aptitude purge bacula-server bacula-sd-sqlite3 bacula-director-sqlite3 \ bacula-director-common bacula-console there are a lot of files left in /etc/bacula: # la bacula/ total 64 drwxr-xr-x 3 root root 4096

Bug#412016: vdr: fails to restart if timers set

Hello, 27 Feb 2007 00:07:55 Thomas Günther [EMAIL PROTECTED] wrote: Stefan Wagner wrote: Then it is again not possible to restart vdr until the line ist removed from timers.conf. vdr refresh the channels, but only in memory. to write the channels.conf, you must manuell editing a

Bug#412016: vdr: fails to restart if timers set

Just for the records: We now tried (off-list) 1) /etc/init.d/vdradmin-am stop 2) /etc/init.d/vdr stop 3) rm /var/cache/vdr/epg.data 4) rm /var/lib/vdr/timers.conf 5) /etc/init.d/vdr start 6) /etc/init.d/vdradmin-am start but after creating a new timer (via vdradmin-am web-interface) and

Bug#412016: vdr: fails to restart if timers set

Tobias Grimm schrieb: Paul Muster wrote: When timers are defined (no matter on if it was set via vdr's osd or via vdradmin) vdr fails to start or restart with an error message vdr: [6081] ERROR: channel T-8468-13057-16394 not defined (T-xxx-x-x changes). What happens if you remove

Bug#412016: vdr: fails to restart if timers set

Package: vdr Version: 1.4.4-1 Severity: important When timers are defined (no matter on if it was set via vdr's osd or via vdradmin) vdr fails to start or restart with an error message vdr: [6081] ERROR: channel T-8468-13057-16394 not defined (T-xxx-x-x changes). channels.conf looks:

Bug#348891: capisuite: wrong date format in status mails

Package: capisuite Version: 0.4.5-3 Severity: minor Tags: patch Message-ID: [EMAIL PROTECTED] Problem mit falschen Datumsangaben bei CapiSuite-Mails: https://lists.berlios.de/pipermail/capisuite-users/2005-March/001378.html (der ganze Thread ist interessant) Patch:

Bug#348891: Acknowledgement (capisuite: wrong date format in status mails)

Following patch can be found at http://bugs.gentoo.org/show_bug.cgi?id=96540 --- cs_helpers.pyin 2004-11-28 14:35:23.0 +0100 +++ cs_helpers.py 2005-06-19 20:55:49.0 +0200 @@ -10,6 +10,7 @@ # (at your option) any later version. import os +import time # the name of