sending email not working

[MarkMLl]

Yes, that is for output and works with a program that runs until it gets a sigint or sigterm.

If a program is terminating immediately it sees no input and doesn't have an option to run until it sees an explicit EOF (i.e. pipe closure etc.) then it's obviously a problem. OTOH my experience with things like sendmail was that they ran until they got an explicit EOM, e.g.  .  as the first character of a line.

MarkMLl

[Remy Lebeau]

And if the command sees there is no bytes in the inputstream it could quit directly.
So my guess was that you first need to begin filling the inputstream before you do Execute.

Unless the command really waits before any input (which isn't certain).

According to https://marlam.de/msmtp/msmtp.html:

In its default mode of operation, it reads a mail from standard input...

So, it's safe to assume that it waits for the caller to enter input so it knows what to send.

[TRon]

I am also not familiar with the details of such piping as shown by your example Remy but could it perhaps be that msmtp sits and (ultimately) waits for a terminating character such as CR/LF or EOF ? (I am unfamiliar with what the piped stream actually sends to the command)

[MarkMLl]

I am also not familiar with the details of such piping as shown by your example Remy but could it perhaps be that msmtp sits and (ultimately) waits for a terminating character such as CR/LF or EOF ? (I am unfamiliar with what the piped stream actually sends to the command)

Or a dot at the start of a line, possibly by itself. That was "the UNIX way" in days of yore.

MarkMLl

[rvk]

Code: Pascal  [Select][+][-]

1. sp.Executable := 'msmpt';
2.  

When I run your code, it hangs up on L.LoadFromStream(sp.Output);. The program doesn't freeze or crash. It is just sitting at that line for an output from the command, but there is NO output from the command. Command executes and exits without no output. So, I not sure why this is.

You did change the msmpt to msmtp, didn't you? 

I did a quick test. There is no output so if you comment out the reading of the non-existing output, it will go through.

Code: Pascal  [Select][+][-]

1. program mailtest;
2. {$MODE OBJFPC}{$H+}
3. uses classes, sysutils, process;
4.  
5. const
6.   frommail = 'me@meme.com';
7.   tomail = 'me@meme.com';
8.  
9. function foo(): Boolean;
10. var
11.   sp: TProcess;
12.   L: TStringList;
13. begin
14.   L := TStringList.Create;
15.   sp := TProcess.Create(nil);
16.   try
17.     sp.Options := [poUsePipes];
18.     sp.Executable := 'msmtp';
19.     sp.Parameters.Add('--from=' + frommail);
20.     sp.Parameters.Add(tomail);
21.     sp.Execute;
22.     L.Text := 'Hello World';
23.     L.SaveToStream(sp.Input);
24.  
25.     {
26.     L.Clear;
27.     L.LoadFromStream(sp.Output);
28.     WriteLn(L.Text);
29.     }
30.  
31.     writeln('Exit status: ', sp.exitstatus);
32.     writeln('Exit code: ', sp.exitcode);
33.  
34.   finally
35.     sp.free;
36.     L.free;
37.   end;
38.   Result := true;
39. end;
40.  
41.  
42. begin
43.   writeln('Start');
44.   writeln('Date = ', {$i %DATE%});
45.   writeln('FPC target = ', {$i %FPCTARGET%});
46.   writeln('FPC target CPU = ', {$i %FPCTARGETCPU%});
47.   writeln('FPC target OS = ', {$i %FPCTARGETOS%});
48.   writeln('FPC version = ', {$i %FPCVERSION%});
49.  
50.   foo();
51.  
52. end.

Start
Date = 2024/06/14
FPC target = aarch64
FPC target CPU = aarch64
FPC target OS = Linux
FPC version = 3.3.1
Exit status: -1
Exit code: 0

[Remy Lebeau]

Code: Pascal  [Select][+][-]

1. sp.Executable := 'msmpt';

You did change the msmpt to msmtp, didn't you? 

  thanks, I fixed it in my earlier example.

[Awesome Programmer]

Sorry, I couldn't get back right away.

That's what I end up doing. Commented out the output part of the code and it went straight through.

What doesn't make sense is that after reading your comments about not receiving input characters or ending the inputstream with dots or CR/LF, well by the time the program reached the outputstream pause the email has already be sent and received.

just thought i should let them no...

Thank you for your answers and suggestions.

[MarkMLl]

What doesn't make sense is that after reading your comments about not receiving input characters or ending the inputstream with dots or CR/LF, well by the time the program reached the outputstream pause the email has already be sent and received.

All that indicates is that the mailer is not actually waiting for a . terminator or for further input. I wouldn't generally expect something in that position to be concerned about the lifetime of the program that's called it, which is what your final fix changed.

MarkMLl

[Remy Lebeau]

What doesn't make sense is that after reading your comments about not receiving input characters or ending the inputstream with dots or CR/LF, well by the time the program reached the outputstream pause the email has already be sent and received.

It does make sense, if you take into account that when using poUsePipes, TProcess.Execute() closes its end of the pipes it creates before exiting back to the caller.  So, when msmtp has read in all of the data from the stdin pipe, and the pipe has been closed, it knows there is no more data to read in and can send what data it did read.