Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!wang!comm.wang.com!lws
From: lws@comm.wang.com (Lyle Seaman)
Newsgroups: comp.mail.sendmail
Subject: Re: '\n.\n' in body of mail
Message-ID: <1990Dec28.200505.11003@comm.wang.com>
Date: 28 Dec 90 20:05:05 GMT
References: <1990Dec14.141102.17655@mp.cs.niu.edu> <757@keele.keele.ac.uk> 	<1990Dec17.180410.2699@mp.cs.niu.edu> <BARNETT.90Dec19070428@grymoire.crd.ge.com>
Organization: Wang Labs, Platform Comms.
Lines: 25

Me again.  I started this off by wondering about why Sendmail truncates
input after the '\n.\n', and it's wandered a bit.  Some more details:

yes, it's running on a Sun, but it's not Sun's Sendmail.  I got rid of that.
No, there is no Oi flag currently, I put one in to try to deal with this,
but took it back out, because all deliveries were terminating ungracefully
when the connection went down.  
Yes, I'm using the X flag on the relevant mailer, but that's not the
problem.  The dots are being doubled going over the network, that's fine.

The problem is that I can't get a single dot ('\n.\n') INTO sendmail
("/usr/lib/sendmail -t <somefile") to see if that is doubled correctly,
and singled correctly by the other end...  

So I was trying to figure out why sendmail truncates stdin, and where.
If I do something like ("/usr/lib/sendmail -t -oi <somefile") isn't
that going to change the behavior of the code that handles the SMTP
protocol?  Hmmm.  Oi just says whether to take '\n.\n' as EOM, doesn't
it?  So the dot doubling should work the same way it used to.  And 
since this sendmail isn't receiving the '\n.\n', there shouldn't be
any problem with aborting connections.  Yeah, that just might work.

-- 
Lyle                  Wang           lws@capybara.comm.wang.com
508 967 2322     Lowell, MA, USA     Source code: the _ultimate_ documentation.