Hi Guys. We've got a dispatching program at work that uses SMTP to send emails to our technician's phones. We've had nextel phones for years and we recently switched to verizon because nextel's coverage is horrible in some of the areas we are working regularly.
So, I'm sending pages to the technicians phones via the 10-digit phone number @ vtext.com (email@example.com
). However, two problems I'm running into - (1) vtext limits texts to 140 characters and then just truncates whatever is after that - nextel didn't do that. So we're working around that for now. (2) because of the way I have to have it set up, we're getting blocked by vtext pretty regularly as being some kind of spammer.
The way I've got things configured is the dispatch software is pointed to our local exchange server (server.domain.local) which I have pointed to a yahoo smtp server via a Smallbusiness SMTP Connector (server is running SBS 2003). I don't honestly remember how I arrived at that arrangement a few years ago (when this was giving us trouble before) but I needed to have an SMTP server that didn't require Encryption, which I think just about all of them do now. It was working fine with the nextel phones when they had service, but now with the verizon phones (that have much better service) it's been nothing but painful.
So, the dispatch program sends it to the exchange server that forwards it the yahoo smtp server that sends it to vtext and ultimately to the phone, assuming we haven't exceeded some kind of spammer limit and been blocked by vtext.
At this point, I know the proper thing would be to upgrade my dispatch sofware to a version that supports encryption, and that's on the to-do list, but right now there isn't time or money for that. I don't know enough about the ins and outs of exchange to fix it on my own, so there might be a solutio there I'm missing.
Short term, I plan on switching to using mobile email on the phones (I have 2 configured as a test right now) to get past the 140 character limit of vtext, but I'm not confident that the whole limit thing with getting bounced as a spammer won't happen again.
We're not sending that many messages (maybe 100 a day?) but I think my exchange server isn't really a trusted source or something like that (we have a dynamic IP too) which might be causing some of our pain but that's the only way I could get it to work with our program.
So, all of that to say - does any one have any ideas or know a more reliable solution I should be looking at? Any "trusted" smtp servers that don't require encryption? Authentication (username and password) I can do, but not encryption.
Thanks in advance.