Support

All our products use the standard JMail API in Joomla! to send email. If you do not hook into JMail for your custom mail queue you'll have to modify the source code of our software. If you modify the source code of our software you will no longer be eligible for any kind of support.

Instead of hacking core you can very simply overload the JMail API like CCMandrill does. FWIW we are using CCMandrill on our own site to send all transactional email, including the one notifying you for this reply, through Mandrill. It is licensed under GPL and would make a perfect example on how to properly implement what you're trying to do ;)

No. We will not add anything to our code. As explained, our code uses Joomla!'s standard JMail API to send out emails. This is what we have to do to be Joomla!-compatible and that's the only thing we're willing to do. Basically, I'm not willing to have our developers debug your code for free.

Feel free to fork the relevant plugin (under plugins/ats/postemail). BUT! If you do that we won't provide any more support regarding any email related issue to you. Why? Our plugin uses the Akeeba\TicketSystem\Admin\Helper\Email::getMailer to get a JMail object configured in such a way that guarantees emails will be sent correctly, including attachments. Instead of that you are going to use your own code which stores "stuff" in the database and then "does something" to send it as email. I can't guarantee that your code covers every possible case or that it even works for emails with attachments. I strongly doubt it since you say that you THEN use JMail in that "does something"step. I consider it 99.9999% certain that your code will screw up email delivery for ATS. We're not going to debug your code for free, therefore no support for email issues to you. Fair enough? :)

Moreover, do note that ccMandrill does not use Siteground's SMTP servers at all. It uses HTTP requests to Mandrill's service to send the emails. As such, it is not confined by the restrictions set by Siteground regarding the use of their server's SMTP service to send out emails. I don't understand why you are implementing a mail queue for Mandrill. Mandrill is its own mail queue. That's the entire point of using it instead of SMTP. That's why we switched to Mandrill – we're hosted on SiteGround too. We had too many transactional emails to send and we were hitting SiteGround's daily message limit.