Contact

Talk to a person who built it

There is no support tier that determines whether you get a real answer. The team is small enough that the person replying is the person who wrote the code.

Send us a message

If it is about a specific send, include the message id — it goes straight to the delivery record and usually to the answer.

We use what you send here to reply to you, and nothing else.

Or write to the right address directly

Early access
[email protected]
Posthaste is in private testing. Tell us roughly what you send and how much of it, and we will let you know when we can take you on.
Support
[email protected]
Include the message id if it is about a specific send — it is the fastest route to the delivery record, and usually to the answer.
Abuse reports
[email protected]
If mail from our infrastructure is unwanted or looks fraudulent, tell us here. Include full headers if you have them. Monitored, and acted on.
Security disclosures
[email protected]
Vulnerability reports. Acknowledged within three working days — the terms we work under are on the security page.
Data protection
[email protected]
Access, deletion and other data protection requests, and anything about the data processing terms.

Before you write about a specific message

If a message did not arrive, the delivery record usually already contains the answer — the receiving server’s response code and its own diagnostic text. That is what we would look at first, so quoting it saves a round trip.

The docs show how to fetch it, and the deliverability page explains what the common refusals actually mean.

Response times

We aim to answer within one working day, and we would rather tell you “we do not know yet, here is what we are checking” than go quiet. Security reports are acknowledged within three working days. There is no phone line, and pretending otherwise would waste your time.