adding new senders to MW with api

[Jeff Guynn]

I'm experimenting with TurboSMTP as a sender: http://serversmtp.com/. MW already makes provisions for me to do so via SMTP, so non problem there.

But TurboSMTP also has api: http://serversmtp.com/en/smtp-api

If I wanted their api to be a part of MW, what's the process for getting support behind that idea?

MW already has numerous sender api options, so this isn't urgent at all. Just curious about how MW functionality is expanded moving forward. Thanks.

 

[twisted1919]

The easiest way is to look in apps/common/models for DeliveryServer[NAME]WebApi.php files and see how they are implemented

 

[Jeff Guynn]

@twisted1919 - Are you saying all I need to do is configure an appropriate file named DeliveryServer[TurboSMTPWebApi.php, upload it to the same folder, and I'm done?

How does my new addition become included in the choices presented here: backend/index.php/settings/customers/servers?

 

[twisted1919]

@Jeff Guynn - It would be perfect if it would be that simple, but what i wanted to tell you is that that is a starting point to code your own because it's a great example. It requires to have some PHP/OOP knowledge though.

How does my new addition become included in the choices presented here: backend/index.php/settings/customers/servers?

There's a mapping in place for this, shown in apps/common/models/DeliveryServer.php at line 697, but again, needs some php knowledge