How Bit Beyond LLC sends email, and how to make it stop.
This address is the operations point for all outbound email from Bit Beyond LLC. If a message from one of our domains reached you and you want it to stop, or you are a mail provider assessing our sending, everything you need is on this page.
Every message we send carries a working unsubscribe — both the one-click control
your mail client shows (List-Unsubscribe, RFC 8058) and a link in
the message itself. Either one is permanent and takes effect before anything else
is sent. If one has failed you, write to
postmaster@bitbeyond.com and we will
action it by hand.
Bit Beyond LLC runs several small products. Their mail falls into two kinds, and we keep them structurally separate so that a problem with one cannot degrade the other.
| Lane | Sending domain | What it carries |
|---|---|---|
| Transactional | bitbeyond.com |
Receipts, password resets, order confirmations, operator alerts — every app on the server. This is the mail that MUST arrive, which is exactly why it is kept away from outreach. |
| Outreach (shared) | queries.postscript.pub |
Query letters for writers who have not connected their own mailbox. Every complaint this lane earns lands on ONE domain shared by all of them, so it is capped hardest and watched closest. |
We do not buy, rent, scrape or exchange mailing lists, and we do not send campaigns to purchased audiences. Outbound business correspondence goes only to organisations whose own published policy states they accept it, at the address they publish for that purpose — for example a literary agency that lists a submissions address and says it is open to queries.
Each such record stores the source URL used to verify that policy and the date it was checked, alongside whether the organisation is currently open. When a party closes to submissions, they stop being contacted.
Sending is paced rather than burst. Our queue drains every minute and takes a small share, so mail leaves at a steady rate over hours instead of arriving at a receiving server in a single spike. Each lane carries its own hourly pace and daily ceiling, and a message that would exceed them waits rather than being dropped.
Every message is recorded in a ledger with its delivery outcome. Bounce and complaint notifications are consumed automatically, and the affected address is added to a suppression record. A recipient who declines is recorded permanently and is not contacted again by that sender.
We monitor bounce and complaint rates per sending domain continuously and hold ourselves below the thresholds published by the major receiving providers.
Every sending domain publishes SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail) and DMARC (Domain-based Message Authentication, Reporting and Conformance) records, and DMARC aggregate reports are collected and reviewed. Mail that does not authenticate as ours is not ours.
Domains covered:
postscript.pubpatchbay.iomercmate.comfanforge.comaethra.ioabuse@bitbeyond.com reaches a person, and postmaster@bitbeyond.com reaches the same person about operational matters. Both are monitored.