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

Format: 1.7
Date: Tue, 26 Jun 2007 20:22:10 -0700
Source: dkim-milter
Binary: dkim-filter
Architecture: source i386
Version: 1.2.0.dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Mike Markley <[EMAIL PROTECTED]>
Changed-By: Mike Markley <[EMAIL PROTECTED]>
Description: 
 dkim-filter - DomainKeys Identified Mail for Sendmail
Closes: 428392
Changes: 
 dkim-milter (1.2.0.dfsg-1) unstable; urgency=low
 .
   * New upstream version
   * Support setting listening socket in /etc/default/dkim-filter
   * Minor rephrasing of deluser test in postrm so the if block can
     be later extended if needed
   * Fixes for socket permissions; Closes: #428392
     - Create dkim-filter group and assign as primary GID of same user
       in postinst
     - Set umask in init script to force group writable socket
     - dkim-filter now picks up primary GID of its run user
     - Added a doc note for Postfix users who need write permissions
       to the socket
   * Remove pidfile on normal shutdown
Files: 
 a0de7a771b531179226854f1bc7e6c4a 647 mail extra dkim-milter_1.2.0.dfsg-1.dsc
 a315f6ea94b9bdcb7aabb3f27f62ff06 403474 mail extra 
dkim-milter_1.2.0.dfsg.orig.tar.gz
 88ba30f75c45accb077a22a14985061c 8257 mail extra 
dkim-milter_1.2.0.dfsg-1.diff.gz
 46824b2c1b5702bf76f3e9353a2810d7 79018 mail extra 
dkim-filter_1.2.0.dfsg-1_i386.deb

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

iD8DBQFGhKCfd6jzajsEcIQRAnz9AKCtRAHMskR18x8ljaaO81kzRSmt4ACfccg8
zjdPunXdzrl9E2fvZxZzPQY=
=vCmw
-----END PGP SIGNATURE-----


Accepted:
dkim-filter_1.2.0.dfsg-1_i386.deb
  to pool/main/d/dkim-milter/dkim-filter_1.2.0.dfsg-1_i386.deb
dkim-milter_1.2.0.dfsg-1.diff.gz
  to pool/main/d/dkim-milter/dkim-milter_1.2.0.dfsg-1.diff.gz
dkim-milter_1.2.0.dfsg-1.dsc
  to pool/main/d/dkim-milter/dkim-milter_1.2.0.dfsg-1.dsc
dkim-milter_1.2.0.dfsg.orig.tar.gz
  to pool/main/d/dkim-milter/dkim-milter_1.2.0.dfsg.orig.tar.gz


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

Reply via email to