vuMailKit Basic Edition is now available

marketplace
1

vuMailKit Basic Edition has now been released as the modern replacement for vuMail.

It supports secure SMTP, POP3, Microsoft OAuth, Google OAuth, built-in autodetect, and a guided Setup Wizard designed to make account setup dramatically easier for both developers and end users.

This is especially relevant for three groups of Clarion developers:

  • developers who need a current email solution for modern secure hosts
  • existing vuMail users who need a practical upgrade path away from the old CDO-based approach
  • developers using other mail solutions who would like to reduce setup headaches and support calls by using our autodetect and wizard

One of the features we are emphasizing is Zero Code OAuth. The developer does not have to write OAuth code. The wizard handles the user-facing flow, and the DLL handles the OAuth implementation behind the scenes.

We also published the docs and a dedicated OAuth setup guide that shows developers where to go to get their credentials, what to enter, and where to put it in the product.

There is also a downloadable demo that lets you:

  • run the Setup Wizard
  • set up a profile
  • send a test message
  • go back and try different types of accounts

So whether you want to test a standard email account, Gmail / Google OAuth, or Microsoft OAuth, you can see it working for yourself.

Pricing

  • New purchase: $149.00
  • Upgrade from any version of vuMail: $99.99

Links:

1 Like
2

Just bought it! Thanks for the update, I use Capesoft’s Nettalk and Mike Duglas’ Libcurl. It’s always useful to keep the tools up to date!
Thanks
Rohan

1 Like
3

Hi Rohan,

Thank you. I really appreciate your support, and I’m glad to hear you picked it up.

You’re absolutely right that it helps to keep tools like this current, especially with how much email requirements have changed.

One thing that has stood out already is that several developers who bought the update have commented on how much they like the fact that the advanced features are there, but they do not have to write a bunch of extra code to benefit from them. Things like auto-detecting server settings and handling OAuth are built in, but from the developer’s side it can still be as simple as running the wizard, saving the profile, and then using just a line or two of code to send mail.

That was a very important goal for me with vuMailKit. I wanted it to be modern and capable, without making developers fight through all the complexity just to send an email.

Thanks again for your support.

Charles

1 Like
4

Charles,

a few questions about vuMailKit:

The vuMailKit.dll is precompiled and there is no source available, right?

Are there any dependencies on other system or Windows DLLs?

Are there any dependencies on the OS itself?
What happens if Windows 12 or 13 will be available in years in the future?

I’m missing a function (or I’ve overseen it) to set individual email headers.

Can an email certificate be used to digitally sign the email?
I’m using a smime class1 certificate.

Thanks.

Jens

5

Hi Jens,

Thanks for the questions. They are all good ones.

At the moment, vuMailKit is supplied as a precompiled DLL, and the source code is not included with the standard product.

That said, I do understand why many Clarion developers prefer not to depend on black-box components. I am not against offering source availability for vuMailKit. It is something I am open to, but I want to give proper thought to what that should include, how it should be licensed, and what the pricing should be before I make any commitment on it.

As far as dependencies go, the goal has been to keep deployment straightforward and controlled, without requiring unusual external components or special third-party system add-ons.

In terms of OS dependence, there is no intentional tie to a specific Windows release beyond normal Windows compatibility expectations. As with any compiled Windows component, future operating systems have to be tested when they arrive, but the goal is for vuMailKit to remain a stable long-term replacement rather than something fragile or narrowly tied to one Windows version.

You also asked about setting individual email headers. That is not currently exposed as a general-purpose function in the present release, but it is a reasonable feature request and one I can certainly consider.

Regarding digital signing with an email certificate, vuMailKit does not currently support S/MIME signing of outgoing mail. Since you mentioned using a Class 1 S/MIME certificate, that is also a worthwhile feature request and something I will keep in mind for future development.

I appreciate you taking the time to ask about these items. Questions like these are very helpful because they point to the kinds of real-world capabilities developers may want to see added.

Best regards,

Charles

1 Like