So what's the state of the fix for the earlier affected releases, esp.
LTS servers?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/777855
Title:
resolver failures without even
Am 02.05.2012 18:46, schrieb Ben Bird:
I have the same scenario of IPv6 + bind9 + dnssec.
b-coleman's suspicion that this is related to debian bug# 578052 seems
plausible. I upgraded my affected machine to Precise (12.04), and the
problem has stopped.
The problem isn't with the init
Public bug reported:
This happened during an upgrade with sudo do-release-upgrade from
natty (11.04) to oneiric (11.10) which is supposed to be an intermediate
step on the way to 12.04.
Note that the questions asked by apport about the samba setup (which
clients fail to connect, what my setup
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/998766
Title:
package samba 2:3.5.8~dfsg-1ubuntu2.5 failed to install/upgrade:
ErrorMessage: Unterprozess neues post-removal-Skript
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1026261
Title:
[regression] mail stalls; postfix chroot setup nests /etc/ssl/certs to
deep
To manage notifications about this bug
Public bug reported:
Since the (overdue) update from maverick to natty, my Postfix no longer
recognizes the certificates.
Apparently the reason is that the smtp_tls_CApath, which is set to
/etc/ssl/certs, is improperly copied into the chroot area, namely
to
** Attachment added: result from running sh -x /etc/init.d/postfix start
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1026261/+attachment/3227425/+files/postfix-log.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Attachment added: result from find /var/spool/postfix/etc to show actual
directory layout
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1026261/+attachment/3227428/+files/var-spool-postfix-etc.txt
--
You received this bug notification because you are a member of Ubuntu
Server
Fix confirmed for precise; not tested on the others.
Can this be fixed for natty please?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1026261
Title:
[regression] mail stalls;
ping - this still hurts on natty. Please fix!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/718188
Title:
dovecot won't be restarted after failure
To manage notifications about
Public bug reported:
Binary package hint: postfix
/usr/share/doc/postfix/RELEASE_NOTES.gz references a RELEASE_NOTES-2.6
documentation file that isn't installed, neither as part of postfix, nor
postfix-doc. Please add this file.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: postfix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/777033
Title:
installation lacks RELEASE_NOTES-2.6 documentation file
--
Ubuntu-server-bugs mailing list
Public bug reported:
Binary package hint: postfix
I've been bitten by a Postfix SMTP/LMTP implementation defect that has
been fixed in one of the upstream patch-level releases 2.7.X.
Basically Postfix sends XFORWARD PORT=unknown ... to amavsid via LMTP.
Amavisd later returns the same attribute
** Summary changed:
- [fixed upstream] Postfix smtp does not skip unknown XFORWARD attributes,
causing SMTP syntax errors
+ [fixed upstream, regression] Postfix smtp does not skip unknown XFORWARD
attributes, causing SMTP syntax errors
** Tags added: regression
** Tags added:
Public bug reported:
Binary package hint: postfix
I have a particular Postfix relay configuration where I need to forward
SMTP to an SSH tunnel, and configure a relayhost_maps (sender_dependent
actually) as [localhost]:12345.
This worked in maverick, but fails in natty. The new Postfix 2.8
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/777868
Title:
Postfix smtp can no longer resolve localhost - regression from
maverick.
--
Ubuntu-server-bugs mailing list
No improvement in 2.8.2-1ubuntu2 from -updates, and with a fundamentally
different cause, so removing duplicate mark.
** This bug is no longer a duplicate of bug 764096
DNS hostname lookups fail in chroot after natty upgrade
--
You received this bug notification because you are a member of
Additional remark: Bug #764096 is about an incomplete chroot setup caused by
the start script.
To differentially diagnose this, I had ruled a broken chroot setup out in my
testing by forcing smtp(8) outside the chroot per master.cf.
This bug is fundamentally a resolver bug, exhibited through a
patches, a backport is less tested, thus
more dangerous, than just reviewing the point-release patch.
Anyways, I don't care how Ubuntu will choose to fix this regression, but
I do care that it happens soon.
--
Matthias Andree
--
You received this bug notification because you are a member
Guys, can we please stop distracting with lame excuses for not going for
bugfix releases, or backports of another feature release?
This particular regression was already fixed by the upstream maintainers
in a particular bugfix-only release series of Postfix (2.7.1 is 2.7.0 +
fixes), so any any
make that 2.7.4. Admittedly even 2.7.1 was past the lucid release, but
the upstream has fixed this regression one full year and four days ago.
Can we now start the fixing?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/807153
Title:
named does not shut down after service bind9 stop
To manage notifications about this bug go to:
Public bug reported:
I am running the standard natty BIND9 package in an IPv6- and DNSSEC-
enabled configuration as a resolver. The zones are unaltered.
After service bind9 stop (or equivalently service bind9 restart),
named receives and logs the control command, but remains running. I have
to
Marked Confirmed
** Changed in: bind9 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/807153
Title:
named does not shut down after service
** Changed in: eglibc (Ubuntu Natty)
Status: New = Confirmed
** Changed in: postfix (Ubuntu Natty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
Am 06.08.2011 17:05, schrieb Clint Byrum:
I think we can also close the task on Postfix, since this is a glibc
issue, unless there is something we can do to postfix to fix this.
Postfix is one of the few software packages whose default configuration
(in newer Postfix versions) triggers this
So, I see three options to fix this, which one to use isn't my call to
decide:
1. patch spamassassin package, to make sure sa-learn doesn't complain if
use_bayes is set to 0
2. patch amavisd-new package, to not run sa-learn if use_bayes is set to
0. There should be a way to query SpamAssassin's
That's not a complete solution; since the job keeps complaining if bayes
is disabled.
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
The resolution is bogus. The installation must be possible regardless of
changed configuration.
** Changed in: fetchmail (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to fetchmail in Ubuntu.
s/installation/deinstallation/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to fetchmail in Ubuntu.
https://bugs.launchpad.net/bugs/1025051
Title:
package fetchmail 6.3.21-2 failed to install/upgrade: subprocess
installed
You can safely assume that unless someone deliberately changed the
Debian/Ubuntu scripts and left relevant information in the changes file,
the bug persists.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to fetchmail in Ubuntu.
How do you make sure there is only one account per init script?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to fetchmail in Ubuntu.
https://bugs.launchpad.net/bugs/1021699
Title:
fetchmail: IDLE - multiple daemons should be started
The limitation is documented, and I have always been considering killing
the IDLE option upstream. Some server NOTIFY extension that is not as
limited as IDLE is, might help, but I don't know how widespread that is.
Else fetchmail would have to undergo internal restructuring and go on
wasting
Public bug reported:
Binary package hint: bacula
This happens on regular upgrade (from Desktop) from Ubuntu 9.10 to
10.04.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: bacula-director-pgsql 5.0.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
Uname: Linux
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/47960248/Dependencies.txt
** Attachment added: VarLogDistupgradeAptlog.gz
http://launchpadlibrarian.net/47960249/VarLogDistupgradeAptlog.gz
** Attachment added: VarLogDistupgradeApttermlog.gz
Key is adding -not -xtype l which weeds out stuff that is a symbolic
link when dereferenced. This is only true for broken (dangling) symbolic
links.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
Public bug reported:
Postfix frequently fails to start after security updates to the ca-
certificates package because upgrading the latter sometimes leaves
dangling symlinks behind. If that happens, the /etc/init.d/postfix
script aborts.
# handle files in subdirectories
*** This bug is a security vulnerability ***
Public security bug reported:
Marking security because this causes loss of logging information.
1 /var/log/samba/log.smbd {
2 weekly
3 missingok
4 rotate 7
5 postrotate
6
38 matches
Mail list logo
