+* \231 considered harmful.
+
+ Header addresses that have the \231 character (and possibly others
+ in the range \201 - \237) behave in odd and usually unexpected ways.
+
+* DEC Alphas (OSF/1 1.3) sometimes time out on sending mail.
+
+ I have one report that DEC Alphas acting as SMTP clients sometimes
+ will apparently not see the "250 OK" message in response to the
+ dot that indicates the end of the message. This only happens if
+ the message is run from the queue -- if it gets through on first
+ try, everything is fine. I have been unable to reproduce this
+ problem at Berkeley.
+
+* accept() problem on SVR4.
+
+ Apparently, the sendmail daemon loop (doing accept()s on the network)
+ can get into a wierd state on SVR4; it starts logging ``SYSERR:
+ getrequests: accept: Protocol Error''. The workaround is to kill
+ and restart the sendmail daemon. We don't have an SVR4 system at
+ Berkeley that carries more than token mail load, so I can't validate
+ this. It is likely to be a glitch in the sockets emulation, since
+ "Protocol Error" is not possible error code with Berkeley TCP/IP.
+
+ I've also had someone report the message ``sendmail: accept:
+ SIOCGPGRP failed errno 22'' on an SVR4 system. This message is
+ not in the sendmail source code, so I assume it is also a bug
+ in the sockets emulation. (Errno 22 is EINVAL "Invalid Argument"
+ on all the systems I have available, including Solaris 2.x.)
+
+* 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.
+
+
++-------------------------------------------+
+| THE FOLLOWING PROBLEMS ARE FIXED IN 8.6.5 |
++-------------------------------------------+
+
+* Route-addrs missing angle brackets.
+
+ There are cases where route-addrs do not get angle brackets around them,
+ such as in the "-r" flag on mailers or in the From_ line created when
+ mailing to files.
+
+* No "exposed users" in "nullrelay" configuration.
+
+ The "nullrelay" configuration hides all addresses behind the mail
+ hub name. Some sites might prefer to expose some names such as
+ root. This information is always available in Received: lines.
+
+* owner-* alias that uses :include: broken.
+
+ If you have aliases set up as:
+
+ owner-listname: :include:/some/file
+
+ sendmail will break because it considers this a "sender address",
+ which is not permitted to use the :include: syntax. The easiest
+ workaround is to change this to:
+
+ owner-listname: :include:/some/file,
+
+ (note the trailing comma); a somewhat cleaner solution is to use:
+
+ owner-listname: listname-request
+ listname-request: :include:/some/file
+
+* "SYSERR: openmailer(local): fd 1 not open" message
+
+ 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.)
+
+(Version 8.15, last updated %G%)
projects / unix-history / blobdiff