Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<40A0F567.F580ECBB@dessent.net>
Date:	Tue, 11 May 2004 08:46:47 -0700
From:	Brian Dessent <brian AT dessent DOT net>
Organization:	My own little world...
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: mailx mail replacement - solution in shell script
References:	<NUTMEGOeIiGXix4A2Dr0000006a AT NUTMEG DOT CAM DOT ARTIMI DOT COM>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

Dave Korn wrote:

> > Yes, it relies on MTA (and I thought that ssmtp is good default for
> > Cygwin) since original mailx does the same. Althought one could simply
> > use netcat, but that brakes SMTP protocol and this behaviour
> > is recently  becoming forbidden.
> 
>   I'm curious: in what way does using netcat break the smtp protocol?

I'm guessing because it just blasts the entire SMTP conversation at the
remote server and hopes that it accepts it.  The standard says you
musn't send anything until the server first sends its banner, and each
command waits for the status code of the previous, etc.  Some mailers
(e.g. exim) will drop the session with a "violated SMTP synchronization"
error.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -