MailBee.NET Queue helps applications send e-mails faster by means of the background delivery. Instead of actual sending, your application can just write all the e-mails as .EML files into a certain folder, and MailBee.NET Queue will do the rest.

Internally, Windows service of MailBee.NET Queue monitors that disk folder, picks up all .EML files other applications submit to it, and sends them out through SMTP server. To feed the pickup folder, you can use any tool capable of producing .EML files, including MailBee.NET Objects and MailBee Objects products.

MailBee.NET Queue fully supports SSL connections with SMTP servers, a number of ESMTP authentication methods including advanced ones like NTLM, GSSAPI, Integrated Windows Authentication, sending e-mails in multiple threads and can log all the activities into a file. This functionality can be configured with an easy-to-use Control Panel application.

In addition, with MailBee.NET Queue API you can make the application use multiple relay SMTP servers with different priorities, perform DNS MX based delivery in case of the SMTP relay server failure and otherwise tune e-mail delivery process in many ways. For instance, you can limiting the number of e-mails the service sends per a single SMTP session, maximum number of connections to the server, etc to comply with the restrictions imposed by many SMTP servers to prevent abuse).

MailBee.NET Queue API is just a thin wrapper over well-documented MailBee.NET SMTP classes. If you're familiar with them, you know the API. For instance, you can simply serialize objects like SmtpServers and DnsServers collections you're using in your applications, and MailBee.NET Queue will re-use them to populate its own collections of SMTP and DNS servers.

To run MailBee.NET Queue, you need a valid MailBee.NET SMTP license key. A unified MailBee.NET Objects key will work as well.

As the source code is available, you can also use MailBee.NET Queue as an advanced sample of using MailBee.NET Objects for bulk mail delivery, multi-threading, events processing, using backup servers, and putting all the pieces of the functionality together.

AfterLogic