PieMail Email Testing & PieSocket Server v4.7.7

Another Tuesday, another Pie.host update!

Last week we shipped improvements across PieMail and PieSocket, with a focus on making it easier to test outbound emails and giving teams more control over how long piesocket-server self-hosted message logs are retained.

The PieMail update makes cadence testing more practical, while PieSocket Server v4.7.7 (self-hosted) introduces daily log partitioning and configurable retention for deployments that generate large volumes of message data.

What We Shipped

Test Emails Directly From PieMail Cadences

Testing an automated email sequence should not require waiting for the cadence to reach a real contact.

You can now send a test email directly from your PieMail cadence settings. This lets you see the actual email you are about to send and verify that its content and formatting look right before the cadence reaches your contacts.

You can also select an existing contact when sending the test. Their information is used to populate the cadence's placeholders, making it possible to preview the email with realistic contact data instead of generic or empty variables.

This is particularly useful for emails containing personalization, dynamic contact attributes, or multiple placeholders where a simple static preview isn't enough.

PieSocket Server v4.7.7: Daily Log Rotation and Retention

PieSocket Server (self-hosted) v4.7.7 adds two configuration options for managing message log storage:

LOG_PARTITIONING=daily enables daily message log tables instead of keeping all logs in a single unbounded message_logs table. Daily tables follow the format message_logs_YYYY_MM_DD.

The second option, LOG_RETENTION_DAYS, lets operators automatically remove logs older than a specified number of days.

When daily partitioning is enabled, retention can remove entire daily tables rather than deleting individual rows. Without partitioning, matching rows are deleted directly from message_logs.

Both settings are optional. By default, partitioning is disabled and logs are retained indefinitely.

For deployments with high message volumes, this provides a more predictable way to manage log growth without requiring operators to manually clean up old data.

Small Improvements

This week's work continues a broader focus on giving developers more control over the infrastructure behind their applications, while making everyday product workflows easier to verify before they reach production.

For PieMail users, that means being able to validate personalized cadence emails before sending them. For PieSocket Server operators, it means having explicit controls over log organization and retention.

Try the latest PieMail improvements and PieSocket Server v4.7.7 in your next deployment.

See you next Tuesday