Are you running Send Mail as a scheduled server script, or are you running it from a local client when connected to the filemaker file?
Send Mail is not supported as a filemaker server scheduled script:
If you're getting an error on the local machine though, you'll want to check to make sure your ISP or firewall is not blocking port 25, a lot of ISPs do to combat spam. Try using alternate port 587.
Also, what are your authentication settings and encryption settings? Those matter for troubleshooting this as well.
It will ultimately run as a scheduled server script. But, right now, I am just trying to make sure it works first, so local client for now.
1 of 1 people found this helpful
You'll need a server plugin, like 360works Email:
to perform a scheduled script for sending mail.
Else it's not natively supported by filemaker to run "send mail" as a scheduled script.
Thanks, I was not aware of that. I just checked to make sure it was compatible with the server. I will probaly use the plug in when the time comes.
I do need to authenticate. But when I type in my username and password on the FM Server SMTP Info page, it rejects it. And, I already tried various variations taking this into account (including a different port, such as the one you suggested 587) on FM.
Seems like it should be simple, doesn't it? But it's not.
SavvyData has a great example file that helps you automate testing of many different configurations and find the ones that actually work.
1 of 1 people found this helpful
Mike: Send Mail via SMTP is supported as a Server-Side script, but only with the Perform without Dialog option enabled. The Help file reference you linked to is ultimately, not correct. It would be better if FMI would just clarify what does work server-side.
Lizie33: +1 for checking out the Savvy Data blog/tool that Bruce recommended. I also recommend a plug-in that would run on the FM server, if your mail needs are anything more that basic.
If your needs are basic - and you can get the authentication issues sorted reliably - you can do this natively on the FM server. I have many databases doing this. I accomplished this by creating an "email" table in my solution. Whenever an action (script) needs to send email, it creates a record in the email table with the pertinent data. The email table also has a status field in it that automatically gets set to 0 upon creation. I then have a scheduled task that runs on the FM server every X number of minutes. This script finds all records in the email table with status of 0; loops through them sending them out via SMTP, and marks the status field with a 1. If the last error result of the Send Mail script step is anything other than 0, I set the error code in the email table record and act on this separately.
Thanks for clarifying that Doug, I've never gotten over some of the limitations and unreliability of the native functions so always use a plugin myself. Which incidentally is why I found the article above. I'll send that along with a note to Filemaker support, and hopefully they will update it.
I had already used SavvyData's fm file to run variations and they were all unsuccessful. But, I think I have to change the relaying settings on Exchange since I just realized that the IP address would probably be different.
Hard to tell when neither the URL or anything on the page stated what version of filemaker it was for.
I'll keep an eye out for /12help/ in links, but Filemaker could save us some grief by reorganizing legacy data into the correct structure.
True, they should make the version info more obvious. However, when you click the "home" link then you'll see that it shows "New features in FileMaker 10" etc.
FYI I was finally able to send e-mails successfully from the database and then use FM Server's scheduled tasks to run the script. But, the problem was not with the SMTP configuration, but rather the calculations in the fields "To," "CC," "BCC," and "Subject." Apparently, it refuses to send e-mails with ANY calculations in these fields. Also, multiple addresses must be written as follow:
Sorry but you have misunderstood several things about the SMTP Send Mail option.
We use the SMTP option extensively with a standard SMTP server.
mailto: is a URL protocol and is never used in an actual email address. The address "mailto:firstname.lastname@example.org" is invalid and will be ignored.
The TO, CC, and BCC entries can be calculations. But you must choose the Specify calculation option to enter the calculation and the results have to be well formed email addresses.
The separator between TO email addresses is dependent on the recipient SMTP service. The typical character used to separate addresses is the ";" semi-colon. Sometimes a comma or return are allowed. I suggest asking the SMTP server administrator how its been set up.
A valid email address list would typically be :
I hope that helps you get it working correctly.