Open-Source Cold Email & Warmup Platform
Warmbly 是開源的冷郵件平台:溫暖您的收件箱、發送活動、並對每個回覆進行分流。可在我們的雲端運行或自行託管整個系統。
AI 翻譯
尚未收集儲存庫資訊。
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
Send all the email you want, and keep it private.
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗PostRider is a self-hosted mail relay. It takes outbound mail over an HTTP API and SMTP submission and delivers it direct to MX with DKIM; it takes inbound mail on MX for the domains an account registers; and it reports what happened to each message through webhooks.
For anyone who wants deliverability without renting it: transactional mail a recipient is already expecting, apps that would rather run their own relay than integrate a SaaS sending provider, teams done paying rent on a problem they mostly don't have.
PostRider handles:
Ship the email. Trust that the people who want it will find it.
Not the concept. The panic.
Somewhere along the way, "send an email" became a SaaS category. Dashboards. Reputation scores. Warm-up schedules. Pricing tiers built around inbox placement. All of it makes sense if you're blasting newsletters at people who never asked. Most email isn't that. Most email is something a person is actually waiting for.
Take the clearest case: a password reset, sent to someone who signed up ninety seconds ago and is staring at their inbox right now. That person isn't a cold prospect. They're mid-task. They triggered the email. They want the email. If it's not in the inbox, they'll check spam without a second thought. The context does the deliverability work for you — you just have to stop getting in its way. And the same holds, to varying degrees, for most of the mail you send: notifications, receipts, updates, the message that lands because someone was expecting it.
So PostRider is a bet: run your own relay, keep it clean, do the fundamentals, and stop paying rent on a problem you mostly don't have. In real use, the bet holds. Mail lands.
Outlook is still Outlook and occasionally has opinions. So do the people you're paying to avoid it.
Because you can. That used to be reason enough. It still is.
Ship the email. Trust that the people who want it will find it. Then go spend your engineering time on your actual product instead of babysitting a sender score.
View the changelog.
See CONTRIBUTING. To report a vulnerability, see SECURITY.
MIT. See MIT-LICENSE.