hey all,
my company is currently searching for a web based mailing list service for our clients to be able to receive emails from us about updates and whatnot and be able to remove themselves from that service and add themselves when they please....one i've been told about was jangomail...are there any others out there better then jango? if anyone knows of other services, please let me know...thanks!

Dani AI

Generated

For — short, practical advice that builds on ’s “build it yourself” idea and ’s pointers to packaged tools.

Three realistic paths: hosted provider (fast setup, deliverability/bounce handling and unsubscribe built in), a ready open-source package (quicker than coding from scratch), or a custom system (lowest recurring cost but higher development and operations work). Building is reasonable if the team can handle queueing, bounce processing, throttling, authentication (SPF/DKIM), and legal/opt-in requirements; otherwise a hosted service buys that expertise.

Minimal self-hosted architecture and a tiny schema to start:

-- subscribers
id INT PK, email VARCHAR(255) UNIQUE, status ENUM('pending','active','unsub','bounced'),
token CHAR(32), created_at DATETIME

-- suppression_list
email VARCHAR(255) PK, unsub_at DATETIME, reason VARCHAR(255)

-- mail_queue
id INT PK, subject VARCHAR(255), body TEXT, scheduled_at DATETIME, status ENUM('queued','sending','sent','failed')

Workflow: add subscriber → send confirmation (double opt‑in) → mark active only after confirmation. Insert sends into mail_queue; a worker (cron/service) pulls small batches, sends via SMTP, logs successes and bounces, and immediately writes hard bounces to suppression_list. Always include a one-click unsubscribe tokened link and honor it immediately.

Exchange note and deliverability: Exchange is a mail server, not a database host. Keep the DB on a web/DB server and send mail through a reliable SMTP relay or a dedicated sending service if volume or reputation matters — sending large lists directly from an Exchange IP often causes throttling or blacklisting. Configure SPF/DKIM, provide a List-Unsubscribe header, include plain-text alternatives, and throttle sends to avoid ISP blocks.

Operational cautions: treat bounce handling, suppression, segmentation, and testing as core features, not extras. If time or resources are limited, use a hosted or packaged solution to avoid reinventing nuanced deliverability and compliance work. Follow applicable anti-spam and privacy laws and document opt-ins and unsubscribes for auditing.

Recommended Answers

All 3 Replies

Not sure if it is an option but why not create something your self?

Its not very difficult to setup a database store lists of mail and then set a flag ACTIVE or INACTIVE and let them mail out...

Just seems like paying for that kind of service is silly.

[/opinion]

i actually havent checked out dadamail or hotscripts...i'll check them out today. how would i go about setting up my own DB for something like that? it would obviously be setup on my exchange server, correct? or does it not matter? if i could set it up myself, that would actually be a good idea so we dont have to waste $$

thanks!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.