-revolution.278305.n4.nabble.com/Sending-mail-from-on-server-tp4670581p4670583.html
Sent from the Revolution - User mailing list archive at Nabble.com.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe
support@on-rev about a week ago and apart from the
automated reply never heard any more from them...
Can any of you shed some light?
Kind regards
Dave
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Sending-mail-from-on-server-tp4670581p4670583.html
Sent
.nabble.com/Sending-mail-from-on-server-tp4670581p4670583.html
Sent from the Revolution - User mailing list archive at Nabble.com.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
/Sending-mail-from-on-server-tp4670581p4670592.html
Sent from the Revolution - User mailing list archive at Nabble.com.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
On Thu, Oct 3, 2013 at 11:35 AM, Dave Kilroy wrote:
Hi, I decided to email support again and got the following reply:
Thank you for your request.
We are very much aware of this issue and are actively working on it. As
soon as we
have a solution we will let you know.
Regards,
Roger-
Thursday, October 3, 2013, 11:44:11 AM, you wrote:
Is that server configured for assynchronous communications? shameful
groan
--
-Mark Wieder
mwie...@ahsoftware.net
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit
ZING!
On Thu, Oct 3, 2013 at 3:27 PM, Mark Wieder mwie...@ahsoftware.net wrote:
Roger-
Thursday, October 3, 2013, 11:44:11 AM, you wrote:
Is that server configured for assynchronous communications? shameful
groan
--
-Mark Wieder
mwie...@ahsoftware.net
Runrev support does not respond, so asking help from the community.
There used to be a good code strip in the LC guides, which allowed kicking out
e-mail from the server. Great way to automate a lot of follow-up and support
for your app.
For a couple of weeks ago someone changed something in