Postmark

6.3K posts

Postmark banner
Postmark

Postmark

@postmarkapp

The email delivery service that people actually like. We get your emails to the inbox—fast and reliably. By @ActiveCampaign.

Katılım Mayıs 2009
1.4K Takip Edilen7.1K Takipçiler
Postmark
Postmark@postmarkapp·
@MaGSchrijft Hi Martin, sorry about that! Will you please DM the support ticket and account info?
English
0
0
0
5
Martin Gijzemijter
Martin Gijzemijter@MaGSchrijft·
@postmarkapp Hi. I was wondering why you are not responding to anything. I recently switched to postmark. I had some questions after the initial setup, so I sent you four emails and a dm over the course of a month. No reply whatsoever. What’s going on?
English
1
0
0
18
Postmark retweetledi
Brian Graham
Brian Graham@iroasmas·
me as i read 40% of what claude wrote back and type in “continue”
Brian Graham tweet media
English
183
1.1K
20.3K
542.6K
Postmark retweetledi
larsnow
larsnow@larsnow·
Been running @postmarkapp on @feedjolt since day one. Zero deliverability headaches, zero “did the email go out?” moments. Every transactional email lands. Every time. Building stuff is hard enough. Email shouldn’t be.
GIF
English
0
2
3
272
Postmark
Postmark@postmarkapp·
Headers passed. The attack lived in the HTML... For anyone sending login attempt emails: The vulnerability here isn't your email auth setup, it's dynamic content rendering inside your template. -Lock down your CTA URLs. -Audit every variable that touches your email body. And if you're not sure what went out, your sent message activity is your first stop. Real emails can be weaponized. Build like they will be.
abraham@abemil7

Got a legit-looking @RobinhoodApp email today. Haven’t touched the account in years. Downloaded the raw .eml and checked headers. SPF ✅ DKIM ✅ DMARC ✅ It was actually sent from Robinhood’s infrastructure. But the body had a phishing payload injected into it. The top half of the email was normal: “Your recent login to Robinhood” Then inside the HTML, mid-content, it suddenly injected: “UNRECOGNIZED ACTIVITY — Case #RH-6801” with a “Review Activity” button. That button did NOT go to robinhood.com. It went to: googletagmanager.com → redirect → tinzio.net Classic cloaking. This is what makes it dangerous: This isn’t a spoof. This isn’t a random phishing email. It passed all authentication checks and came from a real sender. What likely happened: Some part of the email pipeline (template / dynamic field / notification system) got abused and allowed HTML injection. So attackers piggybacked on a legit email. Why this matters: Most advice says “check the sender”. That doesn’t work here. Everything looked legit at the header level. What to do instead: Never click email buttons for anything financial Always go directly to the app or type the URL manually Treat urgency + “case numbers” as a red flag Inspect link destinations (not just the visible text) If something feels off, it probably is What I did: I downloaded the .eml file and sent it to an AI to analyze Logged in manually Changed password Rotated 2FA Checked devices + account changes If you use Robinhood (or any fintech), assume this technique will get reused. Real emails can still be weaponized. Stay sharp.

English
3
0
5
845
Postmark
Postmark@postmarkapp·
The MessageID we return on every accepted send is the closest thing to a stable idempotency anchor — if you're storing that alongside your retry state, you can check "did we get a MessageID back?" as your single source of truth rather than a separate success flag. On the empty From: totally fair... strict validation on batch items is by design, but we know it can obscure upstream bugs. Worth logging the full error response per message, not just the batch-level status. Let us know if there's anything else we can do to help!
English
0
0
3
130
larsnow
larsnow@larsnow·
Burned an afternoon on @Feedjolt's AI digest mailer. Retry loop checked "request succeeded", not "email already sent." Two different states, both truthy, neither right. @postmarkapp also rejected an empty From header in the batch, masking the first bug entirely. Your idempotency key and your success check need to be the same thing. They rarely are.
English
1
0
1
166
OrcDev
OrcDev@orcdev·
.@shadcn just joined shipper.club thank you for the support legend 💚 truly a dream come true, I cannot explain how happy I am let's build ⛏️
OrcDev tweet media
English
22
6
144
6.9K
Postmark
Postmark@postmarkapp·
[Resolved] SMTP Sending Delays in the European Union: Good news - this issue has been resolved and everything should be working normally now. We're continuing to monitor closel... status.postmarkapp.com/notices/p5t8a0…
English
0
0
2
333
Postmark
Postmark@postmarkapp·
[Recovering] SMTP Sending Delays in the European Union: The issue has been identified and a fix has been deployed. Previously delayed messages are now sending. We will continue... status.postmarkapp.com/notices/p5t8a0…
English
0
0
2
289
Postmark
Postmark@postmarkapp·
[Identified] SMTP Sending Delays in the European Union: We have identified the source of the delays impacting outbound SMTP sending for customers on our EU infrastructure. Our ... status.postmarkapp.com/notices/p5t8a0…
English
0
0
0
241
Postmark
Postmark@postmarkapp·
[Investigating] SMPT Sending Delays in the European Union: Some customers sending from the European Union are experiencing delays in outbound message delivery. Affected message... status.postmarkapp.com/notices/cvezcy…
English
0
0
0
228
Postmark retweetledi
Tanner Linsley
Tanner Linsley@tannerlinsley·
Finally, @Tan_Stack Start now supports React Server Components! Start's RSCs are a truly fetchable, cacheable and composable primitive that work with your favorite tools instead of dictating your entire architecture. Oh, and one more thing... "Composite Components" 😉 🔗⬇️🧵
Tanner Linsley tweet media
English
112
269
2.2K
288.9K
Postmark
Postmark@postmarkapp·
@amandanat aka the best marketer in the world: “Search keeps growing, but the slice that reaches your website is getting smaller.” Another stellar talk at @MicroConf
English
0
1
3
190
Postmark
Postmark@postmarkapp·
[Resolved] Inbound & SMTP Delivery Delays (Network Connectivity Issues): **[UPDATE]** We determined that yesterday's network instability was caused by a widespre... status.postmarkapp.com/notices/udmp2f…
English
0
0
0
207
Postmark
Postmark@postmarkapp·
[Resolved] Inbound & SMTP Delivery Delays (Network Connectivity Issues): On **April 8th starting at ~16:50 UTC**, Postmark experienced an issue involving network... status.postmarkapp.com/notices/udmp2f…
English
0
0
0
221
Postmark
Postmark@postmarkapp·
[Resolved] Sending Delays: **[UPDATE]** On **April 2nd** starting at **~07:00pm UTC**, Postmark experienced an incident that resulted in delayed message delivery and webhook notifications for some custom... status.postmarkapp.com/notices/yy9yoi…
English
0
0
1
200