Bob,

I had a similar problem with JTMAIL when I first used it where my message
text was becoming part of the subject.  I edited the source do transmit a
'new line' character after the subject and that took care of it.  The
problem would occur *only* when the message text had leading spaces.  I
informed Jim Wowchuk about it, he explained why it was being done that way
(I don't remember the explanation well, but it had something to do with
allowing sites to specify additional 'custom' headers) and also indicated
that he would fix it on subsequent releases.   I never got a 'newer' version
since there were additional 'mods' that I had made to our version so that it
would work 'better' in batch.

Below you'll find the section of code that I changed in order to correct the
'subject scope' error.

Regards

Paul H. Christidis
(310) 513-5808


         /* if there is a new subject, include it */
     if (gszSubject) {
         SendCmd(gsk, "Subject: %s", gszSubject);
         strcpy(buff, "\n");   /* Send new line to end subject */
         Transmit(gsk, buff, strlen(buff));
     }



______________________________ Reply Separator _________________________________
Subject: Question using JTMAIL
Author:  bob mcgregor <[log in to unmask]> at CCGATE
Date:    04/18/97 12:30 PM


I have downloaded JTMAIL and sucessfully sent e-mail with it, but the =
text of the message is ending up in the RFC header block of our e-mail =
client.  Does anyone know if there is a way, when sending the mail =
message to a mail server to specify RFC data with JTMAIL or is there a =
way, according to RFC specs, to identify end of RFC information?

TIA    Bob McGregor