Xref: utzoo comp.sys.att:12130 comp.mail.sendmail:3027 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uwm.edu!linac!midway!mimsy!nocusuhs!nmrdc1!rdc30 From: rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson) Newsgroups: comp.sys.att,comp.mail.sendmail Subject: Sendmail-5.65+IDA-1.4.3 on AT&T 3B2 Message-ID: <1991Apr12.204413.9515@nmrdc1.nmrdc.nnmc.navy.mil> Date: 12 Apr 91 20:44:13 GMT Article-I.D.: nmrdc1.1991Apr12.204413.9515 Organization: Naval Medical Research & Development Command Lines: 28 I have been attempting to do this port with assistance from Neil Rickert, Paul Pomes and Mark Baushke, but with only limited success. Has anyone already done this? If not, perhaps someone has some insight into the following problem which has stymied the four of us. I can get it to compile and link with only a few warnings about int/pointer combinations. It works fine for resolving all sorts of addresses in test mode. It can even send local mail to users on the host. In daemon mode it can deliver incoming mail, although it attempts to send a failure message back to the originator. However, attempts to send a message via SMTP fail during the fprintf() call in smtpmessage() while sending the intial HELO message. I get a bus error -- core dump. Using the debugger shows the failure is occuring in an internal floating point routine, e_mant2(). We suspect something is munging the values in the FILE structs *SmtpOut, *SmtpIn, **outfile and **infile, but have been unable to track it down. Hopefully someone out there on the net has seen this behavior and can provide a fix. The OS is AT&T SysVR3.2.2 w/ WIN/TCP 3.0 (4.2BSD socket compatibility library). Thanks for any suggestions, -- Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil nmrdc1.nmrdc.nnmc.navy.mil | UUCP: ...uunet!mimsy!nmrdc1!rdc30 AT&T 3B2/600G Sys V R 3.2.2 | BITNET: dobson@usuhsb or nrd0mxd@vmnmdsc WIN/TCP for 3B2 | MCI-Mail: 377-2719 or 0003772719@mcimail.com