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

[Paul Muster]

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 tainted data read from untrusted sources, like e.g. message
  sender or recipient. This tainted data (e.g. $local_part or $domain)
  cannot be used among other things as a file or directory name or command
  name.

  This WILL BREAK configurations which are not updated accordingly.
  Old Debian exim configuration files also will not work unmodified, the new
  configuration needs to be installed with local modifications merged in.

  Typical nonworking examples include:
  * Delivery to /var/mail/$local_part. Use $local_part_data in combination
with check_local_user.
  * Using
data = ${lookup{$local_part}lsearch{/some/path/$domain/aliases}}
instead of
data = ${lookup{$local_part}lsearch{/some/path/$domain_data/aliases}}
for a virtual domain alias file.

  The basic strategy for dealing with this change is to use the result of a
  lookup in further processing instead of the original (remote provided)
  value.

  To ease upgrading there is a new main configuration option to temporarily
  downgrade taint errors to warnings, letting the old configuration work with
  the newer exim. To make use of this feature add
  .ifdef _OPT_MAIN_ALLOW_INSECURE_TAINTED_DATA
   allow_insecure_tainted_data = yes
  .endif
  to the exim configuration (e.g. to /etc/exim4/exim4.conf.localmacros)
  *before* upgrading to exim 4.93/4.94 and check the logfile for taint
  warnings. This is a temporary workaround which will stop working in 4.95.

---

See also:

https://bugs.debian.org/987133
https://bugs.debian.org/987924

Thanks,

Paul

Bug#987133: links to more info

[Paul Muster]

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

[Paul Muster]

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 configurations.


The feature requires "un-tainting" of all external information used in 
Exim's config for security reasons. Upstream unfortunately introduces 
this in a minor release and not in an Exim major release so that most of 
the users will get aware of it in the moment their mailserver stops working.


@the guys already working on the issue: Please add more information and 
get in touch with the Release Manager(s).


Thanks,

Paul

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

[Paul Muster]

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 config option 'detail_affix' with parameters 'prefix'
and 'suffix', defaulting to 'suffix' making sur
If 'detail_affix' is switched to 'prefix' the expected format of local
parts turns into  respec

2) Add documentation to the Wiki https://wiki2.dovecot.org/LMTP:

* detail_affix = suffix

3) Add description to the relevant default config files¹:

  # The separator that is expected between the :user and :detail
  # address parts introduced by the subaddress extension. This may
  # also be a sequence of characters (e.g. '--'). The current
  # implementation looks for the separator from the left of the
  # localpart and uses the first one encountered. The :user part is
  # left of the separator and the :detail part is right. This setting
  # is also used by Dovecot's LMTP service.
  #recipient_delimiter = +
+
+ # Define if :detail is a prefix or a suffix to the :user address part,
+ # e.g. left or right, when using subaddress extension.
+ # Defaults to 'suffix' making sure not to break existing setups using
+ #  format.
+ # Switch to 'prefix' if you use the  format
+ # described in RfC 5233.
+ #detail_affix = suffix

4) Changelog

   + now we _fully_ support IETF RfC 5233² (Sieve Subaddress Extension),
 see new config parameter 'detail_affix'.


What do you think?

BTW: Posting on Upstream's Mailing List dove...@dovecot.org:
https://dovecot.org/pipermail/dovecot/2019-May/115884.html

Thanks & greetings,

Paul


¹ On my Debian this is
/etc/dovecot/conf.d/20-lmtp.conf
and
/etc/dovecot/conf.d/90-sieve.conf

² https://tools.ietf.org/html/rfc5233

-- Package-specific info:

-- System Information:
Debian Release: 9.6
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500,
'proposed-updates')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-8-686-pae (SMP w/3 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages dovecot-lmtpd depends on:
ii  dovecot-core  1:2.2.27-3+deb9u4
ii  libc6 2.24-11+deb9u3
ii  ucf   3.0036

dovecot-lmtpd recommends no packages.

dovecot-lmtpd suggests no packages.

Versions of packages dovecot-lmtpd is related to:
ii  dovecot-core [dovecot-common]  1:2.2.27-3+deb9u4
pn  dovecot-dbg
pn  dovecot-dev
pn  dovecot-gssapi 
ii  dovecot-imapd  1:2.2.27-3+deb9u4
ii  dovecot-ldap   1:2.2.27-3+deb9u4
ii  dovecot-lmtpd  1:2.2.27-3+deb9u4
ii  dovecot-managesieved   1:2.2.27-3+deb9u4
pn  dovecot-mysql  
pn  dovecot-pgsql  
pn  dovecot-pop3d  
ii  dovecot-sieve  1:2.2.27-3+deb9u4
pn  dovecot-sqlite 

-- no debconf information

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

[Paul Muster]

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 config option 'detail_affix' with parameters 'prefix'
and 'suffix', defaulting to 'suffix' making sure not to break existing
setups using  respectively
:user:detail format.
If 'detail_affix' is switched to 'prefix' the expected format of local
parts turns into  respectively
:detail:user.

2) Add documentation to the Wiki https://wiki2.dovecot.org/LMTP:

* detail_affix = suffix

3) Add description to the relevant default config files¹:

  # The separator that is expected between the :user and :detail
  # address parts introduced by the subaddress extension. This may
  # also be a sequence of characters (e.g. '--'). The current
  # implementation looks for the separator from the left of the
  # localpart and uses the first one encountered. The :user part is
  # left of the separator and the :detail part is right. This setting
  # is also used by Dovecot's LMTP service.
  #recipient_delimiter = +
+
+ # Define if :detail is a prefix or a suffix to the :user address part,
+ # e.g. left or right, when using subaddress extension.
+ # Defaults to 'suffix' making sure not to break existing setups using
+ #  format.
+ # Switch to 'prefix' if you use the  format
+ # described in RfC 5233.
+ #detail_affix = suffix

4) Changelog

   + now we _fully_ support IETF RfC 5233² (Sieve Subaddress Extension),
 see new config parameter 'detail_affix'.


What do you think?

BTW: Posting on Upstream's Mailing List dove...@dovecot.org:
https://dovecot.org/pipermail/dovecot/2019-May/115884.html

Thanks & greetings,

Paul


¹ On my Debian this is
/etc/dovecot/conf.d/20-lmtp.conf
and
/etc/dovecot/conf.d/90-sieve.conf

² https://tools.ietf.org/html/rfc5233


-- Package-specific info:

-- System Information:
Debian Release: 9.6
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500,
'proposed-updates')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-8-686-pae (SMP w/3 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages dovecot-sieve depends on:
ii  dovecot-core  1:2.2.27-3+deb9u4
ii  libc6 2.24-11+deb9u3
ii  ucf   3.0036

dovecot-sieve recommends no packages.

dovecot-sieve suggests no packages.

Versions of packages dovecot-sieve is related to:
ii  dovecot-core [dovecot-common]  1:2.2.27-3+deb9u4
pn  dovecot-dbg
pn  dovecot-dev
pn  dovecot-gssapi 
ii  dovecot-imapd  1:2.2.27-3+deb9u4
ii  dovecot-ldap   1:2.2.27-3+deb9u4
ii  dovecot-lmtpd  1:2.2.27-3+deb9u4
ii  dovecot-managesieved   1:2.2.27-3+deb9u4
pn  dovecot-mysql  
pn  dovecot-pgsql  
pn  dovecot-pop3d  
ii  dovecot-sieve  1:2.2.27-3+deb9u4
pn  dovecot-sqlite 

-- no debconf information

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

[Paul Muster]

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

[Paul Muster]

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: OK
libdvd-pkg: Unpacking and configuring...
libdvd-pkg: Building the package... (it may take a while)
libdvd-pkg: Build log will be saved to
/usr/src/libdvd-pkg/libdvdcss2_1.3.99-1~local_i386.build
Current: = 
/cap_chown,cap_dac_override,cap_dac_read_search,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_linux_immutable,cap_net_bind_service,cap_net_broadcast,cap_net_admin,cap_net_raw,cap_ipc_lock,cap_ipc_owner,cap_sys_module,cap_sys_rawio,cap_sys_chroot,cap_sys_ptrace,cap_sys_pacct,cap_sys_admin,cap_sys_boot,cap_sys_nice,cap_sys_resource,cap_sys_time,cap_sys_tty_config,cap_mknod,cap_lease,cap_audit_write,cap_audit_control,cap_setfcap,cap_mac_override,cap_mac_admin,cap_syslog,35,36,37+ep
Bounding set =cap_chown,cap_dac_override,cap_fowner,35,36,37
Securebits: 024/0x14/5'b10100
 secure-noroot: no (unlocked)
 secure-no-suid-fixup: yes (unlocked)
 secure-keep-caps: yes (unlocked)
uid=0(root)
gid=0(root)
groups=0(root)
dpkg-buildpackage: unknown option or argument 
>/usr/src/libdvd-pkg/libdvdcss2_1.3.99-1~local_i386.build

Usage: dpkg-buildpackage [...]


   * What outcome did you expect instead?

a working .deb package.


Maybe the problem results in too low defined dependencies. Maybe a minimum
version of some dependency has to be added to the .deb.

Thanks & Greetings,

Paul


-- System Information:
Debian Release: 7.9
  APT prefers oldstable
  APT policy: (990, 'oldstable'), (500, 'oldstable-updates'), (500, 
'oldstable-proposed-updates')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-0.bpo.4-686-pae (SMP w/1 CPU core)
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 libdvd-pkg depends on:
ii  build-essential11.5
ii  debconf [debconf-2.0]  1.5.49
ii  debhelper  9.20120909
ii  dh-autoreconf  7
ii  wget   1.13.4-3+deb7u2

Versions of packages libdvd-pkg recommends:
ii  libcap2-bin  1:2.22-1.2

libdvd-pkg suggests no packages.

-- debconf information:
  libdvd-pkg/title_b-i:
  libdvd-pkg/title_u:
* libdvd-pkg/post-invoke_hook-install: true
  libdvd-pkg/upgrade:
* libdvd-pkg/first-install:
  libdvd-pkg/build: true
  libdvd-pkg/post-invoke_hook-remove: false

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

[Paul Muster]

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 >4 hours before your e-mail.

>  Said that, that doesn't mean I object to ejabberd supporting seperated
> files, but that's something for upstream to handle.

Fine. Yes, of course, this is an upstream topic. Therefore I asked:

>> Do you know if upstream already has an issue open for this (I
>> cannot find one)?


Greetings,

Paul

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

[Paul Muster]

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, but I guess you could just run
> 
> $ cat key.pem cert.pem chain.pem > ejabberd.pem
> 
> after doing whatever has to be done to maintain their certificates, no?

Yes, but this has to be done _every time_ the 'Let's Encrypt agent'
updates the cert - a use case which should happen without admin's
involvement.

Better wording:
It's especially _necessary_ to split key, cert and chain to different
files to be able to use Let's Encrypt's certificate renewal machanism.


Greetings,

Paul



smime.p7s
Description: S/MIME Cryptographic Signature

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

[Paul Muster]

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
> keyfile, not just the certfile, such that it then loads the key from
> there.

Is there any point one could assist you with on this bug?

Do you know if upstream already has an issue open for this (I cannot
find one)?

It's especially _necessary_ to split key, cert and chain to different
files to be able to use Let's Encrypt certificates.


Thanks & Greetings,

Paul

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

[Paul Muster]

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
> > http://rt.openssl.org/Ticket/Display.html?id=2860.
> > 
> > [openssl.org #2860] [PATCH 2/4] Fix infinite loop on s_client starttls
> > xmpp
> 
> I can confirm that this patch works.
> 
> Any chance of getting this fixed before Stretch is released?

any news on this?

Shouldn't be a big thing since patch is available and confirmed...


Thanks & Greetings,

Paul

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

[Paul Muster]

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 Jessie.


Thanks & Greetings,

Paul

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

[Paul Muster]

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 address the problem
> with slow-to-appear devices.  Ofcourse it is better to be able
> to boot from a degraded raid than to be able to boot from slow
> devices, esp. since the latter had a workaround.  So in this
> sense, serverfault solution will fix _this_ bug.

so, couldn't you patch the package to fix the problem for all people
that do not have "slow-to-appear devices"?


> But I also dislike doing work which is being thrown away by others,
> since this is a pure waste of time/energy, and time is a very scarse
> resource.  I don't want to do any work if I know this work will be
> thrown away, and here, debian-installer people did throw my work
> a) without a good reason and b) without actual rights for that.

Of course what you describe is extremely disappointing for you. Since I
don't know what exactly happened: There should be a decision committee
which listens to both sides and decides _for Debian_.

> So I stopped maintaining all software which is related to debian-installer,
> because now I know it is just a waste of time.  As simple as that, and
> there's nothing like dislike of someone in there, there's nothing
> personal.

It's not obvious to me why a bug in mdadm can't be fixed because there
is a conflict with the d-i maintainers. Why can d-i maintainers decide
about mdadm?

> In short, I don't maintain mdadm anymore, so there's no reason to
> ask me about it.

That would be very sad because it's a really important package.


Thanks & Greetings,

Paul

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

[Paul Muster]

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

[Paul Muster]

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 report would be better fitted in the upstream issue 
tracker:


https://github.com/fruux/sabre-dav/issues


Yes, but it's important to me to automatically get the information from 
Debian BTS when the feature is available _in my distribution_.


Could you please check if the issue still exists in version 2.2 as 
already

available from experimental?


Sorry, but: No, I can't. I tried, but after upgrading php-sabre-dav 
whole WebDAV of owncloud didn't work any more and complained about mixed 
versions.


I could help with, let's say, the second half of the problem: My working 
Icedove and SoGo-Connector. If you could provide an owncloud instance 
(with php-sabre-dav 2.2) and tell me URL, username and password, I'd add 
this as address book so you can see what happens on server side.



Greetings,

Paul


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

[Paul Muster]

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 (including such a Mailing List) with SoGo 
Connector
24.0.5 or 31.0.1 between Icedove 31.4.0 and Owncloud an error is shown in 
Icedove's error console:

---
Upload failure uploading list:
https://URL/remote.php/carddav/addressbooks/user/default/ID.vlf.
HTTP Status Code:415
  * card properties:
  0 prop: [xpconnect wrapped nsIProperty];  name: DisplayName; value: TEstlist
  1 prop: [xpconnect wrapped nsIProperty];  name: RecordKey; value: 57
  2 prop: [xpconnect wrapped nsIProperty];  name: PreferMailFormat; value: 0
  3 prop: [xpconnect wrapped nsIProperty];  name: DbRowID; value: 1
  4 prop: [xpconnect wrapped nsIProperty];  name: PopularityIndex; value: 0
  5 prop: [xpconnect wrapped nsIProperty];  name: LastName; value: TEstlist
  6 prop: [xpconnect wrapped nsIProperty];  name: LastModifiedDate; value: 0
  * done
---

On server side the following is logged:

---
ownCloud[6315]: {carddav} Sabre\DAV\Exception\UnsupportedMediaType: This 
collection can only support vcard objects.
---

If you need more information please tell me about!


Thanks  greetings,

Paul

-- System Information:
Debian Release: 7.8
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'testing-updates'), (500, 
'testing-proposed-updates'), (500, 'stable-updates'), (500, 
'proposed-updates'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages php-sabre-dav depends on:
ii  php-sabre-vobject  2.1.5-3
ii  php5-cli   5.4.36-0+deb7u3
ii  php5-common5.4.36-0+deb7u3

php-sabre-dav recommends no packages.

Versions of packages php-sabre-dav suggests:
pn  php5-apcu  none
ii  php5-curl  5.4.36-0+deb7u3

-- 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#779911: mailman: Upstream 2.1.19 available

[Paul Muster]

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
   improvements apart from DEFAULT_SUBSCRIBE_OR_INVITE?


Many new features which might be interesting for one or another user, 
e.g. this one:


| - Added real name display to the web roster.  (LP: #266754)

Many resolved bugs.


 Any security-related
   improvements?


At least one important privacy topic:

|  - Organization: headers are now unconditionally removed from posts to
|anonymous lists.


- upcoming debian jessie will very likely ship with mailman 1:2.1.18-1+b1; even
   if we package and upload 2.1.19 today.  2.1.19 will likely be available via
   unstable and testing and jessie+1.


You could try to use the privacy topic mentioned above to get 2.1.19 
into Jessie. If this doesn't work, 2.1.19 will hopefully appear in 
Jessie-Backports.



Greetings,

Paul


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#779911: mailman: Upstream 2.1.19 available

[Paul Muster]

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:

https://mail.python.org/pipermail/mailman-announce/2015-February/000202.html

I'd be really happy to use the new parameter DEFAULT_SUBSCRIBE_OR_INVITE


Greetings,

Paul


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

[Paul Muster]

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 prefix length, e.g. 32 for Comcast or 28 for Vodafone

Interface specific subnet would be configured like for 6to4 tunnel in 
the prefix statement:

prefix 0:0:000B:EEF::/64  {

(If additional parameters are required for different setups, maybe 
6rdIPv4MaskLength, these could be added in a second step.)



A complete config with two subnets would look like this:

interface eth0
{
AdvSendAdvert on;
prefix 0:0:000B:EEF::/64
{
AdvOnLink on;
AdvAutonomous on;
Base6rdInterface ppp0;
6rdPrefix 2001:55c;
6rdPrefixLength 28;
};
};

interface eth1
{
AdvSendAdvert on;
prefix 0:0:000D:EAD::/64
{
AdvOnLink on;
AdvAutonomous on;
Base6rdInterface ppp0;
6rdPrefix 2001:55c;
6rdPrefixLength 28;
};
};


-- System Information:
Debian Release: 7.8
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 
'proposed-updates')


Architecture: i386 (i686)

Kernel: Linux 3.16.0-0.bpo.4-686-pae (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 radvd depends on:
ii  adduser 3.113+nmu3
ii  libc6   2.13-38+deb7u7
pn  libdaemon0  none

radvd recommends no packages.

radvd suggests no packages.

-- 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#774416: RFP: openca-ocspd -- OCSP responder

[Paul Muster]

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: Massimiliano Pala madw...@openca.org
* URL: https://pki.openca.org/projects/ocspd/
* License: Apache-style


Thanks  Greetings,

Paul


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

[Paul Muster]

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 interface in
conf.d/main/000_localmacros instead of changing the above metioned file?

Thanks  greetings,

Paul


-- Package-specific info:
Exim version 4.80 #2 built 02-Jan-2013 19:40:19
Copyright (c) University of Cambridge, 1995 - 2012
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 
- 2012

Berkeley DB: Berkeley DB 5.1.29: (October 25, 2011)
Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS 
move_frozen_messages Content_Scanning DKIM Old_Demime
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm 
dbmjz dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql 
sqlite

Authenticators: cram_md5 cyrus_sasl dovecot 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: 7.6
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 
'proposed-updates')

Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/3 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 exim4-config depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.49

exim4-config recommends no packages.

exim4-config suggests no packages.

-- Configuration Files:
/etc/email-addresses changed [not included]
/etc/exim4/conf.d/auth/30_exim4-config_examples changed [not included]
/etc/exim4/conf.d/main/02_exim4-config_options changed [not included]
/etc/exim4/conf.d/router/200_exim4-config_primary changed [not included]
/etc/exim4/conf.d/router/900_exim4-config_local_user changed [not included]
/etc/exim4/conf.d/transport/30_exim4-config_maildrop_pipe changed [not 
included]
/etc/exim4/conf.d/transport/30_exim4-config_remote_smtp changed [not 
included]
/etc/exim4/passwd.client [Errno 13] Permission denied: 
u'/etc/exim4/passwd.client'


-- debconf information excluded


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

[Paul Muster]

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 placeholders/examples for Xen kernel config to /etc/default/grub



I would rather not change /etc/default/grub except when absolutely
necessary, because doing so causes configuration file prompts for
everyone.


Everyone or just people who have local modifications?


Sadly it winds up being significantly more people than I'd like because
the maintainer script code for handling /etc/default/grub has lots of
terrible stuff in it for historical reasons.  And of course editing
/etc/default/grub to add some kernel arguments is very common, even
among people who don't really know what they're doing thanks to various
web guides


That makes sense, thanks for explaining.


Well, do we really need to care about 'people who don't really know what 
they're doing'?



Perhaps this suggested change could be queued up to be applied when the
file needs to change for some other reason?


Or is there a possibility to deliver different files a) at first 
package install and b) at updates?



  (the number of bugs I've seen that were due to Unicode quotes
in /etc/default/grub thanks to copying and pasting from web pages would
probably startle you).


Almost nothing about this sort of thing surprises me any more ;-)


Some days ago I learnt a new (to me) English saw: If you make something 
idiot proof, someone will just make a better idiot. ;-)



Greetings,

Paul



smime.p7s
Description: S/MIME Cryptographic Signature

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

[Paul Muster]

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=
#GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT=xen-pciback.hide=(01:02.0)

# Xen mini-os boot parameters for all Xen boots
#GRUB_CMDLINE_XEN=
# Xen boot parameters for non-recovery Xen boots (in addition to
# GRUB_CMDLINE_XEN)
GRUB_CMDLINE_XEN_DEFAULT=dom0_mem=1024M dom0_max_vcpus=2 dom0_vcpus_pin

---

(after QA).


Thanks  Greetings,

Paul



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#744018: update for stable is on the way

[Paul Muster]

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 the changes to the security team so hopefully there will new
| package soon.
|
| The version you are looking for will be 3.6.1+dfsg-1~deb7u2 and will
| be on the Debian security mirrors.


Greetings,

Paul



smime.p7s
Description: S/MIME Cryptographic Signature

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

[Paul Muster]

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 update) owncloud still not appears
in the list Obsolete and Locally Created Packages.

# aptitude versions owncloud
Package owncloud:
p   4.0.4debian2-3.3testing-proposed-updates500 
i   4.0.8debian-1.6 100 

# cat /etc/apt/sources.list
deb http://debian:/debian/ wheezy main 
deb http://debian:/debian-security/ wheezy/updates main 
deb http://debian:/debian wheezy-updates main 
deb http://debian:/debian wheezy-proposed-updates main 

I got no information, that the installed package has been removed from
Wheezy.
Furthermore no information, that there will be no security updates for
owncloud!

Maybe this is only a problem in understanding on my side. But maybe there is
a conceptual problem which leads to security risks.


Thanks  kind regards,

Paul

-- Package-specific info:
Terminal: xterm
$DISPLAY not set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.6.8.2 compiled at Nov  5 2012 06:20:41
Compiler: g++ 4.7.2
Compiled against:
  apt version 4.12.0
  NCurses version 5.9
  libsigc++ version: 2.2.10
  Ept support enabled.
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 5.9.20110404
  cwidget version: 0.5.16
  Apt version: 4.12.0

aptitude linkage:
linux-gate.so.1 =  (0xb771)
libapt-pkg.so.4.12 = /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12 
(0xb71a7000)
libncursesw.so.5 = /lib/i386-linux-gnu/libncursesw.so.5 (0xb7174000)
libtinfo.so.5 = /lib/i386-linux-gnu/libtinfo.so.5 (0xb7154000)
libsigc-2.0.so.0 = /usr/lib/i386-linux-gnu/libsigc-2.0.so.0 
(0xb714e000)
libcwidget.so.3 = /usr/lib/libcwidget.so.3 (0xb704e000)
libept.so.1.aptpkg4.12 = /usr/lib/libept.so.1.aptpkg4.12 (0xb6fbb000)
libxapian.so.22 = /usr/lib/sse2/libxapian.so.22 (0xb6dd2000)
libz.so.1 = /lib/i386-linux-gnu/libz.so.1 (0xb6db9000)
libsqlite3.so.0 = /usr/lib/i386-linux-gnu/libsqlite3.so.0 (0xb6d07000)
libboost_iostreams.so.1.49.0 = /usr/lib/libboost_iostreams.so.1.49.0 
(0xb6cf)
libpthread.so.0 = /lib/i386-linux-gnu/i686/nosegneg/libpthread.so.0 
(0xb6cd6000)
libstdc++.so.6 = /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb6bea000)
libm.so.6 = /lib/i386-linux-gnu/i686/nosegneg/libm.so.6 (0xb6bc4000)
libgcc_s.so.1 = /lib/i386-linux-gnu/libgcc_s.so.1 (0xb6ba6000)
libc.so.6 = /lib/i386-linux-gnu/i686/nosegneg/libc.so.6 (0xb6a4)
libutil.so.1 = /lib/i386-linux-gnu/i686/nosegneg/libutil.so.1 
(0xb6a3c000)
libdl.so.2 = /lib/i386-linux-gnu/i686/nosegneg/libdl.so.2 (0xb6a38000)
libbz2.so.1.0 = /lib/i386-linux-gnu/libbz2.so.1.0 (0xb6a27000)
libuuid.so.1 = /lib/i386-linux-gnu/libuuid.so.1 (0xb6a2)
librt.so.1 = /lib/i386-linux-gnu/i686/nosegneg/librt.so.1 (0xb6a17000)
/lib/ld-linux.so.2 (0xb7711000)

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 
'testing-proposed-updates'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages aptitude depends on:
ii  aptitude-common   0.6.8.2-1
ii  libapt-pkg4.120.9.7.8
ii  libboost-iostreams1.49.0  1.49.0-3.2
ii  libc6 2.13-38
ii  libcwidget3   0.5.16-3.4
ii  libept1.4.12  1.0.9
ii  libgcc1   1:4.7.2-5
ii  libncursesw5  5.9-10
ii  libsigc++-2.0-0c2a2.2.10-0.2
ii  libsqlite3-0  3.7.13-1
ii  libstdc++64.7.2-5
ii  libtinfo5 5.9-10
ii  libxapian22   1.2.12-2
ii  zlib1g1:1.2.7.dfsg-13

Versions of packages aptitude recommends:
pn  apt-xapian-indexnone
pn  aptitude-doc-en | aptitude-doc  none
pn  libparse-debianchangelog-perl   none
ii  sensible-utils  0.0.7

Versions of packages aptitude suggests:
pn  debtags  none
ii  tasksel  3.14+nmu2

-- 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#705860: Acknowledgement (aptitude: removed (from release) package does not appear in list obsolete ... packages)

[Paul Muster]

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

# aptitude search '~i ~Atesting'

...
i A openssh-server  - secure shell (SSH) server
i A openssl - Secure Socket Layer (SSL) binary
i   owncloud- cloud storage for files, music,
i   owncloud-mysql  - meta-package providing MySQL
i   passwd  - change and administer password
i   pciutils- Linux PCI Utilities
...
(and 395 more packages from Testing)


Please tell me which additional information I should provide.


Greetings,

Paul


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#680458: fixed before Wheezy release?

[Paul Muster]

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 UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

[Paul Muster]

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 server_condition:
19:23:32 29767   $auth1 =
19:23:32 29767   $auth2 = paul
19:23:32 29767   $auth3 = password
19:23:32 29767   $1 =
19:23:32 29767   $2 = paul
19:23:32 29767   $3 = password
19:23:32 29767 expanding:
19:23:32 29767result:
19:23:32 29767 expanding: $auth2
19:23:32 29767result: paul
19:23:32 29767 expanding: $auth2
19:23:32 29767result: paul
19:23:32 29767 expanding: $auth3
19:23:32 29767result: password
19:23:32 29767 expanding:
user=uid=${quote_ldap_dn:$auth2},ou=Users,dc=BASIS
pass=${quote:$auth3} ldap://ldap/
19:23:32 29767result: user=uid=paul,ou=Users,dc=BASIS
pass=password ldap://ldap/
19:23:32 29767 LDAP parameters: user=uid=paul,ou=Users,dc=BASIS
pass=password size=0 time=0 connect=0 dereference=0 referrals=on
19:23:32 29767 perform_ldap_search: ldapauth URL = ldap://ldap/;
server=NULL port=0 sizelimit=0 timelimit=0 tcplimit=0
19:23:32 29767 after ldap_url_parse: host=ldap port=389
19:23:32 29767 ldap_initialize with URL ldap://ldap:389/
19:23:32 29767 initialized for LDAP (v3) server ldap:389
19:23:32 29767 LDAP_OPT_X_TLS_TRY set
19:23:32 29767 binding with user=uid=paul,ou=Users,dc=BASIS
password=password
19:23:32 29767 failed to bind the LDAP connection to server ldap:389 -
ldap_bind() returned -1
19:23:32 29767 failed to expand: ${if and{{ !eq{}{$auth2} }{
ldapauth{user=uid=${quote_ldap_dn:$auth2},ou=Users,dc=BASIS
pass=${quote:$auth3} ldap://ldap/} }} }
19:23:32 29767error message: failed to bind the LDAP connection to
server ldap:389 - ldap_bind() returned -1 inside and{...} condition
19:23:32 29767 expansion failed: failed to bind the LDAP connection to
server ldap:389 - ldap_bind() returned -1 inside and{...} condition
19:23:32 29767 expanding: $auth2
19:23:32 29767result: paul
19:23:32 29767 SMTP 435 Unable to authenticate at present
19:23:32 29767 tls_do_write(0xb8b33840, 39)
19:23:32 29767 gnutls_record_send(SSL, 0xb8b33840, 39)
19:23:32 29767 outbytes=39
19:23:32 29767 LOG: MAIN REJECT
19:23:32 29767   plain_server_ldap authenticator failed for client:
435 Unable to authenticate at present (set_id=paul): failed to bind the
LDAP connection to server ldap:389 - ldap_bind() returned -1 inside
and{...} condition
19:23:32 29767 Calling gnutls_record_recv(0xb8b55570, 0xb8cf01a8, 4096)


On the LDAP server no connection comes in.


Thanks  greetings,

Paul


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

[Paul Muster]

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
Address:192.168.1.1#53

Name:   ldap.domain.tld
Address: 192.168.1.8

\h:\w$ host ldap
ldap.domain.tld has address 192.168.1.8
\h:\w$


Thanks  greetings,

Paul


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

[Paul Muster]

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
 \h:\w$ nslookup ldap
 Server: 192.168.1.1
 Address:192.168.1.1#53
 
 Name:   ldap.domain.tld
 Address: 192.168.1.8
 
 \h:\w$ host ldap
 ldap.domain.tld has address 192.168.1.8
 \h:\w$

nslookup and host are successful while dig fails:

# su Debian-exim
\h:\w$ dig ldap

;  DiG 9.8.4-rpz2+rl005.12-P1  ldap
;; global options: +cmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 51789
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;ldap.  IN  A

;; AUTHORITY SECTION:
.   4051IN  SOA a.root-servers.net.
nstld.verisign-grs.com. 2013030701 1800 900 604800 86400

;; Query time: 0 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Thu Mar  7 21:01:44 2013
;; MSG SIZE  rcvd: 97

\h:\w$

Accordingly ist also works when putting LDAP server's FQDN in Exim
authenticator. But why?

# cat /etc/resolv.conf
domain domain.tld
search domain.tld
nameserver 192.168.1.1


Thanks  greetings,

Paul



smime.p7s
Description: S/MIME Cryptographic Signature

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

[Paul Muster]

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 to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

[Paul Muster]

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 would work:
 
 plain_server_ldap:
   driver = plaintext
   public_name = PLAIN
   server_prompts = :
   server_condition = ${if and{{ \
 !eq{}{$auth2} }{ \
 ldapauth{\
   user=uid=${quote_ldap_dn:$auth2},ou=Users,dc=BASE \
   pass=${quote:$auth3} \
   ldap://ldap/} }} }
   server_set_id = $auth2
 
 login_server_ldap:
   driver = plaintext
   public_name = LOGIN
   server_prompts = Username:: : Password::
   server_condition = ${if and{{ \
 !eq{}{$auth1} }{ \
 ldapauth{\
   user=uid=${quote_ldap_dn:$auth1},ou=Users,dc=BASE \
   pass=${quote:$auth2} \
   ldap://ldap/} }} }
   server_set_id = $auth1

... but not the final solution. Also with your authenticators (replacing
mine) it does not work. Exim's log message is the same as before (yes, I
restarted Exim) and the LDAP server still doesn't show any connection
from mail server.


Greetings,

Paul


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

[Paul Muster]

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: user=uid=paul,ou=Users,dc=BASIS pass=password
size=0 time=0 connect=0 dereference=0 referrals=on
17519 perform_ldap_search: ldapauth URL = ldap://ldap/; server=NULL
port=0 sizelimit=0 timelimit=0 tcplimit=0
17519 after ldap_url_parse: host=ldap port=389
17519 ldap_initialize with URL ldap://ldap:389/
17519 initialized for LDAP (v3) server ldap:389
17519 LDAP_OPT_X_TLS_TRY set
17519 binding with user=uid=paul,ou=Users,dc=BASIS password=password
17519 failed to bind the LDAP connection to server ldap:389 -
ldap_bind() returned -1
17519 expansion failed: failed to bind the LDAP connection to server
ldap:389 - ldap_bind() returned -1 inside and{...} condition
17519 SMTP 435 Unable to authenticate at present
17519 tls_do_write(0xb8ec8840, 39)
17519 gnutls_record_send(SSL, 0xb8ec8840, 39)
17519 outbytes=39
17519 LOG: MAIN REJECT
17519   plain_server_ldap authenticator failed for client: 435 Unable
to authenticate at present (set_id=paul): failed to bind the LDAP
connection to server ldap:389 - ldap_bind() returned -1 inside
and{...} condition
17519 Calling gnutls_record_recv(0xb8eea560, 0xb90851a0, 4096)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

[Paul Muster]

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 (IP=0.0.0.0:389)
Mar  4 18:28:06 ldap slapd[9942]: conn=5292 op=0 BIND
dn=uid=paul,ou=Users,dc=BASIS method=128
Mar  4 18:28:06 ldap slapd[9942]: conn=5292 op=0 RESULT tag=97 err=49 text=
Mar  4 18:28:06 ldap slapd[9942]: conn=5292 op=1 UNBIND
Mar  4 18:28:06 ldap slapd[9942]: conn=5292 fd=70 closed

Exim version 4.80 uid=0 gid=0 pid=14864 D=fbb95cfd
Berkeley DB: Berkeley DB 5.1.29: (October 25, 2011)
Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS
move_frozen_messages Content_Scanning DKIM Old_Demime
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm
dbmjz dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql
sqlite
Authenticators: cram_md5 cyrus_sasl dovecot 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
Compiler: GCC [4.7.2]
Library version: GnuTLS: Compile: 2.12.20
 Runtime: 2.12.20
Library version: Cyrus SASL: Compile: 2.1.25
 Runtime: 2.1.25 [Cyrus SASL]
Library version: PCRE: Compile: 8.31
   Runtime: 8.30 2012-02-04
Total 19 lookups
Library version: MySQL: Compile: 5.5.28 [(Debian)]
Runtime: 5.5.28
Library version: SQLite: Compile: 3.7.15.1
 Runtime: 3.7.13
WHITELIST_D_MACROS: OUTGOING
TRUSTED_CONFIG_LIST: /etc/exim4/trusted_configs
changed uid/gid: -C, -D, -be or -bf forces real uid
  uid=0 gid=0 pid=14864
  auxiliary group list: 0
seeking password data for user uucp: cache not available
getpwnam() succeeded uid=10 gid=10
changed uid/gid: calling tls_validate_require_cipher
  uid=104 gid=106 pid=14865
  auxiliary group list: 0
tls_validate_require_cipher child 14865 ended: status=0x0
configuration file is /var/lib/exim4/config.autogenerated
log selectors = 0ffc 00612001
trusted user
admin user
seeking password data for user mail: cache not available
getpwnam() succeeded uid=8 gid=8
user name root extracted from gecos field root
originator: uid=0 gid=0 login=root name=root
sender address = r...@mailname.tld
LDAP parameters: user=uid=paul,ou=Users,dc=BASIS pass=geheim size=0
time=0 connect=0 dereference=0 referrals=on
perform_ldap_search: ldapauth URL = ldap://ldap/; server=NULL port=0
sizelimit=0 timelimit=0 tcplimit=0
after ldap_url_parse: host=ldap port=389
ldap_initialize with URL ldap://ldap:389/
initialized for LDAP (v3) server ldap:389
LDAP_OPT_X_TLS_TRY set
binding with user=uid=paul,ou=Users,dc=BASIS password=geheim
Invalid credentials: ldapauth returns FAIL

search_tidyup called
unbind LDAP connection to ldap:389
 Exim pid=14864 terminating with rc=0 


* with existing user and right password:

Mar  4 18:29:48 ldap slapd[9942]: conn=5293 fd=70 ACCEPT from
IP=192.168.1.4:37313 (IP=0.0.0.0:389)
Mar  4 18:29:48 ldap slapd[9942]: conn=5293 op=0 BIND
dn=uid=paul,ou=Users,dc=BASIS method=128
Mar  4 18:29:48 ldap slapd[9942]: conn=5293 op=0 BIND
dn=uid=paul,ou=Users,dc=BASIS mech=SIMPLE ssf=0
Mar  4 18:29:48 ldap slapd[9942]: conn=5293 op=0 RESULT tag=97 err=0 text=
Mar  4 18:29:48 ldap slapd[9942]: conn=5293 op=1 UNBIND

Exim version 4.80 uid=0 gid=0 pid=14867 D=fbb95cfd
Berkeley DB: Berkeley DB 5.1.29: (October 25, 2011)
Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS
move_frozen_messages Content_Scanning DKIM Old_Demime
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm
dbmjz dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql
sqlite
Authenticators: cram_md5 cyrus_sasl dovecot 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
Compiler: GCC [4.7.2]
Library version: GnuTLS: Compile: 2.12.20
 Runtime: 2.12.20
Library version: Cyrus SASL: Compile: 2.1.25
 Runtime: 2.1.25 [Cyrus SASL]
Library version: PCRE: Compile: 8.31
   Runtime: 8.30 2012-02-04
Total 19 lookups
Library version: MySQL: Compile: 5.5.28 [(Debian)]
Runtime: 5.5.28
Library version: SQLite: Compile: 3.7.15.1
 Runtime: 3.7.13
WHITELIST_D_MACROS: OUTGOING
TRUSTED_CONFIG_LIST: /etc/exim4/trusted_configs
changed uid/gid: -C, -D, -be or -bf forces real uid
  uid=0 gid=0 pid=14867
  auxiliary group list: 0
seeking password data for user uucp: cache not available
getpwnam() succeeded uid=10 gid=10
changed uid/gid: calling tls_validate_require_cipher
  uid=104 gid=106 pid=14870
  auxiliary group list: 0

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

[Paul Muster]

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 environment:

-- /etc/exim4/conf.d/auth/40_LDAP-auth
plain_server:
  driver = plaintext
  public_name = PLAIN
  server_prompts = Username:: : Password::
  server_condition = ${if and{{ \
!eq{}{$auth2} }{ \
ldapauth{\
  user=uid=${quote_ldap_dn:$auth2},ou=Users,dc=BASE \
  pass=${quote:$auth3} \
  ldap://ldap/} }} }

ldap is my LDAP server and 'telnet ldap 389' on mailserver (192.168.1.4) 
shows that *there
is no packet filter between*:
Mar  2 21:20:03 ldap slapd[9942]: conn=1113 fd=43 ACCEPT from
IP=192.168.1.4:60401 (IP=0.0.0.0:389)
Mar  2 21:21:25 ldap slapd[9942]: conn=1113 fd=43 closed (connection lost)

*When delivering to Exim with SMTP auth* I get this in Exim's logs:

2013-03-02 20:52:49 plain_server authenticator failed for client:
435 Unable to authenticate at present (set_id=paul): failed to bind the LDAP 
connection
to server ldap:389 - ldap_bind() returned -1 inside and{...} condition

*LDAP server does not see any incoming connection from mailserver.*

I tried removing and{{ clause, that changed Exim's log entry:

2013-02-20 23:10:00 plain_server authenticator failed for client: 435
Unable to authenticate at present (set_id=paul):
failed to bind the LDAP connection to server ldap:389 - ldap_bind()
returned -1

Also adding a return code in server_condition...
   ldap://ldap/} }} {yes} {no} } 
... did not help.


In the meantime I'm of the opinion that there must be something defect in
Exim's LDAP functionality...


Thanks  kind regards,

Paul


-- Package-specific info:
Exim version 4.80 #2 built 02-Jan-2013 19:40:19
Copyright (c) University of Cambridge, 1995 - 2012
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2012
Berkeley DB: Berkeley DB 5.1.29: (October 25, 2011)
Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS 
move_frozen_messages Content_Scanning DKIM Old_Demime
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite
Authenticators: cram_md5 cyrus_sasl dovecot 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: 7.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 
'testing-proposed-updates')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/3 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 exim4-daemon-heavy depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  exim4-base 4.80-7
ii  libc6  2.13-38
ii  libdb5.1   5.1.29-5
ii  libgnutls262.12.20-4
ii  libldap-2.4-2  2.4.31-1
ii  libmysqlclient18   5.5.28+dfsg-1
ii  libpam0g   1.1.3-7.1
ii  libpcre3   1:8.30-5
ii  libperl5.145.14.2-18
ii  libpq5 9.1.8-1
ii  libsasl2-2 2.1.25.dfsg1-6
ii  libsqlite3-0   3.7.13-1

exim4-daemon-heavy recommends no packages.

exim4-daemon-heavy suggests no packages.

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#614801: USB 3.0 still not working in Wheezy

[Paul Muster]

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 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

in dmesg:
[8.496083] xhci_hcd :00:02.0: Timeout while waiting for a slot
[8.498708] hub 1-0:1.0: couldn't allocate port 2 usb_device


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#614801: USB 3.0 still not working in Wheezy

[Paul Muster]

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 Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse

dmesg:

[3.484101] usb 1-2: new high-speed USB device number 2 using xhci_hcd
[3.503719] usb 1-2: New USB device found, idVendor=05e3, idProduct=0608
[3.503724] usb 1-2: New USB device strings: Mfr=0, Product=1,
SerialNumber=0
[3.503728] usb 1-2: Product: USB2.0 Hub
[3.504641] hub 1-2:1.0: USB hub found
[3.505219] hub 1-2:1.0: 4 ports detected
[3.780559] usb 1-2.2: new low-speed USB device number 3 using xhci_hcd
[3.804800] usb 1-2.2: New USB device found, idVendor=046d,
idProduct=c03d
[3.804806] usb 1-2.2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[3.804810] usb 1-2.2: Product: USB-PS/2 Optical Mouse
[3.804814] usb 1-2.2: Manufacturer: Logitech
[3.804944] usb 1-2.2: ep 0x81 - rounding interval to 64 microframes,
ep desc says 80 microframes


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#614801: USB 3.0 still not working in Wheezy

[Paul Muster]

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])
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at df00 (64-bit, non-prefetchable) [size=8K]
Capabilities: [50] Power Management version 3
Capabilities: [70] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [90] MSI-X: Enable+ Count=8 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number ff-ff-ff-ff-ff-ff-ff-ff
Capabilities: [150] Latency Tolerance Reporting
Kernel driver in use: xhci_hcd

# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

leads to this in dmesg:

[8.724056] xhci_hcd :00:02.0: Timeout while waiting for a slot
[8.726695] hub 1-0:1.0: couldn't allocate port 2 usb_device

and USB devices are not detected.


Please tell me if you need more info or if I should test something!


Thanks,

Paul


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#680458: squirrelmail: Q-encoded header issue

[Paul Muster]

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 snapshot packages located on our downloads page. Especially
if you use the Mail Fetch plugin and want to upgrade to PHP 5.4, you
should download one of our snapshot packages.

UPDATE:If you are running SquirrelMail under PHP 5.4, please help test and
refine the patches found here [
http://sourceforge.net/tracker/?func=detailatid=100311aid=3491925group_id=311
]. There is one patch for each of the two SquirrelMail SVN snapshot
versions available on our downloads page.

---

Thanks,

Paul


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

[Paul Muster]

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:]-]*)+ 
\((/[._[:alnum:]-]*)+\)$

to

^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rpc\.mountd\[[0-9]+\]: authenticated 
(un|)mount request from [._[:alnum:]-]+:[0-9]+ for (/[._[:alnum:]-]*)+ 
\((/[._[:alnum:]-]*)+\)$

for compatibility with Debian Wheezy.

Thanks

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 
'testing-proposed-updates')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- Configuration Files:
/etc/logcheck/ignore.d.server/dovecot changed [not included]
/etc/logcheck/ignore.d.server/nfs changed [not included]

-- 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#688339: Acknowledgement (logcheck-database: dhcp: match IPv6-aware records, too)

[Paul Muster]

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

[Paul Muster]

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 lines like

Sep 21 20:38:30 dns dhcpd: if w3.mydomain.tld IN A rrset doesn't exist and 
w3.mydomain.tld IN  rrset doesn't exist delete w3.mydomain.tld IN TXT 
1221121212ababbba: success.

Maybe _someone_ could merge with existing IPv4-only regex...

^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd: if [._[:alnum:]-]+ IN A rrset doesn't 
exist delete [._[:alnum:]-]+ IN TXT [[:alnum:]]+: success\.$

...but _I_ don't know, how to do this.


-- System Information:
Debian Release: 6.0.5
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 
'proposed-updates')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-xen-686 (SMP w/1 CPU core)
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 logcheck depends on:
ii  adduser  3.112+nmu2  add and remove users and groups
ii  cron 3.0pl1-116  process scheduling daemon
ii  exim4-daemon-light [mail 4.72-6+squeeze2 lightweight Exim MTA (v4) daemon
ii  lockfile-progs   0.1.15  Programs for locking and unlocking
ii  logtail  1.3.13  Print log file lines that have not
ii  mime-construct   1.11construct/send MIME messages from 
ii  rsyslog [system-log-daem 4.6.4-2 enhanced multi-threaded syslogd

Versions of packages logcheck recommends:
ii  logcheck-database 1.3.15 database of system log rules for t

Versions of packages logcheck suggests:
ii  syslog-summary1.14-2 summarize the contents of a syslog

-- 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#687990: logcheck-database: bind: updating zone...PTR and signer...approved

[Paul Muster]

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 '[-._[:alnum:]]+/IN':
(adding an RR|deleting rrset) at '[._[:alnum:]-]+' A$

to

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

(please note (A|PTR) instead of A only at the end of the line)

(2) please add

^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ named\[[[:digit:]]+\]: client
[.:[:xdigit:]]+#[[:digit:]]+: signer [-._[:alnum:]]+ approved$


-- System Information:
Debian Release: 6.0.5
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500,
'proposed-updates')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-xen-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 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#687990: logcheck-database: bind: updating zone...PTR and signer...approved

[Paul Muster]

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:]]+\]: client
 [.:[:xdigit:]]+#[[:digit:]]+: updating zone '[-._[:alnum:]]+/IN':
 (adding an RR|deleting rrset|deleting an RR) at '[._[:alnum:]-]+' (A|PTR|TXT)$


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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]

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
  Description : a shared library which is required by ldap_abook_backend 
and ldap_prefs_backend plugins for Squirrelmail

LDAP common plugin is a shared library which is required by
ldap_abook_backend and ldap_prefs_backend plugins. LDAP common
is helper plugin which does not provide any feature for
SquirrelMail itself, rather it is like a shared library for
the LDAP Address Book and the LDAP Preferences plugin.

This plugin requires at least SquirrelMail version 1.4.3.

I.e. Depends: squirrelmail


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)



-- 
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]

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
  Description : LDAP abook backend plugin for Squirrelmail makes it 
possible to store Personal Address Books in LDAP

LDAP abook backend is a generic solution to store SquirrelMail Personal
Address Book entries in an LDAP directory. It can use any LDAP class,
SquirrelMail attributes can be freely mapped to LDAP attributes.
Address Book entries can be stored directly under the user's object, or a
dedicated container object can be used. The plugin is capable of creating
this container object automatically when it is required.

Depends: squirrelmail-ldap-common


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

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

[Paul Muster]

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
  Description : LDAP prefs backend plugin makes it possible to store 
SquirrelMail user preferences in your LDAP directory

LDAP prefs backend plugin makes it possible to store SquirrelMail user
preferences in your LDAP directory, instead of the file or database backends
that are shipped with SquirrelMail.

Depends: squirrelmail-ldap-common

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

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]

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]

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 of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

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

[Paul Muster]

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 exited with code 1.
3301 Issuing autochanger loaded drive 0 command.
3991 Bad autochanger loaded drive 0 command: ERR=Child exited with code 1.
3304 Issuing autochanger load slot 2, drive 0 command.
Server.2007-10-23_19.15.00 Fatal error:
3992 Bad autochanger load slot 2, drive 0: ERR=Child exited with code 1.
Server.2007-10-23_19.15.00 Fatal error: job.c:1617 Bad response to Append
Data command. Wanted 3000 OK data, got 3903 Error append data


Thanks  kind regards,

Paul

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages bacula-sd depends on:
ii  bacula-common  1.38.11-8 Network backup, recovery and verif
ii  libacl12.2.41-1  Access control list shared library
ii  libc6  2.3.6.ds1-13etch2 GNU C Library: Shared libraries
ii  libgcc11:4.1.1-21GCC support library
ii  libssl0.9.80.9.8c-4etch1 SSL shared libraries
ii  libstdc++6 4.1.1-21  The GNU Standard C++ Library v3
ii  libwrap0   7.6.dbs-13Wietse Venema's TCP wrappers libra
ii  mtx1.2.17rel-2   controls tape autochangers
ii  python 2.4.4-2   An interactive high-level object-o
ii  python2.4  2.4.4-3   An interactive high-level object-o
ii  zlib1g 1:1.2.3-13compression library - runtime

Versions of packages bacula-sd recommends:
ii  bacula-sd-sqlite3 [bacula-sd- 1.38.11-8  Network backup, recovery and verif
pn  mt-st none (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#440719: mount: happens in Etch, too

[Paul Muster]

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 20:38:19 2007: swapon: /dev/volg1/logv4: Device or resource busy

but is has actived swap indeed

$ dmesg | grep swap
Adding 1048568k swap on /dev/volg1/logv4.  Priority:-1 extents:1 across:1048568k


Greetings,

Paul


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages mount depends on:
ii  libblkid 1.39+1.40-WIP-2006.11.14+dfsg-2 block device id library
ii  libc62.3.6.ds1-13GNU C Library: Shared libraries
ii  libuuid1 1.39+1.40-WIP-2006.11.14+dfsg-2 universally unique id library

mount recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#440719: mount: happens in Etch, too

[Paul Muster]

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 2007: swapon: /dev/volg1/logv4: Device or resource busy

but is has actived swap indeed

$ dmesg | grep swap
Adding 1048568k swap on /dev/volg1/logv4.  Priority:-1 extents:1 across:1048568


Greetings,

Paul

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (900, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages mount depends on:
ii  libblkid 1.39+1.40-WIP-2006.11.14+dfsg-2 block device id library
ii  libc62.3.6.ds1-13etch2   GNU C Library: Shared libraries
ii  libuuid1 1.39+1.40-WIP-2006.11.14+dfsg-2 universally unique id library

mount recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

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

[Paul Muster]

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 Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (900, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages bacula-sd depends on:
ii  bacula-common   1.38.11-8Network backup, recovery and verif
ii  libacl1 2.2.41-1 Access control list shared library
ii  libc6   2.3.6.ds1-13 GNU C Library: Shared libraries
ii  libgcc1 1:4.1.1-21   GCC support library
ii  libssl0.9.8 0.9.8c-4 SSL shared libraries
ii  libstdc++6  4.1.1-21 The GNU Standard C++ Library v3
ii  libwrap07.6.dbs-13   Wietse Venema's TCP wrappers libra
ii  mtx 1.2.17rel-2  controls tape autochangers
ii  python  2.4.4-2  An interactive high-level object-o
ii  python2.4   2.4.4-3  An interactive high-level object-o
ii  zlib1g  1:1.2.3-13   compression library - runtime

Versions of packages bacula-sd recommends:
ii  bacula-sd-mysql [bacula-sd-to 1.38.11-8  Network backup, recovery and verif
ii  mt-st 0.9b-3 Linux SCSI tape driver aware magne

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

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

[Paul Muster]

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 2007-08-02 10:18 .
drwxr-xr-x 112 root   root   8192 2007-08-02 10:16 ..
-rw-r-   1 root   root   1097 2007-08-02 10:09 bacula-fd.conf
-rw-r--r--   1 root   root   1096 2007-08-02 10:16 bacula-fd.conf.dist
-rw-r-   1 bacula bacula 2370 2007-08-02 10:09 bacula-sd.conf
-rw-r--r--   1 root   root   5379 2007-08-02 10:16 bacula-sd.conf.dist
-rw-r-   1 root   bacula  226 2007-08-02 10:09 bconsole.conf
drwxr-xr-x   2 root   root   4096 2007-08-02 10:18 scripts



-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (900, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

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

[Paul Muster]

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 channel,or move
 the position of a channel.

 This is only true for VDR  1.3.13.

 From HISTORY 1.3.13:
 Automatic channel modifications will be saved every 10 minutes if no
 recording is currently active.

My vdr does not write the channel list it has in memory to disk, neither
every 10 minutes nor on a restart.

 I think Pauls problem is the old channels.conf entry without NID and TID:

 EinsPlus:184500:I999B7C34D12M16T8G4Y0:T:27500:97:98:516:0:6:0:0:0

 The timers.conf entry

 1:T-8468-12289-6:2007-02-22:2058:2155:50:99:nix wie raus ...:

 is for a channel like

 EinsPlus:184500:I999B7C34D12M16T8G4Y0:T:27500:97:98:516:0:6:8468:12289:0

Where can I get the valid (O)NID and the TID for a channel?

I tried replacing the rear :0:0:0 with :8468:13058:0 for all
lines/channels. This did not have not the expected effect, but two others:
1. For the changed channels EPG does not work any more. 2. vdr (with
UpdateChannels = 5 in setup.conf) found all the changed channels as new.
With the new channels EPG works, but switching to them does not show a
picture.

 VDR should automatically rewrite the changed entry to the channels.conf.

Unfortunately mine does not. So I cannot show the newly created lines for
the channels vdr found itself as mentioned above.


Thanks  best wishes


Paul



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

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

[Paul Muster]

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

/etc/init.d/vdr restart

the known error

| Feb 27 20:38:18 vdr1 vdr: [3244] ERROR: channel T-8468-514-514 not defined
| Feb 27 20:38:18 vdr1 vdr: [3244] ERROR: error in
/var/lib/vdr/timers.conf, line 1

occured again.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

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

[Paul Muster]

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 this entry from the timers.conf and add the
 timer again?

Then it is again not possible to restart vdr until the line ist removed
from timers.conf.

(Ich gebe zu, die Frage nicht wirklich verstanden zu haben. Evtl. kann
jemand mal [EMAIL PROTECTED] in de.comp.tv+video
anschauen.)


Greetings

Paul



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

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

[Paul Muster]

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:

EinsPlus:184500:I999B7C34D12M16T8G4Y0:T:27500:97:98:516:0:6:0:0:0

timers.conf looks:

1:T-8468-12289-6:2007-02-22:2058:2155:50:99:nix wie raus ...:

vdr does not start until removing the timer from timers.conf.

Maybe (if it's really a bug, not only a mistake on my part) this could be
fixed for the release of sarge?

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages vdr depends on:
ii  adduser 3.102Add and remove users and groups
ii  debconf [debconf-2.0]   1.5.11   Debian configuration
management sy
ii  libc6   2.3.6.ds1-10 GNU C Library: Shared libraries
ii  libcap1 1:1.10-14support for getting/setting
POSIX.
ii  libgcc1 1:4.1.1-21   GCC support library
ii  libjpeg62   6b-13The Independent JPEG Group's
JPEG
ii  libstdc++6  4.1.1-21 The GNU Standard C++ Library v3
ii  makedev 2.3.1-83 creates device files in /dev
ii  psmisc  22.3-1   Utilities that use the proc
filesy

Versions of packages vdr recommends:
ii  lirc  0.8.0-9Linux Infra-red Remote
Control sup

-- debconf information excluded




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

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

[Paul Muster]

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:

https://lists.berlios.de/pipermail/capisuite-users/2005-March/001380.html


-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.27
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages capisuite depends on:
ii  exim4-daemon-heavy [m 4.50-8 exim MTA (v4) daemon with extended
ii  gs8.01-5 Transitional package
ii  gs-gpl [gs]   8.01-5 The GPL Ghostscript PostScript int
ii  libc6 2.3.2.ds1-22   GNU C Library: Shared libraries an
ii  libcapi20-2   1:3.6.2005-01-03-5 libraries for CAPI support
ii  libgcc1   1:3.4.3-13 GCC support library
ii  libstdc++51:3.3.5-13 The GNU Standard C++ Library v3
ii  libtiff-tools 3.7.2-3TIFF manipulation and conversion t
ii  python2.3.5-2An interactive high-level object-o
ii  python2.3 2.3.5-3sarge1  An interactive high-level object-o
ii  sfftobmp  3.0-4  SFF (Structed Fax File) Converter
ii  sox   12.17.7-2  A universal sound sample translato

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

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

[Paul Muster]

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 the config file read by the scripts; see there for
options and
 # descriptions
@@ -170,6 +171,7 @@
msg['Subject']=mail_subject
msg['From']=mail_from
msg['To']=mail_to
+   msg['Date']=time.ctime()

msg.preamble = 'This is a Multipart-MIME-message. Please use a
capable mailer.\n'
msg.epilogue = '' # To guarantee the message ends with a newline
@@ -267,6 +269,7 @@
msg['Subject'] = mail_subject
msg['From'] = mail_from
msg['To'] = mail_to
+   msg['Date']=time.ctime()

try:
server = smtplib.SMTP('localhost')


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]