In certain industries, legal requirements mandate email archiving, and some companies maintain internal policies about email retention. While AhaSend can retain your full message data for up to 30 days, this duration may not suffice to meet your compliance requirements. To provide you with complete control over your message data and retention preferences, AhaSend offers the option to save your message data and delivery logs to any S3-compatible Object Storage service.
Requirements for enabling S3 retention
To send message data to S3, AhaSend must have access to it. Therefore, Message Data Retention must be enabled, and the message data must be retained for at least 1 day on AhaSend.
AhaSend requires write access to an S3-compatible Object Storage API. You can obtain S3-Compatible Object Storage services from providers such as Amazon AWS, BackBlaze, DigitalOcean, and others.
Enable S3 Retenion
You can enable S3 retention in your account settings by providing the following configuration parameters:
Endpoint URL: Use HTTPS endpoints for security. For AWS endpoints, refer to AWS documentation.
Bucket Name: Enter the name of the bucket you've created for storing message data in the Object Storage service provider.
Access Key and Secret Key: These keys are provided by your Object Storage service provider for authentication.
How messages are saved on S3
AhaSend saves the full message data as an EML file and the delivery logs as a CSV file in your bucket. To facilitate easy navigation and retrieval of individual messages, the files are stored in directories according to the following pattern:
RECIPIENT_EMAIL_ADDRESS/YYYY-MM-DD/MESSAGE_ID.eml
RECIPIENT_EMAIL_ADDRESS/YYYY-MM-DD/MESSAGE_ID.logs.csvThe @ symbol in the recipient email address is replaced by _AT_ as some S3 providers do not support having this character in object names.
For example, the email data and delivery logs for all emails sent to [email protected] on January 1st, 2024, would be stored under the directory path someone_AT_example.com/2024-01-01/ in your S3 bucket.
The delivery logs detail every attempt made to deliver the email, recorded in CSV format. Each row in the CSV file includes the date and time of the delivery attempt, the log type (such as Delivery, Bounce, Transient Failure, etc.), and the unaltered response or error message from the delivery attempt. Here are a few examples:
"2024/06/18 16:07:15","Delivery","OK 1718732564 d9443c01a7336-1f855eff682si97962965ad.490 - gsmtp"
"2024/06/17 11:52:52","Bounce","The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. For more information, go to https://support.google.com/mail/?p=NoSuchUser d2e1a72fcca58-705ccb718c4si8702600b3a.272 - gsmtp"
"2024/06/13 13:00:31","TransientFailure","The recipient's inbox is out of storage space. Please direct the recipient to https://support.google.com/mail/?p=OverQuotaTemp d9443c01a7336-1f855f1a529si12710625ad.594 - gsmtp"
