| Home | Getting Started | Browse by Category | All functions |
Before any send, autodetect, or profile operation, vuMailKit licensing must be initialized for the running EXE.
The normal template-based path is:
Once that succeeds, the profile is ready to use. That is the normal zero-OAuth-code path: the wizard performs OAuth authorization when needed, and your send code uses the saved profile.
Enter the license string in the template field as a quoted Clarion string.
Example format:
'license-string'
The global template generates the startup call to vuMailKitInitialize. Hand-coded integrations must call that function directly before using setup, autodetect, profile, or send functions.
If this startup step is missing, send and profile functions return -9001, and vuMailLastError reports a vuMailKit licensing/setup failure rather than a mail-server authentication failure.
In a Clarion multi-DLL application, add the vuMailKit global template to the EXE app, not to each supporting DLL app.
The EXE initializes vuMailKit licensing once for the process. After that, vuMailKit can be called from code reached anywhere in the running application.
After the global template is on the EXE application and the required template settings are entered, use the Clarion Utility Template command, CTRL+U, to import the vuMailKit Email Setup Wizard.
The vuMailKit Email Setup Wizard handles the normal first-run work: email-address validation, provider detection, OAuth authorization when enabled and required, test send, and profile save.
See vuMailKit Email Setup Wizard for the full workflow.
Some developers coming from older vuMail usage expect setup to be more involved than it is now.
With vuMailKit, the common path is meant to be fast: initialize licensing, use the vuMailKit Email Setup Wizard to save a profile, and call the send functions.
After the profile is saved, go to:
| Home | Getting Started | Browse by Category | All functions |