Mailio

Commercial version of the Mailio library offers several advantages over the open source version.

OAuth 2.0

OAuth 2.0 (Open Authorization 2.0) is a widely used authorization framework that enables applications to securely access resources on behalf of a user without requiring the user to share their credentials (e.g., username and password). Instead, it uses access tokens issued by an authorization server to grant limited access to protected resources hosted by a resource server. OAuth 2.0 is the backbone for many modern authentication and authorization mechanisms, including Single Sign-On (SSO) and social logins like Google or Facebook.

SPF and DMARC analysis

SPF is an email authentication protocol designed to prevent spoofing and ensure that only authorized mail servers can send emails on behalf of a domain. It works by allowing domain owners to publish a list of IP addresses or hostnames authorized to send emails for their domain in the DNS (Domain Name System). How SPF Works:

1. A domain owner sets up an SPF record in their DNS. This record lists authorized mail servers or IP addresses.
2. When an email is sent, the recipient's mail server checks the SPF record of the sender's domain to verify if the sending server is authorized.
3. Based on the result, the recipient's server accepts, flags, or rejects the email.

DMARC builds on SPF and DKIM (DomainKeys Identified Mail) to provide an additional layer of email authentication. It aligns the "From" address (visible to the user) with the domain validated by SPF and/or DKIM and provides reporting capabilities. Key Features of DMARC:

1. Alignment: Ensures that the "From" address aligns with SPF or DKIM results.
2. Policies: Specifies how a receiver should handle authentication failures (e.g., reject, quarantine, or none).
3. Reporting: Provides visibility into authentication attempts through reports.

UTF8 formatting

Message body can be formatted in various encodings. Some of them like UTF8 require more than one character. Line wrapping of UTF-8 encoded text must respect character boundaries, because splitting a UTF-8 multibyte character incorrectly can lead to invalid byte sequences and display errors. Thus, wrapping has to be done at character boundaries (code points), not byte count.

Non-ASCII directory names

IMAP was designed to be compatible with 7-bit ASCII communication protocols, so it couldn't handle full Unicode directly. To support international characters in mailbox names (like folder names in non-English languages), the IMAP protocol (as defined in RFC 3501) specifies the use of this modified UTF-7 encoding. A mailbox name like 邮件 (Chinese for "mail") would be encoded using IMAP-modified UTF-7 before being transmitted over the IMAP protocol.

The following packages are available for a free download as well the commercial licenses. Plans are priced in US dollars and are non-recurring. Please login to access them. For more questions please reach us at sales@mailio.dev.