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:	<017a01c394b2$db44baf0$657ba8c0@neth.hp.com>
From:	"Frank Slootweg" <franks_cygwin AT yahoo DOT com>
To:	<cygwin AT cygwin DOT com>
References:	<00be01c393c0$869213b0$647ba8c0 AT neth DOT hp DOT com> <20031016115054 DOT GH28997 AT cygbert DOT vinschen DOT de> <021e01c3940b$9ef6c770$647ba8c0 AT neth DOT hp DOT com> <20031017093307 DOT GK25076 AT cygbert DOT vinschen DOT de> <e5fvovkqm0m6l0coe2cpp78k89dvluh6qc AT 4ax DOT com> <20031017100840 DOT GN25076 AT cygbert DOT vinschen DOT de> <20031017102654 DOT GO25076 AT cygbert DOT vinschen DOT de>
Subject:	Re: ssmtp 2.38.7-4 reads headers from message body.
Date:	Fri, 17 Oct 2003 15:30:39 +0200
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
x-mimeole:	Produced By Microsoft MimeOLE V6.00.2600.0000
X-Antivirus:	avast! (VPS 13/10/2003), Outbound message
X-Antivirus-Status:	Clean

Corinna Vinschen <corinna-cygwin AT cygwin DOT com> wrote:
> On Fri, Oct 17, 2003 at 12:08:40PM +0200, Corinna Vinschen wrote:
> > On Fri, Oct 17, 2003 at 11:04:19AM +0100, Sam Edge wrote:
> > > Corinna Vinschen <corinna-cygwin AT cygwin DOT com> wrote in
> > > <20031017093307 DOT GK25076 AT cygbert DOT vinschen DOT de>
> > > in gmane.os.cygwin on Fri, 17 Oct 2003 11:33:07 +0200:
> > >
> > > > I'm not familar with the mail-related RFCs.  Is
> > > > it allowed to send lines with DOS lineendings?
> > >
> > > The RFCs for SMTP e-mail (RFC2821 and its predecesors) /require/
> > > CR-LF ("\r\n" i.e. "DOS") line endings. (Probably because
> > > debugging using dumb terminals or printers was easier that way in
> > > days of yore.)
> >
> > Interesting.  So a check as in ssmtp:
> >
> >   while ((fgets (buffer, sizeof buffer, stdin) != NULL) &&
(buffer[0] != '\n'))
> >     {
> >       /* It's a header line */
> >     }
> >
> > seems a bit oversimplified, right?
>
> Well, this happens when reading the input file.  When writing the
> output stream to the mailhub, it uses \r\n explicitely.
>
> So ssmtp assumes that the input file is using only \n.  Of course,
> ssmtp has never been written with textmode mounts in mind...

  Thanks! That is it! I converted the input file from DOS (\r\n) to UNIX
(\n) format and now ssmtp works correctly, i.e. it only reads From: and
To: from the header, not from the body. So now I only have to
incorporate this conversion into my tin (newsreader) setup.

  So my problem is solved, but what about the generic problem? IMO ssmtp
in a Cygwin environment should be able to handle DOS format data. AFAIK,
there are (POSIX? XPG?) standards for opening a stream in text mode,
which should make things compatible between ('DOS' and UNIX) platforms.
Anyway, even if ssmtp is supposed to be 'UNIX-only', then why can it
(apparently) handle DOS format lines *in* the header and *in* the body,
but not *between* the header and body?

  What happens now? Do the author(s)/maintainer(s) of ssmtp pick up this
issue? The Cygwin "Where should I send problem reports?" page
(<http://cygwin.com/problems.html>) requests not to send bug reports
directly to the author(s)/maintainer(s), but will they really pick up
bug reports from this high volume mailing list (cygwin AT cygwin DOT com)?







--
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 -