improve exit status handling for program map code

[unix-history] / usr / src / usr.sbin / sendmail / KNOWNBUGS

diff --git a/usr/src/usr.sbin/sendmail/KNOWNBUGS b/usr/src/usr.sbin/sendmail/KNOWNBUGS
index d27ca23..a6d87c6 100644 (file)
--- a/usr/src/usr.sbin/sendmail/KNOWNBUGS
+++ b/usr/src/usr.sbin/sendmail/KNOWNBUGS
@@ -1,22 +1,18 @@
 
 
             K N O W N   B U G S   I N   S E N D M A I L
 
 
             K N O W N   B U G S   I N   S E N D M A I L

-                            (for 8.6.5)
+                            (for 8.6.9)

 
 
 The following are bugs or deficiencies in sendmail that I am aware of
 but which have not been fixed in the current release.  You probably
 want to get the most up to date version of this from FTP.CS.Berkeley.EDU
 
 
 The following are bugs or deficiencies in sendmail that I am aware of
 but which have not been fixed in the current release.  You probably
 want to get the most up to date version of this from FTP.CS.Berkeley.EDU

-in /ucb/sendmail/KNOWNBUGS.
+in /ucb/sendmail/KNOWNBUGS.  For descriptions of bugs that have been
+fixed, see the file RELEASE_NOTES (in the root directory of the sendmail
+distribution).

 
 

-* "SYSERR: openmailer(local): fd 1 not open" message
+This list is not guaranteed to be complete.

 
 

-  File descriptor 1 (standard output) should not be closed during normal
-  processing.  This is checked periodically, and sometimes this condition
-  is found and this message is produced.  Sendmail repairs the problem,
-  and the mail is still delivered, but I still don't know why it happens.
-  (There was a bug that was fixed in 8.6.beta.13 that might be related,
-  but I think this bug still exists.)

 
 * Null bytes are not handled properly.
 
 
 * Null bytes are not handled properly.
 


@@ -24,7 +20,8 @@ in /ucb/sendmail/KNOWNBUGS.
   any value from 0x01-0xFF in the body and 0x01-0x80 and 0xA0-0xFF in
   the header.  Notably missing is 0x00, which would require a major
   restructuring of the code -- for example, almost no C library support
   any value from 0x01-0xFF in the body and 0x01-0x80 and 0xA0-0xFF in
   the header.  Notably missing is 0x00, which would require a major
   restructuring of the code -- for example, almost no C library support

-  could be used to handle strings.
+  could be used to handle strings.  Fixed (for the message body only)
+  in 8.7.

 
 * Duplicate error messages.
 
 
 * Duplicate error messages.
 


@@ -72,7 +69,7 @@ in /ucb/sendmail/KNOWNBUGS.
   case is hostB, which is unknown.  It probably ought to eliminate
   hostB early in processing.
 
   case is hostB, which is unknown.  It probably ought to eliminate
   hostB early in processing.
 

-* NAME environment variables with commas break.
+* NAME environment variables with commas and unbalanced quotes break.

 
   If you define your NAME environment variable to have a comma
   (e.g., ``Lastname, Firstname''), and you are using the $q definition
 
   If you define your NAME environment variable to have a comma
   (e.g., ``Lastname, Firstname''), and you are using the $q definition


@@ -81,6 +78,9 @@ in /ucb/sendmail/KNOWNBUGS.
   can work around this by changing the $q definition to use
   ``address (name)''.
 
   can work around this by changing the $q definition to use
   ``address (name)''.
 

+  If you have an unbalanced double quote (e.g., ``Firstname"Lastname'')
+  the auto-quoting algorithm breaks.
+

 * \231 considered harmful.
 
   Header addresses that have the \231 character (and possibly others
 * \231 considered harmful.
 
   Header addresses that have the \231 character (and possibly others


@@ -111,4 +111,25 @@ in /ucb/sendmail/KNOWNBUGS.
   in the sockets emulation.  (Errno 22 is EINVAL "Invalid Argument"
   on all the systems I have available, including Solaris 2.x.)
 
   in the sockets emulation.  (Errno 22 is EINVAL "Invalid Argument"
   on all the systems I have available, including Solaris 2.x.)
 

-(Version 8.13, last updated %G%)
+* Sending user deletion not done properly in :include: lists.
+
+  If you don't have the "m" (me too) option set, then a person
+  sending to a list that contains themselves should not get a copy
+  of the message.  However, if that list points to a :include: file
+  that has one address per line, this will break, and the sender
+  will always get a copy of their own message, just as though the
+  "m" option were set.
+
+  You can eliminate this by adding commas at the end of each line
+  of the :include: file.
+
+* Excessive mailing list nesting can run out of file descriptors.
+
+  If you have a mailing list that includes lots of other mailing
+  lists, each of which has a separate owner, you can run out of
+  file descriptors.  Each mailing list with a separate owner uses
+  one open file descriptor (prior to 8.6.6 it was three open
+  file descriptors per list).  This is particularly egregious if
+  you have your connection cache set to be large.
+
+(Version 8.19, last updated %G%)