Debian Bug report logs - #311812
postfix: syslog reconnection

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: juan <bugs@niluje.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: postfix: syslog reconnection

Date: Fri, 03 Jun 2005 15:10:11 +0200

Package: postfix
Version: 2.1.5-9
Severity: important

If you happend to stop and restart syslog some postfix daemon do not reconnect to syslog and critical information can be lost.
cleanup,qmgr are concerned. smtpd,smtp,virtual seem to be ok.

FIX: if syslog has to be restarted for any reason (logroate ?), postfix should be restarted too.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.30-vs1.2.10
Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages postfix depends on:
ii  adduser                     3.63         Add and remove users and groups
ii  debconf [debconf-2.0]       1.4.30.13    Debian configuration management sy
ii  dpkg                        1.10.27      Package maintenance system for Deb
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libdb4.2                    4.2.52-18    Berkeley v4.2 Database Libraries [
ii  libgdbm3                    1.8.3-2      GNU dbm database routines (runtime
ii  netbase                     4.21         Basic TCP/IP networking system

-- debconf information excluded

Message #10 received at 311812@bugs.debian.org (full text, mbox, reply):

From: Martin Zobel-Helas <zobel@ftbfs.de>

To: 311812@bugs.debian.org

Subject: Re: postfix: syslog reconnection

Date: Thu, 17 Jan 2008 17:01:15 +0100

[Message part 1 (text/plain, inline)]

Hi, 

On Fri, Jun 03, 2005 at 03:10:11PM CEST, juan <bugs@niluje.net> wrote:

> If you happend to stop and restart syslog some postfix daemon do not
> reconnect to syslog and critical information can be lost.
> cleanup,qmgr are concerned. smtpd,smtp,virtual seem to be ok.

Why does that happen? Does postfix not communicate via /dev/log?

> FIX: if syslog has to be restarted for any reason (logroate ?),
> postfix should be restarted too.

Bah, that is an ugly workaround. I wish the underlying problem would be
fixed and not workarounded. 

Greetings
Martin
-- 
 Martin Zobel-Helas <zobel@debian.org> |  Debian Release Team Member
 Debian & GNU/Linux Developer          |           Debian Listmaster
 Public key at http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870
 GPG Fingerprint:  5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870

[signature.asc (application/pgp-signature, inline)]

Message #15 received at 311812@bugs.debian.org (full text, mbox, reply):

From: Martin Zobel-Helas <zobel@ftbfs.de>

To: 311812@bugs.debian.org

Subject: Re: postfix: syslog reconnection

Date: Thu, 17 Jan 2008 17:06:29 +0100

Hi Lamot,

you might want to have a look on 
http://archives.neohapsis.com/archives/postfix/2008-01/0821.html

Greetings
Martin

Message #20 received at 311812@bugs.debian.org (full text, mbox, reply):

From: Alexander Wirt <formorer@debian.org>

To: 311812@bugs.debian.org

Cc: control@bugs.debian.org

Subject: postfix: syslog reconnection - please provide syslogd socket in jail

Date: Thu, 17 Jan 2008 16:17:12 +0000

severity 311812 grave
thanks

Hi, 

today I have been hit by this bug, which made logs from 3 days mostly
useless. Asking on postfix-users about it gave me the following answer:

	Complain to your maintainer.

	The bug is that YOUR DISTRIBUTION uses Postfix chroot with an
	incomplete chroot jail. In particular, the jail lacks a syslogd
	socket that the queue manager can connect to after the syslogd
	process is restarted. 

Which is what I'm doing here. It would be nice if you could add a fix also for etch r3 oder r4. 

Thanks 

Alex

Message #27 received at 311812@bugs.debian.org (full text, mbox, reply):

From: LaMont Jones <lamont@debian.org>

To: Alexander Wirt <formorer@debian.org>, 311812@bugs.debian.org

Cc: control@bugs.debian.org

Subject: Re: Bug#311812: postfix: syslog reconnection - please provide syslogd socket in jail

Date: Thu, 17 Jan 2008 09:33:55 -0700

severity 311812 important
--

On Thu, Jan 17, 2008 at 04:17:12PM +0000, Alexander Wirt wrote:
> severity 311812 grave

It's only grave if the bug is against syslogd.  Syslogd doesn't provide
a method for postfix to change the config file, and therefore it would
be a policy violation for postfix to edit syslog's config file so that
it sees things when it restarts.

Once there's a way for postfix to hook up to syslogd in a
policy-conformant manner, we can fix this bug.

lamont

Message #34 received at 311812@bugs.debian.org (full text, mbox, reply):

From: Bernd Zeimetz <bernd@bzed.de>

To: 311812@bugs.debian.org, control@bugs.debian.org

Subject: Re: Bug#311812: postfix: syslog reconnection - please provide, syslogd socket in jail

Date: Sun, 27 Jan 2008 00:01:57 +0100

severity 311812 grave
#rationale: data loss
tags 311812 + etch lenny sid
thanks

This bug introduce a serious risk of loosing important log data, which
is - especially for a MTA - not acceptable. Asking people to restart
postfix after reloading syslog is a *stupid* workaround, which also
results in the loss of log entries (during the time when syslog is
restarted but postfix not yet). The only working, but not less ugly,
workaround is to stop postfix first, then reload/restart syslog, and
start postfix again.

It seems you're just doing nothing to fix this bug, this behavior is a
shame as you're ruining the image of postfix as the best MTA we have in
Debian. If you really think the bug should be fixed in sysklogd -
where's the open grave bug in sysklogd, syslog-ng and other syslog
daemons which block *this* bug?

There're a few ways to get a syslog socket into the chroot, like
- using syslog-ng: my suggested way, but depending on a syslog daemon is
not nice.
- using bind mounts: not available on older kernels, also a bind mount
needs to be recreated after re{loading,starting} the syslog daemon

None of the ways is an optimal way for the common user, so my suggestion
is to write a little daemon which does nothing but providing a syslog
socket in the chroot and relying messages to the real syslog daemon,
like a proxy for sockets. Due to the flexibility of postfix's master.cf
the daemon could just be deactivated if a user prefers to have a real
syslog daemon dropping it's socket in there.


Best regards,

-- 
Bernd Zeimetz
<bernd@bzed.de>                         <http://bzed.de/>

Message #49 received at 311812@bugs.debian.org (full text, mbox, reply):

From: LaMont Jones <lamont@debian.org>

To: Bernd Zeimetz <bernd@bzed.de>, 311812@bugs.debian.org

Cc: control@bugs.debian.org

Subject: Re: Bug#311812: postfix: syslog reconnection - please provide, syslogd socket in jail

Date: Sat, 26 Jan 2008 23:19:59 -0700

On Sun, Jan 27, 2008 at 12:01:57AM +0100, Bernd Zeimetz wrote:
> This bug introduce a serious risk of loosing important log data, which
> is - especially for a MTA - not acceptable. Asking people to restart
> postfix after reloading syslog is a *stupid* workaround, which also
> results in the loss of log entries (during the time when syslog is
> restarted but postfix not yet). The only working, but not less ugly,
> workaround is to stop postfix first, then reload/restart syslog, and
> start postfix again.

The only long-term workable solution to this bug is for syslog to allow
postfix to specify an alternate socket.

> It seems you're just doing nothing to fix this bug, this behavior is a
> shame as you're ruining the image of postfix as the best MTA we have in
> Debian. If you really think the bug should be fixed in sysklogd -
> where's the open grave bug in sysklogd, syslog-ng and other syslog
> daemons which block *this* bug?

Cloned and filed, as anyone could have done.  Tracking down how to do
that took me a little while, as I've not done it previously.

> There're a few ways to get a syslog socket into the chroot, like
> - using syslog-ng: my suggested way, but depending on a syslog daemon is
> not nice.
> - using bind mounts: not available on older kernels, also a bind mount
> needs to be recreated after re{loading,starting} the syslog daemon

3) change /etc/default/syslog to say
  SYSLOG="-a /var/spool/postfix/dev/log"
and then rsync -av /dev/log /var/spool/postfix/dev/log

Note that any admin can do that, postfix may not edit the config file of
another package.

lamont

Message #54 received at 311812@bugs.debian.org (full text, mbox, reply):

From: Martin Zobel-Helas <zobel@ftbfs.de>

To: 311812@bugs.debian.org

Subject: Re: Bug#311812: postfix: syslog reconnection - please provide, syslogd socket in jail

Date: Sun, 27 Jan 2008 08:55:47 +0100

Hi,

has anyone thought of having a look how other distributions solved this
problem? I am pretty sure some might already have solved that problem.

Greetings
Martin

-- 
 Martin Zobel-Helas <zobel@debian.org>  |  Debian Release Team Member
 Debian & GNU/Linux Developer           |           Debian Listmaster
 Public key http://zobel.ftbfs.de/5d64f870.asc   -   KeyID: 5D64 F870
 GPG Fingerprint:  5DB3 1301 375A A50F 07E7  302F 493E FB8E 5D64 F870

Message #61 received at 311812@bugs.debian.org (full text, mbox, reply):

From: Thijs Kinkhorst <thijs@debian.org>

To: 311812@bugs.debian.org

Subject: Re: postfix: syslog reconnection - solved?

Date: Fri, 25 Jul 2008 12:41:34 +0200

[Message part 1 (text/plain, inline)]

Hi LaMont,

You wrote:
> 3) change /etc/default/syslog to say
>   SYSLOG="-a /var/spool/postfix/dev/log"
> and then rsync -av /dev/log /var/spool/postfix/dev/log
>
> Note that any admin can do that, postfix may not edit the config file of
> another package.

As it seems the bug you cloned this one as against syslogd, 462739, has been 
fixed for a while with this changelog entry:

   * Add support for syslogd configuration files under /etc/syslog.d/.
     (Closes: #370349, #462739)

Do you think this bug can now also be solved on the postfix side?


cheers,
Thijs

[Message part 2 (application/pgp-signature, inline)]

Message #66 received at 311812@bugs.debian.org (full text, mbox, reply):

From: Bernd Zeimetz <bernd@bzed.de>

To: Thijs Kinkhorst <thijs@debian.org>, 311812@bugs.debian.org

Subject: Re: Bug#311812: postfix: syslog reconnection - solved?

Date: Fri, 25 Jul 2008 13:45:13 +0200

Thijs Kinkhorst wrote:
> Hi LaMont,
> 
> You wrote:
>> 3) change /etc/default/syslog to say
>>   SYSLOG="-a /var/spool/postfix/dev/log"
>> and then rsync -av /dev/log /var/spool/postfix/dev/log
>>
>> Note that any admin can do that, postfix may not edit the config file of
>> another package.
> 
> As it seems the bug you cloned this one as against syslogd, 462739, has been 
> fixed for a while with this changelog entry:
> 
>    * Add support for syslogd configuration files under /etc/syslog.d/.
>      (Closes: #370349, #462739)
> 
> Do you think this bug can now also be solved on the postfix side?

Only if rsyslog supports that, too, as it is the new default syslog
daemon. I didn't look into rsyslog due to missing spare time, but
support for such configurations needs to be added if it's not there yet.


-- 
 Bernd Zeimetz                           Debian GNU/Linux Developer
 GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79

Message #71 received at 311812@bugs.debian.org (full text, mbox, reply):

From: LaMont Jones <lamont@debian.org>

To: Thijs Kinkhorst <thijs@debian.org>, 311812@bugs.debian.org

Subject: Re: Bug#311812: postfix: syslog reconnection - solved?

Date: Fri, 25 Jul 2008 06:16:47 -0600

On Fri, Jul 25, 2008 at 12:41:34PM +0200, Thijs Kinkhorst wrote:
>    * Add support for syslogd configuration files under /etc/syslog.d/.
>      (Closes: #370349, #462739)

> Do you think this bug can now also be solved on the postfix side?

From reading the bug report, it would appear that he added support for
additional syslog.conf-ish config files, not specifying additional log
files.  There is also another syslogd that seems to be more common in
the wild.

In any case, I'm thinking I'll solve the issue by asking if the user
wants to chroot postfix, and if so telling him that he needs to deal
with making syslog happier, or (assuming it actually works) bind
mounting /dev/log.  If not chrooted, then the issue is non-existent.

lamont

Message #76 received at 311812@bugs.debian.org (full text, mbox, reply):

From: Bernd Zeimetz <bzed@debian.org>

To: LaMont Jones <lamont@debian.org>, 311812@bugs.debian.org

Cc: Thijs Kinkhorst <thijs@debian.org>

Subject: Re: Bug#311812: postfix: syslog reconnection - solved?

Date: Fri, 25 Jul 2008 15:28:48 +0200

> In any case, I'm thinking I'll solve the issue by asking if the user
> wants to chroot postfix, and if so telling him that he needs to deal
> with making syslog happier, or (assuming it actually works) bind
> mounting /dev/log.  If not chrooted, then the issue is non-existent.

That's indeed probably the best way to fix it and at the same time gives
th euser a reminder to fix their syslog config, even if they're using
some other syslog daemon.


Cheers,

Bernd
-- 
 Bernd Zeimetz                           Debian GNU/Linux Developer
 GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79

Message #79 received at 311812@bugs.debian.org (full text, mbox, reply):

From: Christoph Berg <myon@debian.org>

To: 311812@bugs.debian.org

Subject: Re: Bug#311812: [PATCH] postfix: syslog reconnection - solved?

Date: Sun, 7 Sep 2008 14:16:34 +0200

[Message part 1 (text/plain, inline)]

tags 311812 + patch pending
thanks

Hi,

Re: LaMont Jones 2008-07-25 <20080725121647.GA22539@mix.mmjgroup.com>
> >    * Add support for syslogd configuration files under /etc/syslog.d/.
> >      (Closes: #370349, #462739)
> 
> > Do you think this bug can now also be solved on the postfix side?
> 
> >From reading the bug report, it would appear that he added support for
> additional syslog.conf-ish config files, not specifying additional log
> files.  There is also another syslogd that seems to be more common in
> the wild.

The fix for inetutils-syslogd is indeed broken in the sense that it
doesn't fix this issue. sysklogd is also unfixable without an NMU as
/etc/default/syslogd is a conffile.

> In any case, I'm thinking I'll solve the issue by asking if the user
> wants to chroot postfix, and if so telling him that he needs to deal
> with making syslog happier, or (assuming it actually works) bind
> mounting /dev/log.  If not chrooted, then the issue is non-existent.

I don't think un-chrooting postfix is worth the issue. Most users
won't care enough about mail logs, and even the broken mail logs
contain enough information for the occasional log reader.

Lenny will have rsyslog as default log daemon. The patch below
provides a fix for the socket-in-chroot problem for this syslog
daemon, and adds a note to postfix's README.Debian for the others.
IMHO that closes this bug.

I intend to upload the NMU after the weekend (LaMont has indicated he
was away for a few days).


diff -u postfix-2.5.5/debian/README.Debian postfix-2.5.5/debian/README.Debian
--- postfix-2.5.5/debian/README.Debian
+++ postfix-2.5.5/debian/README.Debian
@@ -27,0 +28,11 @@
+3.  Note that the chrooted daemons open /dev/log before chrooting, so if your
+    syslog daemon is restarted, the daemons will be unable to reconnect to the
+    syslog socket, and hence being unable to log.  The postfix package provides
+    a config snipped for the rsyslog daemon in /etc/rsyslog.d/postfix.conf to
+    also open a socket in /var/log/postfix/dev.  For other syslog daemons, you
+    will also have to restart postfix after restarting the syslog daemon, or
+    configure it to open an additional socket.
+  a. For sysklogd (the default in Debian versions prior to Lenny), add
+     SYSLOG="-a /var/spool/postfix/dev/log" to /etc/default/syslog.
+  b. For inetutils-syslogd, add SYSLOGD_OPTS="-a /var/spool/postfix/dev/log" to
+     /etc/default/inetutils-syslogd.
diff -u postfix-2.5.5/debian/changelog postfix-2.5.5/debian/changelog
--- postfix-2.5.5/debian/changelog
+++ postfix-2.5.5/debian/changelog
@@ -1,3 +1,12 @@
+postfix (2.5.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add rsyslog.d config snipped to create a /dev/log syslog socket in the
+    postfix chroot.  Also, add a note about other syslog daemons to
+    README.Debian.  Closes: #311812
+
+ -- Christoph Berg <myon@debian.org>  Sun, 07 Sep 2008 14:02:15 +0200
+
 postfix (2.5.5-1) unstable; urgency=low
 
   [Wietse Venema]
diff -u postfix-2.5.5/debian/rules postfix-2.5.5/debian/rules
--- postfix-2.5.5/debian/rules
+++ postfix-2.5.5/debian/rules
@@ -135,6 +135,7 @@
 	install -m 0644 conf/main.cf.debian $(sharedir)/main.cf.debian
 	install -m 0644 conf/main.cf.tls $(sharedir)/main.cf.tls
 	install -m644 debian/postfix.ufw.profile debian/postfix/etc/ufw/applications.d/postfix
+	install -m644 debian/rsyslog.conf debian/postfix/etc/rsyslog.d/postfix.conf
 
 	install man/man1/*.1 ${base}/usr/share/man/man1
 	install man/man5/*.5 ${base}/usr/share/man/man5
diff -u postfix-2.5.5/debian/postfix.dirs postfix-2.5.5/debian/postfix.dirs
--- postfix-2.5.5/debian/postfix.dirs
+++ postfix-2.5.5/debian/postfix.dirs
@@ -5,6 +5,7 @@
 etc/network/if-up.d
 etc/network/if-down.d
 etc/postfix/sasl
+etc/rsyslog.d
 etc/ufw/applications.d
 usr/bin
 usr/sbin
@@ -18,6 +19,7 @@
 etc/postfix
 etc/resolvconf/update-libc.d
 var/spool/postfix
+var/spool/postfix/dev
 var/spool/postfix/etc
 var/spool/postfix/lib
 var/spool/postfix/usr
only in patch2:
unchanged:
--- postfix-2.5.5.orig/debian/rsyslog.conf
+++ postfix-2.5.5/debian/rsyslog.conf
@@ -0,0 +1,4 @@
+# Create an additional socket in postfix's chroot in order not to break
+# mail logging when rsyslog is restarted.  If the directory is missing,
+# rsyslog will silently skip creating the socket.
+$AddUnixListenSocket /var/spool/postfix/dev/log

Christoph
-- 
cb@df7cb.de | http://www.df7cb.de/

[signature.asc (application/pgp-signature, inline)]

Message #86 received at 311812-close@bugs.debian.org (full text, mbox, reply):

From: Christoph Berg <myon@debian.org>

To: 311812-close@bugs.debian.org

Subject: Bug#311812: fixed in postfix 2.5.5-1.1

Date: Sun, 14 Sep 2008 14:02:05 +0000

Source: postfix
Source-Version: 2.5.5-1.1

We believe that the bug you reported is fixed in the latest version of
postfix, which is due to be installed in the Debian FTP archive:

postfix-cdb_2.5.5-1.1_amd64.deb
  to pool/main/p/postfix/postfix-cdb_2.5.5-1.1_amd64.deb
postfix-dev_2.5.5-1.1_all.deb
  to pool/main/p/postfix/postfix-dev_2.5.5-1.1_all.deb
postfix-doc_2.5.5-1.1_all.deb
  to pool/main/p/postfix/postfix-doc_2.5.5-1.1_all.deb
postfix-ldap_2.5.5-1.1_amd64.deb
  to pool/main/p/postfix/postfix-ldap_2.5.5-1.1_amd64.deb
postfix-mysql_2.5.5-1.1_amd64.deb
  to pool/main/p/postfix/postfix-mysql_2.5.5-1.1_amd64.deb
postfix-pcre_2.5.5-1.1_amd64.deb
  to pool/main/p/postfix/postfix-pcre_2.5.5-1.1_amd64.deb
postfix-pgsql_2.5.5-1.1_amd64.deb
  to pool/main/p/postfix/postfix-pgsql_2.5.5-1.1_amd64.deb
postfix_2.5.5-1.1.diff.gz
  to pool/main/p/postfix/postfix_2.5.5-1.1.diff.gz
postfix_2.5.5-1.1.dsc
  to pool/main/p/postfix/postfix_2.5.5-1.1.dsc
postfix_2.5.5-1.1_amd64.deb
  to pool/main/p/postfix/postfix_2.5.5-1.1_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 311812@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Berg <myon@debian.org> (supplier of updated postfix package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sun, 07 Sep 2008 14:02:15 +0200
Source: postfix
Binary: postfix postfix-ldap postfix-cdb postfix-pcre postfix-mysql postfix-pgsql postfix-dev postfix-doc
Architecture: source amd64 all
Version: 2.5.5-1.1
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones <lamont@debian.org>
Changed-By: Christoph Berg <myon@debian.org>
Description: 
 postfix    - High-performance mail transport agent
 postfix-cdb - CDB map support for Postfix
 postfix-dev - Loadable modules development environment for Postfix
 postfix-doc - Documentation for Postfix
 postfix-ldap - LDAP map support for Postfix
 postfix-mysql - MySQL map support for Postfix
 postfix-pcre - PCRE map support for Postfix
 postfix-pgsql - PostgreSQL map support for Postfix
Closes: 311812
Changes: 
 postfix (2.5.5-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add rsyslog.d config snipped to create a /dev/log syslog socket in the
     postfix chroot.  Also, add a note about other syslog daemons to
     README.Debian.  Closes: #311812
Checksums-Sha1: 
 2b3aa8a023a2974c17a8f234c39d75c2d02aac66 1423 postfix_2.5.5-1.1.dsc
 3b5c64519938cbfb45894fe4e877019ac5d386fb 217642 postfix_2.5.5-1.1.diff.gz
 ef03267d9ffaf63b7514e13a844bdadce7a408b8 1301256 postfix_2.5.5-1.1_amd64.deb
 1bd990894d4aeadbfb01111bf2ef0af5c7927fc0 49414 postfix-ldap_2.5.5-1.1_amd64.deb
 1709eb580625be6dbdb4ebecac0d908e3a7397ef 41924 postfix-cdb_2.5.5-1.1_amd64.deb
 5e83f91310ff89cb92b89c0a1930651045a370b4 43704 postfix-pcre_2.5.5-1.1_amd64.deb
 92d5235eb03474a64aeee05232f4c11575e5586e 43654 postfix-mysql_2.5.5-1.1_amd64.deb
 2174bdc10a92f24619a47d15349e48f7958b45f0 43734 postfix-pgsql_2.5.5-1.1_amd64.deb
 6693dca709b90920e899578ff501078cf4f2afd3 140646 postfix-dev_2.5.5-1.1_all.deb
 680a0b69322d991e098b1741802869ded17602ad 914566 postfix-doc_2.5.5-1.1_all.deb
Checksums-Sha256: 
 6377ad024d822a445459dc4a5b5f0ff14ce93a4b77ca8595c7ca1c908d18ba5e 1423 postfix_2.5.5-1.1.dsc
 61d0f3be8be78d767abf4c8bf4229840e470b2447643f8583f90a12e3949a879 217642 postfix_2.5.5-1.1.diff.gz
 2a233249a0bc96bbf2b5479566b91d567ade9c3b0ed8363661b0ab531601f3eb 1301256 postfix_2.5.5-1.1_amd64.deb
 6af3d3e3417cff0d487b94bba8c6311f94aef1a44aaf5be0aa646e41ac8b7ef1 49414 postfix-ldap_2.5.5-1.1_amd64.deb
 422b61001abbd70b05a5b71a3d3aaa9f5280dad47159056615afb7f2463f7ca5 41924 postfix-cdb_2.5.5-1.1_amd64.deb
 e1386fd15d17c68dc738cebcff2698a54e7150ec1d39e47e01ad292a43a87607 43704 postfix-pcre_2.5.5-1.1_amd64.deb
 37913a86ff0f52d890eaee7fab34a63b79f09d8fcaed77878899660ff352277e 43654 postfix-mysql_2.5.5-1.1_amd64.deb
 c13c1fadb8dba0c9298407c9ed4fde2834db79429f4783e12d0c980e3af578fe 43734 postfix-pgsql_2.5.5-1.1_amd64.deb
 27ed009f11edfe5a3109cc61e916e966eb7cc5ce2be2f8c51f422ce78598016e 140646 postfix-dev_2.5.5-1.1_all.deb
 96e17b1641cacae68b18af352dd8993f67741f33fb7d340a6b001dbd1b469add 914566 postfix-doc_2.5.5-1.1_all.deb
Files: 
 a88cfb4fd876fe8bc9354754009f89a5 1423 mail extra postfix_2.5.5-1.1.dsc
 dc3457875693051b6a7fc53e376c357e 217642 mail extra postfix_2.5.5-1.1.diff.gz
 aebddc4bc1b62f90b10e8dbf56855035 1301256 mail extra postfix_2.5.5-1.1_amd64.deb
 2c0561432e17cd8dc5e273a2faa9756c 49414 mail extra postfix-ldap_2.5.5-1.1_amd64.deb
 b69ecb2720f055500091aae39a275860 41924 mail extra postfix-cdb_2.5.5-1.1_amd64.deb
 be1b70942cf8bca73586c103da51b654 43704 mail extra postfix-pcre_2.5.5-1.1_amd64.deb
 42dc4b4e4bf467b8785657b149da3b8e 43654 mail extra postfix-mysql_2.5.5-1.1_amd64.deb
 56536b7f495441b5ce54db4c1059aba1 43734 mail extra postfix-pgsql_2.5.5-1.1_amd64.deb
 d083f62eebb322cc4c7f6556af50871c 140646 devel extra postfix-dev_2.5.5-1.1_all.deb
 ad858d1ee4d42473744eb9d4afad4145 914566 doc extra postfix-doc_2.5.5-1.1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkjNF7gACgkQxa93SlhRC1oyUwCg02MGcfipWGSGCAjkkaqxYA2X
OLcAniXDJBwnWt7Tc/Q8w4bqrledUVBo
=60ln
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.