Hi John,
At 10:21 AM 07-04-2025, John Levine via mailop wrote:
I'm consulting for a non-profit that needs to upgrade its mail
system. They send
about 100,000 messages a day, a combination of a nightly update message that
people can subscribe to, and transactional mail reporting when things happen.
There's no discussion lists, and the inbound mail is a relative trickle,
adequately hosted at Google. The mail stream is very clean and most of the
complaints we get are people asing where's my nightly update when the job that
creates them burps.
It's currently running through an old sendmail server but surely we can do
better than that. What should I use? We particularly want good logging so when
someone asks why didn't I get my update we can tell them without grepping
through a whole day's logs. We also have problems of people signing
up with fake
addresses so I need to be able to collect signup confirmation failures fairly
quickly and turn off the corresponding accounts. (Yeah, I know about sending a
message with a link, but people use throwaway address places that
work for a day
and then stop.)
I have a place to host a VPS and send mail which is not Google or AWS or Azure
so that's not a problem.
I operated a system which sent emails to customers. The emails being
sent out using VERP. The sendmail logs were parsed to track delivery
status. You may be able to get similar functionality with other
MTAs. I probably used some queueing tweaks on the MTA end. One of
the goals was to be able to answer questions such as "was the email
delivered to X?" The information was accessible through a web interface.
The usual mail servers should be able to send 100,000 messages daily.
Regards,
-sm
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
