I have no quota limits. What sending settings could be causing this? Also, what malformed data could there be and how can I identify it?It could stem from quota settings or sending settings or if you have an old version and data was from that time the app can get stuck from malformed data.
It'd be easier if you'd post screen shots of all of them. It could be e.g. no reset on quota, but in your case it is more on/off, this could be from overload, I saw s/t like this on someone else's server, their dbf was not optimized, and the DS' queue can get filled.What sending settings could be causing this?
This could be if you have some of the elsewhere on the forum mentioned characters that are not being processed properly by SwiftMailer. Also, if you imported data a few versions earlier other malformed data could have persisted. This is also elsewhere on the forum. I recommend using PHPmailer, it was in my tests 2.6x faster than SwiftMailer (and does not have those mentioned problems); it also does not delay (hang a bit) which can be observed in verbose sending (especially when you run many processes in pcntl).what malformed data could there be and how can I identify
It is possible, but I don't think this is the problem for two reasons:
I lowered the delivery settings and same problem just happened. What the heck is going on?
See my post 10 days ago. Post all sending settings, all relevant logs, and verbose sending output. This may allow helpers to become more specific.I lowered the delivery settings and same problem just happened. What the heck is going on?
It doesn't happen all the time, but it is happening periodically.
Again, what logs and how to get verbose output? If I knew what logs to look at, I would be able to figure out why myself.See my post 10 days ago. Post all sending settings, all relevant logs, and verbose sending output. This may allow helpers to become more specific.