Difference between revisions of "MT SMTP Auth"

From SMS Wiki
Jump to: navigation, search
 
(7 intermediate revisions by one user not shown)
Line 1: Line 1:
Sending SMS messages by SMTP Auth is fairly straightforward. Essentially, your application will send your username and password as authentication credentials when connecting to our SMTP server. Your application will submit your account credentials in plain text.
+
Sending SMS messages by SMTP Auth relies on an email server to authenticate a request for sending email. An application connects to the SMTP server using a valid username and password (in plain text) as authentication credentials and sends a specially formatted email message to request the server to convert the information stored in this email into SMS and send it.  
  
 
SMTP host name:  '''smtp.upsidewireless.com'''  
 
SMTP host name:  '''smtp.upsidewireless.com'''  
  
There is a second phase of authentication that occurs internally, verification of the senders email address. It must be in the form of '''username@smtp.upsidewireless.com''' where you would replace 'username' with your actual username (for example jsmith@smtp.upsidewireless.com).
+
There is a second phase of authentication that occurs internally, verification of the senders email address. It must be in the form of '''username@smtp.upsidewireless.com''' where 'username' represents an actual account name with our service (for example jsmith@smtp.upsidewireless.com).
  
If the sender email address is not exactly as specified above, you will receive the following error: "503 Incorrect Authentication for Specified Email Address"
+
If the sender email address is not exactly as specified above, an error is returned: "503 Incorrect Authentication for Specified Email Address"
  
  
Line 19: Line 19:
 
Once your application has authenticated with our server and sent the message, your message will be routed. If the route is successful, the credits for that message will be deducted from your account.
 
Once your application has authenticated with our server and sent the message, your message will be routed. If the route is successful, the credits for that message will be deducted from your account.
  
Please refer to the list below for examples of applications that send using SMTP Auth.
+
Please refer to the list below for examples of applications that send using SMTP Auth (provided for your convenience only).
  
* [[Send SMS from your C# application]]
+
* [[Send SMS from PHP]]  
* Send SMS from your PHP application
+
* [[Send SMS from Java]]
* Send SMS from your Java application
+
 
 +
 
 +
----
 +
[[APIs | back]]

Latest revision as of 22:44, 8 May 2008

Sending SMS messages by SMTP Auth relies on an email server to authenticate a request for sending email. An application connects to the SMTP server using a valid username and password (in plain text) as authentication credentials and sends a specially formatted email message to request the server to convert the information stored in this email into SMS and send it.

SMTP host name: smtp.upsidewireless.com

There is a second phase of authentication that occurs internally, verification of the senders email address. It must be in the form of username@smtp.upsidewireless.com where 'username' represents an actual account name with our service (for example jsmith@smtp.upsidewireless.com).

If the sender email address is not exactly as specified above, an error is returned: "503 Incorrect Authentication for Specified Email Address"


The message format is as follows:

The "To:" field must be in the following format +NNNNNNNN@sms.upsidewireless.com where the 'N's are replaced with the number you wish to send to. The number must be in international format.

The "Subject:" field contains parameters for modifying the contents of the message to further compress the text while maintaining human readability. The parameters are comma separated and correlate the the following options: a = abbreviate certain words, p = delete prepositions, c = delete spaces. If you leave the subject empty, the message will be sent without any compression being applied. For more information please consult the SMS compression options page.

The "Body:" of your message can be any length, however your account settings and network will determine how long each SMS message ends up and how much of text is sent by splitting the message into the maximum number of parts you indicated in your account. In general the message will be split into pieces that have roughly 150-160 characters in them.


Once your application has authenticated with our server and sent the message, your message will be routed. If the route is successful, the credits for that message will be deducted from your account.

Please refer to the list below for examples of applications that send using SMTP Auth (provided for your convenience only).



back