SMS SMTP Interface
Send SMS through E-Mail even without programming skills.
Messages to the SMTP interface MUST contain ASCII-Plaintext. Special characters MUST be encoded using ISO-8859-1 standard. HTML or any other encoding will be rejected. E-mail- and webmail-clients, sending HTML-encoded e-mails are not suitable for testing purposes (e.g. GMail etc.).
Valid destination addresses
Sends a plain text message to an SMS recipient. The subject line must contain at least the userkey, the password and the recipient number.Example:
Optionally, the SMS originator can be specified in the subject line. Use: Originator=MYORIGINATOR
In case the subject line doesn't accept the necessary number of characters, you can just use the first letter to adress the keyword:
Userkey = U, Password = P, Recipient = R, Originator = O.Example:
Delivery status notifications for SMS
The optional subject line parameter "Notify" can be set to the following values:
Email notifications are sent for the statuses "Delivered","Buffered" and "Failed".
No Email notifications will be sent.
Email notifications are sent for the status "Failed" but not for the statuses "Delivered" and "Buffered".
Email notifications are sent for the statuses "Delivered" and "Failed" but not for the status "Buffered".
Sends a plain text message to an SMS recipient. Usage:
From: <SMTP Originator Client>
Body: <MessageText>Important: SMS recipient numbers must start with 00. The plus character is not accepted by the SMTP interface.
From: firstname.lastname@example.org To: email@example.com Subject: Originator=+41760000000 Body: Hello world!
The following applies:
The SMTP interface only processes ASCII Plain Text. Special characters must be encoded in ISO-8859-1 standard. HTML or other code are rejected. E-Mail and webmail clients that send HTML-encoded e-mails are unsuitable for testing (eg GMail etc.).
The subject is optional. If no originator is defined, the ASPSMS system sets the Originator 'SMS' or uses a predefined default Originator (eg +417912345678).
Authentication is based on the sender's e-mail address (SMTP Originator)*. This e-mail address should be different from the ASPSMS account e-mail address. Before SMS can be delivered to <Recipient>@smtp.aspsms.com, the used e-mail sender address must be authorized.
(* This implicit authentication by SMTP Originator means that the sender email address is the "secret" and not the usually used combination of Userkey and password. You therefore should choose an e-mail address which is different from the account e-mail address. It should not be self-explanatory and you have to keep this e-mail address secret, similar to your combination of Userkey and password.)
Settings 2-Factor Authentification on Barracuda SSL-VPN Appliance with ASPSMS
Sends an XML formatted message to the ASPSMS system. For further information on the required XML format see:
Any XML reply from the system will be routed back to the sender's address of the request E-Mail. If there is no sender address, the XML reply will be silently discarded.
The subject line has no meaning for this destination address, and can be left empty.
Outgoing mail server
To send emails to the SMTP interface, you can use your own outgoing mail server, the outgoing mail server of your Internet service provider or the ASPSMS outgoing mail server. Using STARTTLS on port 25 or port 587, the delivery of SMS jobs to the ASPSMS system using the SMTP interface is encrypted end-to-end. For this reason, we recommend using the ASPSMS outgoing mail server via port 587.
Authorized SMTP Originators
In order to use the SMTP interface for sending to recipient addresses according to the pattern <Recipient>@smtp.aspsms.com (e.g. firstname.lastname@example.org), the used sender e-mail address must first be authorized as SMTP originator. This implicit authentication by SMTP originator means that not the combination of userkey and password is the "secret", but the used sender e-mail address. For each authorized SMTP originator a standard SMS originator can be defined. This is used if no SMS originator has been set explicitly.
Click here for the ASPSMS new user registration.
Have you already registered? Log in with your user e-mail address and password.
|Purpose and business examples|
|SMS tools for End Users|
|Try it out now: New SMS Blaster Version||free|
|Microsoft Office Outlook 2013-2016: Email to SMS||free|
|Microsoft Office Outlook 2010 Mobile Service||free|
|Microsoft Office Outlook 2007 Mobile Service||free|
|SMSBLASTER web edition||free|
|SMS Blaster Windows Edition||free|
|SMS touch for iPhone and iPod touch||Shareware|
|ECO-SMS - Ökologische SMS!||Shareware|
|Cybersystems mscrmSMS||see price list for details|
|Jabber-Client Chatopus for Palm OS||small one-time payment|
|delight Software GmbH||see price list for details|
|ASPSMS Widget for Mac||free|
|SMS scripts and interfaces for developers|
|ASPSMS Dot Net Assembly on NuGet||free|
|ASPSMS JSON API (REST)||free|
|C# Microsoft ASP.NET Identity MVC (for SOAP)||free|
|Node.js interface for ASPSMS||free|
|PHP Class for ASPSMS SOAP web service||free|
|SOAP Web Service||free|
|ASPSMS SMTP Interface||free|
|VBscript Class (ASP)||free|
|PHP - Python - C# - Java||free|
|Jabber to SMS for Server Admins||free (open source)|
|SMS Blaster Visual Basic Source Code||free|
|Supported networks around the world|
Latest NewsNew SMS Blaster Windows Version: Try it out now
Supported operators in your country: