Package: courier-mlm
Version: 0.73.1-1.6
Severity: normal
Dear Maintainer,
I've encountered some bugs in couriermlm, when a list is setup the
option 'NOBOZOS=1' is set by default, which should bounce bad ctl
command messages sent to user-list@domain instead of
user-list-command@domain.
What's su
Inspection of mkdhaparams, reveals to me that it's just a shell script and
that the "bug" is that the environment variable in the shell script is
actually:
$DH_BITS
because the script sets:
BITS="$DH_BITS"
if test "@ssllib@" = "openssl"
then
if test "$BITS" = ""
then
BITS=76
Package: courier-ssl
Version: 0.73.1-1.6
Severity: normal
Dear Maintainer,
according to the mkdhparams man page:
ENVIRONMENT VARIABLES
BITS Customize the DH parameter bit size. The
default value depends on whether this script uses OpenSSL or
GnuTLS libraries. For OpenSSL the defau
After some further investigation, I think what's going on is this:
the "sticky bit" based locking applies to maildrop, however, it does
not seem to apply to mail delivered by the courierlocal transport
module. The courier online documentation:
http://www.courier-mta.org/local.html
Output modu
Package: courier-maildrop
Version: 0.73.1-1.6
Severity: normal
Dear Maintainer,
According the courier documentation (man maildrop, amongst other sources):
"If in delivery mode the user's home directory has the sticky bit set,
maildrop immediately terminates with an exit code of EX_TEMPFAIL,
with
Hello Maintainers, bug-subscribers,
I also experience this bug with:
Package: linux-image-3.16.0-4-amd64
Version: 3.16.7-ckt20-1+deb8u4
I've been using the backports kernel:
Package: linux-image-4.3.0-0.bpo.1-amd64
Version: 4.3.5-1~bpo8+1
without any btrfs-related errors occurring.
Note, t
I goofed up the install of the upstream package, but the after moving
some files around by hand, it would appear that both the database
connection and sql method objects from ZMySQLDA and run queriess.
So I think one can conclusively say the problem is that debian
packages zope-mysqlda without pr
Upon further investigation, I believe zope-mysqlda depends on another
zope product, ZSQLMethods, which contains the Shared.DC.ZRDB module
which is no longer part of the core zope-2.13 distribution.
https://github.com/zopefoundation/Products.ZSQLMethods
I'm trying to figure out how to install thi
Package: zope-common
Version: 0.5.54
Severity: minor
when you create a new zope instance with dzhandle and then immediatly run
dzhandle list-instances
this instance will show up as 'purged' because of this test: (lines 1897-1902)
if os.path.exists(zope_conf) and \
filter(lamb
Package: zope-mysqlda
Version: 3.1.1-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
I've been trying to migrate an existing zope instance running using
zope-2.13 to a new server using the debian zope packages. The old
instance uses the ZMySQLDA product provide by the zope-m
10 matches
Mail list logo
