*BSD News Article 18650


Return to BSD News archive

Xref: sserve comp.mail.sendmail:8040 comp.unix.bsd:12297
Path: sserve!newshost.anu.edu.au!munnari.oz.au!metro!sequoia!ultima!kralizec.zeta.org.au!kralizec.zeta.org.au!not-for-mail
From: nick@kralizec.zeta.org.au (Nick Andrew)
Newsgroups: comp.mail.sendmail,comp.unix.bsd
Subject: Re: SunOS 4.0 sendmail won't accept end-of-message
Date: 20 Jul 1993 23:03:43 +1000
Organization: Kralizec Dialup Unix Sydney: +61-2-837-1183 V.32bis
Lines: 46
Message-ID: <22gqffINN59j@kralizec.zeta.org.au>
References: <22e6rgINNqtv@kralizec.zeta.org.au>
NNTP-Posting-Host: kralizec.zeta.org.au

In <22e6rgINNqtv@kralizec.zeta.org.au> nick@kralizec.zeta.org.au (Nick Andrew) writes:

Summary: dot-termination problem solved but I need to port Sendmail 5.67
to SunOS anyway, so read on ...

>Sendmail asks for the message
>text and says "Enter . on a line by itself to finish the message" but it
>does not accept it when I type it.

There is a configuration option 'Oi' with the semantics "Ignore dots in
incoming messages" and that option was turned ON in my configuration file.

So much for the "well-known bug". It's my fault. I expected that option
would allow sendmail to pass incoming (stdin, not SMTP) mail directly
without the "." business.

>Eventually Sun's sendmail times out waiting for Linux to send something ...

The code in this place is a little strange. It can only break out of the
loop on EOF or ERROR, however I wasn't able to simulate this when typing
^D from telnet. Also there is a test for (OpMode == MD_SMTP) in which
one could easily say that if receiving mail using SMTP, never ignore
dots. Anyway fixed.

>I am now "porting" 5.67 to SunOS 4.0 however Sun's resolver library
>seems to have fewer functions than Sendmail 5.67 expects ... and so I
>just got the appropriate BSD lib.tar.Z and include.tar.Z via Ftp.

I compiled and linked them. There are many #ifdefs throughout the resolver
functions about which I don't have a clue. I defined only VMUNIX ... can
anybody help here? The others are (from a quick scan...) DBM, NDBM, LOG,
EXAMPLE_CODE (?), SETPROCTITLE, WNOHANG, DAEMON, NAMED_BIND, SMTP, HOSTINFO,
UGLYUUCP (darn right!), QUEUE, NO_WILDCARD_MX, SCANF and SMTPDEBUG.

When I run the new Sendmail it is able to function in a limited manner.
One problem is that when I connect to it, it takes 3+ minutes to display
the "220 Sendmail ... ready at ..." message. Another is that startup
processing (reading the .cf file) takes some minutes.

Time to continue debugging...

Nick.
-- 
Kralizec Dialup Unix (Public Access)    Data: +61-2-837-1183, 14400 24hrs 8N1
Zeta Microcomputer Software             Data: +61-2-837-1868, 2400 24hrs 8N1
P.O. Box 177, Riverstone NSW 2765       Plan: To beat Gnuchess 4.1 !