Planimail Relays

The Planimail system has special AVAS Relays that verify that the user is authenticated before sending an email.

Most email systems currently tend to block emails that are not authenticatedwith SASL-SMTP (i.e., emails where the sender is NOT authenticated with user and password).

While this type of automatic email is acceptable within an organization as internal emails, Planimail needs to verify that the senders existeither as aliasesor email accounts to avoid generating bounce loopsor accidental backscattering.

Authenticated Users

Warning

If you want to use a relay to send system emails (e.g., monitoring alerts),you must create an alias or an account to register the sender, otherwise,the email will be discarded. Although the system accepts senders from IPsdeclared in AVAS as Relays, it is always recommended to program automaticemails with SASL-SMTP user and password authentication.

Automatic Email Traffic

Note

It is recommended not to mix email sent by people with email sent by systems onthe same relay. You can request from the commercial department the purchase of aspecific relay for automatic emails. The reason is that excessive alertscan expose the relay’s IP to rate limits in systems like Gmail, Outlook,Yahoo, and others, resulting in low reputation and poor acceptance by end users.

Sending Invoices, Policies, Receipts

If you need more information than that provided by AVAS Mailauditabout what happened with a particular email (if it was delivered, read,bounced, etc.), Planisys provides the email tracking service through the DMDS system.

Note

For emails that require tracking, such as Invoices,Notifications, Receipts, Policies, Receipts, etc.,you should use SMTP-DMDS or alternatively REST API outsideof the Planimail system, to have tracking and bounce information available via Web and API.

Last Updated on 2024-08-20