No. But there are several plugins like CNS's POP3It.
Also, be aware that FileMaker's send mail has a lot of limitations including the character set, number of attachments, lack of HTML support, etc. That is why people often use Mail plugins even though FileMaker has mail built in. For commercial purposes, I've used CNS's SMTPIt for large mail projects. It takes care of everything FileMaker left out of their support plus more.
I developed an email solution for Filemaker: Dotleft Project FileMailer 1.0
Version 1.0 is free for using permanently.
You can download my template on my website: www.dotleft.com
I use Plugin Mailit 5.0 to recieve email.
You can buy or download Mailit trial version on their website: http://www.dacons.net/fmplugins/mailit5/
1 of 1 people found this helpful
You could interact with a web script (php or something) that is capable of checking an email account and providing you with some data you could import by either setting the contents of a field from a URL or scraping a web viewer.
This wouldn't involve any plugins.
I want to emphasize what Mike is saying here: a lot of interaction with any mail server can be done outside of FM without plugins and have that "middleware" talk to FM on any of its APIs (CWP, XML, xDBC,...)
Thanks Mike Duncan for your response !!
Thanks wimdecorte !!!
But I think It will make my script complex ?
I just wanted to know that if there any simple script step or function.
Anirudh, if you want simple, use a plugin. That is why software develoipers make the plugins to make this simple for you.
If you have lots of knowledge and programming with other APIs that can connnect to FileMaker (PHP, XML, ODBC, JDBC), feel free to make use of them, but they clearly will be a lot more complicated and far beyond what most FileMaker users can handle.
I agree that when possible, it is good to make solutions without plugins so that they are more universal and avoids plugin licensing issues. But sometimes the best and easiest solution is that provided by a plugin. Keep in mind duplicating what a plugin does may take you weeks worth of work and you still will not get it as refined as the plugin developer. If the only thing you're trying to do is save a few hundred dollars in plugin licensing costs, then that just doesn't make financial sense (assuming your time is worth more than $10 an hour).
I just wanted to make the point that I've seen people have such aversions to plugins that they waste tons of time on workaround that are less elegant and end up costing much more in terms of your time.
There is another consideration to make: plugins work from inside FM, whereas middleware that uses the non plugin FM APIs work from outside FM. That means they can have less of an impact on the FM client, especially for periodic tasks like checking email.