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: <024a01c394bd$6967b580$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> <017a01c394b2$db44baf0$657ba8c0 AT neth DOT hp DOT com> <20031017134523 DOT GT25076 AT cygbert DOT vinschen DOT de>
Subject: Re: ssmtp 2.38.7-4 reads headers from message body.
Date: Fri, 17 Oct 2003 16:46:13 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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 03:30:39PM +0200, Frank Slootweg wrote:
[deleted]
> >   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".

  Sorry, but I do not agree. In a mail message (i.e. header(s) and
body/bodies), a "binary attachment" is not really binary. It is encoded
as 'text' (i.e. uuencode, base64, etc.) and those text lines can have a
normal text end-of-line, i.e. \r\n for 'DOS' and \n for UNIX.

[deleted]

> Erm... are you reading the cygwin announcements?

  No, I don't. Can you give a pointer where/how I can read "the cygwin
announcements"? Thanks.

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

  You would have to ask Urs et al whether or not this is a tin problem.
As shown in my 'basenote', I originally posted about this in the
news.software.readers Newsgroup. I'll report my findings there.
Personally I consider it normal that under Windows, tin will write
DOS-format text files (because some generic Windows stuff (for example
notepad) still has problems with UNIX-format). Until now most 'free'
software has been very transparent with regard to DOS and UNIX format
text. Case in point: I used to do most of my text stuff on UNIX systems
(at work). Now I'm doing most on my (private) Windows system. Most of my
old files are still UNIX format, but give no problems. So I think that
ssmtp is somewhat unique and somewhat 'broken'.

> Before I forget it:  PATCHES GRATEFULLY ACCEPTED!

  Don't hold your breath. I have only very limited programming
experience and none in a Cygwin environment, so this will probably be
too hard for me to patch.







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