This email component library supports SMTP, POP3, and IMAP protocols for sending and receiving emails with HTML and encoded attachments. SSL/TLS authentication, ISO-8859 and UTF-8 encoding for messages are available via a basic API.
The MarshallSoft SMTP/POP3/IMAP dBase email component library (SEE4DB) is a top-notch software solution that comes with a variety of features to make email communication easier and more effective. With its simple API, SEE4DB allows you to send and receive email, including HTML, MIME Base64, and quoted-printable encoded attachments, directly from within a dBase application.
One of the most notable features of SEE4DB is its ability to send email with inline HTML, GIF, TIF, JPG, BMP, and Rich Text attachments. You can also choose from a variety of character coding options, including ISO-8859 and UTF-8, as well as CHARSET_WIN_1250. SEE4DB also supports email servers that require SSL/TLS.
With SEE4DB, you can quickly and easily get the number of messages on your email server or retrieve header lines from any email on your server without reading the entire email. You can also delete any email on the server without downloading the entire email or copy any email without deleting it. Additionally, SEE4DB enables you to receive any email on your server, including MIME attachments, and automatically decode MIME attachments when downloading email.
SEE4DB comes with a range of other useful features, including the ability to remove contents of incoming attachments, copy email, and navigate between IMAP mailboxes. There are also dozens of switches to control how email is sent and received, and you can run up to 32 independent threads concurrently.
Other benefits of SEE4DB include its support for SMTP (ESMTP) and POP3 authentication, multiple dBase example programs, and royalty-free distribution with your compiled application. SEE4DB does not depend on support libraries, as it calls only core Windows API functions, and free technical support and updates are available for one year. You can also try SEE4DB with its fully functional evaluation version.
Plus, SEE4DB works flawlessly with all 32-bit versions of dBase and with 32-bit and 64-bit Windows through Windows 11. When it comes to email communication within a dBase application, SEE4DB is a top choice for software developers looking for a reliable and feature-rich solution.
One of the most notable features of SEE4DB is its ability to send email with inline HTML, GIF, TIF, JPG, BMP, and Rich Text attachments. You can also choose from a variety of character coding options, including ISO-8859 and UTF-8, as well as CHARSET_WIN_1250. SEE4DB also supports email servers that require SSL/TLS.
With SEE4DB, you can quickly and easily get the number of messages on your email server or retrieve header lines from any email on your server without reading the entire email. You can also delete any email on the server without downloading the entire email or copy any email without deleting it. Additionally, SEE4DB enables you to receive any email on your server, including MIME attachments, and automatically decode MIME attachments when downloading email.
SEE4DB comes with a range of other useful features, including the ability to remove contents of incoming attachments, copy email, and navigate between IMAP mailboxes. There are also dozens of switches to control how email is sent and received, and you can run up to 32 independent threads concurrently.
Other benefits of SEE4DB include its support for SMTP (ESMTP) and POP3 authentication, multiple dBase example programs, and royalty-free distribution with your compiled application. SEE4DB does not depend on support libraries, as it calls only core Windows API functions, and free technical support and updates are available for one year. You can also try SEE4DB with its fully functional evaluation version.
Plus, SEE4DB works flawlessly with all 32-bit versions of dBase and with 32-bit and 64-bit Windows through Windows 11. When it comes to email communication within a dBase application, SEE4DB is a top choice for software developers looking for a reliable and feature-rich solution.
What's New
Version 8.4: Protocol XOAUTH2 must be explicitly enabled. Fixed problem when renaming attachments "on the fly" [oldname:newname]. Added renaming of inline images "on the fly" [oldname:newname]. Write authentication protocol selected by user to the log file. Allow "From:" header to be split over multiple lines.
Version 8.3: Protocol XOAUTH2 must be explicitly enabled. Fixed problem when renaming attachments "on the fly" [oldname:newname]. Added renaming of inline images "on the fly" [oldname:newname]. Write authentication protocol selected by user to the log file. Allow "From:" header to be split over multiple lines.