diff options
Diffstat (limited to 'KNOWNBUGS')
| -rw-r--r-- | KNOWNBUGS | 96 |
1 files changed, 87 insertions, 9 deletions
@@ -1,7 +1,7 @@ K N O W N B U G S I N S E N D M A I L - (for 8.8.6) + (for 8.9.0) The following are bugs or deficiencies in sendmail that I am aware of @@ -37,7 +37,7 @@ This list is not guaranteed to be complete. * If you EXPN a list or user that has a program mailer, the output of EXPN will include ``@local.host.name''. You can't actually mail to - this address. It's not clear what the right behaviour is in this + this address. It's not clear what the right behavior is in this circumstance. * \231 considered harmful. @@ -48,7 +48,7 @@ This list is not guaranteed to be complete. * 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: + can get into a weird 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 @@ -65,15 +65,18 @@ This list is not guaranteed to be complete. * accept() problem on Linux. - Apparently, the accept() in sendmail daemon loop can return ETIMEDOUT - and cause sendmail to sleep for 5 seconds during which time no new - connections will be accepted. An error is reported to syslog: + The accept() in sendmail daemon loop can return ETIMEDOUT. An + error is reported to syslog: Jun 9 17:14:12 hostname sendmail[207]: NOQUEUE: SYSERR(root): getrequests: accept: Connection timed out "Connection timed out" is not documented as a valid return from - accept(2) and this is believed to be a bug in the Linux kernel. + accept(2) and this was believed to be a bug in the Linux kernel. + Later information from the Linux kernel group states that Linux + 2.0 kernels follow RFC1122 while sendmail follows the original BSD + (now POSIX 1003.1g draft) specification. The 2.1.X and later kernels + will follow the POSIX draft. * Excessive mailing list nesting can run out of file descriptors. @@ -103,5 +106,80 @@ This list is not guaranteed to be complete. account for the SMTP on-the-wire \r\n expansion. It probably doesn't allow for 8->7 bit MIME conversions either. - -(Version 8.25, last updated 6/13/97) +* Paths to programs being executed and the mode of program files are + not checked. Essentially, the RunProgramInUnsafeDirPath and + RunWritableProgram bits in the DontBlameSendmail option are always + set. This is not a problem if your system is well managed (that is, + if binaries and system directories are mode 755 instead of something + foolish like 777). + +* 8-bit data in GECOS field + + If the GECOS (personal name) information in the passwd file contains + 8-bit characters, those characters can be included in the message + header, which can cause problems when sending SMTP to hosts that + only accept 7-bit characters. + +* 8->7 bit MIME conversion + + When sendmail is doing 8->7 bit MIME conversions, and the message + contains certain MIME body types that cannot be converted to 7-bit, + sendmail will strip the message to 7-bit. + +* 7->8 bit MIME conversion + + If a message that is encoded as 7-bit MIME is converted to 8-bit and + that message when decoded is illegal (e.g., because of long lines or + illegal characters), sendmail can produce an illegal message. + +* MIME encoded full name phrases in the From: header + + If a full name phrase includes characters from MustQuoteChars, sendmail + will quote the entire full name phrase. If MustQuoteChars includes + characters which are not special characters according to STD 11 (RFC + 822), this quotation can interfere with MIME encoded full name phrases. + By default, sendmail includes the single quote character (') in + MustQuoteChars even though it is not listed as a special character in + STD 11. + +* bestmx map with -z flag truncates the list of MX hosts + + A bestmx map configured with the -z flag will truncate the list + of MX hosts. This prevents creation of strings which are too + long for ruleset parsing. This can have an adverse effect on the + relay_based_on_MX feature. + +* Saving to ~sender/dead.letter fails if su'ed to root + + If ErrorMode is set to print and an error in sending mail occurs, + the normal action is to print a message to the screen and append + the message to a dead.letter file in the sender's home directory. + In the case where the sender is using su to act as root, the file + safety checks prevent sendmail from saving the dead.letter file + because the sender's uid and the current real uid do not match. + +* Berkeley DB 2.X race condition with fcntl() locking + + There is a race condition for Berkeley DB 2.X databases on + operating systems which use fcntl() style locking, such as + Solaris. Sendmail locks the map before calling db_open() to + prevent others from modifying the map while it is being opened. + Unfortunately, Berkeley DB opens the map, closes it, and then + reopens it. fcntl() locking drops the lock when any file + descriptor pointing to the file is closed, even if it is a + different file descriptor than the one used to initially lock + the file. As a result there is a possibility that entries in a + map might not be found during a map rebuild. As a workaround, + you can use makemap to build a map with a new name and then + "mv" the new db file to replace the old one. + +* File open timeouts not available on hard mounted NFS file systems + + Since SIGALRM does not interrupt an RPC call for hard mounted + NFS file systems, it is impossible to implement a timeout on a file + open operation. Therefore, while the NFS server is not responding, + attempts to open a file on that server will hang. Systems with + local mail delivery and NFS hard mounted home directories should be + avoided, as attempts to open the forward files could hang. + +(Version 8.36, last updated 2/4/1999) |