| |
| Search found 5 matches |
| Author | Message |
|---|---|
| sebrewer Replies: 5 Views: 18042 |
|
| Probably the cleanest way to automate this is to use a scripting language like Perl or Python to periodically scan the appropriate logfile(s) to look for the results of your test page, and have it e-mail/page you on an error ... | |
| sebrewer Replies: 2 Views: 12427 |
|
| You might also look at using Perl ... the SMTP.pm module is quick and easy to use, and I've found it to be highly reliable ... with a little clever scripting you can use it to build a multi-platform solution generate page or e-mail notifications. | |
| sebrewer Replies: 6 Views: 21189 |
|
| I encountered this issue as well. I guess I saw it about once every 2-3 months, and sometimes I'd get several occurrences at a time. I'd be interested to hear NotePage's take on it.
At the time, I was attributing the problem to the fact that the offending source e-mails were being generated by Visual Basic components in our world. I figured that the weakness was in the MS libraries, since I never saw the issue happen with pages sourced from any other system (and there were several of these, all non-Microsoft, with relatively high volumes). Opening the pagegate.mdb in MS Access and deleting any rows containing null message fields fixes the problem immediately. If you have multiple dialers, pages will still continue to trickle through the bottleneck, but very, very slowly. |
|
| sebrewer Replies: 8 Views: 35487 |
|
| ... FYI, I'm using PageGate ... found this post while searching the forum. PageGate shows a different error message, indicating that the ClientOriginator is bad ... | |
| sebrewer Replies: 8 Views: 35487 |
|
| I would be interested in seeing this solution as well. Is there any way to specify a sender ID as well as a password when defining a WCTP carrier ? | |
All times are GMT - 5 Hours |