Re: ssmtp 2.38.7-4 reads headers from message body.
Corinna Vinschen [EMAIL PROTECTED] wrote: On Sat, Oct 18, 2003 at 09:08:48PM +0200, Frank Slootweg wrote: Anything else you need? Your /etc/ssmtp/ssmtp.conf file would be interesting. Here it is (wrapped (at 72 columns) by OE): # # /etc/ssmtp.conf -- a config file for sSMTP sendmail. # # The person who gets all mail for userids 10 root=postmaster # The place where the mail goes. The actual machine name is required # no MX records are consulted. Commonly mailhosts are named mail.domain.com # The example will fit if you are in domain.com and you mailhub is so named. mailhub=smtp.cablewanadoo.nl # Where will the mail seem to come from? rewriteDomain=wanadoo.nl # The full hostname hostname=ipc1fs02.wanadoo.nl # Set this to never rewrite the From: line (unless not given) and to # use that address in the from line of the envelope. FromLineOverride=YES -- 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/
Re: ssmtp 2.38.7-4 reads headers from message body.
On Sat, Oct 18, 2003 at 09:08:48PM +0200, Frank Slootweg wrote: Anything else you need? Your /etc/ssmtp/ssmtp.conf file would be interesting. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] 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/
Re: ssmtp 2.38.7-4 reads headers from message body.
On Fri, Oct 17, 2003 at 04:46:13PM +0200, Frank Slootweg wrote:
Corinna Vinschen [EMAIL PROTECTED] 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.
[...]
So I think that
ssmtp is somewhat unique and somewhat 'broken'.
I've took some time to investigate the situation and I have to say that
I can't reproduce your effect. I created an appropriate testfile from
your template and regardless of having the file on a textmode mount or
a binmode mount, regardless of the shell in which I call `ssmtp -t file'
and regardless if the file has LF or CRLF lineendings, ssmpt always got
that right. Especially I found that ssmtp already opens the file in
textmode (yeah, I didn't remember) so the problem you found is even more
weird. Which means, I'll not change anything unless somebody (you?) can
explain what *exactly* goes wrong.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developermailto:[EMAIL PROTECTED]
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/
Re: ssmtp 2.38.7-4 reads headers from message body.
Corinna Vinschen [EMAIL PROTECTED] wrote:
On Fri, Oct 17, 2003 at 04:46:13PM +0200, Frank Slootweg wrote:
Corinna Vinschen [EMAIL PROTECTED] 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.
[...]
So I think that ssmtp is somewhat unique and somewhat 'broken'.
I've took some time to investigate the situation and I have to say
that I can't reproduce your effect. I created an appropriate testfile
from your template and regardless of having the file on a textmode
mount or a binmode mount, regardless of the shell in which I call
`ssmtp -t file' and regardless if the file has LF or CRLF
lineendings, ssmpt always got that right. Especially I found that
ssmtp already opens the file in textmode (yeah, I didn't remember) so
the problem you found is even more weird. Which means, I'll not
change anything unless somebody (you?) can explain what *exactly* goes
wrong.
Thanks for your efforts.
To be Frank :-), I am not aware that I have any special kind of
'mount'. I understand what you mean, but I have just a basic Cygwin
setup on my C: drive. The only related thing I can think of is that I
always specify Default Text File Type as Unix when I run Cygwin
Setup (I don't know what that does, but that is what I specify).
In my normal setup, tin is invoked from a DOS Command Prompt window
(i.e. not from bash) and tin invokes ssmtp as indicated in my
'basenote'. However after your posting, I tried in a bash shell and can
also reproduce the problem there:
$ /usr/sbin/ssmtp -t .letter.save
/usr/sbin/ssmtp: smtp server didn't accept RCPT To: command, replied
450 [EMAIL PROTECTED]: Sender address rejected: Domain not
found.
[EMAIL PROTECTED] ~
$
The [EMAIL PROTECTED] address is only in the body, so ssmtp
clearly gets the address from the body.
To show that it is really the DOS-format which is the problem:
$ cat .letter.save | /usr/sbin/ssmtp -t
/usr/sbin/ssmtp: smtp server didn't accept RCPT To: command, replied
450 [EMAIL PROTECTED]: Sender address rejected: Domain not
found.
Using cat(1) and a pipe to show that the problem is not related to
input redirection.
[EMAIL PROTECTED] ~
$ cat .letter.save | tr -d '\015' | /usr/sbin/ssmtp -t
[EMAIL PROTECTED] ~
$
I.e. without \r (\015), ssmtp works correctly.
Anything else you need?
It would be interesting to hear if other people can reproduce my
problem.
--
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/
Re: ssmtp 2.38.7-4 reads headers from message body.
Yesterday, I wrote: Of course ssmtp should only use the From: line from the header, not from the body. Suppose the body contained for example From: [EMAIL PROTECTED]. We would not want the message to be sent with that From: line, do we? :-) I did some more testing and found that ssmtp does apparently *not* use the To: line from the body. That would of course be even worse. Well, things *are* worse. Apparently ssmtp uses From: *and* To: from the body, but just not the way I thought. I did another test with four addresses, From: and To: in the header (FH and TH) and From: and To: in the body (FB and TB). ssmtp uses them as follows (when using the -t option): FH: OK, mail is sent with this From: address. TH: OK, mail is sent to this To: address. FB: Wrong, this address is set in a Return-Path: header (with uppercase downcased). TB: Wrong, mail is *also* sent to this address and shown in an Apparently-To: header. I hope we all agree that processing FB and TB is totally wrong. The body should not be interpreted in any way and mailing to TB is pretty annoying and potentially dangerous and mailing with a Return-Path: set to FB is misrepresenting the real sender. In hindsight, I probably agree with Felix van Hove that -t is not supported, because while ssmtp does not complain about -t, it says this when using -ba: /usr/sbin/ssmtp: -ba is not supported by sSMTP sendmail, nor is -t. OTOH, I also tried to use -FFrank Slootweg [EMAIL PROTECTED] [EMAIL PROTECTED] instead of -t. That works a little better because it does not send the message to TB, but it still sets FB in a Return-Path: header, which is really wrong. When using -d9 (debugging) you can see that ssmtp says Read Header: when reading the *body* (both with -t and with -F... -f... address). Does anybody have some other suggestions? Another tool which can do the same job (i.e. read From:, To:, Subject: (and possibly Cc: and Bcc:) only from the header part of the input file)? -- 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/
Re: ssmtp 2.38.7-4 reads headers from message body.
On Fri, Oct 17, 2003 at 10:57:27AM +0200, Frank Slootweg wrote: Does anybody have some other suggestions? Another tool which can do the same job (i.e. read From:, To:, Subject: (and possibly Cc: and Bcc:) only from the header part of the input file)? exim ? Gruss Olaf Föllinger -- Olaf Föllinger Berater S.E.S.A. Software und Systeme AG -- 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/
Re: ssmtp 2.38.7-4 reads headers from message body.
On Thu, Oct 16, 2003 at 07:33:32PM +0200, Frank Slootweg wrote: [I hope this reply is threaded correctly. The digest version of this list does not preserve References: etc.. I got a copy of your message from the archive and used ssmtp :-) to send it to myself (in OE).] Corinna Vinschen [EMAIL PROTECTED] wrote: On Thu, Oct 16, 2003 at 10:35:59AM +0200, Frank Slootweg wrote: [This is my first posting to this list. I hope the format is OK.] I am trying to use ssmtp (2.38.7-4) as my 'mailer' in tin, the newsreader. tin invokes ssmtp as /usr/sbin/ssmtp -t %F where %F is a file which contains the header (lines), a blank line (only \r\n) and body. I just saw this. Ssmtp checks for an empty line by testing the first character being a \n. I'm not familar with the mail-related RFCs. Is it allowed to send lines with DOS lineendings? In that case it's a fault in ssmtp. Otherwise... are you using textmode mounts? What editor are you using to create mails/news in tin? Please send also an attached cygcheck output as descibed on http://cygwin.com/problems.html. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] 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/
Re: ssmtp 2.38.7-4 reads headers from message body.
Corinna Vinschen [EMAIL PROTECTED] wrote in [EMAIL PROTECTED] 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.) Regards, -- Sam Edge -- 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/
Re: ssmtp 2.38.7-4 reads headers from message body.
On Fri, Oct 17, 2003 at 11:04:19AM +0100, Sam Edge wrote:
Corinna Vinschen [EMAIL PROTECTED] wrote in
[EMAIL PROTECTED]
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?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developermailto:[EMAIL PROTECTED]
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/
Re: ssmtp 2.38.7-4 reads headers from message body.
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 [EMAIL PROTECTED] wrote in
[EMAIL PROTECTED]
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...
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developermailto:[EMAIL PROTECTED]
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/
Re: ssmtp 2.38.7-4 reads headers from message body.
Corinna Vinschen [EMAIL PROTECTED] 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 [EMAIL PROTECTED] wrote in
[EMAIL PROTECTED]
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 ([EMAIL PROTECTED])?
--
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/
Re: ssmtp 2.38.7-4 reads headers from message body.
On Fri, Oct 17, 2003 at 03:30:39PM +0200, Frank Slootweg wrote:
Corinna Vinschen [EMAIL PROTECTED] 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 ([EMAIL PROTECTED])?
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 Developermailto:[EMAIL PROTECTED]
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/
Re: ssmtp 2.38.7-4 reads headers from message body.
Olaf Foellinger [EMAIL PROTECTED] wrote: On Fri, Oct 17, 2003 at 10:57:27AM +0200, Frank Slootweg wrote: Does anybody have some other suggestions? Another tool which can do the same job (i.e. read From:, To:, Subject: (and possibly Cc: and Bcc:) only from the header part of the input file)? exim ? Thanks for the pointer! As you can see in my other response, I already have a usable workaround for ssmtp (convert DOS-format input to UNIX-format), but exim may come in handy at some time. I installed it and played a little with it. Even without bothering to configure it, it 'automagically' worked, but then stopped working with mail stuck in the mail queue. As I have too litlle experience with sendmail (I only used it as a user, i.e. sendmail -t, not as an admin), it is not clear to me if I can only use exim -t inputfile or that I also have to run exim (with -bd?) as a daemon. Anyway, that is for the future. For the moment I can use ssmtp with UNIX-format input. But thanks again for your pointer! -- 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/
Re: ssmtp 2.38.7-4 reads headers from message body.
Corinna Vinschen [EMAIL PROTECTED] wrote in
[EMAIL PROTECTED]
in gmane.os.cygwin on Fri, 17 Oct 2003 12:26:54 +0200:
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...
Answered your own question. :-D
The translation between the SMTP stream's CRLF and the UNIX (or DOS
text-mode) LF is maybe done elsewhere?
Does ssmtp explicitly set stdin to be text-mode? If it's coming from a
UNIX background maybe not. Might be a simple fix then, to get it to do
so before starting to read?
Regards,
--
Sam Edge
--
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/
Re: ssmtp 2.38.7-4 reads headers from message body.
Corinna Vinschen [EMAIL PROTECTED] 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/
Re: ssmtp 2.38.7-4 reads headers from message body.
On Fri, 17 Oct 2003, Frank Slootweg wrote: Corinna Vinschen [EMAIL PROTECTED] wrote: 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. http://www.cygwin.com/ml/cygwin-announce/ But, better yet, just check /usr/share/doc/Cygwin/ssmtp-2.38.7.README for the current maintainer. Well..., it is only implied, I guess, by the tail: Have fun, Corinna -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- 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/
Re: ssmtp 2.38.7-4 reads headers from message body.
On Fri, Oct 17, 2003 at 04:46:13PM +0200, Frank Slootweg wrote: 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. http://cygwin.com/lists.html -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to [EMAIL PROTECTED] and be permanently blocked from mailing lists at sources.redhat.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/
ssmtp 2.38.7-4 reads headers from message body.
[This is my first posting to this list. I hope the format is OK.] I am trying to use ssmtp (2.38.7-4) as my 'mailer' in tin, the newsreader. tin invokes ssmtp as /usr/sbin/ssmtp -t %F where %F is a file which contains the header (lines), a blank line (only \r\n) and body. I have found that apparently ssmtp keeps reading 'header' lines (like From:, etc.) *after* it has read the full header, i.e. it also reads 'header' lines from the *body* of the message. For example it will fail (on the From: Frank Slootweg [EMAIL PROTECTED] line in the *body*) with the below input file. Of course sending a message which contains a header in the body is quite common, so at the moment I can not use ssmtp. Is this a known problem? Any solutions/workarounds/etc. (other than 'manually' quoting () the header lines in the body)? Thanks in advance for any and all responses. [start example input file:] From: Frank Slootweg [EMAIL PROTECTED] To: Frank Slootweg [EMAIL PROTECTED] Subject: ssmtp test -- forwarded message -- From: Frank Slootweg [EMAIL PROTECTED] Subject: Re: [tin +OE ] Use OE to mail from tin? Newsgroups: news.software.readers References: [EMAIL PROTECTED] Organization: NOYB Date: 11 Oct 2003 19:42:24 GMT Message-ID: [EMAIL PROTECTED] Thanks, Dirk and Urs. I probably first will have a look at the Cygwin ssmtp package. In hindsight, it probably isn't fair on tin to ask it to invoke OE. It is already sad that it 'has' to *run on* a virus, but asking it to willingly *invoke* one is plain cruel. My apologies! [1] [1] For the HI: :-) -- end of forwarded message -- [end example input file.] [Note: I am sending this with OE, which may and may not correctly preserve the blank line (^\r\n$) between the header and body. Of course I have tested things with a correct blank line.] -- 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/
Re: ssmtp 2.38.7-4 reads headers from message body.
On Thu, Oct 16, 2003 at 10:35:59AM +0200, Frank Slootweg wrote: [This is my first posting to this list. I hope the format is OK.] I am trying to use ssmtp (2.38.7-4) as my 'mailer' in tin, the newsreader. tin invokes ssmtp as /usr/sbin/ssmtp -t %F where %F is a file which contains the header (lines), a blank line (only \r\n) and body. I have found that apparently ssmtp keeps reading 'header' lines (like From:, etc.) *after* it has read the full header, i.e. it also reads 'header' lines from the *body* of the message. For example it will fail (on the From: Frank Slootweg [EMAIL PROTECTED] line in the *body*) with the below input file. More input. What means fail? What is ssmtp doing with the mail? Reading too much doesn't sound very desctructive to me. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] 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/
Re: ssmtp 2.38.7-4 reads headers from message body.
-t isn't supported, see man ssmtp. I have no problem to forward your message without this option, same ssmtp version 2.38.7. Felix Frank Slootweg wrote: [This is my first posting to this list. I hope the format is OK.] I am trying to use ssmtp (2.38.7-4) as my 'mailer' in tin, the newsreader. tin invokes ssmtp as /usr/sbin/ssmtp -t %F where %F is a file which contains the header (lines), a blank line (only \r\n) and body. I have found that apparently ssmtp keeps reading 'header' lines (like From:, etc.) *after* it has read the full header, i.e. it also reads 'header' lines from the *body* of the message. For example it will fail (on the From: Frank Slootweg [EMAIL PROTECTED] line in the *body*) with the below input file. Of course sending a message which contains a header in the body is quite common, so at the moment I can not use ssmtp. Is this a known problem? Any solutions/workarounds/etc. (other than 'manually' quoting () the header lines in the body)? Thanks in advance for any and all responses. [start example input file:] From: Frank Slootweg [EMAIL PROTECTED] To: Frank Slootweg [EMAIL PROTECTED] Subject: ssmtp test -- forwarded message -- From: Frank Slootweg [EMAIL PROTECTED] Subject: Re: [tin +OE ] Use OE to mail from tin? Newsgroups: news.software.readers References: [EMAIL PROTECTED] Organization: NOYB Date: 11 Oct 2003 19:42:24 GMT Message-ID: [EMAIL PROTECTED] Thanks, Dirk and Urs. I probably first will have a look at the Cygwin ssmtp package. In hindsight, it probably isn't fair on tin to ask it to invoke OE. It is already sad that it 'has' to *run on* a virus, but asking it to willingly *invoke* one is plain cruel. My apologies! [1] [1] For the HI: :-) -- end of forwarded message -- [end example input file.] [Note: I am sending this with OE, which may and may not correctly preserve the blank line (^\r\n$) between the header and body. Of course I have tested things with a correct blank line.] -- 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/ -- easynet GmbH (http://www.de.easynet.net) Felix van Hove, system integration Harburger Schlossstrasse 1, D-21079 Hamburg fon: +49-40-77175-457, fax: +49-40-77175-498 # easynet is part of the easynet group plc (www.easynetgroup.net) -- 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/
Re: ssmtp 2.38.7-4 reads headers from message body.
[I hope this reply is threaded correctly. The digest version of this list does not preserve References: etc.. I got a copy of your message from the archive and used ssmtp :-) to send it to myself (in OE).] Corinna Vinschen [EMAIL PROTECTED] wrote: On Thu, Oct 16, 2003 at 10:35:59AM +0200, Frank Slootweg wrote: [This is my first posting to this list. I hope the format is OK.] I am trying to use ssmtp (2.38.7-4) as my 'mailer' in tin, the newsreader. tin invokes ssmtp as /usr/sbin/ssmtp -t %F where %F is a file which contains the header (lines), a blank line (only \r\n) and body. I have found that apparently ssmtp keeps reading 'header' lines (like From:, etc.) *after* it has read the full header, i.e. it also reads 'header' lines from the *body* of the message. For example it will fail (on the From: Frank Slootweg [EMAIL PROTECTED] line in the *body*) with the below input file. More input. What means fail? What is ssmtp doing with the mail? Reading too much doesn't sound very desctructive to me. Sorry for not being clearer. With the example, ssmtp failed, i.e. it did not send a message. It should not have failed, but it failed because it used the (second) From: line from the *body*, and that From: line was invalid (From: Frank Slootweg [EMAIL PROTECTED]. It *should* have sent the message to the From: line in the *header* (From: Frank Slootweg [EMAIL PROTECTED]). The failure message was: /usr/sbin/ssmtp: smtp server didn't accept RCPT To: command, replied 450 [EMAIL PROTECTED]: Sender address rejected: Domain not found. (I don't know why the failure message says RCPT To: instead of From:.) Of course ssmtp should only use the From: line from the header, not from the body. Suppose the body contained for example From: [EMAIL PROTECTED]. We would not want the message to be sent with that From: line, do we? :-) I did some more testing and found that ssmtp does apparently *not* use the To: line from the body. That would of course be even worse. I hope this explains the problem better. -- 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/
Re: ssmtp 2.38.7-4 reads headers from message body.
Felix van Hove [EMAIL PROTECTED] wrote: -t isn't supported, see man ssmtp. I have no problem to forward your message without this option, same ssmtp version 2.38.7. I beg to differ (that -t isn't supported). (Of course) I have looked into this in detail before I posted. The SSMTP(8) manpage says: OPTIONS Most sendmail options are irrelevent to sSMTP. Those marked ``ignored'' or ``default'' have no effect on mail transfer. Those marked ``unsupported'' are fatal errors. Those marked ``simulated'' are not errors, but the result is for the program to exit with an informative message. A sort of fatal non-error. I.e. an unsupported option should give a fatal error, but -t does *not* give a fatal error if the From: address in the body is correct. Also the manual page says: -t Read message, searching for recipients. ``To:'', `Cc:'', and ``Bcc:'' lines will be scanned for people to send to. Any addresses in the argument list will be suppressed (not sup- ported). For all other options, (unsupported) is listed *directly after* the option, i.e. for example: -bd(unsupported) Run as a daemon. For the -t option it is listed at the *end* (and, to nit-pick, says not supported, not unsupported). I take it to mean that it only applies to the last sentence (Any addresses in the argument list will be suppressed). My tests prove my thinking, i.e. -t *is* processed. However ssmtp should not interpret the body of the message in any way (i.e. it should not interpret any From: line in the body), it should just send it. -- 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/
