[Bug 156500] Please backport dkim-milter 2.0.2.dfsg-1ubuntu1 to Gutsy/Feisty/Dapper

[Scott Kitterman]

Public bug reported:

dkim-milter (2.0.2.dfsg-1ubuntu1) hardy; urgency=low

  * Merge from Debian unstable. Remaining Ubuntu changes:
    - Change default connection method from socket to localhost port 8891 in
      debian/dkim-filter.default for Postfix chroot compatibility
    - In debian/DEBIAN.Readme describe the changes in default configuration
      and Postfix configuration changes needed to use dkim-filter
    - Change maintainer to MOTU
    - Add test/install of pid dir to debian/dkim-filter.postinst to be safe
    - Change debian/rules and debian/control to add dpatch (No patches
      currently needed)

dkim-milter  (2.0.2.dfsg-1) unstable; urgency=low

   * New upstream version
   * Created standalone libdkim2 and libdkim-dev packages
   * Install RELEASE_NOTES as upstream changelog
   * Fixed thinko in init script default socket
   * Add v= tag to example record in README.Debian since, as Scott
     Kitterman pointed out, it's now mandatory. Closes: #433717
   * Create $RUNDIR in init script if it doesn't exist. Closes: #433718

 -- Mike Markley <mike at markley.org>  Sun, 05 Aug 2007 16:31:50 -0700

** Affects: dapper-backports
     Importance: Undecided
         Status: New

** Affects: feisty-backports
     Importance: Undecided
         Status: New

** Affects: gutsy-backports
     Importance: Undecided
         Status: New

** Also affects: feisty-backports
   Importance: Undecided
       Status: New

** Also affects: dapper-backports
   Importance: Undecided
       Status: New

-- 
Please backport dkim-milter 2.0.2.dfsg-1ubuntu1 to Gutsy/Feisty/Dapper
https://bugs.launchpad.net/bugs/156500
You received this bug notification because you are a member of Ubuntu
Backporters, which is the bug contact for Dapper Backports.