1. I take it that you refer to the Email Connector, the other connectors do not have this functionality.
In almost all cases the send result should be returned to the sender of the message so I don't think there is a good reason to change the way it works at the moment. It is possible to use HTTP callbacks to change the email address of the sender of the message but this is not trivial.
2. Diafaan SMS Server is designed to make sure, as much as possible, that a message will be sent. In some cases this means that the message is repeated unnecessarily if the result of the previous send attempt is unclear.
If the message has a bad number format, it is possible that one gateway won't accept the message but another one will, therefore Diafaan SMS Server will keep trying to send the message. One way to add support for your request that does not change the default behavior is to add an option to enter a list of permanent error codes for each gateway. I'll add that option to the requested feature list.
3. There is no simple way to do this but you can use HTTP callbacks to forward error events to a PHP script (locally or on a web server). The PHP script can then write a log file to the intended network location.
I wished to pose some suggestions on how you could improve Diafaan at least in the use cases I deal with on a daily basis.
1. Connectors have an option to reply to the email in the case of a failure, it would be great if instead of sending it back to the source, you can specify the email address that failures should be sent to. This allows us to send the messages to the admin of the app sending the messages without them having to use their personal email as the source address of the message which is just poor admin practices.
2. In our setup, we use a combination of Twilio and a PORTech MV-372 with two SIM cards as a backup. What I see as the result is anytime a number is bad and rejected by Twilio, Diafaan assumes that this was a failure of Twilio and in turn sends it out the GSM Modem which of course eventually sends a reply saying hey, this is a bad number. I am not sure that is bad logic, but it would be nice to be able to have Diafaan send a message when Twilio rejects a number rather than send it to the GSM Modem. To me, a failure to deliver due to rejection is different than a failure due to inability to connect. Perhaps some way to toggle this.
3. I wish there was a simple way to have a continual simple text or CSV log be continually written per connector that I could store on a network drive that I could share with the app specific owner who uses the connector in Diafaan so they can check for errors and verify sending themselves. As it stands now, I have to export the logs and send to them or give them much more access to Diafaan that I want to. I wish I could just given someone read-only to their connector at best.
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 485
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 894