Debian Bug report logs - #670681
postgrey: stop action of init script does not work

Toggle useless messages

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

From: Nye Liu <nyet@nyet.org>

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

Subject: /etc/init.d/postgrey script doesn't work properly

Date: Fri, 27 Apr 2012 17:16:14 -0700

Package: postgrey
Version: 1.34-1.1
Severity: important
Tags: patch


/etc/init.d/postgrey passes --name to start-stop-daemon, but start-stop-daemon
apparently expects a full path (/usr/sbin/postgrey vs postgrey)

However, start-stop-daemon is also limited to 15 characters

So stop/reload do NOT work at all.

--- /etc/init.d/postgrey-dist	2012-04-27 16:58:30.000000000 -0700
+++ /etc/init.d/postgrey	2012-04-27 17:05:53.000000000 -0700
@@ -23,6 +23,7 @@
 PATH=/sbin:/bin:/usr/sbin:/usr/bin
 DAEMON=/usr/sbin/postgrey
 NAME=postgrey
+SSNAME=`echo $DAEMON | cut -c -15`
 DESC="postfix greylisting daemon"
 
 PIDFILE=/var/run/$NAME.pid
@@ -51,7 +52,7 @@
   start)
 	log_daemon_msg "Starting $DESC" "$NAME"
 	if start-stop-daemon --start --oknodo --quiet \
-		--pidfile $PIDFILE --name $NAME \
+		--pidfile $PIDFILE --name $SSNAME \
 		--startas $DAEMON -- $POSTGREY_OPTS "$POSTGREY_TEXT_OPT"
 	then
 	    log_end_msg 0
@@ -63,7 +64,7 @@
   stop)
 	log_daemon_msg "Stopping $DESC" "$NAME"
 	if start-stop-daemon --stop --oknodo --quiet \
-		--pidfile $PIDFILE --name $NAME
+		--pidfile $PIDFILE --name $SSNAME
 	then
 	    log_end_msg 0
 	else
@@ -75,7 +76,7 @@
   reload|force-reload)
 	log_action_begin_msg "Reloading $DESC configuration..."
 	if start-stop-daemon --stop --signal 1 --quiet \
-		--pidfile $PIDFILE --name $NAME
+		--pidfile $PIDFILE --name $SSNAME
 	then
 	    log_action_end_msg 0
 	else

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages postgrey depends on:
ii  adduser                       3.102      Add and remove users and groups
ii  debconf [debconf-2.0]         1.5.39     Debian configuration management sy
ii  libberkeleydb-perl            0.49-1     use Berkeley DB 4 databases from P
ii  libnet-dns-perl               0.66-2+b2  Perform DNS queries from a Perl sc
ii  libnet-server-perl            0.94-1     An extensible, general perl server
ii  perl                          5.14.2-9   Larry Wall's Practical Extraction 
ii  ucf                           3.007      Update Configuration File: preserv

Versions of packages postgrey recommends:
ii  libnet-rblclient-perl         0.5-1      Queries multiple Realtime Blackhol
ii  libparse-syslog-perl          1.10-1     Perl module for parsing syslog ent
ii  postfix                       2.9.1-4    High-performance mail transport ag

-- debconf information:
  postgrey/1.32-3_changeport:

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

From: "David R. Hedges" <david@thelittleman.net>

To: 670681@bugs.debian.org

Subject: Re: /etc/init.d/postgrey script doesn't work properly

Date: Wed, 23 Jan 2013 22:45:08 -0600

I can verify that this patch has resolved my ability to reload postgrey 
after upgrading from Squeeze to Wheezy. (Thanks, Nye Liu!) It'd be great 
to see this patch get accepted (or this bug otherwise fixed, if the 
package maintainers know of a "more correct" way to resolve the issue).

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

From: Mike Gerber <mike@sprachgewalt.de>

To: Nye Liu <nyet@nyet.org>

Cc: 670681@bugs.debian.org

Subject: Re: /etc/init.d/postgrey script doesn't work properly

Date: Tue, 19 Mar 2013 16:28:23 +0100

The patch supplied by Nye Liu fixes this issue for me, too.

# dpkg -l | grep postgrey
ii  postgrey          1.34-1.1      all   greylisting implementation for Postfix

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

From: Olaf Zaplinski <olaf@zaplinski.de>

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

Subject: Re: /etc/init.d/postgrey script doesn't work properly

Date: Sun, 26 May 2013 15:07:35 +0200

Package: postgrey
Version: 1.34-1.1
Followup-For: Bug #670681

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

Patch did not work for me. What worked was this change of init script:

# line 80 - replaced
--pidfile $PIDFILE --name $SSNAME
# with
--pidfile $PIDFILE



-- System Information:
Debian Release: 7.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages postgrey depends on:
ii  adduser                3.113+nmu3
ii  debconf [debconf-2.0]  1.5.49
ii  libberkeleydb-perl     0.51-1
ii  libnet-dns-perl        0.66-2+b2
ii  libnet-server-perl     2.006-1
ii  perl                   5.14.2-21
ii  ucf                    3.0025+nmu3

Versions of packages postgrey recommends:
ii  libnet-rblclient-perl  0.5-2
ii  libparse-syslog-perl   1.10-2
ii  postfix                2.9.6-2

postgrey suggests no packages.

-- Configuration Files:
/etc/init.d/postgrey changed [not included]

-- debconf information excluded

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

From: Leoš Bitto <leos.bitto@gmail.com>

To: 670681@bugs.debian.org

Subject: Re: /etc/init.d/postgrey script doesn't work properly

Date: Thu, 12 Sep 2013 09:47:25 +0200

The patch supplied by Nye Liu fixes this issue for me on a system
running Debian stable (wheezy). However, on another system which is
updated to Debian testing (jessie) the startup script does not work at
all - it just prints green [ok] but postgrey is actually not started!

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

From: Marius Gedminas <marius@gedmin.as>

To: 670681@bugs.debian.org

Subject: Upstream bug about postgrey's process name

Date: Tue, 19 Nov 2013 09:15:56 +0200

I filed https://github.com/schweikert/postgrey/issues/5 for this.

If upstream reconsiders trying to change its process name, it would go
back to 'postgres' and the current init.d script will continue to work.

Marius Gedminas
-- 
After having done some test using hi-tech istruments (moving my mouse
during a kernel build) [...]
        -- Davide Libenzi on lkml

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

From: Matthias Wamser <mw@ilk.net>

To: 670681@bugs.debian.org

Subject: /etc/init.d/postgrey script doesn't work properly

Date: Thu, 17 Apr 2014 17:29:29 +0200

It seems like the start-stop-daemon uses /proc/pid/stat to find the
matching process name like 'pgrep' does it.

The man page of 'pgrep' describes the limitation:

NOTES
The process name used for matching is limited to the 15 characters
present in the output of /proc/pid/stat.
Use the -f option to match  against  the  complete command line,
/proc/pid/cmdline.


For the postgrey init script this behaviour of start-stop-daemon renders
it unusable.
The only functions working is "start" and "restart" - that's not enough.

So we can work around this like Nye Liu did. We even can completely
ommit the "--name" option leaving the risk of killing the wrong process.
Or we can just use "postg" as search pattern.
start-stop-daemon does not expect the full path, it's just only able of
recongnizing the first 15 characters (see pgrep limitation).

The finest solution will be, if the start-stop-daemon could the able to
match on /proc/pid/cmdline, like pgrep does if choosen the "-f" switch.

Perhaps we should file another bug at the dpkg package?

Searching for i just found one similiar bug:
 start-stop-daemon: --exec should also check the first argument of
/proc/PID/cmdline
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=202719

But in the meanwhile the init script of postgrey should be fixed without
relying on start-stop-daemosn limitations.

regards,
Matthias
-- 
   Matthias Wamser, Senior Systems Engineer, mailto: mw@ilk.net
   ILK Internet GmbH, Am Sandfeld 15, D-76149 Karlsruhe
   Tel: +49 (0) 721 9100 0, http://www.ilk.net
   Geschaeftsfuehrer Matthias Felger, AG Mannheim, HRB 107037

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

From: Andreas Metzler <ametzler@bebt.de>

To: 670681@bugs.debian.org

Subject: Re: /etc/init.d/postgrey script doesn't work properly

Date: Sat, 21 Jun 2014 08:10:14 +0200

Control: severity 670681 serious

Hello,

FYI this totally broke greylisting for me after upgrading to wheezy
and migrating to a new server as
service postgrey restart
did not restart the daemon and therefore did not apply the
configuration changes I made which were necessary for a working
postgrey installation. 

I am therefore upgrading the bug-severity (rationale "makes the
package in question unusable or mostly so").

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

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

From: Axel Beckert <abe@debian.org>

To: Andreas Metzler <ametzler@bebt.de>, 670681@bugs.debian.org

Subject: Re: Bug#670681: /etc/init.d/postgrey script doesn't work properly

Date: Thu, 26 Jun 2014 11:19:49 +0200

Control: tag -1 + confirmed

Hi,

Andreas Metzler wrote:
> FYI this totally broke greylisting for me after upgrading to wheezy
> and migrating to a new server as
> service postgrey restart
> did not restart the daemon and therefore did not apply the
> configuration changes I made which were necessary for a working
> postgrey installation. 

While I disagree with "totally broke greylisting"...

> I am therefore upgrading the bug-severity (rationale "makes the
> package in question unusable or mostly so").

... or "makes the package in question unusable or mostly so" (which is
a reason for "grave", but not for "serious" btw.), I do agree with
RC-severity and can confirm the issue. :-)

I'll look into the patch and will likely do an NMU for Sid as a start.
I may look into a stable update for Wheezy later, too.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-    |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5

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

From: Axel Beckert <abe@debian.org>

To: Andreas Metzler <ametzler@bebt.de>, 670681@bugs.debian.org

Subject: Re: Bug#670681: /etc/init.d/postgrey script doesn't work properly

Date: Thu, 26 Jun 2014 11:26:00 +0200

Control: found -1 1.34-1.2

Axel Beckert wrote:
> [...] can confirm the issue. :-)

... in Wheezy as well as in Jessie and Sid.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-    |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5

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

From: Axel Beckert <abe@debian.org>

To: 670681@bugs.debian.org

Cc: Leoš Bitto <leos.bitto@gmail.com>, Olaf Zaplinski <olaf@zaplinski.de>, Nye Liu <nyet@nyet.org>

Subject: Re: Bug#670681: /etc/init.d/postgrey script doesn't work properly

Date: Thu, 26 Jun 2014 16:57:17 +0200

Hi,

Nye Liu wrote:
> /etc/init.d/postgrey passes --name to start-stop-daemon, but start-stop-daemon
> apparently expects a full path (/usr/sbin/postgrey vs postgrey)
> 
> However, start-stop-daemon is also limited to 15 characters
> 
> So stop/reload do NOT work at all.

Yes. That's the core of the issue.

> --- /etc/init.d/postgrey-dist	2012-04-27 16:58:30.000000000 -0700
> +++ /etc/init.d/postgrey	2012-04-27 17:05:53.000000000 -0700
> @@ -23,6 +23,7 @@
>  PATH=/sbin:/bin:/usr/sbin:/usr/bin
>  DAEMON=/usr/sbin/postgrey
>  NAME=postgrey
> +SSNAME=`echo $DAEMON | cut -c -15`
>  DESC="postfix greylisting daemon"
>  
>  PIDFILE=/var/run/$NAME.pid
> @@ -51,7 +52,7 @@
>    start)
>  	log_daemon_msg "Starting $DESC" "$NAME"
>  	if start-stop-daemon --start --oknodo --quiet \
> -		--pidfile $PIDFILE --name $NAME \
> +		--pidfile $PIDFILE --name $SSNAME \
>  		--startas $DAEMON -- $POSTGREY_OPTS "$POSTGREY_TEXT_OPT"
>  	then
>  	    log_end_msg 0
> @@ -63,7 +64,7 @@
>    stop)
>  	log_daemon_msg "Stopping $DESC" "$NAME"
>  	if start-stop-daemon --stop --oknodo --quiet \
> -		--pidfile $PIDFILE --name $NAME
> +		--pidfile $PIDFILE --name $SSNAME
>  	then
>  	    log_end_msg 0
>  	else
> @@ -75,7 +76,7 @@
>    reload|force-reload)
>  	log_action_begin_msg "Reloading $DESC configuration..."
>  	if start-stop-daemon --stop --signal 1 --quiet \
> -		--pidfile $PIDFILE --name $NAME
> +		--pidfile $PIDFILE --name $SSNAME
>  	then
>  	    log_action_end_msg 0
>  	else

The stop and restart actions of an init script with this patch work
fine for any postgrey process started with the same script.

Contrary to my expectations, it though can't stop a process started by
the current (i.e. buggy) init script. I currently don't know why this
doesn't work.

This patch also has another disadvantage (which was not known at the
time the patch was written, so that's not a fault of the patch or its
author :-), namely that since 1.35 upstream writes "postgrey" and the
beginning of the arguments into that "comm" field:

https://github.com/schweikert/postgrey/commit/d496dfbc13412fda9d72dc1c1eb6506c84265543

So the above variant will need to be changed with the next upstream
release anyways...

Olaf Zaplinski wrote:
> Patch did not work for me. What worked was this change of init script:
> 
> # line 80 - replaced
> --pidfile $PIDFILE --name $SSNAME
> # with
> --pidfile $PIDFILE

Works, too, but also fails to stop a postgrey daemon which was started
by the previous version of the init script.

In comparison to Nye Liu's solution, this one at least throws an error
in this case and would likely continue to work unmodified with the
recent new upstream release 1.35.

So I currently tend to this solution, but I'll first need to check if
it has other implications.

Another variant would be to use "-u postgrey" given that no other
process runs under the user "postgrey". But according to its man page,
"postgreyreport" runs under the "postgrey" user by default, too, and
if it's running while the init script tries to stop the postgrey
daemon, that script would be killed, too. Not perfect either...

Leoš Bitto wrote on 12 Sep 2013:
> The patch supplied by Nye Liu fixes this issue for me on a system
> running Debian stable (wheezy). However, on another system which is
> updated to Debian testing (jessie) the startup script does not work at
> all - it just prints green [ok] but postgrey is actually not started!

The latter may be a different issue, maybe
https://bugs.debian.org/748918 (postgrey fails to start on Wheezy,
fixed in Sid in November 2013, but unclear under which circumstances
it shows up on Wheezy, too)

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-    |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5

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

From: Axel Beckert <abe@debian.org>

To: Antonio Radici <antonio@dyne.org>

Cc: 670681@bugs.debian.org, 630353@bugs.debian.org

Subject: NMU for RC bug in postgrey

Date: Thu, 26 Jun 2014 19:25:49 +0200

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

Control: tag -1 + pending

Hi Antonio,

Antonio Radici wrote:
> if you have time it would be great if you could prepare an NMU for the patch at
> the existing release

This sentence of yours was originally meant for #748918 which arose to
being already fixed in Sid and Jessie.

Me closing #748918 in Sid and Jessie bumped the autoremoval date from
tomorrow to 11th of July. The cvurrent autoremoval is triggered by
#670681 which has been upped to RC severity on Saturday IIRC.

I've prepared an NMU to fix #670681. See the git commit at
http://anonscm.debian.org/gitweb/?p=collab-maint/postgrey.git;a=commitdiff;h=0f28b7d153ea42de08054f542e81deb4c04631e6
(I pushed it to a newly created "nmu" branch which I'll merge and
remove as soon as the package hits the archive.)

This seems to also fix #630353 which is likely a follow up error of
#670681 (or vice versa; they're at least related).

I hope this NMU is ok for you, too. If so, please tell me and I'll
upload it more or less immediately. If I don't hear from you, I'll
upload it to DELAYED/2 -- probably tomorrow.

> and then I can add you as co-maintainer and we can work on
> the 1.35 packaging (there is already a git, you just need to be on
> collab-maint).
> 
> On the long run we should run postgrey using a team rather than a single person
> (me), that should make things easier in terms of maintainership and uploads.

Having worked through the package and bugs, I may start working on
importing 1.35 and modernising the packaging a little bit on my own.
But I'll do that in a separate branch for now, so you can review it in
case you're not happy about e.g. source format "3.0 (quilt)" or a "dh"
style debian/rules file.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-    |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5

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

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

From: Axel Beckert <abe@debian.org>

To: 670681@bugs.debian.org, 630353@bugs.debian.org

Subject: Re: Bug#670681: NMU for RC bug in postgrey

Date: Fri, 27 Jun 2014 13:45:30 +0200

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

Hi,

Axel Beckert wrote:
> I've prepared an NMU to fix #670681. See the git commit at
> http://anonscm.debian.org/gitweb/?p=collab-maint/postgrey.git;a=commitdiff;h=0f28b7d153ea42de08054f542e81deb4c04631e6
> (I pushed it to a newly created "nmu" branch which I'll merge and
> remove as soon as the package hits the archive.)
[...]
> I hope this NMU is ok for you, too. If so, please tell me and I'll
> upload it more or less immediately. If I don't hear from you, I'll
> upload it to DELAYED/2 -- probably tomorrow.

Uploaded to DELAYED/2 with the attached debdiff. (Should be the same
as the diff linked above, but included for completeness.)

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-    |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5

[postgrey_1.34-1.2_1.34-1.3.debdiff (text/plain, attachment)]

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

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

From: Axel Beckert <abe@debian.org>

To: 670681-close@bugs.debian.org

Subject: Bug#670681: fixed in postgrey 1.34-1.3

Date: Sun, 29 Jun 2014 11:19:45 +0000

Source: postgrey
Source-Version: 1.34-1.3

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

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 670681@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert <abe@debian.org> (supplier of updated postgrey 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@ftp-master.debian.org)


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

Format: 1.8
Date: Thu, 26 Jun 2014 16:03:15 +0200
Source: postgrey
Binary: postgrey
Architecture: source all
Version: 1.34-1.3
Distribution: unstable
Urgency: high
Maintainer: Antonio Radici <antonio@dyne.org>
Changed-By: Axel Beckert <abe@debian.org>
Description:
 postgrey   - greylisting implementation for Postfix
Closes: 630353 670681
Changes:
 postgrey (1.34-1.3) unstable; urgency=high
 .
   * Non-maintainer upload in accordance with maintainer.
   * Fix "stop" action of init script. (Closes: #670681, #630353)
     + Add preinst script which kills postgrey daemons neither stoppable by
       the old nor by the new init.d script.
Checksums-Sha1:
 cf691bcc66e9375bf2c003a9ef51bf14ee299d37 1242 postgrey_1.34-1.3.dsc
 cde19964d90030af0ac90e6b8852f83048c51c41 22689 postgrey_1.34-1.3.diff.gz
 c81d4a4d727265d479d45b3d11d2dea888111d11 57508 postgrey_1.34-1.3_all.deb
Checksums-Sha256:
 728a732643eeb85c759ca57dd1ff45d83f76c30e0bc8a78f19b378d37576ac82 1242 postgrey_1.34-1.3.dsc
 ca6e0c7461dfa0b3fd8b327f62975ec29e27598d68baf3136128203b959f4e53 22689 postgrey_1.34-1.3.diff.gz
 f21d750dc62a7bbc8495c22d7d4054acf0609f0c3822010cc41ca97ffeabce67 57508 postgrey_1.34-1.3_all.deb
Files:
 81ffd734d10469c150ff06d5497c3ac9 57508 mail optional postgrey_1.34-1.3_all.deb
 e95695b93b464926e1e614e6ef2f05df 1242 mail optional postgrey_1.34-1.3.dsc
 57fbb02a6191b43e4725396338a7856b 22689 mail optional postgrey_1.34-1.3.diff.gz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlOtSXYACgkQwJ4diZWTDt7MgwCeO/bflUHqeTcb7mqvJHYrlv6i
Km0AnjSQ870ArkG43I9PKf05GGseCfQT
=4y8B
-----END PGP SIGNATURE-----

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

From: 河本陽一 <komoto.yoichi@kcc.co.jp>

To: 670681@bugs.debian.org

Subject: wheezy patch?

Date: Mon, 11 Aug 2014 10:33:09 +0900

I am using postgrey 1.34-1.1 in wheezy.
The wheezy, this patch do you apply?

Send a report that this bug log contains spam.