1.1 --- a/NEWS	Mon May 10 11:03:26 2010 +0200
     1.2 +++ b/NEWS	Mon May 10 12:26:54 2010 +0200
     1.3 @@ -1,6 +1,39 @@
     1.4 -Here I add changes which may be important for you. See ChangeLog for more
     1.5 -details and the manual pages for a more complete description
     1.6 -of added options.
     1.7 +This files lists changes which may be important for you, especially
     1.8 +in regard to compatiblity in upgrades.
     1.9 +
    1.10 +See ChangeLog file for more details and technical changes that don't
    1.11 +affect users directly.
    1.12 +
    1.13 +The manual pages describe newly added options. Take them for reference.
    1.14 +
    1.15 +
    1.16 +0.3.0
    1.17 +
    1.18 +- Hello, I'm meillo, the new maintainer and developer of masqmail. Oku
    1.19 +handed masqmail over to me, as he wasn't active anymore. I will release
    1.20 +new code with version numbers starting from 0.3.0 to ease dividing
    1.21 +between oku's releases and mine.
    1.22 +
    1.23 +- This release includes various fixes for problems in 0.2.21, mainly
    1.24 +based on bugs from Debian.
    1.25 +
    1.26 +- Distribution specific data has been excluded from the distribution,
    1.27 +but is separately available on the website.
    1.28 +
    1.29 +- Man pages will not be generated from xml sources in future, but the
    1.30 +nroff sources will be maintained directly.
    1.31 +
    1.32 +- The default online status file is now
    1.33 +/var/run/masqmail/masqmail-route, as it already was in the Debian
    1.34 +package.
    1.35 +
    1.36 +0.2.21
    1.37 +
    1.38 +- Retrospective: Probably, this version was not published in the usual
    1.39 +way by oku. I (meillo) grabbed it from Debian's package archive. It does
    1.40 +not introduce new functions but fixes security problems, such as writing
    1.41 +log files as user `mail'. It also changes the location for pid files;
    1.42 +they are stored in /var/run/masqmail/ now.
    1.43  
    1.44  0.2.18
    1.45  
    1.46 @@ -9,8 +42,7 @@
    1.47  networks, a connection failure will merely generate a warning by default.
    1.48  If you deliver in a local network and use the default local_net route,
    1.49  this would generte a failure. You can change this behaviour by setting
    1.50 -connect_error_fail
    1.51 -to either true or false in the route configurations.
    1.52 +'connect_error_fail' to either true or false in the route configurations.
    1.53  
    1.54  0.2.17
    1.55  
    1.56 @@ -125,7 +157,7 @@
    1.57  
    1.58  - there is a new option for the main conf: online_gets. Using this option,
    1.59  you can retrieve mail with just calling masqmail -go, masqmail will detect
    1.60 -whether it is online (similar to conect_routes (which is now called
    1.61 +whether it is online (similar to connect_routes (which is now called
    1.62  online_routes)).
    1.63  
    1.64  0.2.0
    1.65 @@ -155,7 +187,7 @@
    1.66  
    1.67  instead of
    1.68  
    1.69 -online_etect=mserver
    1.70 +online_detect=mserver
    1.71  mserver_iface="localhost:222"
    1.72  
    1.73  0.1.9