You can purchase a Dacons plug-in license through our website www.dacons.net and hit Buy in the main menu. Dacons sells it plug-ins exclusively through FastSpring.

Satisfaction Guaranteed Policy: You can test-drive our plug-ins before purchase for free. If you buy a Dacons license, your satisfaction is guaranteed. You can return your license within 14 days after purchase if you are not fully satisfied and get a refund.

We sell our plug-ins exclusively through FastSpring.

FastSpring accepts:
- all major credit cards
- PayPal
- bank transfers
- checks
- local payment methods around the world
- and more

Right after purchase, together with your purchase confirmation FastSpring will send you a link to your invoice.

Yes, we do offer significant discounts for educational and non-profit organisations. Please fill in your educational and non-profit form to receive an offer. You find a link to the form on bottom of the "Buy" page.

Our reseller FastSpring is a United States-based seller of digital goods. EU laws require FastSpring to charge VAT Tax (sales tax) on purchases of electronically delivered products for buyers based in the European Union. FastSpring is required to charge VAT Tax at the VAT rate of the buyer’s country.

VAT taxes are reported and paid to the EU by FastSpring. The invoice we provide to you at purchase completion will include the VAT amount as well as the FastSpring VAT ID.

Businesses making digital purchases can be exempted from VAT Tax by providing their valid VAT ID at the time of purchase. See next topic...

More information about VAT: https://fastspring.com/vat/

Yes, businesses making digital purchases can be exempted from VAT Tax by providing their valid VAT ID at the time of purchase. For those providing a VAT ID, no VAT Tax will be charged, and the VAT ID will be included on the invoice we provide at purchase completion.
You can enter the EU VAT number below the published VAT rate on the FastSpring Checkout page before concluding the purchase.

A network license has to be purchased if the plug-in will be used by an enterprise solution (a solution that is developed for and used in one organization). The developer license can be used by one named developer company and can be distributed royalty free with his solution that is intended for a third party. A Server license permits to run the plug-in on FileMaker® Server and FileMaker® Server Advanced for server site scripting and Web Publishing. The Server license is included into all Developer Licenses and in Network licenses, which allows for 10 or more users in the network. For details please refer to the license agreement. The links to the license agreements can be found on the 'Buy' page of each plug-in.

A single user license can be used on one computer. A 10 user license for example can be used by 10 clients in the network at the same time.

The amount of users in a developer license specifies how many plug-ins can run at the same time in the end users network. If you distribute your solution with a developer license for 10 user of our plug-in up to 10 clients at your end users network can run your solution at the same time.

You would use a plug-in on FileMaker® Server if you intend to use plug-in functions on server side, e.g. for Server-Side Scripting (SSS). You would also use a plug-in with FileMaker® Server (Advanced) for solutions that you share via Web Publishing. Licenses that support FileMaker® Server show a FileMaker® Server icon on the purchase pages.

If your only makes use of the plug-in functions on client side FileMaker® Server support of the plug-in is not required.

For solutions that make use of the plug-in on client and server side higher network licenses (15 users and above) and all developer licenses cover FileMaker® Server use with the plug-in. If your solution requires the plug-in functions only on server side (Server-Side Scripting or Web Publishing, no client side the plug-in functions) the plug-in license for FileMaker® Server is your choice.

No. After purchase of a the developer license no further fees or royalties have to be paid to Dacons. Your solution can be distributed to an unlimited number of customers.

Corresponding plug-in file(s) should be included in to your database distribution. The plug-in file(s) should be installed to the 'Extensions' folder of your solution.

The licensee must not modify or remove copyright notices or serial numbers or signatures that may be included within the software or displayed on the screen. Licensee may only distribute the plug-in in conjunction with and as a part of Licensee's own software product. When distributing FileMaker® Pro solutions to end users, Licensee must ensure that the plug-in registration code is not made visible to end users.

All license versions of our plug-ins are fully cross-platform.

You find a link to the license agreement on the 'purchase and license' page of each plug-in.

The software is delivered electronically. You will receive an email from us. Please make sure you white list @dacons.net in your spam filter. You can download the latest version of the plug-in from www.dacons.net and the downloaded version becomes the registries version as soon as you enter the registration data. The process is described in the registration data email.

By default, customers receive a link to the invoice directly with the purchase confirmation from FastSpring.
If you have questions to the invoice please visit http://questionacharge.com or contact us.

The software is delivered electronically. You will receive an email from us. Please make sure you white list @dacons.net in your spam filter. You can download the latest version of the plug-in from www.dacons.net and the downloaded version becomes the registries version as soon as you enter the registration data. The process is described in the registration data email.

Please allow up to 2 business days for the license delivery. We apologise for this rather long time and are working on improving this process. Please make sure you white list @dacons.net in your spam filter and check your 'junk mail' to make sure your spam engine did not filter our message. You can also contact sales@dacons.net with your name and company name to request a copy of the registration data. In this email please provide an alternative email address preferably from a different email host.

No. After purchase of a the developer license no further fees or royalties have to be paid to Dacons. Your solution can be distributed to an unlimited number of customers.

For distribution Dacons plug-ins you must own a developer license.
Corresponding plug-in file(s) should be included in to your database distribution. The plug-in file(s) should be installed to the 'Extensions' folder of your solution.

The licensee must not modify or remove copyright notices or serial numbers or signatures that may be included within the software or displayed on the screen. Licensee may only distribute the plug-in in conjunction with and as a part of Licensee's own software product. When distributing FileMaker® Pro solutions to end users, Licensee must ensure that the plug-in registration code is not made visible to end users.

You can change your current license to a license that allows more users. Single licenses are excluded from this. Please contact sales@dacons.net with the registration data of the current license you consider to change and with information about which license you want to use. We will send you a cost estimate with a special link for direct purchase of the upgrade.

Satisfaction Guaranteed Policy: You can test-drive our plug-ins before purchase for free. If you buy a Dacons license, your satisfaction is guaranteed. You can return your license within 30 days after purchase if you are not fully satisfied and get a refund.

Remove any previous versions the Dacons plug-in from the FileMaker® Pro extension folder (if there is any) and make sure you download the latest version plug-in version from out website. Enter the registration code again.

Please visit Dacons' exclusive reseller FastSpring's FAQ page

Please contact us through sales@dacons.net.

Instant Use of Mailit 10 in Exchange for Mailit 9 / 8 / 7 in FileMaker Solutions
Please notice that none of the code changes described below are critical while employing Mailit 9 / 8 / 7 in ex­change for Mailit 10 in a FileMaker solution.
Any programming time invested leads to direct improvements of your FileMaker solution by leveraging new Mailit 9 features. Your migration effort is minimized close to zero!
General recommendations:
­ "Emai_Version" : Update if necessary (Mailit 10 function call will return the major version based on ”10”).
Utilization of Mailit 9 / 8 / 7 message download history after Mailit 10 upgrade:
­ Mailit 10 maintains it’s own POP3 messages download history file. In order to utilize the message his­ tory file that were generated by Mailit 8, the following files should be copied:
Windows:
FM: C:\Documents and Settings\ \Application Data\net.dacons.mail.it \mailit.9.uidl FMS: C:\Windows\System32\config\systemprofile\AppData\Roaming\net.dacons.mailit\mailit.9.uidl
Mac OS X:
FM: /Users/ /Library/Preferences/net.dacons.mailit/mailit.9.uidl
FMS: /VolumeName/Library/FileMaker Server/Library Preferences/net.dacons.mailit/mailit.8.uidl
Into the following location:
Windows:
FM: C:\Documents and Settings\ \Application Data\net.dacons.mailit \mailit.9.uidl FMS: C:\Windows\System32\config\systemprofile\AppData\Roaming\net.dacons.mailit\mailit.9.uidl
Mac OS X:
FM: /Users/ /Library/Preferences/net.dacons.mailit/mailit.9.uidl
FMS: /VolumeName/Library/FileMaker Server/Library Preferences/net.dacons.mailit/mailit.9.uidl

This is possible and you can trade in the full value of your license in the process.

Is calculated in 3 steps.

1. Upgrade your Mailit license to the same Mailit 10 license.

2. Upgrade seats of your network license. Now you can trade in the full value of your current (Mailit 10) license for up to 3 years.

3. A US $ 20 handling fee applies.

Join those steps and contact on sales@dacons.net attaching your proof of purchase your Mailit license and the Mailit 10 license you would like to receive. We will send you a transparent calculation and a purchase link

This depends of the particular plug-in. Please see the plug-in related section for Mailit and FileFire.

This depends of the particular plug-in. Please see the plug-in related section:

Make sure the plug-in is located in appropriate folder at FileMaker Server:

AutoUpdate Folder
> Plug-in parent folder (The plug-in parant fronder must have the same name as the plug-in)
> Subfolder containing the plug-in file (The subfolder containing the plug-in must have the same name as the plug-in version number)
> Plug-in

See folder structure for FileMaker Server

Windows
To store plug-in files on a Windows server, create a folder in the AutoUpdate folder named after the plug-in, and a subfolder for each version of the plug-in. Store the plug-in file in the version subfolder.

Mac OS
To store plug-in files on a Mac OS server, create a folder in the AutoUpdate folder named after the plug-in, and a subfolder for each version of the plug-in. Store the plug-in file in the version subfolder.

Important To function properly on Mac OS, plug-ins and the folders in which they are stored must have the following file permissions:

To do this:
1. Launch the Terminal application ([hard disk]/Applications/Utilities/Terminal).
2. Navigate to the parent folder of the file or folder whose permissions you intend to change and enter the following at the command line:

chmod g+rx

or

chmod g+wrx

The g+rx is necessary because scripts and plug-ins must have the group read and executable bits enabled. Use the g+wrx form to permit write permission as well. Some plug-ins or scripts that use preferences or folders of additional files may require write permission to those files or folders.

Setting up Auto Update in your database
Import the Update scripts from the example database: AutoUpdate.zip

Move the old plug-in to the Trash with 'Option' key pressed (delete locked items) and then copy the new plug-in to the Extension folder.

Since plug-in update v4.0.5.b47, download package contains an updated 'Simple Mass Mail' Starter Solution, which now has a 'Tags' section, where you can define your own tags and fields correspondence.

We can suggest you to review the following applications, that are dedicated to transferring emails in to FileMaker database format:

Entourage Email Archive X
Visit Softhing.com to download

Mail to FileMaker Importer Visit automatedworkflows.com to download

Mailit can be used together with Google Mail service, but this requires a certain settings to be used, which you can find at:

SMTP & POP3
Visithttp://mail.google.com/support/bin/answer.py?answer=13287

SMTP & IMAP
Visit http://mail.google.com/support/bin/answer.py?answer=78799

Unfortunately there is no group-ware solution available yet, which could illustrate a shared mailing system using Mailit plug-in. However many of our clients are customizing the 'Personal Mail' Starter Solution, available , in order to use it in a workgroup as a shared mailing system.

The route to this SMTP host may be down, or blocked by your ISP. Please make sure you can access your SMTP and POP3 host using common mail client, like AppleMail or OutlookExpress from the computers, where you experience problems with connection. Please contact your IT person or ISP to resolve this kind of problem.

We can suggest you to review the following applications, that are dedicated to transferring emails in to FileMaker database format:

Entourage Email Archive X
Visit Softhing.com to download

Mail to FileMaker Importer Visit automatedworkflows.com to download

For this purpose you should utilize the 'Emai_ExportHtml' plug-in function, to export the message HTML code, or better complete message object in to a temporary location. By default, 'Emai_ExportHtml' function will export the object in to the system temporary folder, and return the full path to the saved folder, that should be then passed to the WEB viewer. For details, please review the 'Simple Receiving' example solution set, that illustrates this technique.

We suggest you the following steps, which should help you to customize one of the example solutions, available for Mailit 5 plug-in:

1. Pick the example solution, which fits your needs, and edit the mail retrieving script
2. Locate the 'Emai_PopRetrieveMessage' function call.
3. In front of the 'Emai_PopRetrieveMessage' function call insert the 'Emai_PopGetMessageInfo' function call, using the same parameter as 'Emai_PopRetrieveMessage' function call.
4. After the 'Emai_PopGetMessageInfo' add the 'Emai_PopGetMessageField' function call, to retrieve the corresponding field of the message (From, To, Cc, Subject, etc)
5. Use the condition operator ('If / End If') to retrieve those messages, which fit your criteria.

This problem is related to the message formatting and mail server(s) the message is going though. According to the RFC 2822 the length of one line should not exceed 998 characters. Some mail servers take the responsibility to reformat the message, if it does not meet the requirements of the RFC 2822, which may cause the problems. To resolve the issue we recommend you to format the code of your message in a way to avoid the lines longer then 998 characters. For example instead of writing:

... [990 characters] ... text ... [and so on]...

you should write:

... [990 characters] ... text

       ... [and so on]...

This will not affect the resulting HTML rendered view, as far as line breaks other then special HTML tags (like
) are not considered by HTML rendering engines.

First of all please make sure the plug-in is properly installed and enabled.

In case if you are using Windows Vista or Windows 7, 'Mailit.log' file can be also located at:
C:\Users\ \AppData\Local\VirtualStore\Program Files\FileMaker\ \Extensions
or:
C:\Users\ \Documents\net.dacons.mailit\Mailit.log

In case if you are distributing the plug-in over FileMaker Server AutoUpdate feature, 'Mailit.log' file can be also located at:
C:\Documents and Settings\ \Local Settings\Application Data\FileMaker\Extensions

'Winmail.dat' file is a transport encapsulation format, that can be created either by Microsoft Outlook, or while the message is passing through Microsoft Exchange Server. As far as this format is not RFC compliant, very few messengers can decode it. For more details on the 'Winmail.dat' topic we can suggest the following article for review:
http://en.wikipedia.org/wiki/Winmail.dat

In order to decode this file, we can suggest the following (free) service:
http://www.winmaildat.com/

Suggested check points:
1. Antivirus. Some antivirus software packages do not allow network activity for applications, which have not been allowed explicitly. We suggest you to disable any antivirus software during your tests.
2. Personal Firewall software. Most of the Personal Firewall software packages do not allow network activity for applications, which have not been allowed explicitly. We suggest you to disable any personal firewall software during your tests.

We strongly suggest you to make sure, that 'Windows Firewall' is not blocking the FileMaker application connections. To do this, please open your 'Control Panel', double-click the 'Windows Firewall' icon (if you are using 'Category View', you should first open 'Security Center' at your 'Control Panel'), and disable Firewall by clicking 'Off' radio-button (please confirm your choice by clicking 'Ok' button).

An example from our customer, related to the McAfee Virus Scan Enterprise:

1. Right click the McAfee shield icon in the systray (lower right-hand corner of screen) and select "VirusScan Console".
2. Right-click Access Protection and select Properties. Under Port Blocking, select "Prevent mass mailing worms from sending email" and choose Edit.
3. Add the text "FileMaker Pro.exe" to the Excluded Processes list.

The plug-in is choosing the encoding for the message automatically, based on the characters present at the message. For example, if the plug-in chooses the 'windows-1250' encoding, this should mean that your message contains character(s), which belong to one of the languages designated at:

http://en.wikipedia.org/wiki/Windows-1250

So, in order to get a message with 'Western' or 'US' characters encoding, you should use (only) the corresponding characters in your message.

Please notice, that if you use a combination of characters in your message, which can not be put in 8 bit encoding, the plug-in will use the Unicode encoding for this message.

You can generate a PDF and attach it immediately (automatically) to the new message. To do this, you should put a 'Save Records as PDF' script step in front of the 'Emai_SmtpAddAttachment' function call(s), and modify (or add another) 'Emai_SmtpAddAttachment' function call, to add attachment directly from the disk, from a temporary location.

For example:
Set Variable [$pdf; Value: Get (TemporaryPath) & "layout.pdf"]
Save Records As PDF [$pdf; Records Being Browsed]
Emai_SmtpAddAttachment( Emai_ImportFile(); "attachment"; Emai_GetFileName($pdf); "once"; "" )

This technique is illustrated at the 'Layout Sending PDF' example file, available at the download package.

HTML messages can also contain embedded files such as inline images. The following describes procedure in the Simple Mass Mail example file.

Select an attachment in the attachment portal. Define it as 'inline' in the pop-up menu (beside the actual attachment file). Click the 'CID' button, which will generate a Content ID for this image to be embedded and places it in the clipboard. i.e.:

MyPicture.jpg@4D5C9F1F.CA30.11D9.A446.000393A54002

In the HTML code place the following line where the image should be appear:



In general other file formats (like sound) can be embedded into emails the same way. However, JPEG and GIF are the only file formats that are supported by most receiving email clients

Suggested check points:

1. Make sure you have generated a Content ID for the image
2. Make sure you chose a proper file type ('inline')
3. Make sure you use correct inline reference syntax (for example:
4. Make sure you use lower case 'cid' prefix
5. Make sure that image file name contains only US characters, and does not contain spaces

In order to send multiple pages layout message you should compose an HTML message with a set of inline attachments, where each attachment is a layout image imported using the 'Emai_ImportJpegClipboard' function, representing each particular page. This technique is illustrated at the 'Layout Sending Multiple Pages' example file, available at the download package.

It is not possible to send the messages in background, as it is possible to do in a regular email client application, like Microsoft Outlook. The point is that FileMaker is taking part in the message sending process by feeding the updated message parts, and processing sending result. So even if you will disable Mailit 5 status dialog, FileMaker will remain busy, until the scripts execution is complete.

CSS styles support depends of particular email client application. Unfortunately there is no official list of the email applications which support CSS styles, however we can suggest you the following site:

http://www.campaignmonitor.com/reports/Guide_to_CSS_Support_in_Email.pdf

First of all please make sure the plug-in is properly installed and enabled.

In case if you are using Windows Vista or Windows 7, 'Mailit.log' file can be also located at:
C:\Users\ \AppData\Local\VirtualStore\Program Files\FileMaker\ \Extensions
or:
C:\Users\ \Documents\net.dacons.mailit\Mailit.log

In case if you are distributing the plug-in over FileMaker Server AutoUpdate feature, 'Mailit.log' file can be also located at:
C:\Documents and Settings\ \Local Settings\Application Data\FileMaker\Extensions

Yes, Mailit is fully compatible to IWP (Instant Web Publishing) and SSS (Server Side Scripting).

In order to run the plug-in under FileMaker Server SSS (Server Side Scripting), available since FileMaker Server 9, you should make sure the plug-in is installed in to the proper Server location:

FileMaker Server 8
Windows: \Program Files\FileMaker\FileMaker Server\Extensions\Plugins\
Mac OS: /Library/FileMaker Server/Extensions/Plugins/

FileMaker Server 9
Windows: \Program Files\FileMaker\FileMaker Server\Extensions\
Mac OS: /Library/FileMaker Server/Extensions/

FileMaker Server 10-12
Windows: \Program Files\FileMaker\FileMaker Server\Database Server\Extensions\
Mac OS: /Library/FileMaker Server/Database Server/Extensions/

Please notice, that you should ''Enable the FileMaker Server to use plug-ins', before you can enable each particular plug-in.

Please notice, that you should ''Enable the FileMaker Server to use plug-ins', before you can enable each particular plug-in, as it is illustrated on the screen-shots here:

see screenshots


In order to run the plug-in under FileMaker Server IWP (Instant Web Publishing), the plug-in should be installed to:

Windows:
C:\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\wpc\Plugins
Mac OS:
/Library/FileMaker Server/Web Publishing/publishing-engine/wpc/Plugins

Please notice, that plug-in installed in to IWP 'Plugins' folder will not get shown in the FileMaker Server Console. FileMaker Server SSS and FileMaker Server IWP are two different modules, that will look for the plug-in in two different locations. And FileMaker Server Console will only show the plug-in installed in FileMaker Server (SSS) 'Extensions' folder.

In order to register the plug-in installed on the Server side, you should use the 'Emai_RegisterSession' plug-in function, that should be triggered on the Server side either using the SSS (Server Side Scripting) technique, or over IWP. Please notice that 'Emai_RegisterSession' plug-in function will only register the running FileMaker Server session. In order to register the plug-in permanently, please use the 'Emai_RegisterServer' plug-in function, available since update v4.0.6.b54.

When plug-in is installed on the Server side, it is only accessible to the FileMaker Server, and inaccessible to any FileMaker Pro Workstations, that are connection to the FileMaker Server. In other words, FileMaker Server does not share any plug-in functionality with connected FileMaker Pro Workstations.

Therefore, if you only need the plug-in to be executed on the Server side, such as scheduled 'Server Side Scripting' or 'Instant Web Publishing', you could install the plug-in strictly on the Server side. Otherwise, if you need the plug-in to be executed also on the Workstations, you should install the plug-in on each Workstation, that will be using the plug-in functions. Please notice, that FileMaker Server includes an 'AutoUpdate' facilities, that allows automated plug-in updates distribution to any connected FileMaker Pro Workstations.

Yes, Mailit is a cross platform plug-in and available for Windows, macOS and for Windows-, macOS and Linux servers

In case if you are using an 'AutoUpdate' FileMaker Server feature, a copy of the plug-in file can be stored at:

Windows 2000, XP: $HOME > Local Settings > Application Data > FileMaker > FileMaker Pro > [Version] > Extensions
Windows 7 and later: $HOME > AppData > Local > FileMaker > FileMaker Pro > [Version] > Extensions

macOS: $HOME > Library > Application Support > FileMaker > Extensions