As far as I can see, it is not possible to set the e-mail-address of the sender?
You are correct with the Send Mail script step:
Setting the From usually requires an authentication. You might research plug-in or mailing services where you may be able to set the "From" dynamically.
You select the email account that is sending the email in the email client. From is automatically set by the email account that sends the email.
I am totally happy with the e-mail client. Mostly because it is clear what you are going to send.
Choosing the sender is a small action. But of course it is a user action. And as such prone to error. The sender-address is dependent on the app. Client wants to keep the possibility to edit the text in the mail-body. So I'll leave it at that right now.
I'm agreeing with you! In a script set to send mail (with email client or SMTP, locally or on FMServer) there may be an advantage of sending email to allow FROM to be dynamic. Or it may be an advantage to use a "company email address" rather than a "user email address" for the FROM.
I'd love to have some way to get this value set for sending email! With correct authentication, of course, and without having to reveal the stored authentication.
Client wants to keep the possibility to edit the text in the mail-body.
Please note that this is also possible when using the other options for sending email. It's a common misconception that you can't, but it just takes a different approach to how you design the process of sending out an email.
You put text fields on a layout for showing/editing/creating the subject and body of your email, then use those text fields to create and send the needed email.
Am working on a project right now that uses this capability in my Employer's Solution. In my case, the user clicks to select a 'standard response' to another user's inquiry about a purchase order and what I am building puts that standard response into just such a pair of text fields. The user can see and edit both the subject and body thus produced to customize it to their needs before clicking send--which then queues up an email record in an email table where a server side scheduled script then uses a plug in to send out the email via smtp.
I Agree philmodjunk. But the customer doesn't want to pay for the extra development time.
Your solution is elegant and I am going to explore it too.
If you use smtp then it will use that email account. I recommend.
If you are using a email client then it uses the account that is setup on that user's computer. The email client let you specify a default email account. FM does not setup a new account in the users email client.
It prevents user from spoofing a user email account. Someone sending spam email and making it look like it was sent from a different email account.
I fully understand. I just felt it important to correct a common misconception about what you can do with Send Mail (with client email app) vs. What you can do with the other email options available. Keep in mind that others read discussions such as this one in search of answers to their own questions.
Again, sharing to the community at large rather than trying to change your mind, It may also be helpful to keep in mind some of the draw backs to using the client machine's email client:
Not all email apps are compatible. Your customer may change what computer they are using only to find that your solution's email no longer works because the email app and/or the OS is different.
The "email client" option depends also on the correct install of that "compatible" email app on the correct OS. Future updates of FileMaker, The email client software or the OS could cause send mail to fail in the future. This isn't totally eliminated by using SMTP, a plug in, web service or URL, but the number of possible "failure points" are less.
Retrieving data ...