Rebex Secure Mail
SMTP, IMAP, EWS, POP3, S/MIME .NET library
Download 30-day free trial Buy from $299More .NET components
-
Rebex FTP/SSL
.NET FTP client
-
Rebex MSG
Outlook MSG file format library
-
Rebex Total Pack
All Rebex components together
Back to feature list...
Compatibility
On this page:
XCOPY deployment
When distributing an application using Rebex Secure Mail library, simply copy the following DLL files (.NET assemblies) with your application:
Rebex.Common.dll
Rebex.Networking.dll
Rebex.Mail.dll
Rebex.Imap.dll
Rebex.Smtp.dll
Rebex.Pop3.dll
Rebex.Ews.dll
There is no need to install, configure or distribute anything else to make them work.
Supported SMTP, IMAP, POP3 servers
Rebex Secure Mail component works with all standard-compliant SMTP, IMAP and POP3 servers.
Recommended and tested mail servers:
Also works with:
- XMail
- Yahoo mail server
- Dovecot
- Postfix
- Courier mail server
- All other standard-compliant SMTP, IMAP, POP3 servers
Supported Exchange Web Services versions
Exhange Web Services client supports following Exchange Server versions:
- Exchange 2007
- Exchange 2007 SP1
- Exchange 2010
- Exchange 2010 SP1
- Exchange 2010 SP2
- Exchange 2013
- Exchange 2013 SP1
- Exchange 2016
- Exchange Office 365 and Outlook.com
Fine-tuning client behavior
The Smtp
, Imap
and Pop3
objects makes it possible to adjust various client settings
and workarounds. Most of them are available through Settings
property (see the next section for details).
Some settings are available at the Smtp
, Imap
and Pop3
objects themselves.
This includes the Encoding
property that specifies a charset to be used when encoding commands and decoding responses.
However, since all of those should normally use ASCII, changing the default value is seldom needed.
// create POP3 client instance pop3 = new Pop3(); // set encoding to UTF-8 pop3.Encoding = Encoding.UTF8;
' create POP3 client instance pop3 = New Pop3() ' set encoding to UTF-8 pop3.Encoding = Encoding.UTF8
The common settings include a Timeout
property as well.
Use it to change the default timeout value of 60,000 miliseconds.
Workarounds for common server issues
Workarounds for some server issues are not enabled by default because detecting them automatically would be troublesome.
They can be changed through properties of Smtp.Settings
, Imap.Settings
and Pop3.Settings
objects.
// create POP3 client instance pop3 = new Pop3(); // ignore invalid message headers pop3.Settings.IgnoreUnparsableHeaders = true;
' create POP3 client instance pop3 = New Pop3() ' ignore invalid message headers pop3.Settings.IgnoreUnparsableHeaders = True
List of common tweaks and workarounds:
Object | Property | Purpose |
---|---|---|
Imap Pop3 |
IgnoreUnparsableHeaders | Ignore unparsable headers when parsing mail message received from the POP3 or IMAP server. |
Imap Pop3 |
IgnoreUnparsableSignatures | Ignore unparsable S/MIME signature entities when parsing mail message received from the POP3 or IMAP server. |
Pop3 | DisableGmailRetrieveWorkaround | Disables workaround for non-standard behavior of POP3 Gmail's RETR command. |
Pop3 | DisableApopAuthentication | Explicitly disables APOP authentication for those POP3 servers, which falsely advertises APOP support. |
Smtp | AllowNullSender | Allows null sender (<> ) to be specified in Smtp.Send call. Used when sending delivery status notifications. |
Back to feature list...