Board index » delphi » SMTP SMS Indy

2005-10-06 10:13:41 AM
delphi167
Hi All,
I'm putting text messaging to cell phones in my application for use in USA.
In MS Outlook I can compose an email and send it to my cell phone by
addressing it to XXXX@XXXXX.COM. My carrier is Verizon and vtext.com
is their SMS gateway server. I have a fairly complete list of all the other
major wireless carriers in USA. Thus, this means that you can send an email
to a cell phone and have it show up as a text message.
When I try to do this in my Delphi app with a Indy SMTP component the email
gets rejected by vtext.com with a 'SMTP connection refused' message.
Do I need to do this with a SMS gateway server that costs money? Is this
becuase of possible spam reasons that it gets rejected? Lastly, why can I
do this from MS Outlook, how is it getting the email to vtext.com where the
SMTP component doesn't?
Thanks,
Joe
 

"Joe Reiss" <XXXX@XXXXX.COM>writes
As for 'connection refused', that error means that you tried to connect to a
port that does not have a server socket listening on it. Double-check your
Host and Port settings in TIdSMTP.
that Outlook is NOT doing that. You should be sending messages through your
ISP's own SMTP server.
Gambit
 

Thanks for responding:
settings.
Below is additional data that I get back:
"
Reporting-MTA: dns; imf24aec.mail.bellsouth.net
Arrival-Date: Wed, 5 Oct 2005 17:52:27 -0400
Received-From-MTA: dns; ibm71aec.bellsouth.net (65.9.193.37)
Final-Recipient: RFC822; <XXXX@XXXXX.COM>
Action: failed
Status: 5.1.1
Remote-MTA: dns; smtpsp.vtext.com (66.174.76.30)
Diagnostic-Code: smtp; 550 SMTP connection refused
"
Thanks,
Joe
 

"Joe Reiss" <XXXX@XXXXX.COM>writes
server is working fine. It is the SMTP's own connection to the SMS network
that is not working. There is nothing you can do about that other than to
talk to your ISP about it.
Gambit
 

I saw another lengthy thread you had with 'Chris' on the
atozedsoftware.indy.smtp newsgroup on this exact same issue. He is having
the same problem as me. I am beginning to think that this is a issue with
Verizon and possibly the Indy component idSMTP.
I'm a newbie in port sniffing, however, I will do what it takes to resolve
this.
Do you have any other insight on this issue?
"Remy Lebeau (TeamB)" <XXXX@XXXXX.COM>writes

"Joe Reiss" <XXXX@XXXXX.COM>writes
Gambit
 

OK Remy, I got the answer.
Apparently, the Indy component (version 8) was being blacklisted by Verizon
and who knows who else. Anyway, I had gotton the following info (don't
remember from where anymore) to do the following:
"
A SMTP server is treating E-Mail from my program as if it was spam or the
server rejects it with a 554 error. I don't have any problems with Outlook.
How do I fix this?
Previous Top Next
The reason this is occuring is because some spam filtering software is
screening E-Mail for the "X-library:" header. This header is sent by Indy
8.0 and the release versions of Indy 9.0. In and of itself, this is not
bad. However, some malware such as spam bulk E-Mails and even a worm
(W32/Nicehello@MM), were built with Indy meaning that they sent the same
"X-Library:" header that most Indy-based E-Mail programs do.
For this reason, we have decided to remove the X-Library header from Indy
9.0 code and you can obtain it from our VCS. Instructions are at:
www.indyproject.org/download/DevSnapshot.html
If you are using Indy 8.0 and you can't upgrade to this code, you can
remove the X-Library header by editing IdMessage and removing line 439 which
reads:
Values['X-Library'] := gsIdProductName + ' ' + gsIdVersion ; {do not
localize}
and then rebuild Indy using the FULL*.BAT file for your system.
"
I commented out the line, did the rebuild, it then worked like a charm.
Thanks,
Joe
 

"Joe Reiss" <XXXX@XXXXX.COM>writes
versions, service providers started blacklisting Indy-based messages because
of that. Then Indy started working on making itself more
standards-compliant, even to make extra efforts so that high-level spam
filters such as SpamAssasin would stop rejecting Indy-based messages just
because they were sent by Indy.
Gambit
 

Email is not SMS. SMS is limited to 160 characters per message. This,
however, is not your problem.
The SMS space has several interesting quirks:
1) Bulk SMS needs to go through a carrier. This means charges of around
$0.07 per message.
2) Bulk SMS requires a short code ($500/mo fee) for all US bound SMS
traffic unless your carrier provides one for you -- this is a recent
change by the CTIA. Some carriers are providing the short codes and
routing as their customers adjust. However, that can stop at any time.
3) Individual SMS usually needs to be sent from the same network carrier.
4) Verizon requires that you use secure SMTP sign-on to send e-mail.
5) Verizon does not expose their SMS gateway except from their web page.
6) They may be blocking your email client because of it is headers.
Good luck.
Charles
Joe Reiss writes: