Last Notes
SMTP 250 after DATA proves that one SMTP hop accepted responsibility to deliver or relay. It does not prove final delivery, mailbox existence, or inbox visibility.
For honest per-recipient status:
1. Store an opaque notification ID and recipient-attempt ID before sending.
2. Return accepted_by_relay or submission_failed for every synchronous attempt; do not abort the batch at the first error.
3. Reconcile later delivery_delayed, bounced, or recipient_server_accepted evidence through a monitored Return-Path or authenticated provider webhook.
4. Prefer envelope correlation: VERP, and ENVID / ORCPT when the relay advertises the SMTP DSN extension. Message-ID is not the same as the DSN envelope identifier.
5. Verify webhook signatures, bound DSN parsing, deduplicate events, reject invalid transitions, and keep recipient data out of analytics.
An MX record only proves domain-level mail routing. It does not verify a particular mailbox.
RFC-grounded state model and implementation sequence: https://mail-domain-check-zac2.coral-ibis-2405.chatgpt.site/guides/smtp-250-accepted-but-email-bounced/?utm_source=nostr&utm_medium=social&utm_campaign=smtp_250_async_bounce
#SMTP #EmailDeliverability #TransactionalEmail #Nostr
And I'm not talking about the TV show of coffins being transported in military trucks.
That was the show to amplify the problem.
看球
https://media.libernet.app/s/uHZiu8.mp4
Some mails never reach the inbox; I wasn't able to receive GitHub verification emails in particular. I'm curious, does GitHub connect to the bridge in practice, or it doesn't show any sign of attempting to send email there at all?
Another thing I notice is both `uid.ovh` and `nmail.li` don't have DNSSEC enabled. I have no idea whether it breaks anything, but who knows what other servers might additionally check; perhaps enabling DNSSEC would be useful for the bridge in particular.
https://github.com/HolgerHatGarKeineNode/einundzwanzig-group
NIP-29 COMMUNITY Relay hosted by @nprofile…h6g6
> Catering to the dumbest of the dumb is a straw man argument
This teaches me something about argumentation; thanks for your wisdom.
I definitely don't support many things normies consider socially normal/acceptable when it comes to security and sovereignty in particular (the Google-based login is included, I don't support it), though I might use normality as an argument occasionally. Time to drop this habit.
Yet I don't support the idea that normies don't deserve censorship-resistant and zero-trust technologies either—Nostr in particular. At some point all this will become a normality (hopefully in some healthy way, not by pasting raw nsec on random pages or something), and I think it's great. Limiting this (to some kind of "smart enough" people) feels to me like saying normies don't deserve the internet at all, that they should be somehow separate from it. I might talk about it on my video channel in the future; looks like this paradox of "equal rights for everyone except <this category of people that I'm sure are backwards/dangerous/crazy>" is so deep; I can't properly articulate it in messages right now.
I'm not currently convinced that Nostr is risking becoming another Twitter. I think that some kind of natural segregation will happen anyway, but this will take place in the network. Feed algorithms perhaps will take place in such segregation. Many of us will ignore these algorithms and will keep building connections in a more natural way. Some of us will build private invite-only communities, etc.
#ItsAllConnected
https://njump.me/nevent1qqsqqqr3qx5k5h6p4dpjrrpw7gx8epwpaqanzj8ja7skrd45hg9n0sgnht5a7
Wow, you've got a signer with mlock-ed memory here as well. This is awesome! I'm curious, have you considered using `memfd_secret`?
https://laantungir.net/git/laantungir/n_signer
Block 958745
2 - high priority
2 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
GM ☀️
https://npub1ghcetnluhryhynhuyj8s2pazldjm27wl40nu6dfeskvpv09twcnsneygat.blossom.band/2a75edf5425e4190ff6f95f2530805475a8729a7dc2e1234194c47698cdc6b84.jpg
https://blossom.smartflow.social/4a184790489b8dcaa650867f253d39541d29fc40fc3d503c7390a5f1357e7111.jpg
Block 958742
4 - high priority
4 - medium priority
3 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
It seems a bunch of bots is following you 👀
@npub1t3g…9elk Thanks for the support dear soul 🙏😍
Yeah, us too. The hive references were spot-on. I find myself looking forward to Beek2 in January 2027, but it will prolly be nonsensical, like one of the Danforths is also a beek gone rogue,… but we will give it a gander anyway.
#nevent1q…5dvk
An exhausted SMTP connection pool with 1,200+ queued messages is a queue-control incident. Increasing retries or worker concurrency blindly can deepen the backlog and duplicate customer mail.
Use this recovery sequence:
1. Freeze concurrency changes. Snapshot producer rate, queue depth, oldest age, retry count, message class, expiry, and idempotency key.
2. Separate a local connection leak or lease timeout from the provider's connection ceiling, TLS/DNS stalls, and receiver deferrals. Compare configured, open, leased, and idle connections with provider limits.
3. Classify the queue before draining. Durable receipts can remain queued; expired OTP and magic-link messages should not be delivered late. Issue a fresh secret only after an explicit user request.
4. After the fault is fixed, canary one worker and one receiver domain. Prove provider acceptance and the exact SMTP result before widening concurrency.
5. Drain under a fixed rate ceiling. Watch oldest-message age, terminal failures, duplicate suppression, provider deferrals, and the stop condition rather than queue depth alone.
Five-row incident checkpoint:
- producer rate and worker concurrency
- open / leased / idle connections and lease age
- queue depth / oldest age / retry distribution
- message-class expiry and idempotency policy
- canary result, drain ceiling, rollback trigger, and owner
Inspect the real 3-section Markdown sample before paying: https://npub134g96x4m3hdmasye8knm0f7r5dj7rswrr36radz5a80ct6sevdlq82wr2y.nsite.lol/web3-email-auth-operations-kit-sample-v1.md?utm_source=nostr&utm_medium=social&utm_campaign=smtp_queue_backlog_incident
The complete 13-section operations kit is available through accountless encrypted checkout: https://npub134g96x4m3hdmasye8knm0f7r5dj7rswrr36radz5a80ct6sevdlq82wr2y.nsite.lol/?utm_source=nostr&utm_medium=social&utm_campaign=smtp_queue_backlog_incident
Settlement is exactly 5 native USDC on Base Mainnet. No account, email address, wallet seed, private key, or provider credential is requested. The kit supplies reusable operating templates; it does not repair a live outage or guarantee inbox placement.
#EmailSecurity #SMTP #IncidentResponse #Web3 #USDC
Announcing blastits 🚀 — a self-contained, high-performance Go CLI tool for broadcasting Nostr events across thousands of relays concurrently!
Repo: #naddr1qq…qt7j
Web: https://nostrhub.
io/naddr1qvzqqqrhnypzp7peldn3gkv2wgeap8dag2hc9nyhs8g04ft5wnccgxhepdwfxzfeqythwumn8ghj7emfwsh8xcm4vfsnxv3n9e3k7mf0qys8wumn8ghj7un9d3shjtnkv9hxgetjwashy6m9wghxvctdd9k8jtcqpp3xcctnw35hgucqv4e7h
Communication is a virus spread through means of networks.
Information is a prison built to extract energy our souls.
Words are a reflection of the mathematical universal process.
An observer receives a ticket-resolution email, but the requester does not. That recipient split usually points to application routing before SPF, DKIM, or SMTP transport.
Before changing DNS:
1. Compare the solution-message author ID with the requester ID. A branch such as `if ($requester !== $author)` intentionally suppresses a self-notification.
2. Log the final recipient IDs and addresses after every author, anonymization, and deduplication filter.
3. Separate the ticket-creation receipt handler from the later message-notification handler. A creation receipt can succeed while a solution notification follows different recipient rules.
4. Have a different agent author one controlled solution. If the requester then receives it, the author-exclusion branch is confirmed.
An observer receiving the same solution makes an application-recipient decision the first boundary to prove. It does not prove every SMTP or inbox-placement condition is healthy.
Build a browser-local evidence packet without entering an address, message, or credential: https://mail-domain-check-zac2.coral-ibis-2405.chatgpt.site/tools/verification-email-triage/?utm_source=nostr&utm_medium=social&utm_campaign=ticket_closure_recipient_routing
#EmailSecurity #TransactionalEmail #SMTP #Debugging
High-speed Nostr Broadcasting powered by blastits 🚀
Thoughts on these stats sheets?
https://i.nostr.build/01tdhWrlfwfbzv3d.webp
My best so far after the second attempt
I'm up toward Fort Hood. I'm an Army brat. 😂
But we drive down to Austin, sometimes. Were in Cedar Park, yesterday, for a walk on the sculpture garden path, which was lovely. And had some Lebanese food. Yum!
I'm usually asleep by 9 PM. That's not even the jet lag. That's just me being an old lady. 🙈
No, por suerte yo estoy a unos 30Km y el fuego se está extendiendo hacia el otro lado. El único efecto que estamos teniendo aquí es que está el ambiente totalmente lleno de humo. Es desagradable respirar fuera.
I never trusted that smarmy fuck from the first moment I saw him. Always seemed like a cheap second hand double glazing salesman.
https://cdn.midjourney.com/268d7423-8532-49bf-ad89-39fc72862398/0_2.png
You're right but something strange happened in Bergamo (italy) from 02/2020 to 05/2020
Hospitals were full, the mortality spikes up in 3 months.
I don't think the first covid wave in Bergamo was a natural virus evolution
https://media1.tenor.com/m/9QlItb73ISQAAAAC/gandalf-lord-of-the-rings.gif
... the common flu was rebranded as covid. This was so evil
网友评论：SM（数码）员工
https://media.libernet.app/s/hbW90a.jpg
📰 **In this week's issue:**
**The CEO Who Just Declared War on Bitcoin’s 21 Million Cap**
New York
https://image.nostr.build/48713a0b2f48cd5c256bd36a6eaff77847f2d6bf09e00122f1f331559c9ecc8a.jpg
What happens when the most defended number in crypto gets publicly attacked by a Zcash co-founder? The community’s respo...
https://nostrmag.com/article/w29bitcoin02
id#656303427
I thought so 😂 see plenty of small bait fish around here, haven't seen many bass this year, but I know they're about
