SEDNA does not access a customer's existing messaging infrastructure or require an integration to receive or send email. This gives you complete control over what data is sent to SEDNA and provides greater security over your private company data.
Instead, SEDNA ingests a forwarded copy of each message that should be seen in SEDNA. For simple setups, a mail-enabled external contact is created within your domain which points towards a dedicated mail address we supply. This would be done once for each shared email address that will exist in SEDNA.
For more complex IT environments, any mechanism that achieves the end result of an email arriving to a specific address on a domain you control is forwarded to an address on our domain is acceptable, whether this be via transport rules or a network appliance capable of routing email.
Another benefit to this approach is that SEDNA is effectively system-agnostic. Providing there is a mechanism in place to forward email to SEDNA, we can ingest that content and make it visible to permissioned users.
For archive and recovery purposes, SEDNA retains an original copy of each message in addition to the online version. This archive copy is used by validation and verification processes to ensure database and search index contents are correct, and for compliance exports.
Emails sent via SEDNA are delivered reliably, securely, and are always sent from your company’s domain, e.g., @customer.com.
Successful, reliable sending of email to recipients is critical to our customers. To ensure this, SEDNA partners with SendGrid for outbound email. As part of the Onboarding process, we work with your IT teams to configure SPF and DMARC records that allow outgoing messages to be sent from your domain.
When emails are composed or responded to from SEDNA, no copy is sent through your Exchange server or stored therein. Instead, emails sent from SEDNA are routed through our mail delivery partner, SendGrid. Inbound and outbound Email is delivered with TLS/SSL encryption when available.
In the rare event that an email is not received by the receiving party, we are responsible for troubleshooting up to the point that the message leaves the SendGrid gateway and can provide logs to evidence the successful transit of any message to this point. This is similar to the level of investigation that can be performed in a traditional email setup, i.e. when the message goes out to the Internet it is not possible to provide a full trace from source to destination.