Date: Mon, 19 Apr 1999 23:05:42 -0700 (PDT) From: jef@cs.miami.edu To: freebsd-gnats-submit@freebsd.org Subject: bin/11231: sendmail 3.9.1 kills the system dead when it receives a specific message from vm.sc.edu Message-ID: <19990420060542.C90A0152EF@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 11231 >Category: bin >Synopsis: sendmail 3.9.1 kills the system dead when it receives a specific message from vm.sc.edu >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Apr 19 23:10:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: jef moskot >Release: 3.0CAM-1998080806-SNAP >Organization: University of Miami >Environment: FreeBSD hurricane.cs.miami.edu 3.0CAM-19980806-SNAP FreeBSD 3.0CAM-19980806-SNAP #0: Thu Sep 10 14:24:20 EDT 1998 root@hurricane.cs.miami.edu:/usr/src/sys/c ompile/HURRICANE i386 >Description: A message was sent to a user at vm.sc.edu (W000232@VM.SC.EDU) from one of my users. This user no longer exists at vm.sc.edu, and some kind of automatic notification software keeps trying to deliver a message to our system that kills it dead (the system hangs and the only way to reboot is to cycle the power on the machine). The message sent had hundreds of users listed in the Bcc: field, which was the only abnormal thing about it. I don't know if the off-site machine knows about other addresses in the Bcc: field, so this might not have anything to do with the problem. >How-To-Repeat: Just reboot our machine and the offending file will try to be sent to hurricane.cs.miami.edu and will kill us dead. I have not attempted to send another message to that address, for fear that it will imprison another of our mail servers. >Fix: I have rerouted mail thru a different server on our side and for some reason this message does not attempt to connect to this server (or at least sendmail there (8.8.8) does not record any attempts. However, we are currently a prisoner of this message. If the sendmail daemon is turned on on hurricane, the system will take a dive within minutes. This has happened once before and we waited a week before routing mail back thru the original server and things were fine until another message was sent to that address. The message probably timed out on the other side, altho that is just a theory. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990420060542.C90A0152EF>