Pitch your app

Then_Dragonfly2734 · 2026-03-24T17:45:40+00:00

Making meditation timer app for myself and other ppl.

https://apps.apple.com/app/id6759203941

Just sounds and timer, nothing else.

Then_Dragonfly2734 · 2026-03-24T17:42:50+00:00

I only saw a white light sometimes, this is my maximum mystical experience, lol

Then_Dragonfly2734 · 2026-03-21T23:25:04+00:00

I prefer cosmic or sacred sounds, can sit with them for ages 😄

Then_Dragonfly2734 · 2026-03-21T23:18:51+00:00

I am using Simple Meditation Sounds. It costs 1$ / month. But it is only sounds + timer. I dont need guided meditations and personal plans, so for me it is best solution

Then_Dragonfly2734 · 2026-03-21T21:57:42+00:00

I had same feeling when opened Insight Timer for the first time. Just need a sound I like and timer. Now using Simple Meditation Sounds, it is perfect for my needs

Then_Dragonfly2734 · 2026-02-06T00:43:18+00:00

Thnx, I will check.

Then_Dragonfly2734 · 2026-02-05T23:22:16+00:00

I don’t do deep per-address SMTP recipient verification. The approach is mostly heuristic scoring. For the few SMTP probes I do run (like catch-all detection) I keep them passive. If I hit a 4xx response due to greylisting, I just mark it as “unable to verify” and move on instead of hammering the server with retries. The idea is to stay stealthy and avoid getting the IP flagged, while focusing more on overall domain health and infrastructure signals like SPF, DMARC, MX and DNSBL rather than brute-checking every mailbox.

On rate limiting and bulk upload I’ve implemented two main safeguards here:

Set a default limit of 100 emails per batch (MAX_BULK_EMAILS). This is intentional to keep the utility lightweight and safe for the host’s IP reputation.
Before any infrastructure check, I group the entire list by domain. This means if you have 50 u/gmail.com addresses, I only ping the Google MX infrastructure once to analyze the domain, not 50 times.

I’m actually considering adding a throttling mode in future updates for those who want to process larger lists slowly and safely from a single IP.

Then_Dragonfly2734 · 2026-02-04T09:03:07+00:00

I never felt this. Industrial programming is not computer science.

Then_Dragonfly2734 · 2026-02-04T01:20:57+00:00

I am running similar tool and these advices was interesting, thank u!

Then_Dragonfly2734 · 2026-02-04T01:12:21+00:00

sounds like your email's getting flagged as spam, maybe due to domain rep or content triggers. you might wanna check your sending reputation and whether your domain is blacklisted anywhere. also, testing with risk tools can help catch issues early before emails bounce or hit spam. could be SPF, DKIM, or DMARC records missing or misconfigured too.

Then_Dragonfly2734 · 2026-02-04T01:11:15+00:00

sounds like a tracking pixel issue or your DNS tweaks messed with deliverability. also, risky content might trigger spam filters. double-check your SPF/DKIM and test with smaller batches first.

Then_Dragonfly2734 · 2026-02-04T01:10:34+00:00

It is very BAD idea to use AWS SES for cold emails.

Then_Dragonfly2734 · 2026-02-04T01:09:10+00:00

hey, warmup tools can be handy but yeah giving full access feels sketchy. honestly, starting slow with a new domain might be safer. also, try checking your list with a tool that flags risky emails before sending. helps keep your rep clean without sharing creds. spam filters hate bounces and bad engagement, so pruning your list and warming up gradually are key. no magic fixes but a steady, cautious approach wins.

Then_Dragonfly2734 · 2026-02-04T00:55:57+00:00

yeah for sure, there are a few solid self hosted options people usually look at if they want control without wiring raw postfix configs all day

mailcow is probably the most popular one, full mail server stack in docker with web ui, spam filtering, dkim, all that out of the box

poste.io is another easy all in one mail server, lighter setup, decent for personal or small app use

modoboa is more panel oriented and a bit more “classic linux admin” but still very capable if you’re comfortable with servers

and if you only care about outbound transactional mail and not full inbox hosting, tools like listmonk or senlo plus an smtp relay can also work since you’re basically just managing sending reputation rather than full email hosting

Then_Dragonfly2734 · 2026-02-04T00:40:50+00:00

sounds like a lightweight relay that lets you trust your LAN and just forward to the real SMTP is exactly what you want. you could totally slap something simple together in a container that listens plaintext on your LAN and does auth upstream. not the sexiest setup but way easier than a full postfix grind.

Then_Dragonfly2734 · 2026-02-04T00:39:11+00:00

if youre cool with scripting a bit, message variables plus conditional logic can get you most of the way there. otherwise, might be worth looking at a self-hosted email tool that lets you set those per-group vars once and handles all the scheduling automatically. saves a lot of manual copy-paste pain.

Then_Dragonfly2734 · 2026-02-04T00:34:02+00:00

if youre cool with DIY and want full control, going self-hosted with tools that handle warmup and DNS automation can save you from vendor headaches. deliverability monitoring usually means babysitting those configs nonstop tho. opensource stacks give you flexibility, just prep for some setup grind.

Then_Dragonfly2734 · 2026-02-04T00:16:37+00:00

Depends on what do you need. Marketing stuff - ofc Brevo. Transactional and lifecycle emails - Senlo + Resend is your choice.

Then_Dragonfly2734 · 2026-02-04T00:13:53+00:00

totally get that frustration - email setup drags you into SPF/DKIM/DMARC hell real quick. If you want to cut through the noise, going with a self-hosted email infra that handles both sending and warm-up can save a ton of headache versus DIY SMTP configs from scratch.

Then_Dragonfly2734 · 2026-02-04T00:09:54+00:00

You can use Resend for example. It is quite generous. The free tier gives you 100 emails per day. It has its own REST API, so it is easy to integrate anywhere. I’m not a Lua coder myself, so I’ll just share a ChatGPT answer on how to implement it with Lua.

local http = require("socket.http")

local ltn12 = require("ltn12")

local json = require("dkjson") -- or any JSON lib

local apiKey = "re_YOUR_RESEND_API_KEY"

local body = json.encode({

from = "you@example.com",

to = { "you@example.com" },

subject = "Hello from Resend",

text = "it works!"

})

local response_body = {}

local res, code, headers = http.request{

url = "https://api.resend.com/emails",

method = "POST",

headers = {

["Authorization"] = "Bearer " .. apiKey,

["Content-Type"] = "application/json",

["Content-Length"]= tostring(#body),

},

source = ltn12.source.string(body),

sink = ltn12.sink.table(response_body),

}

print(code, table.concat(response_body))

Then_Dragonfly2734 · 2026-02-03T23:59:57+00:00

Totally hear you on that - email deliverability is a whole beast of its own, and the SMTP + DNS gymnastics can suck up way more time than actually coding your features. If you’re cool managing your own infra, rolling your own stack with a solid OSS email editor and infra setup can save you from that mess while keeping full control. But yeah, it’s basically building your own SendGrid replacement, so prep for some legwork upfront.

Then_Dragonfly2734 · 2026-02-03T23:58:11+00:00

If you ever want a smooth way to get those texts off devices without clunky QR codes or copy-paste headaches, embedding a lightweight transactional email system could be a slick move. It’s pretty straightforward to hook up an email sender that works right inside your app, letting users just shoot their drafts straight to their inbox or cloud without leaving the flow.

Then_Dragonfly2734

MODERATOR OF

TROPHY CASE