[comp.mail.misc] Sendmail-SMTP problem

doug@uwmcsd1.UUCP (11/22/86)

   We have been experiencing problems with sendmail when speaking SMTP 
to some sites on the Internet. Symptoms of the problem are
as follows: Our sendmail connects to the site to attempt to deliver
the mail message, it then sends the To, From and Data messages and
recieves acknowledgement for each. It then sends the Terminate
message but, times out waiting for a reply. Sendmail gives a
'read reply' error and puts the message back in the mailq. This occurs 
everytime it attempts to send the message and, we only experience this problem
when talking to certain sites. From what I have heard from people
on the recieving end they also get a timeout error and in some cases
the recipient gets an empty message everytime sendmail attempts to 
send the mail message (which tends to get rather annoying). 

   We are running 4.2BSD Unix on an ISI68000. Has anyone else experienced
this problem or know of a solution? 




Doug Tiarks
UW-Milwaukee Computing Services Div.
ARPA: doug@csd1.milw.wisc.edu
UUCP: {ihnp4, uwvax, uwmacc}!uwmcsd1!doug

cetron@utah-cs.UUCP (11/22/86)

In article <1524@uwmcsd1.UUCP> doug@uwmcsd1.UUCP (Doug Tiarks) writes:
>
>
>   We have been experiencing problems with sendmail when speaking SMTP 
>to some sites on the Internet. Symptoms of the problem are
>as follows: Our sendmail connects to the site to attempt to deliver
>the mail message, it then sends the To, From and Data messages and
>recieves acknowledgement for each. It then sends the Terminate
>message but, times out waiting for a reply. Sendmail gives a
>'read reply' error and puts the message back in the mailq. This occurs 
>everytime it attempts to send the message and, we only experience this problem

	I have lately been hacking to death the software tools mailer to work
with tek tcp/ip and have seen this kind of situation (or at least similar)

The software tools mailer has this 'problem' also....seems it will ack the
data packets, but NOT SEND THE   250 OK   message UNTIL it has succesfully
saved the message.  So, if the recipeint system is busy, timeout before
sending of  250 OK (and quit won't work yet since receiver is no yet
listening again)  or if the queing of the message is unable to complete 
the same situation could occur.

However, if you DO receive the 250 OK after send the <cr><lf>.<cr><lf> then
my scenario is wrong and then it sounds like a problem in the receiver of
some OTHER nature.

-ed cetron
center for engineering design
univ. of utah