masqmail-0.2

diff NEWS @ 48:f3bdb5b382ec

updated ChangeLog and NEWS
author meillo@marmaro.de
date Thu, 20 May 2010 21:22:33 +0200
parents 03817f849106
children b067916f7256
line diff
     1.1 --- a/NEWS	Thu May 20 21:21:22 2010 +0200
     1.2 +++ b/NEWS	Thu May 20 21:22:33 2010 +0200
     1.3 @@ -1,4 +1,4 @@
     1.4 -This files lists changes which may be important for you, especially
     1.5 +This NEWS file lists changes which may be important for you, especially
     1.6  in regard to compatiblity in upgrades.
     1.7  
     1.8  See ChangeLog file for more details and technical changes that don't
     1.9 @@ -10,13 +10,13 @@
    1.10  0.2.22
    1.11  
    1.12  - Hello, I'm meillo, the new maintainer and developer of masqmail. Oku
    1.13 -handed masqmail over to me, as he wasn't active anymore.
    1.14 +handed masqmail over to me, because he wasn't active anymore.
    1.15  
    1.16  - This release includes various fixes for problems in 0.2.21, mainly
    1.17  based on bugs from Debian.
    1.18  
    1.19  - Distribution specific data has been excluded from the distribution,
    1.20 -but is separately available on the website.
    1.21 +but is separately available on the project's website.
    1.22  
    1.23  - Man pages will not be generated from xml sources in future, but the
    1.24  nroff sources will be maintained directly.
    1.25 @@ -25,6 +25,7 @@
    1.26  /var/run/masqmail/masqmail-route, as it already was in the Debian
    1.27  package.
    1.28  
    1.29 +
    1.30  0.2.21
    1.31  
    1.32  - Retrospective: Probably, this version was not published in the usual
    1.33 @@ -33,9 +34,10 @@
    1.34  log files as user `mail'. It also changes the location for pid files;
    1.35  they are stored in /var/run/masqmail/ now.
    1.36  
    1.37 +
    1.38  0.2.18
    1.39  
    1.40 -- delivery warnings and failures are now also implermented if the
    1.41 +- delivery warnings and failures are now also implemented if the
    1.42  connection to a server fails. Because masqmail is designed for dialup
    1.43  networks, a connection failure will merely generate a warning by default.
    1.44  If you deliver in a local network and use the default local_net route,