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
Date: Fri, 17 Oct 2003 15:45:23 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: ssmtp 2.38.7-4 reads headers from message body.
Message-ID: <20031017134523.GT25076@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-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> <017a01c394b2$db44baf0$657ba8c0 AT neth DOT hp DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <017a01c394b2$db44baf0$657ba8c0@neth.hp.com>
User-Agent: Mutt/1.4.1i

On Fri, Oct 17, 2003 at 03:30:39PM +0200, Frank Slootweg wrote:
> Corinna Vinschen <corinna-cygwin AT cygwin DOT com> wrote:
> > 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.

Yeah, don't write the temporary files on a textmode mount.

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

Nope, that won't work as a generic solution.  Think "binary attachment".

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

Use the source, Luke!  Actually it can't.  It only handles \n but header
lines have a specific format which simplifies things.

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

Erm... are you reading the cygwin announcements?  I'm ssmtp maintainer
for Cygwin but there's no upstream maintainer. ssmtp development has
been abandoned.  Since you're the first one coming across that problem
I don't value it too high, especially since there's a workaround.
And I'm not sure if that's actually a ssmtp problem or if that's not
rather a tin problem.  Yes, I'm also tin maintainer for Cygwin...

Before I forget it:  PATCHES GRATEFULLY ACCEPTED!


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

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