360Works Email/Documentation

From 360Works Product Documentation Wiki
(Difference between revisions)
Jump to: navigation, search
m (Auto-upload documentation)
m (Auto-upload documentation)
 
(30 intermediate revisions by one user not shown)
Line 64: Line 64:
 
Note: Email is sent from whichever machine the plugin is being used on, be sure to open up port 25 for outgoing SMTP access on those machines.
 
Note: Email is sent from whichever machine the plugin is being used on, be sure to open up port 25 for outgoing SMTP access on those machines.
 
<h4>Displaying a name instead of the FROM address</h4>
 
<h4>Displaying a name instead of the FROM address</h4>
The "from" field can be either an email "address you@yourdomain.com" or a name and email address
+
The "from" field can be either an email address "you@yourdomain.com" or a name and email address
 
like "FirstName LastName &#060;you@yourdomain.com&#062;" instead.  Most email clients will then display the name in the from field instead of the address.
 
like "FirstName LastName &#060;you@yourdomain.com&#062;" instead.  Most email clients will then display the name in the from field instead of the address.
 
However, if the address is already in address book, most clients are configured to preempt with that associated name instead.
 
However, if the address is already in address book, most clients are configured to preempt with that associated name instead.
  
 
<h4>Sending Attachments</h4>
 
<h4>Sending Attachments</h4>
The [[#EmailAttachFile|EmailAttachFile]] accepts several different types of arguments.  You can pass in a container fielda URL, or a path.
+
The [[#EmailAttachFile|EmailAttachFile]] accepts several different types of arguments.  You can pass in a container field URL, or a path.
 
A URL can be to a resource on the web, or can be a file url pointing to a local file (e.g. <code>file:///path/to/attachment.jpg</code>).
 
A URL can be to a resource on the web, or can be a file url pointing to a local file (e.g. <code>file:///path/to/attachment.jpg</code>).
 +
 +
<h3>Bulk Mail</h3>
 +
When sending to multiple recipients, instead of creating a new message for each recipient, you can create a single message, connect once to your server, and then send the
 +
same message multiple times, switching the subject, recipients, and message body for each recipient.
 +
 +
// First connect to the SMTP server and create the message.
 +
Set Variable [ $msgCreate =
 +
    EmailConnectSMTP( "mail.example.com" ) and
 +
    EmailCreate( Email::from ; Email::to ; Email::subject ) and
 +
    EmailSetBody( GetAsCSS( Email::body ); "html" )
 +
]
 +
Go To Record/Request [ First ]
 +
Loop
 +
    Set Variable [ $setRecipients = EmailRecipients [ Email::to ] ]
 +
    Set Variable [ $msgSend = EmailSend ]
 +
    Go To Record/Request [ Next ; Exit After Last ]
 +
End Loop
 +
// We've sent the same message to all recipients. Now disconnect
 +
Set Variable [ $disconnect = EmailDisconnect ]
  
 
<h3>Reading Mail</h3>
 
<h3>Reading Mail</h3>
Line 102: Line 121:
 
  // which was created by the EmailReadMessages function
 
  // which was created by the EmailReadMessages function
 
  Import records [$$importUrl ; Update Matching]
 
  Import records [$$importUrl ; Update Matching]
  // disconnect from the IMAP server
+
  // Now disconnect from the IMAP server
  set variable $disconnect = EmailDisconnect
+
  Set Variable [ $disconnect = EmailDisconnect ]
 
  If [$disconnect = "ERROR"]
 
  If [$disconnect = "ERROR"]
 
     Show Custom Dialog [EmailLastError]
 
     Show Custom Dialog [EmailLastError]
Line 127: Line 146:
 
     Set Field[ImportedMessage::messageId ; EmailReadMessageValue( "messageId" )]
 
     Set Field[ImportedMessage::messageId ; EmailReadMessageValue( "messageId" )]
 
  End Loop
 
  End Loop
 +
 +
<h4>Microsoft Exchange Server</h4>
 +
To read mail from a Microsoft Exchange Server, you'll need to enable IMAP access on your exchange server.
 +
<a href="http://technet.microsoft.com/en-us/library/bb124489.aspx?ppud=4">This article</a> covers the steps for doing so.
 +
You may need to restart your server for this change to take effect.
 +
Once IMAP access is enabled, you can connect normally as described above.
  
 
<h3>Modifying Mail Messages</h3>
 
<h3>Modifying Mail Messages</h3>
Line 157: Line 182:
 
=Function Summary=
 
=Function Summary=
 
<div id="toc">
 
<div id="toc">
*[[#EmailAttachFile|EmailAttachFile]] ( data ) &mdash; Attach a file at a URL to an email message, from either a URL, container, or file path.
+
*[[#EmailChooseFile|EmailChooseFile]] ( { initialPath ; fileType ; title } ) &mdash; Shows a file chooser dialog where a user can browse her local hard drive.
*[[#EmailAttachFileInline|EmailAttachFileInline]] ( data ; contentId ) &mdash; Add an inline attachment to an HTML message.
+
*[[#EmailConnect|EmailConnect]] ( host_address_deprecated { ; user_deprecated ; password_deprecated } ) &mdash; Use {@link #EmailConnectSMTP} instead.
*[[#EmailBCCRecipients|EmailBCCRecipients]] ( bcc_addresses { ; append } ) &mdash; Set the BCC (blank carbon copy) recipients for the current message.
+
*[[#EmailGetMessageCount|EmailGetMessageCount]] ( { flag1 ; flag2 ; ... } ) &mdash; Returns a count of messages in a particular mailbox, INBOX is used if no mailbox is specified.
*[[#EmailBodySubstitute|EmailBodySubstitute]] ( searchString ; replaceString ) &mdash; Perform a substitute operation an the HTML or plain-text portion of the current HTML message.
+
*[[#EmailCCRecipients|EmailCCRecipients]] ( cc_addresses { ; append } ) &mdash; Set the CC (carbon copy) recipients for the current message.
+
*[[#EmailConnect|EmailConnect]] ( host_address_deprecated { ; user_deprecated ; password_deprecated } ) &mdash; Connect to a mail server.
+
*[[#EmailConnectIMAP|EmailConnectIMAP]] ( host ; username ; password { ; flag1 ; flag2 ; ... }  ) &mdash; Connect to an incoming IMAP mail server.
+
*[[#EmailConnectPOP|EmailConnectPOP]] ( host ; username ; password { ; flag1 ; flag2 ; ... } ) &mdash; Connect to an incoming POP mail server.
+
*[[#EmailConnectSMTP|EmailConnectSMTP]] ( host { ; username ; password ; flag1 ; flag2 ; ... } ) &mdash; Connect to an outgoing SMTP mail server.
+
*[[#EmailCreate|EmailCreate]] ( from ; to ; subject ) &mdash; Create a new email message, clearing any previous recipients and attachments.
+
*[[#EmailDisconnect|EmailDisconnect]] &mdash; Close any open connections to email servers established via the EmailConnect.
+
 
*[[#EmailGetNextMessage|EmailGetNextMessage]] &mdash; Loads a single message which was fetched in a previous call to the <code>EmailReadMessages</code> function.
 
*[[#EmailGetNextMessage|EmailGetNextMessage]] &mdash; Loads a single message which was fetched in a previous call to the <code>EmailReadMessages</code> function.
 +
*[[#EmailInboundIsConnected|EmailInboundIsConnected]] &mdash;
 
*[[#EmailLastError|EmailLastError]] &mdash; Returns detailed information about the last error generated by this plugin.
 
*[[#EmailLastError|EmailLastError]] &mdash; Returns detailed information about the last error generated by this plugin.
 
*[[#EmailLicenseInfo|EmailLicenseInfo]] &mdash; Retrieve information about the Email plugin licensing and version.
 
*[[#EmailLicenseInfo|EmailLicenseInfo]] &mdash; Retrieve information about the Email plugin licensing and version.
*[[#EmailListMailboxes|EmailListMailboxes]] ( { ; parent ; recursive } ) &mdash; Gets a return-separated list of mailboxes in a specific folder on the currently connected inbound mail server (Note: this is only useful for IMAP mailboxes, not POP).
+
*[[#EmailListMailboxes|EmailListMailboxes]] ( { parent ; recursive } ) &mdash; Gets a return-separated list of mailboxes in a specific folder on the currently connected inbound mail server (Note: this is only useful for IMAP mailboxes, not POP).
*[[#EmailMessageSetFlag|EmailMessageSetFlag]] ( flag { ; value } ) &mdash; Applies a flag to the current message, as retrieved by the function {@link #EmailGetNextMessage()}.
+
*[[#EmailOutboundIsConnected|EmailOutboundIsConnected]] &mdash;  
 
*[[#EmailOutgoingMessageId|EmailOutgoingMessageId]] &mdash; Returns the Message-ID of the last message sent using the Emailer plugin.
 
*[[#EmailOutgoingMessageId|EmailOutgoingMessageId]] &mdash; Returns the Message-ID of the last message sent using the Emailer plugin.
*[[#EmailQuickSend|EmailQuickSend]] ( from ; to ; subject ; body {; attachment } ) &mdash; Convenient way to send a single simple message to one or more recipients.
+
*[[#EmailReadAttachment|EmailReadAttachment]] ( path { ; savePath } ) &mdash; Read a downloaded attachment into a FileMaker container field.
*[[#EmailReadAttachment|EmailReadAttachment]] ( path ) &mdash; Read a downloaded attachment into a FileMaker container field.
+
 
*[[#EmailReadMessages|EmailReadMessages]] ( { flag1 ; flag2 ; ... } ) &mdash; Reads messages from the currently connected inbound mail server.
 
*[[#EmailReadMessages|EmailReadMessages]] ( { flag1 ; flag2 ; ... } ) &mdash; Reads messages from the currently connected inbound mail server.
 +
*[[#EmailReadMessagesFromFile|EmailReadMessagesFromFile]] ( file { ; charset=UTF-8 } ) &mdash; This reads messages from an non-directory <code>MBOX</code> file or raw message content file (<code>.
 
*[[#EmailReadMessageValue|EmailReadMessageValue]] ( key ) &mdash; Retrieves information about the last message which was gotten by the <code>EmailGetNextMessage</code> function.
 
*[[#EmailReadMessageValue|EmailReadMessageValue]] ( key ) &mdash; Retrieves information about the last message which was gotten by the <code>EmailGetNextMessage</code> function.
*[[#EmailRecipients|EmailRecipients]] ( to_addresses { ; append } ) &mdash; Set the TO recipients for the current message.
 
*[[#EmailRegister|EmailRegister]] ( licenseKey ; registeredTo ) &mdash; Registers the Email Plugin.
 
*[[#EmailSend|EmailSend]] &mdash; Send the current email, as specified in the {@link #EmailCreate} function.
 
*[[#EmailSetBody|EmailSetBody]] ( body { ; contentType ; characterSet } ) &mdash; Sets a body part of the current message.
 
*[[#EmailSetBodyFile|EmailSetBodyFile]] ( url ; embedResources ) &mdash; This is used to load an HTML document as the email body part.
 
*[[#EmailSetErrorCapture|EmailSetErrorCapture]] ( errorCapture ) &mdash;
 
*[[#EmailSetHeader|EmailSetHeader]] ( header ; value ) &mdash; Set a custom header in the message.
 
*[[#EmailSetSubject|EmailSetSubject]] ( subject ) &mdash; This allows you to customize the subject of the current outgoing email message, as specified in the {@link #EmailCreate} function.
 
 
*[[#EmailVersion|EmailVersion]] &mdash; Returns the version number of the Email plugin.
 
*[[#EmailVersion|EmailVersion]] &mdash; Returns the version number of the Email plugin.
 +
*[[#IM_GetBuddyIcon|IM_GetBuddyIcon]] ( service ; login ; password ; buddy ) &mdash; Returns a buddy's icon.
 +
*[[#IM_GetBuddyList|IM_GetBuddyList]] ( service ; login ; password ) &mdash; Connects to the messaging service (if necessary) and retrieves the user's buddy list.
 +
*[[#IM_GetBuddyStatusMessage|IM_GetBuddyStatusMessage]] ( service ; login ; password ; buddy ) &mdash; Returns a buddy's status.
 +
*[[#IM_GetBuddyStatusType|IM_GetBuddyStatusType]] ( service ; login ; password ; buddy ) &mdash; Returns a buddy's status type as one of the following: "online", "idle", "away", "mobile", or "offline".
 
*[[#IsValidEmail|IsValidEmail]] ( email ) &mdash; Convenience function for validating an email address.
 
*[[#IsValidEmail|IsValidEmail]] ( email ) &mdash; Convenience function for validating an email address.
 
</div>
 
</div>
 
=Function Detail=
 
=Function Detail=
<div id="EmailAttachFile"></div>
+
<div id="EmailChooseFile"></div>
==EmailAttachFile ( data ) ==
+
==EmailChooseFile ( { initialPath ; fileType ; title } ) ==
Attach a file at a URL to an email message, from either a URL, container, or file path.  For example:
+
Shows a file chooser dialog where a user can browse her local hard drive.  When the user selects a file or directory and clicks "OK" on the file chooser,
 +
this function returns the path to the selected file or directoryIf the user hits the cancel button, nothing is returned.
  
EmailAttachFile("http://localhost:8080/SuperContainer/123/RawData");
+
<h3>File Type</h3>
 +
By supplying a <code>fileType</code> parameter, you can allow the user to just select files, just select directories, or select both files and directories.  The default behavior is to only allow file selection.
  
-or-
 
  
EmailAttachFile("file:///path/to/invoice.pdf");
+
Note: specifying a fileType of "directories" or "files + directories" will cause a non-native file dialog to be used on some platforms, as the native dialogs may not support directory selection.
 
+
-or-
+
 
+
EmailAttachFile("/Macintosh HD/path/to/invoice.pdf");
+
 
+
-or-
+
 
+
EmailAttachFile(myTable::myContainerField);
+
 
+
You can call this multiple times to attach multiple files to a message.
+
 
+
Note on paths vs urls: This function can also accept a path (/path/to/file) instead of a file URL (file://path/to/file).  This is handy for attaching PDFs generated by FileMaker.
+
 
+
If called on a machine running Mac OS X, a file URL is created from a path by prepending the directory <code>/Volumes</code>  to the supplied path, since FileMaker includes the hard drive name in paths.
+
For example, <code>/MacintoshHD/Users/John Smith/Documents/</code> is converted to the file URL <code>file:///Volumes/MacintoshHD/Users/John Smith/Documents/</code>.
+
 
+
<div class="parameters"><strong>Parameters:</strong>
+
<dl><dt><code>data</code> <dd>a path to a file, or a URL pointing to a file to attach to the message.
+
</dl></div>
+
<div class="see"><strong>Returns:</strong> 1 on success, ERROR on error.
+
</div>
+
 
+
<div id="EmailAttachFileInline"></div>
+
==EmailAttachFileInline ( data ; contentId ) ==
+
Add an inline attachment to an HTML message.  If you are sending HTML email with embedded images or other resources, use this function to embed the resource files in the message.
+
 
+
For example:
+
 
+
EmailCreate("to@example.com"; "from@example.com"; "My Newsletter") and
+
EmailSetBody(
+
    "&lt;html&gt;&lt;body&gt;&lt;img src=\"cid:headergif123\"&gt;" &
+
    "This is an HTML message with embedded images" &
+
    "&lt;img src=\"cid:footergif456\"&gt;" &
+
    "&lt;/body&gt;&lt;/html&gt;";
+
    "html"
+
) and
+
EmailAttachFileInline( Globals::headerContainer ; "headergif123" ) and
+
EmailAttachFileInline( Globals::footerContainer ; "footergif456" ) and
+
EmailSend
+
 
+
 
+
<h3>Content IDs</h3>
+
When creating your HTML email message, reference inline containers using <code>cid:contentid</code>, where <code>contentid</code> is an arbitrary unique string you create for each inline attachment.
+
 
+
Your contentIds should be globally unique for a given image/file resource, as mail clients will use this to cache the contents of the message.
+
 
+
You should only use letters and numbers for your content ids, some mail clients have trouble with other characters.
+
 
+
<div class="parameters"><strong>Parameters:</strong>
+
<dl><dt><code>data</code> <dd>a path to a file, or a URL pointing to a file to attach to the message (see EmailAttachFile for valid arguments).
+
<dt><code>contentId</code> <dd>contentId of the attachment.
+
</dl></div>
+
<div class="see"><strong>See also:</strong>  [[#EmailAttachFile|EmailAttachFile]]
+
</div><div class="see"><strong>Returns:</strong> 1 on success, ERROR on error.
+
</div>
+
 
+
<div id="EmailBCCRecipients"></div>
+
==EmailBCCRecipients ( bcc_addresses { ; append } ) ==
+
Set the BCC (blank carbon copy) recipients for the current message.
+
This can be called multiple times before sending, to build up a list of recipients (set <code>append</code> to true if doing this).
+
 
+
<div class="parameters"><strong>Parameters:</strong>
+
<dl><dt><code>bcc_addresses</code> <dd>comma-separated list of addresses
+
<dt><code>append</code> <dd>whether to append the new addresses to existing ones, or overwrite them.
+
</dl></div>
+
<div class="see"><strong>Returns:</strong> 1 on success, ERROR if one or more addresses are invalid.
+
</div>
+
 
+
<div id="EmailBodySubstitute"></div>
+
==EmailBodySubstitute ( searchString ; replaceString ) ==
+
Perform a substitute operation an the HTML or plain-text portion of the current HTML message.  You can call this multiple times on the same message, using the same <code>searchString</code> each time.
+
Once a message is sent, the replaced values are reset to their original values.
+
 
+
This is useful if you are using [[#EmailSetBodyFile|EmailSetBodyFile]] to load static HTML content as the body part, but want to insert dynamic content in the body.  Or, if you are sending many emails and want to merge data into a static body text field.
+
 
+
<div class="parameters"><strong>Parameters:</strong>
+
<dl><dt><code>searchString</code> <dd>the text to replace
+
<dt><code>replaceString</code> <dd>the replacement text
+
</dl></div>
+
<div class="see"><strong>Returns:</strong> 1 on success, or "ERROR" on failure.
+
</div>
+
 
+
<div id="EmailCCRecipients"></div>
+
==EmailCCRecipients ( cc_addresses { ; append } ) ==
+
Set the CC (carbon copy) recipients for the current message.
+
This can be called multiple times before sending, to build up a list of recipients (set <code>append</code> to true if doing this).
+
  
 
<div class="parameters"><strong>Parameters:</strong>
 
<div class="parameters"><strong>Parameters:</strong>
<dl><dt><code>cc_addresses</code> <dd>comma-separated list of addresses
+
<dl><dt><code>initialPath</code> <dd>optional path to set the initial dialog selection to.  If empty, will default to the user's home directory.
<dt><code>append</code> <dd>whether to append the new addresses to existing ones, or overwrite them.
+
<dt><code>fileType</code> <dd>whether to allow <code>"files"</code>, <code>"directories"</code>, or both <code>"files + directories"</code>
 +
<dt><code>title</code> <dd>optional title string to display as the title of the FileChooser dialog
 
</dl></div>
 
</dl></div>
<div class="see"><strong>Returns:</strong> 1 on success, ERROR if one or more addresses are invalid.
+
<div class="see"><strong>Returns:</strong> Path to the selected file, nothing if no file was selected, or "ERROR" if an error occurred.
 
</div>
 
</div>
  
 
<div id="EmailConnect"></div>
 
<div id="EmailConnect"></div>
 
==EmailConnect ( host_address_deprecated { ; user_deprecated ; password_deprecated } ) ==
 
==EmailConnect ( host_address_deprecated { ; user_deprecated ; password_deprecated } ) ==
Connect to a mail server. This function should be called before sending or reading mail.  The username and password are optional, and may not be required for sending mail.
+
Use [[#EmailConnectSMTP|EmailConnectSMTP]] instead.  The username and password are optional, and may not be required for sending mail.
 
This establishes a connection to the email server. When you are finished getting/sending email, you should call [[#EmailDisconnect|EmailDisconnect]] to close the connection.
 
This establishes a connection to the email server. When you are finished getting/sending email, you should call [[#EmailDisconnect|EmailDisconnect]] to close the connection.
  
Line 306: Line 236:
 
</div>
 
</div>
  
<div id="EmailConnectIMAP"></div>
+
<div id="EmailGetMessageCount"></div>
==EmailConnectIMAP ( host ; username ; password { ; flag1 ; flag2 ; ... } ) ==
+
==EmailGetMessageCount ( { flag1 ; flag2 ; ... } ) ==
Connect to an incoming IMAP mail server. This function (or <code>EmailConnectPOP</code>) must be called before reading email messages from the server.
+
Returns a count of messages in a particular mailbox, INBOX is used if no mailbox is specified.
This establishes a connection to the email server. When you are finished getting/sending email, it is a good idea to call [[#EmailDisconnect|EmailDisconnect]] to close the connection.
+
 
+
Here is an example of connecting to a regular mail server:
+
 
+
Set Variable[$result =
+
    EmailConnectIMAP(
+
        "my_email_host" ;
+
        "username" ;
+
        "password"
+
    )
+
]
+
 
+
 
+
<h3>SSL Encryption</h3>
+
Use the optional arguments to enable SSL encryption by passing <code>"ssl=1"</code>.  If you are connecting to GMail, SSL encryption is required.
+
Here is an example of connecting to google mail (gmail) with SSL encryption:
+
 
+
Set Variable[$result =
+
    EmailConnectIMAP(
+
        "imap.gmail.com" ;
+
        "username" ;
+
        "password" ;
+
        '''"ssl=1"'''
+
    )
+
]
+
 
+
  
 
<div class="parameters"><strong>Parameters:</strong>
 
<div class="parameters"><strong>Parameters:</strong>
<dl><dt><code>host</code> <dd>the IMAP host address.  This parameter may contain a port number using a colon syntax, e.g. <code>imap.example.com:2525</code>
+
<dl><dt><code>flags</code> <dd>optional flags which control how messages are counted
<dt><code>username</code> <dd>The authentication username
+
<dt><code>password</code> <dd>The authentication password
+
<dt><code>args</code> <dd>Additional optional arguments (ssl).
+
 
</dl></div>
 
</dl></div>
<div class="see"><strong>See also:</strong>  [[#EmailDisconnect|EmailDisconnect]]
+
<div class="see"><strong>Returns:</strong> number of messages in the mailbox
</div><div class="see"><strong>Returns:</strong> 1 on successful connection, or "ERROR" if an error occurred (use EMailLastError in this case)
+
</div>
+
 
+
<div id="EmailConnectPOP"></div>
+
==EmailConnectPOP ( host ; username ; password { ; flag1 ; flag2 ; ... } ) ==
+
Connect to an incoming POP mail server. This function (or <code>EmailConnectIMAP</code>) must be called before reading email messages from the server.
+
This establishes a connection to the email server. When you are finished getting/sending email, it is a good idea to call [[#EmailDisconnect|EmailDisconnect]] to close the connection.
+
 
+
Here is an example of connecting to a regular mail server:
+
 
+
Set Variable[$result =
+
    EmailConnectPOP(
+
        "my_email_host" ;
+
        "username" ;
+
        "password"
+
    )
+
]
+
 
+
 
+
 
+
<h3>SSL Encryption</h3>
+
Use the optional arguments to enable SSL encryption by passing <code>"ssl=1"</code>.  If you are connecting to GMail, SSL encryption is required.
+
Here is an example of connecting to google mail (gmail) with SSL encryption:
+
 
+
Set Variable[$result =
+
    EmailConnectPOP(
+
        "pop.gmail.com" ;
+
        "username" ;
+
        "password" ;
+
        '''"ssl=1"'''
+
    )
+
]
+
 
+
 
+
<div class="parameters"><strong>Parameters:</strong>
+
<dl><dt><code>host</code> <dd>the POP host address.  This parameter may contain a port number using a colon syntax, e.g. <code>pop.example.com:2525</code>
+
<dt><code>username</code> <dd>The authentication username
+
<dt><code>password</code> <dd>The authentication password
+
<dt><code>args</code> <dd>Additional optional arguments (ssl).
+
</dl></div>
+
<div class="see"><strong>See also:</strong>  [[#EmailDisconnect|EmailDisconnect]]
+
</div><div class="see"><strong>Returns:</strong> 1 on successful connection, or "ERROR" if an error occurred (use EMailLastError in this case)
+
</div>
+
 
+
<div id="EmailConnectSMTP"></div>
+
==EmailConnectSMTP ( host { ; username ; password ; flag1 ; flag2 ; ... } ) ==
+
Connect to an outgoing SMTP mail server. This function must be called before sending mail.  The username and password are optional, and may not be required for sending mail, depending on your SMTP server's setup.
+
This establishes a connection to the email server. When you are finished getting/sending email, it is a good idea to call [[#EmailDisconnect|EmailDisconnect]] to close the connection.
+
 
+
Here is an example of connecting to a regular mail server:
+
 
+
Set Variable[$result =
+
    EmailConnectSMTP(
+
        "my_email_host" ;
+
        "username" ;
+
        "password"
+
    )
+
]
+
 
+
 
+
 
+
<h3>SSL Encryption</h3>
+
Use the optional arguments to enable SSL encryption by passing <code>"ssl=1"</code>.  If you are connecting to GMail, SSL encryption is required.
+
Here is an example of connecting to google mail (gmail) with SSL encryption:
+
 
+
Set Variable[$result =
+
    EmailConnectSMTP(
+
        "smtp.gmail.com:465" ;
+
        "username" ;
+
        "password" ;
+
        '''"ssl=1"'''
+
    )
+
]
+
 
+
 
+
<div class="parameters"><strong>Parameters:</strong>
+
<dl><dt><code>host</code> <dd>the SMTP host address.  This parameter may contain a port number using a colon syntax, e.g. <code>smtp.example.com:2525</code>
+
<dt><code>username</code> <dd>The optional SMTP authentication username
+
<dt><code>password</code> <dd>The optional SMTP authentication password
+
<dt><code>args</code> <dd>Additional optional arguments (ssl).
+
</dl></div>
+
<div class="see"><strong>See also:</strong>  [[#EmailDisconnect|EmailDisconnect]]
+
</div><div class="see"><strong>Returns:</strong> 1 on successful connection, or "ERROR" if an error occurred (use EMailLastError in this case)
+
</div>
+
 
+
<div id="EmailCreate"></div>
+
==EmailCreate ( from ; to ; subject ) ==
+
Create a new email message, clearing any previous recipients and attachments.
+
 
+
<div class="parameters"><strong>Parameters:</strong>
+
<dl><dt><code>from</code> <dd>the FROM address for the new message. Use "Name &#060;you@domain.com&#062;" for displaying the name instead.
+
<dt><code>to</code> <dd>the TO address for the new message
+
<dt><code>subject</code> <dd>the SUBJECT of the new message
+
</dl></div>
+
<div class="see"><strong>Returns:</strong> 1 on success
+
</div>
+
 
+
<div id="EmailDisconnect"></div>
+
==EmailDisconnect==
+
Close any open connections to email servers established via the EmailConnect... functions.
+
 
+
<div class="see"><strong>See also:</strong>  [[#EmailConnectSMTP|EmailConnectSMTP]]
+
</div><div class="see"><strong>Returns:</strong> 1 on success
+
 
</div>
 
</div>
  
Line 461: Line 259:
 
</div><div class="see"><strong>Returns:</strong> 1 if a message is loaded, 0 if there are no more messages, or ERROR if an error occurred.
 
</div><div class="see"><strong>Returns:</strong> 1 if a message is loaded, 0 if there are no more messages, or ERROR if an error occurred.
 
</div>
 
</div>
 +
 +
<div id="EmailInboundIsConnected"></div>
 +
==EmailInboundIsConnected==
 +
 +
 +
  
 
<div id="EmailLastError"></div>
 
<div id="EmailLastError"></div>
Line 478: Line 282:
  
 
<div id="EmailListMailboxes"></div>
 
<div id="EmailListMailboxes"></div>
==EmailListMailboxes ( { ; parent ; recursive } ) ==
+
==EmailListMailboxes ( { parent ; recursive } ) ==
 
Gets a return-separated list of mailboxes in a specific folder on the currently connected inbound mail server (Note: this is only useful for IMAP mailboxes, not POP).
 
Gets a return-separated list of mailboxes in a specific folder on the currently connected inbound mail server (Note: this is only useful for IMAP mailboxes, not POP).
  
Line 489: Line 293:
 
</div>
 
</div>
  
<div id="EmailMessageSetFlag"></div>
+
<div id="EmailOutboundIsConnected"></div>
==EmailMessageSetFlag ( flag { ; value } ) ==
+
==EmailOutboundIsConnected==
Applies a flag to the current message, as retrieved by the function [[#EmailGetNextMessage|EmailGetNextMessage]].
+
 
Note that you must call [[#EmailReadMessages|EmailReadMessages]] with a parameter of <code>readonly=false</code> to use this function.
+
 
The allowed flags are:
+
<ul>
+
<li>deleted</li>
+
<li>replied (IMAP only)</li>
+
<li>draft (IMAP only)</li>
+
<li>flagged (IMAP only)</li>
+
<li>viewed (IMAP only)</li>
+
<li>recent (IMAP only)</li>
+
</ul>
+
<strong>POP</strong> vs <strong>IMAP</strong>.  POP accounts typically do not support persistent flags, so if you flag a message as <code>deleted</code> in a <strong>POP</strong> account,
+
it will be <em>permanently deleted</em>
+
when you disconnect from the server.
+
  
<div class="parameters"><strong>Parameters:</strong>
 
<dl><dt><code>flag</code> <dd>one of the named flags to set
 
<dt><code>value</code> <dd>the optional value to set the flag to. Default is <code>1</code> (or <code>true</code>).
 
</dl></div>
 
<div class="see"><strong>Returns:</strong> 1 on successful delete, or "ERROR" if an error occurred (use EMailLastError in this case)
 
</div>
 
  
 
<div id="EmailOutgoingMessageId"></div>
 
<div id="EmailOutgoingMessageId"></div>
Line 518: Line 304:
  
 
<div class="see"><strong>Returns:</strong> a Message-ID value, or &quot;&quot; if there was no available message.
 
<div class="see"><strong>Returns:</strong> a Message-ID value, or &quot;&quot; if there was no available message.
</div>
 
 
<div id="EmailQuickSend"></div>
 
==EmailQuickSend ( from ; to ; subject ; body {; attachment } ) ==
 
Convenient way to send a single simple message to one or more recipients.
 
 
See [[#EmailAttachFile|EmailAttachFile]] for more information about how to attach a file.
 
 
<div class="parameters"><strong>Parameters:</strong>
 
<dl><dt><code>from</code> <dd>The &quot;from&quot; email address.  Use "Name &#060;you@domain.com&#062;" for displaying the name instead.
 
<dt><code>to</code> <dd>A comma-separated list of &quot;to&quot; email addresses
 
<dt><code>subject</code> <dd>The subject of the message
 
<dt><code>body</code> <dd>The message body.  If the body starts with <code>&lt;html</code> it is assumed to be an HTML-formatted message.
 
<dt><code>attachment</code> <dd>A container holding an attachment to include with the email, or a URL or path to a file to attach.
 
</dl></div>
 
<div class="see"><strong>Returns:</strong> 1 on success, or "ERROR" if something went wrong
 
 
</div>
 
</div>
  
 
<div id="EmailReadAttachment"></div>
 
<div id="EmailReadAttachment"></div>
==EmailReadAttachment ( path ) ==
+
==EmailReadAttachment ( path { ; savePath } ) ==
 
Read a downloaded attachment into a FileMaker container field.  To download attachments, you must pass <code>attachments=true</code> as a parameter to the [[#EmailReadMessages|EmailReadMessages]] function.
 
Read a downloaded attachment into a FileMaker container field.  To download attachments, you must pass <code>attachments=true</code> as a parameter to the [[#EmailReadMessages|EmailReadMessages]] function.
  
Line 553: Line 323:
 
<div class="parameters"><strong>Parameters:</strong>
 
<div class="parameters"><strong>Parameters:</strong>
 
<dl><dt><code>path</code> <dd>The path as returned in the email import
 
<dl><dt><code>path</code> <dd>The path as returned in the email import
 +
<dt><code>savePath</code> <dd>An optional path parameter to save the attachment to a local folder instead of a container field
 
</dl></div>
 
</dl></div>
 
<div class="see"><strong>Returns:</strong> container data for the file at <code>path</code>, or "ERROR" if an error occurred (use EmailLastError in this case)
 
<div class="see"><strong>Returns:</strong> container data for the file at <code>path</code>, or "ERROR" if an error occurred (use EmailLastError in this case)
Line 568: Line 339:
 
The Email plugin supports reading messages from POP and IMAP mailboxes.  Typically, you're interested in only fetching new messages from your mailbox.  There are several approaches to doing this.
 
The Email plugin supports reading messages from POP and IMAP mailboxes.  Typically, you're interested in only fetching new messages from your mailbox.  There are several approaches to doing this.
  
<h4>Option 1: Search by UID (IMAP only)</h4>
+
<h4>Option 1: Search by UID (IMAP or POP3)</h4>
IMAP mailboxes assign each message a unique UID.  When reading messages from an IMAP mailbox, you can get the value for this UID with the following function:
+
<b>Note:</b> POP3 mail servers are not required to support UIDs. Please check with the server administrator about UID support.
 +
IMAP and POP3 mailboxes assign each message a unique UID.  When reading messages from an IMAP or POP3 mailbox, you can get the value for this UID with the following function:
  
 
  Set Field[ImportedMessage::uid ; EmailReadMessageValue( "uid" ) ]
 
  Set Field[ImportedMessage::uid ; EmailReadMessageValue( "uid" ) ]
Line 581: Line 353:
 
  ]
 
  ]
  
This fetches only the messages whose UID is greater than the most recently fetched message.  This is the preferred way to fetch new messages from an IMAP mailbox, as it is very efficient, doesn't modify any messages, and will work even if another email client accesses the mailbox.
+
This fetches only the messages whose UID is greater than the most recently fetched message.  This is the preferred way to fetch new messages from a mailbox, as it is very efficient, doesn't modify any messages, and will work even if another email client accesses the mailbox.
  
  
Line 631: Line 403:
 
<dt>progress
 
<dt>progress
 
<dd>Whether to show a cancellable progress bar (default is false).
 
<dd>Whether to show a cancellable progress bar (default is false).
 +
<dt>progressLocation
 +
<dd>Location of the progress bar, e.g. &quot;<code>100,200</code>&quot;. Default is centered on-screen.
 
<dt>mailbox
 
<dt>mailbox
 
<dd>The name of the mailbox to read messages from (Note: this is only useful for IMAP accounts).  The default behavior is to read messages from the <code>INBOX</code>.
 
<dd>The name of the mailbox to read messages from (Note: this is only useful for IMAP accounts).  The default behavior is to read messages from the <code>INBOX</code>.
 
<dt>attachments
 
<dt>attachments
<dd>Boolean flag indicating whether to download attachment data.  The default value is <code>false</code>, which disables attachment downloading.  This is significantly faster.
+
<dd>Boolean flag indicating whether to download attachment data.  The default value is <code>true</code>, which enables attachment downloading.  Setting this to <code>false</code> will disable downloading attachments, which can be significantly faster.
If attachment downloading is disabled, you can still retrieve a list of the attachments in a message using the <code>EmailReadMessageValue ( "attachments" )</code> function.  You can the re-read the message at a later time to download the attachments (see the EmailClient.fp7 example file).
+
If attachment downloading is disabled, you can still retrieve a list of the attachments in a message using the <code>EmailReadMessageValue ( "attachments" )</code> function.  You can the re-read the message at a later time to download the attachments.
  
 
<dt>skip
 
<dt>skip
Line 642: Line 416:
 
<dd>Do not return more than this many records in the import
 
<dd>Do not return more than this many records in the import
 
<dt>uid
 
<dt>uid
<dd>(IMAP only) only fetch messages whose <code>uid</code> is newer than the one passed in.  This is very useful for only fetching new messages from IMAP mailboxes.  When looping through new messages, call <code>EmailReadMessageValue("uid")</code> on the last message and save this to a field in your database.  Then when fetching new messages, pass this <code>uid</code> in as a filter argument. Only newer messages will be returned.  <strong>Note:</strong> if you specify this option and the mailbox is an IMAP mailbox, all other search filters (skip, max, to, from, date, etc) will be ignored.
+
<dd>(<b>Note:</b> not all POP3 mail servers support UIDs) only fetch messages whose <code>uid</code> is newer than the one passed in.  This is very useful for only fetching new messages from IMAP mailboxes.  When looping through new messages, call <code>EmailReadMessageValue("uid")</code> on the last message and save this to a field in your database.  Then when fetching new messages, pass this <code>uid</code> in as a filter argument. Only newer messages will be returned.  <strong>Note:</strong> if you specify this option and the mailbox is an IMAP mailbox, some of the other search filters (skip, to, from, date) will be ignored.
 +
<dt>dateFrom
 +
<dd>Filter messages to only return messages sent on or after a certain date (some IMAP mailboxes require an additional flag of "deleted=any" for EmailReadMessages to read emails using this parameter).
 +
<dt>dateTo
 +
<dd>Filter messages to only return messages sent on or before a certain date (some IMAP mailboxes require an additional flag of "deleted=any" for EmailReadMessages to read emails using this parameter).
 
<dt>from
 
<dt>from
 
<dd>Filter messages by <code>from</code> address
 
<dd>Filter messages by <code>from</code> address
Line 658: Line 436:
 
<dd>Filter messages by their flagged status.  Pass <code>true</code> to return only flagged messages, <code>false</code> to return only non-flagged messages.
 
<dd>Filter messages by their flagged status.  Pass <code>true</code> to return only flagged messages, <code>false</code> to return only non-flagged messages.
 
<dt>deleted
 
<dt>deleted
<dd>Filter messages by their deleted status.  Pass <code>true</code> to return only deleted messages, <code>false</code> to return only non-deleted messages.
+
<dd>Filter messages by their deleted status.  Pass <code>true</code> to return only deleted messages, <code>false</code> to return only non-deleted messages The default is <code>false</code>, meaning deleted message will be excluded.
 +
<div class=version2>
 +
<dt>alternateDecoding
 +
<dd>Use an alternate method of decoding retrieved emails. Please contact 360Works if you are unsure of when to use this parameter. Pass <code>1</code> to enable (e.g., "alternateDecoding=1"). The alternate decoding method is disabled by default
 +
</div>
 
<dt>readonly
 
<dt>readonly
 
<dd>Whether to open the mailbox folder as readonly or read-write.  The default is <code>true</code> (read-only).
 
<dd>Whether to open the mailbox folder as readonly or read-write.  The default is <code>true</code> (read-only).
Line 681: Line 463:
 
<div class="see"><strong>See also:</strong>  [[#EmailConnectIMAP|EmailConnectIMAP]],  [[#EmailConnectPOP|EmailConnectPOP]],  [[#EmailGetNextMessage|EmailGetNextMessage]],  [[#EmailReadMessageValue|EmailReadMessageValue]]
 
<div class="see"><strong>See also:</strong>  [[#EmailConnectIMAP|EmailConnectIMAP]],  [[#EmailConnectPOP|EmailConnectPOP]],  [[#EmailGetNextMessage|EmailGetNextMessage]],  [[#EmailReadMessageValue|EmailReadMessageValue]]
 
</div><div class="see"><strong>Returns:</strong> The URL of the local XML file.  This URL can be passed to FileMaker as the XML data source location.
 
</div><div class="see"><strong>Returns:</strong> The URL of the local XML file.  This URL can be passed to FileMaker as the XML data source location.
 +
</div>
 +
 +
<div id="EmailReadMessagesFromFile"></div>
 +
==EmailReadMessagesFromFile ( file { ; charset=UTF-8 } ) ==
 +
This reads messages from an non-directory <code>MBOX</code> file or raw message content file (<code>.eml</code>), and stores the parsed messages in an FMPXML file, suitable for import into FileMaker.
 +
In addition, you can use the [[#EmailGetNextMessage|EmailGetNextMessage]] function after calling this to loop over the messages and programatically read individual values using the [[#EmailReadMessageValue|EmailReadMessageValue]].
 +
<h3>Flags</h3>
 +
The following is a description of the available flags:
 +
<dl>
 +
<dt>charset
 +
<dd>Character set of the file. Leave this blank to use the default for your locale.
 +
</dl>
 +
 +
Note: this will disconnect from your current mail server if there is an active connection.
 +
 +
<div class="parameters"><strong>Parameters:</strong>
 +
<dl><dt><code>file</code> <dd>path to an MBOX file
 +
</dl></div>
 +
<div class="see"><strong>Returns:</strong> URL to an FMPXML file containing the parsed messages in the file
 
</div>
 
</div>
  
Line 701: Line 502:
 
<li>sent (The timestamp the message was sent)</li>
 
<li>sent (The timestamp the message was sent)</li>
 
<li>messageID (The unique message ID for the email message)</li>
 
<li>messageID (The unique message ID for the email message)</li>
<li>attachments (A return-separated list of attachments for the message. Each line is either the attachment file path, or the name, depending on the value of the <code>attachments</code> parameter in <code>EmailReadMessages</code>)</li>
+
<li>attachments (A return-separated list of attachments for the message. Each line is either the attachment file path, or the name, depending on the value of the <code>attachments</code> parameter in <code>EmailReadMessages</code>). Note: inlined attachments are excluded from this list.  Use <code>attachmentsAll</code> to get all attachments including inlined ones.</li>
 
<li>text (The plain-text message content, if available)</li>
 
<li>text (The plain-text message content, if available)</li>
<li>html (The HTML body part, if one is available)</li>
+
<li>html (The HTML body part, if one is available.  If attachments are set to download, inline attachment images will be converted to base64 data URLs automatically.  If you don't want this behavior, use <code>htmlRaw</code> instead, or set <code>attachments=false</code> when fetching messages.)</li>
<li>uid (for IMAP only, returns the IMAP folder uid)</li>
+
<li>htmlRaw (The HTML body part unaltered, if one is available.)</li>
 +
<li>uid (returns the IMAP or POP3 folder uid <b>Note:</b> not all POP3 mail servers support UIDs)</li>
 
<li>viewed (1 or empty to indicate whether the message has been read (1) or is unread)</li>
 
<li>viewed (1 or empty to indicate whether the message has been read (1) or is unread)</li>
 
<li>flagged (1 or empty to indicate whether the message is flagged)</li>
 
<li>flagged (1 or empty to indicate whether the message is flagged)</li>
Line 711: Line 513:
 
<li>header:<em>HEADER_NAME</em> (any header value, replace <em>HEADER_NAME</em> with the name of the header to retrieve)
 
<li>header:<em>HEADER_NAME</em> (any header value, replace <em>HEADER_NAME</em> with the name of the header to retrieve)
 
<li>headers (a return-separated list of all message headers)</li>
 
<li>headers (a return-separated list of all message headers)</li>
 +
<li>raw: (the raw source of the entire message)</li>
 
</ul>
 
</ul>
 
<h3>Reading Message Headers</h3>
 
<h3>Reading Message Headers</h3>
Line 723: Line 526:
 
</div>
 
</div>
  
<div id="EmailRecipients"></div>
+
<div id="EmailVersion"></div>
==EmailRecipients ( to_addresses { ; append } ) ==
+
==EmailVersion==
Set the TO recipients for the current message.
+
Returns the version number of the Email plugin.
This can be called multiple times before sending, to build up a list of recipients (set <code>append</code> to true if doing this).
+
  
<div class="parameters"><strong>Parameters:</strong>
+
<div class="see"><strong>Returns:</strong> a text version number
<dl><dt><code>to_addresses</code> <dd>comma-separated list of addresses
+
<dt><code>append</code> <dd>whether to append the new addresses to existing ones, or overwrite them.
+
</dl></div>
+
<div class="see"><strong>Returns:</strong> 1 on success, ERROR if one or more addresses are invalid.
+
 
</div>
 
</div>
  
<div id="EmailRegister"></div>
+
<div id="IM_GetBuddyIcon"></div>
==EmailRegister ( licenseKey ; registeredTo ) ==
+
==IM_GetBuddyIcon ( service ; login ; password ; buddy ) ==
Registers the Email Plugin.
+
Returns a buddy's icon. If the buddy doesn't have an icon set, a default one will be returned corresponding to the
 +
buddy's messaging service. Note that if a connection is made shortly before the function is called, the returned
 +
icon be the default even if the buddy does have one set. A subsequent call will return the appropriate icon after it
 +
has been retrieved and cached by the plugin.
  
 
<div class="parameters"><strong>Parameters:</strong>
 
<div class="parameters"><strong>Parameters:</strong>
<dl><dt><code>licenseKey</code> <dd>a valid license key string.
+
<dl><dt><code>service</code> <dd>the messaging service to use; currently only "AIM" is supported
<dt><code>registeredTo</code> <dd>the company name for the license key used.
+
<dt><code>login</code> <dd>login/account name for the service
 +
<dt><code>password</code> <dd>the password for service account
 +
<dt><code>buddy</code> <dd>the buddy whose icon to get
 
</dl></div>
 
</dl></div>
<div class="see"><strong>Returns:</strong> 1 on success, or &quot;ERROR&quot; on failure.
+
<div class="see"><strong>Returns:</strong> the buddy's icon as a container
 
</div>
 
</div>
  
<div id="EmailSend"></div>
+
<div id="IM_GetBuddyList"></div>
==EmailSend==
+
==IM_GetBuddyList ( service ; login ; password ) ==
Send the current email, as specified in the [[#EmailCreate|EmailCreate]] function.
+
Connects to the messaging service (if necessary) and retrieves the user's buddy list. The list is return-separated
 
+
and can easily be parsed using FileMaker's built-in <code>GetValue()</code> function.
<div class="see"><strong>Returns:</strong> 1 on success, ERROR if something went wrong with sending the message
+
</div>
+
 
+
<div id="EmailSetBody"></div>
+
==EmailSetBody ( body { ; contentType ; characterSet } ) ==
+
Sets a body part of the current message. Common content types are "plain" and "html".  You can call this multiple times for a single message to provide an HTML body part with a plaintext alternative part.
+
 
+
To send formatted FileMaker text as HTML email, use the FileMaker <code>GetAsCSS</code> function to generate the HTML, e.g.
+
 
+
EmailCreate( "from@example.com", "to@example.com", "A multipart message" ) and
+
EmailSetBody( Email::body ; "plain" ) // this is used for mail clients which don't display HTML
+
    and
+
EmailSetBody( GetAsCSS( Email::body ); "html" ) // HTML version with formatting
+
    and
+
EmailSend
+
 
+
  
 
<div class="parameters"><strong>Parameters:</strong>
 
<div class="parameters"><strong>Parameters:</strong>
<dl><dt><code>body</code> <dd>text to be displayed in the message
+
<dl><dt><code>service</code> <dd>the messaging service to use; currently only "AIM" is supported
<dt><code>contentType</code> <dd>type of formatting used in the body, e.g. "plain", "html", "rtf".
+
<dt><code>login</code> <dd>login/account name for the service
<dt><code>characterSet</code> <dd>optional character set
+
<dt><code>password</code> <dd>the password for service account
 
</dl></div>
 
</dl></div>
<div class="see"><strong>Returns:</strong> 1 on success
+
<div class="see"><strong>Returns:</strong> return-separated list of buddies
 
</div>
 
</div>
  
<div id="EmailSetBodyFile"></div>
+
<div id="IM_GetBuddyStatusMessage"></div>
==EmailSetBodyFile ( url ; embedResources ) ==
+
==IM_GetBuddyStatusMessage ( service ; login ; password ; buddy ) ==
This is used to load an HTML document as the email body part. You can use the [[#EmailBodySubstitute|EmailBodySubstitute]] function to perform substitute/replace operations on the body content loaded by this function.
+
Returns a buddy's status. If the buddy doesn't have a status set, an empty string is returned instead. Note that if
<h3>Embedding Resources</h3>
+
a connection is made shortly before the function is called, the returned status may still be blank even if the buddy
If you pass <code>true</code> as the <code>embedResources</code> parameter, any images or stylesheets referenced in the email message will be included as inline attachments in the email message.
+
does have one set. A subsequent call will return the status after it has been retrieved and cached by the plugin.
This means that users will not need to load the resources from the central server, but it can increase the email message size considerably.
+
 
+
If you pass <code>false</code> as the <code>embedResources</code> parameter, any referenced image URLs will be rewritten as absolute URLs.
+
<h3>MHTML Files</h3>
+
This function also accepts .mhtml html archive files, which have the advantage of already having all images embedded in the file.  The <code>embedResources</code> parameter is always effectively <code>true</code> for .mhtml files.
+
  
 
<div class="parameters"><strong>Parameters:</strong>
 
<div class="parameters"><strong>Parameters:</strong>
<dl><dt><code>url</code> <dd>URL to the HTML document.
+
<dl><dt><code>service</code> <dd>the messaging service to use; currently only "AIM" is supported
<dt><code>embedResources</code> <dd>whether resources should be embedded in the HTML email or rewritten as absolute URLs.
+
<dt><code>login</code> <dd>login/account name for the service
 +
<dt><code>password</code> <dd>the password for service account
 +
<dt><code>buddy</code> <dd>the buddy whose status to get
 
</dl></div>
 
</dl></div>
<div class="see"><strong>Returns:</strong> 1 on success, "ERROR" on failure (use the EmailLastError function to get more information)
+
<div class="see"><strong>Returns:</strong> the buddy's current status; if no status is set, an empty string is returned
 
</div>
 
</div>
  
<div id="EmailSetErrorCapture"></div>
+
<div id="IM_GetBuddyStatusType"></div>
==EmailSetErrorCapture ( errorCapture ) ==
+
==IM_GetBuddyStatusType ( service ; login ; password ; buddy ) ==
 
+
Returns a buddy's status type as one of the following: "online", "idle", "away", "mobile", or "offline". If the
 +
buddy doesn't have a status set, an empty string is returned instead. Note that if a connection is made shortly
 +
before the function is called, the returned status type may still be blank even if the buddy does have one set. A
 +
subsequent call will return the status type after it has been retrieved and cached by the plugin.
  
 
<div class="parameters"><strong>Parameters:</strong>
 
<div class="parameters"><strong>Parameters:</strong>
<dl></dl></div>
+
<dl><dt><code>service</code> <dd>the messaging service to use; currently only "AIM" is supported
 
+
<dt><code>login</code> <dd>login/account name for the service
 
+
<dt><code>password</code> <dd>the password for service account
<div id="EmailSetHeader"></div>
+
<dt><code>buddy</code> <dd>the buddy whose status type to get
==EmailSetHeader ( header ; value ) ==
+
Set a custom header in the message.  This is not needed for the majority of cases.  A list of header fields can be found
+
[http://en.wikipedia.org/wiki/Email#Header_fields here].  These should be modified by advanced users only.
+
 
+
<div class="parameters"><strong>Parameters:</strong>
+
<dl><dt><code>header</code> <dd>the header name
+
<dt><code>value</code> <dd>the header value
+
 
</dl></div>
 
</dl></div>
<div class="see"><strong>Returns:</strong> 1 on success, or ERROR on failure
+
<div class="see"><strong>Returns:</strong> the buddy's current status type
</div>
+
 
+
<div id="EmailSetSubject"></div>
+
==EmailSetSubject ( subject ) ==
+
This allows you to customize the subject of the current outgoing email message, as specified in the [[#EmailCreate|EmailCreate]] function.
+
This can be useful if you are sending the same message to multiple recipients, with a custom subject for each recipient.
+
 
+
<div class="parameters"><strong>Parameters:</strong>
+
<dl><dt><code>subject</code> <dd>the email message subject
+
</dl></div>
+
<div class="see"><strong>Returns:</strong> 1 on success
+
</div>
+
 
+
<div id="EmailVersion"></div>
+
==EmailVersion==
+
Returns the version number of the Email plugin.
+
 
+
<div class="see"><strong>Returns:</strong> a text version number
+
 
</div>
 
</div>
  

Latest revision as of 03:41, 7 June 2017

Contents

[edit] 360Works Email User Guide

Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.
-Jamie Zawinski's Law of Software Envelopment


The 360Works Email Plugin offers the following advantages over FileMaker's built-in mail functionality:

  • Read messages from a mailbox (POP, IMAP)
  • Works with Instant Web Publishing / Schedules Server Scripts
  • Send multiple attachments in a single message
  • Send formatted (HTML, etc) emails
  • Speedy delivery of many messages by re-using a single connection to the server
  • Set custom email headers

Example Usages

EmailQuickSend, the easiest way to fire off a single email:

Set Variable [ $result =
    EmailRegister( "mylicensekey", "My Company" ) and
    EmailConnectSMTP( "mail.example.com" ) and
    EmailQuickSend(
        Email::from ;    // required "from" address
        Email::to ;      // comma-separated list of addresses
        Email::subject ; // subject of the message
        Email::body ;    // message body
        Email::attach    // path or URL or container to attach
    ) and
    EmailDisconnect
]


Sending a plain-text email with one attachment:

Set Variable [ $result =
    EmailRegister("myLicenseKey"; "My Company") and
    EmailConnectSMTP( "mail.example.com" ) and
    EmailCreate( Email::from ; Email::to ; Email::subject ) and
    EmailSetBody( Email::body ; "plain" ) and
    EmailAttachFile( $attachment ) and
    EmailSend and
    EmailDisconnect
]


Sending an HTML-formatted email (converts formatted FileMaker text to HTML using the GetAsCSS function):

Set Variable [ $result =
    EmailRegister("myLicenseKey"; "My Company") and
    EmailConnectSMTP( "mail.example.com" ) and
    EmailCreate( Email::from ; Email::to ; Email::subject ) and
    EmailSetBody( GetAsCSS( Email::body ); "html" ) and
    EmailSend and
    EmailDisconnect
]


Sending a single message multiple times to different recipients can be done by creating a message using EmailCreate, then calling EmailRecipients and EmailSend multiple times. If you are sending large messages with attachments, this avoids the overhead of creating a separate message for each recipient.

You can also send a single message to multiple TO, CC, or BCC recipients by passing a comma-separated list of addresses.

Note: Email is sent from whichever machine the plugin is being used on, be sure to open up port 25 for outgoing SMTP access on those machines.

Displaying a name instead of the FROM address

The "from" field can be either an email address "you@yourdomain.com" or a name and email address like "FirstName LastName <you@yourdomain.com>" instead. Most email clients will then display the name in the from field instead of the address. However, if the address is already in address book, most clients are configured to preempt with that associated name instead.

Sending Attachments

The EmailAttachFile accepts several different types of arguments. You can pass in a container field URL, or a path. A URL can be to a resource on the web, or can be a file url pointing to a local file (e.g. file:///path/to/attachment.jpg).

Bulk Mail

When sending to multiple recipients, instead of creating a new message for each recipient, you can create a single message, connect once to your server, and then send the same message multiple times, switching the subject, recipients, and message body for each recipient.

// First connect to the SMTP server and create the message.
Set Variable [ $msgCreate =
    EmailConnectSMTP( "mail.example.com" ) and
    EmailCreate( Email::from ; Email::to ; Email::subject ) and
    EmailSetBody( GetAsCSS( Email::body ); "html" )
]
Go To Record/Request [ First ]
Loop
    Set Variable [ $setRecipients = EmailRecipients [ Email::to ] ]
    Set Variable [ $msgSend = EmailSend ]
    Go To Record/Request [ Next ; Exit After Last ]
End Loop
// We've sent the same message to all recipients. Now disconnect
Set Variable [ $disconnect = EmailDisconnect ]

Reading Mail

Version 1.3 of the Email Plugin introduced support for reading messages from a mailbox. The API for reading messages was revised in version 1.6.

Here is a brief example of how to read the first 25 unread messages from the server:

set variable $registerResult = EmailRegister ( license ; company )
// check for registration success here
set variable $connectResult = EmailConnectIMAP( server ; username ; password )
// check for connection success here
set variable $$importUrl = EmailReadMessages (
    "mailbox=INBOX" ;
    "viewed=false" ;
    "max=25" ;
    "attachments=true"
)
// check for import success here
If [$$importUrl = "ERROR"]
    Show Custom Dialog [EmailLastError]
    Exit Script
End If
// Import the email messages from the local XML file
// which was created by the EmailReadMessages function
Import records [$$importUrl ; Update Matching]
// Now disconnect from the IMAP server
Set Variable [ $disconnect = EmailDisconnect ]
If [$disconnect = "ERROR"]
    Show Custom Dialog [EmailLastError]
    Exit Script
End If

If you're running on FileMaker server or via IWP/CWP, you'll need to iterate over the messages, since [Import XML] is not a web-safe script step. The general pattern looks like this:

set variable $$importUrl = EmailReadMessages (
    "mailbox=INBOX" ;
    "viewed=false" ;
    "max=25" ;
    "attachments=true"
// check for import success here
Loop
    Exit Loop If [not EmailGetNextMessage]
    New Record/Request
    Set Field[ImportedMessage::date ; EmailReadMessageValue( "dateSent" )]
    Set Field[ImportedMessage::from ; EmailReadMessageValue( "from" )]
    Set Field[ImportedMessage::to ; EmailReadMessageValue( "to" )]
    Set Field[ImportedMessage::subject ; EmailReadMessageValue( "subject" )]
    Set Field[ImportedMessage::body ; EmailReadMessageValue( "body" )]
    Set Field[ImportedMessage::messageId ; EmailReadMessageValue( "messageId" )]
End Loop

Microsoft Exchange Server

To read mail from a Microsoft Exchange Server, you'll need to enable IMAP access on your exchange server. <a href="http://technet.microsoft.com/en-us/library/bb124489.aspx?ppud=4">This article</a> covers the steps for doing so. You may need to restart your server for this change to take effect. Once IMAP access is enabled, you can connect normally as described above.

Modifying Mail Messages

Version 1.6 of the Email Plugin provided the ability to modify messages on a remote mailbox. To do this, you must read the messages using the EmailReadMessages function as described above, being sure to include the flag readonly=false. Note: setting readonly=false will cause any fetched messages to be marked as "viewed"! Then iterate to a message using the EmailGetNextMessage function. Finally, use the EmailMessageSetFlag function to apply flags to a message (such as deleted, flagged, viewed, etc).

Here is an example of how to fetch any unread messages from a mailbox, marking them all as viewed (by setting readonly=false). Additionally, any messages from a certain address are marked as deleted:

Set Variable [ $result = EmailReadMessages( "viewed=false" ; "readonly=false" ) ]
If [$result = "ERROR"]
    # Handle Error Here...
End If
Loop
    Exit Loop If [not EmailGetNextMessage]
    Set Variable[$result ; EmailMessageSetFlag("viewed")
    If [EmailReadMessageValue("from") = "deleteme@example.com"]
        Set Variable[$result ; EmailMessageSetFlag("deleted")
    End If
End Loop



[edit] 360Works Plugin Setup Guides

See Plugins_101 for Error reporting, installation, registration, and more.

[edit] Function Summary

  • EmailChooseFile ( { initialPath ; fileType ; title } ) — Shows a file chooser dialog where a user can browse her local hard drive.
  • EmailConnect ( host_address_deprecated { ; user_deprecated ; password_deprecated } ) — Use {@link #EmailConnectSMTP} instead.
  • EmailGetMessageCount ( { flag1 ; flag2 ; ... } ) — Returns a count of messages in a particular mailbox, INBOX is used if no mailbox is specified.
  • EmailGetNextMessage — Loads a single message which was fetched in a previous call to the EmailReadMessages function.
  • EmailInboundIsConnected
  • EmailLastError — Returns detailed information about the last error generated by this plugin.
  • EmailLicenseInfo — Retrieve information about the Email plugin licensing and version.
  • EmailListMailboxes ( { parent ; recursive } ) — Gets a return-separated list of mailboxes in a specific folder on the currently connected inbound mail server (Note: this is only useful for IMAP mailboxes, not POP).
  • EmailOutboundIsConnected
  • EmailOutgoingMessageId — Returns the Message-ID of the last message sent using the Emailer plugin.
  • EmailReadAttachment ( path { ; savePath } ) — Read a downloaded attachment into a FileMaker container field.
  • EmailReadMessages ( { flag1 ; flag2 ; ... } ) — Reads messages from the currently connected inbound mail server.
  • EmailReadMessagesFromFile ( file { ; charset=UTF-8 } ) — This reads messages from an non-directory MBOX file or raw message content file (.
  • EmailReadMessageValue ( key ) — Retrieves information about the last message which was gotten by the <code>EmailGetNextMessage function.
  • EmailVersion — Returns the version number of the Email plugin.
  • IM_GetBuddyIcon ( service ; login ; password ; buddy ) — Returns a buddy's icon.
  • IM_GetBuddyList ( service ; login ; password ) — Connects to the messaging service (if necessary) and retrieves the user's buddy list.
  • IM_GetBuddyStatusMessage ( service ; login ; password ; buddy ) — Returns a buddy's status.
  • IM_GetBuddyStatusType ( service ; login ; password ; buddy ) — Returns a buddy's status type as one of the following: "online", "idle", "away", "mobile", or "offline".
  • IsValidEmail ( email ) — Convenience function for validating an email address.

[edit] Function Detail

[edit] EmailChooseFile ( { initialPath ; fileType ; title } )

Shows a file chooser dialog where a user can browse her local hard drive. When the user selects a file or directory and clicks "OK" on the file chooser, this function returns the path to the selected file or directory. If the user hits the cancel button, nothing is returned.

File Type

By supplying a fileType parameter, you can allow the user to just select files, just select directories, or select both files and directories. The default behavior is to only allow file selection.


Note: specifying a fileType of "directories" or "files + directories" will cause a non-native file dialog to be used on some platforms, as the native dialogs may not support directory selection.

Parameters:

initialPath
optional path to set the initial dialog selection to. If empty, will default to the user's home directory.
fileType
whether to allow "files", "directories", or both "files + directories"
title
optional title string to display as the title of the FileChooser dialog

Returns: Path to the selected file, nothing if no file was selected, or "ERROR" if an error occurred.

[edit] EmailConnect ( host_address_deprecated { ; user_deprecated ; password_deprecated } )

Use EmailConnectSMTP instead. The username and password are optional, and may not be required for sending mail. This establishes a connection to the email server. When you are finished getting/sending email, you should call EmailDisconnect to close the connection.

Parameters:

host_address
the SMTP host address. This parameter may contain a port number using a colon syntax, e.g. smtp.example.com:2525
user
The optional SMTP authentication username
password
The optional SMTP authentication password

[edit] EmailGetMessageCount ( { flag1 ; flag2 ; ... } )

Returns a count of messages in a particular mailbox, INBOX is used if no mailbox is specified.

Parameters:

flags
optional flags which control how messages are counted

Returns: number of messages in the mailbox

[edit] EmailGetNextMessage

Loads a single message which was fetched in a previous call to the EmailReadMessages function.

To use this function, first call EmailReadMessages with the appropriate parameters.

Next, call EmailGetNextMessage, which returns 1 or 0 depending on whether a message was loaded.

Finally, call EmailReadMessageValue to get individual properties of the currently loaded message.

Returns: 1 if a message is loaded, 0 if there are no more messages, or ERROR if an error occurred.

[edit] EmailInboundIsConnected

[edit] EmailLastError

Returns detailed information about the last error generated by this plugin. If another plugin function returns the text "ERROR", call this function to get a user-presentable description of what went wrong.

Returns: Error text, or "" if there was no error.

[edit] EmailLicenseInfo

Retrieve information about the Email plugin licensing and version.

Returns: version, type, registeredTo values.

[edit] EmailListMailboxes ( { parent ; recursive } )

Gets a return-separated list of mailboxes in a specific folder on the currently connected inbound mail server (Note: this is only useful for IMAP mailboxes, not POP).

Parameters:

parent
optional mailbox to traverse. If not specified/empty, the root mailbox is used.
recursive
optional parameter for whether to traverse sub-folders recursively. Default is false.

Returns: a return-separated list of mailboxes. If recursion is enabled, nested mailboxes will be separated by a slash (/) character.

[edit] EmailOutboundIsConnected

[edit] EmailOutgoingMessageId

Returns the Message-ID of the last message sent using the Emailer plugin.

Returns: a Message-ID value, or "" if there was no available message.

[edit] EmailReadAttachment ( path { ; savePath } )

Read a downloaded attachment into a FileMaker container field. To download attachments, you must pass attachments=true as a parameter to the EmailReadMessages function.

After importing an email message into FileMaker, pass any attachment paths to this function to get container data for the attachment path. For example, you might pass the following argument:

EmailReadAttachment(
    "/Macintosh HD/private/tmp/4545776.01203682301836.JavaMail.root@pluto.local/text.html"
)

The supplied path should not begin with file:, image:, or any other prefix - just the path.

Note that this will actually work for any file, it doesn't need to be an email attachment.

Parameters:

path
The path as returned in the email import
savePath
An optional path parameter to save the attachment to a local folder instead of a container field

Returns: container data for the file at path, or "ERROR" if an error occurred (use EmailLastError in this case)

[edit] EmailReadMessages ( { flag1 ; flag2 ; ... } )

Reads messages from the currently connected inbound mail server. After calling this function, you will typically use the EmailGetNextMessage function to iterate over the messages which were fetched. As an alternate approach, you can perform an XML import of the fetched message data, using the value returned from this function as the XML file path.

If an error occurs, this function will return "ERROR". Use the EmailLastError function to get more information about the error.

Fetching Unread Messages

The Email plugin supports reading messages from POP and IMAP mailboxes. Typically, you're interested in only fetching new messages from your mailbox. There are several approaches to doing this.

Option 1: Search by UID (IMAP or POP3)

Note: POP3 mail servers are not required to support UIDs. Please check with the server administrator about UID support. IMAP and POP3 mailboxes assign each message a unique UID. When reading messages from an IMAP or POP3 mailbox, you can get the value for this UID with the following function:

Set Field[ImportedMessage::uid ; EmailReadMessageValue( "uid" ) ]

Once you have the UID of the most recently fetched message, you can pass that in as an argument to subsequent calls to EmailReadMessages, for example:

Go To Record/Request/Page [Last]
Set Variable [ $result = EmailReadMessages (
    "uid=" & ImportedMessage::uid
)
]

This fetches only the messages whose UID is greater than the most recently fetched message. This is the preferred way to fetch new messages from a mailbox, as it is very efficient, doesn't modify any messages, and will work even if another email client accesses the mailbox.


Option 2: Search for Unread Messages

You can specify a filter option to only search for unread messages:

Set Variable [ $result = EmailReadMessages (
    "viewed=false" ;
    "readonly=false"
)
]

After fetching unread messages, you should then set the "viewed" flag to true for each message, so subsequent reads will skip these messages. This is outlined in the following section "Reading Individual Messages" Note: searching for unread messages will not work correctly if other email clients are accessing the same mailbox and marking messages as viewed.


Option 3: Skipping messages

This is similar to option 2, except you don't need to modify the messages on the server. Simple count how many messages have been fetched from the mailbox, and pass a skip parameter to the EmailReadMessages function whose value is this number. Note: If messages are deleted from the mailbox, local messages should be deleted as well, so the local count matches the number of fetched messages on the server.


Reading Individual Messages

After successfully calling EmailReadMessages, you can iterate over the fetched messages using the EmailGetNextMessage function. This pattern typically looks like this:

Loop
    Exit Loop If [not EmailGetNextMessage]
    New Record/Request
    Set Field[ImportedMessage::from ; EmailReadMessageValue( "from" )]
    Set Field[ImportedMessage::to ; EmailReadMessageValue( "to" )]
    Set Field[ImportedMessage::subject ; EmailReadMessageValue( "subject" )]
    Set Field[ImportedMessage::body ; EmailReadMessageValue( "body" )]
    Set Field[ImportedMessage::messageId ; EmailReadMessageValue( "messageId" )]
    // OPTIONAL: mark this messages as "viewed"
    // (You must pass readonly=false during EmailReadMessages to do this)
    Set Variable[$result ; EmailMessageSetFlag("viewed")]
End Loop

Importing Messages via XML

To import email data into FileMaker via XML, use the "Import Records" script step, and specify an XML data source, passing the file URL returned from this function.
Use the "messageId" field in the resulting XML as a match field when defining import options. Note: XML import is not a web-safe script. Use the method described in "Reading Individual Messages" if your script is running in IWP or on the server, or if you need to modify individual messages on the server.

Flags

This function accepts a variety of flags which allow you to fine-tune how the messages are read. Flags should be entered as key=value arguments. You can specify any number of flags you wish. The following is a description of the available flags:

progress
Whether to show a cancellable progress bar (default is false).
progressLocation
Location of the progress bar, e.g. "100,200". Default is centered on-screen.
mailbox
The name of the mailbox to read messages from (Note: this is only useful for IMAP accounts). The default behavior is to read messages from the INBOX.
attachments
Boolean flag indicating whether to download attachment data. The default value is true, which enables attachment downloading. Setting this to false will disable downloading attachments, which can be significantly faster. If attachment downloading is disabled, you can still retrieve a list of the attachments in a message using the EmailReadMessageValue ( "attachments" ) function. You can the re-read the message at a later time to download the attachments.

skip
Skip this many records before reading results. This is useful for fetching messages in batches, if you know that messages will not be deleted from a mailbox during reading.
max
Do not return more than this many records in the import
uid
(Note: not all POP3 mail servers support UIDs) only fetch messages whose uid is newer than the one passed in. This is very useful for only fetching new messages from IMAP mailboxes. When looping through new messages, call EmailReadMessageValue("uid") on the last message and save this to a field in your database. Then when fetching new messages, pass this uid in as a filter argument. Only newer messages will be returned. Note: if you specify this option and the mailbox is an IMAP mailbox, some of the other search filters (skip, to, from, date) will be ignored.
dateFrom
Filter messages to only return messages sent on or after a certain date (some IMAP mailboxes require an additional flag of "deleted=any" for EmailReadMessages to read emails using this parameter).
dateTo
Filter messages to only return messages sent on or before a certain date (some IMAP mailboxes require an additional flag of "deleted=any" for EmailReadMessages to read emails using this parameter).
from
Filter messages by from address
to
Filter messages by to address
subject
Filter messages by subject
messageId
Filter messages by messageId
body
Filter messages by body
viewed
Filter messages by their read/unread status. Pass true to return only previously viewed messages, false to return only unread messages.
flagged
Filter messages by their flagged status. Pass true to return only flagged messages, false to return only non-flagged messages.
deleted
Filter messages by their deleted status. Pass true to return only deleted messages, false to return only non-deleted messages The default is false, meaning deleted message will be excluded.

alternateDecoding
Use an alternate method of decoding retrieved emails. Please contact 360Works if you are unsure of when to use this parameter. Pass 1 to enable (e.g., "alternateDecoding=1"). The alternate decoding method is disabled by default

readonly
Whether to open the mailbox folder as readonly or read-write. The default is true (read-only). If you plan on deleting, moving, or flagging any messages, use false in this parameter. Note: setting readonly=false will cause any fetched messages to be marked as "viewed"!

For example, you might use the following to fetch the first 25 unread messages from your inbox:

EmailReadMessages(
    "mailbox=INBOX" ;
    "attachments=false" ;
    "max=25" ;
    "attachments=false" ;
    "viewed=false"
)


Parameters:

flags
optional flags which control how messages are read.

Returns: The URL of the local XML file. This URL can be passed to FileMaker as the XML data source location.

[edit] EmailReadMessagesFromFile ( file { ; charset=UTF-8 } )

This reads messages from an non-directory MBOX file or raw message content file (.eml), and stores the parsed messages in an FMPXML file, suitable for import into FileMaker. In addition, you can use the EmailGetNextMessage function after calling this to loop over the messages and programatically read individual values using the EmailReadMessageValue.

Flags

The following is a description of the available flags:

charset
Character set of the file. Leave this blank to use the default for your locale.

Note: this will disconnect from your current mail server if there is an active connection.

Parameters:

file
path to an MBOX file

Returns: URL to an FMPXML file containing the parsed messages in the file

[edit] EmailReadMessageValue ( key )

Retrieves information about the last message which was gotten by the EmailGetNextMessage function.

If there are multiple values for a key, each value will be on a separate line.

The parameter must be one of the following values (case-insensitive):

  • count (The total number of messages fetched from the server)
  • from (The FROM address)
  • to (The TO addresses, comma-separated)
  • cc (The CC addresses, comma-separated)
  • bcc (The BCC addresses, comma-separated)
  • replyTo (The reply-to address)
  • subject
  • messageNumber (the integer index of the message on the server. 1 is the first message in the mailbox)
  • sent (The timestamp the message was sent)
  • messageID (The unique message ID for the email message)
  • attachments (A return-separated list of attachments for the message. Each line is either the attachment file path, or the name, depending on the value of the attachments parameter in EmailReadMessages). Note: inlined attachments are excluded from this list. Use attachmentsAll to get all attachments including inlined ones.
  • text (The plain-text message content, if available)
  • html (The HTML body part, if one is available. If attachments are set to download, inline attachment images will be converted to base64 data URLs automatically. If you don't want this behavior, use htmlRaw instead, or set attachments=false when fetching messages.)
  • htmlRaw (The HTML body part unaltered, if one is available.)
  • uid (returns the IMAP or POP3 folder uid Note: not all POP3 mail servers support UIDs)
  • viewed (1 or empty to indicate whether the message has been read (1) or is unread)
  • flagged (1 or empty to indicate whether the message is flagged)
  • replied (1 or empty)
  • deleted (1 or empty)
  • header:HEADER_NAME (any header value, replace HEADER_NAME with the name of the header to retrieve)
  • headers (a return-separated list of all message headers)
  • raw: (the raw source of the entire message)

Reading Message Headers

You can retrieve any message header by using this function. For example, to get information about the mail application which sent the message, you can use EmailReadMessageValue("header:X-Mailer"). If a header has multiple values, they will be returned as a return-separated list.

Parameters:

key
The key to retrieve, must be one of the above listed keys.

Returns: The value for that key in the current message.

[edit] EmailVersion

Returns the version number of the Email plugin.

Returns: a text version number

[edit] IM_GetBuddyIcon ( service ; login ; password ; buddy )

Returns a buddy's icon. If the buddy doesn't have an icon set, a default one will be returned corresponding to the buddy's messaging service. Note that if a connection is made shortly before the function is called, the returned icon be the default even if the buddy does have one set. A subsequent call will return the appropriate icon after it has been retrieved and cached by the plugin.

Parameters:

service
the messaging service to use; currently only "AIM" is supported
login
login/account name for the service
password
the password for service account
buddy
the buddy whose icon to get

Returns: the buddy's icon as a container

[edit] IM_GetBuddyList ( service ; login ; password )

Connects to the messaging service (if necessary) and retrieves the user's buddy list. The list is return-separated and can easily be parsed using FileMaker's built-in GetValue() function.

Parameters:

service
the messaging service to use; currently only "AIM" is supported
login
login/account name for the service
password
the password for service account

Returns: return-separated list of buddies

[edit] IM_GetBuddyStatusMessage ( service ; login ; password ; buddy )

Returns a buddy's status. If the buddy doesn't have a status set, an empty string is returned instead. Note that if a connection is made shortly before the function is called, the returned status may still be blank even if the buddy does have one set. A subsequent call will return the status after it has been retrieved and cached by the plugin.

Parameters:

service
the messaging service to use; currently only "AIM" is supported
login
login/account name for the service
password
the password for service account
buddy
the buddy whose status to get

Returns: the buddy's current status; if no status is set, an empty string is returned

[edit] IM_GetBuddyStatusType ( service ; login ; password ; buddy )

Returns a buddy's status type as one of the following: "online", "idle", "away", "mobile", or "offline". If the buddy doesn't have a status set, an empty string is returned instead. Note that if a connection is made shortly before the function is called, the returned status type may still be blank even if the buddy does have one set. A subsequent call will return the status type after it has been retrieved and cached by the plugin.

Parameters:

service
the messaging service to use; currently only "AIM" is supported
login
login/account name for the service
password
the password for service account
buddy
the buddy whose status type to get

Returns: the buddy's current status type

[edit] IsValidEmail ( email )

Convenience function for validating an email address. This checks for conformance to RFC 822, but does not actually check that an active email account exists at this address.

Parameters:

email
one or more email addresses to validate (comma-separated).

Returns: 1 if the all emails are valid, 0 if any address is invalid, or "" if email is empty.
Retrieved from "http://docs.360works.com/index.php?title=360Works_Email/Documentation&oldid=2252"
Personal tools
Namespaces

Variants
Actions
Plug-in Products
Other Products
Navigation
Toolbox