On Apr 7, 2016, at 11:20 AM, Phil McKerracher phil@mckerracher net [Dada Mail Developers] dadadev@PROTECTED wrote:

That’s interesting The limitations of shared hosting are one issue, but the more important issue here is that Dada Mail can fail to deliver a large number of messages with no obvious indication to the user I for one wasn’t aware that was possible It’s not a bug exactly, but I think it’s definitely worth a feature request to have some indication on the sending screen when this happens

But that's because say, the sendmail command isn't returning an error, when it basically says it would if there is one The mechanics are there to tell you if there's a problem with mail sending - it's just not being utilized - or actually it's just been disabled - the host doesn't tell you that it's that way, they just leave you hanging It's totally infuriating

That's also one of the reasons why

(1 there's a way to test a mass mailing by just sending one message out (the test message isn't getting received? That's strange…)

(2, ditch using the shared mail server on your shared host and use Amazon SES, which doesn't do these types of things If messages bounce, or there's a complaint - they tell you That's worth the $100 per million messages they charge

(3 - the Tracker will give you that data - (no opens/clickthroughs/bounces - also strange!) THAT information is also listed on the message's monitoring screen - and is also sent to you by default, in the "mass mailing finished" notification

If you're on a shared host, just finding out what your hourly email limit is, and setting up your mailing list to work within that limit can save a ton of headaches Again, the SES service advertises to you what your limits are, and because of that, Dada Mail can automatically work within those limits