Sending e-mails using both SMTP and DNS servers - MailBee. NET Objects Tutorials

.NET Components
MailBee.NET Objects .NET email components: SMTP, POP3, IMAP, EWS, Security, AntiSpam, Outlook, Address Validator, PDF
MailBee.NET Queue Easy-to-use .NET service to deliver e-mails in the background

ActiveX Components
MailBee Objects ActiveX email components: SMTP, POP3, IMAP, S/MIME
MailBee Message Queue Queue-based background sending of emails

Web scripts
WebMail Pro PHP Webmail front-end for your existing mail server, with personal calendar, contacts, and mobile sync
WebMail Pro ASP.NET Webmail front-end for your existing mail server, with calendar sharing and global contacts
ActiveServer Premium addon which brings ActiveSync support to WebMail Pro and Aurora

Solutions
Aurora Corporate Groupware system for businesses and providers
Aurora Files Your personal cloud storage
Triton Transactional and newsletter emails sending solution
MailSuite Pro for Linux Mail server (MTA) bundled with WebMail Pro for a complete solution
Unified Messaging Solution Technology platform which provides telecom users with a feature-rich messaging portal

Sending e-mails using both SMTP and DNS servers

If both DnsServers and SmtpServers collections are non-empty, MailBee compares the priorities of the highest-priority DNS server and the highest-priority SMTP relay server. If the top priority SMTP server has the same or higher priority than the top priority DNS server, MailBee attempts to send mail using the SMTP relay server first. If it fails, the DNS MX lookup (direct send) is used. Higher priority value is actually lower integer value. I.e. 0 is the top priority while 999 is the lowest priority.

Thus, it is possible to combine both "direct send" and "send to relay SMTP server" methods to improve reliability of send mail operation even further. For instance, SMTP relay servers are tried first and if they fail, direct send comes as a backup.