CHANGES FROM VERSION 4.1.15 TO VERSION 4.1.16

Version 4.1.16 is a maintenance release in the 4.1 line.
Most of the changes from version 4.1.15 to version 4.1.16 are
minor bug fixes, or minor new features requested by customers.


The following new features have been added:

* The uuencode and uudecode programs can now handle base64 encoding
  as well as the original uuencode format.  [PR 949]


The following problems have been fixed:

* When an SMTP email message is rejected by the recvmail program, the
  log message now includes the text "Message rejected".  Previously, the
  logs could be interpreted as implying that the email message had been
  received.  [PR 913]

* The recvmail program now rejects email addresses where the domain name
  maps to an invalid IP address.  [PR 930]

* When a firewall that is licenced to use the Sophos anti virus
  interface receives an an email message from the Sophos Alert System
  that refers to an IDE file that already exists on the firewall, we
  previously ignored the duplicate.  We now attempt to download the IDE
  file anyway, in case there is a new version of the IDE fiel with the
  same file name.  [PR 934]

* When fetching updated for Sophos anti-virus IDE files, allow the
  remote server to use HTTP redirects, but limit the number of redirects
  and the permitted port numbers and domain names.  Previously, if the
  remote server used redirects, the download could fail due to packet
  filter settings.  [PR 910]

* The postmail program now treats the EX_UNAVAILABLE status from
  sendmail as a temporary error rather than as a permanent error.
  [PR 897]

* Errors during virus scanning of email messages now cause the email to
  be deferred and tried again later.  Previously, email messages could
  pass through without being scanned for viruses.  [PR 938]

* The postmail program now accepts email to <postmaster> (without a
  domain name), and to <postmaster@[i.p.address]>, as required by RFC
  2821.  [PR 939]2821.  [PR 939]

* If machines inside the firewall attempt to send traffic to many
  different destinations outside the firewall, the cdsgw and splitdns
  processes on the firewall could use so many resources that the
  firewall became almost unusable.  This problem was typically seen when
  machines inside the firewall were infected with viruses.  The firewall
  should now be much more responsive under similar conditions.  [PR 940]