{"__v":47,"_id":"5693807af6e0760d005c6174","category":{"__v":3,"_id":"5693740093445b0d00abdad1","pages":["5693740d406c6d0d00a0948e","5693807af6e0760d005c6174","5693b980bcd0a90d0044d1e2"],"project":"568fce2a04440a1700e4cb47","version":"568fce2b04440a1700e4cb4a","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-01-11T09:21:04.208Z","from_sync":false,"order":9,"slug":"email-to-sms","title":"Email to SMS"},"parentDoc":null,"project":"568fce2a04440a1700e4cb47","user":"55116f88e2990b0d00fb0552","version":{"__v":20,"_id":"568fce2b04440a1700e4cb4a","project":"568fce2a04440a1700e4cb47","createdAt":"2016-01-08T14:56:43.101Z","releaseDate":"2016-01-08T14:56:43.101Z","categories":["568fce2b04440a1700e4cb4b","568fd1b8b700ce0d002f4b1c","568fd23804440a1700e4cb5b","568fd2444719c119002ce5d8","568ff21204440a1700e4cbc1","5693732c8aa8040d009f2c28","5693738393445b0d00abdad0","5693740093445b0d00abdad1","56937445974aaa0d001ca699","5693b82173f48f0d0075c90d","5694c4cd1005590d0062cb25","569f854466a5640d00efa54c","56a264cdd15dd70d008d825b","56aa56bf318e6c1700a19ddb","56b0e6347ae4550d000627bd","56b200c0f48f270d00e0de6f","56b200c6f48f270d00e0de70","56b22a9665ddf50d0076ba40","56e92ef71996862200fd7f42","574d6577fb835c0e00ca316a"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-01-11T10:14:18.670Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"## Addressing\nEmail To SMS uses the emails *TO* and *CC* fields to determine what phone numbers the email body content should be sent to as an SMS. *BCC* is ignored. The format of these fields is:\n\n<div class=\"alert alert-success\">{International formatted mobile number}:::at:::dynmark.net</div>\n\nMultiple numbers can be separated using a semicolon or comma, e.g. <span class=\"c-success\">447990123123@dynmark.net;447970321321@dynmark.net</span>\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"If you have been sending email to SMS using the *e-txt.co.uk* domain, you may continue to do so.\"\n}\n[/block]\n ## Subject\nThe subject line within the email may be used to control how Email To SMS processes the email. The optional parameters are separated by the # (hash) character and the value specified using the = (equals) character, therefore the subject line would be composed in the following format:\n\n<div class=\"alert alert-success\">[parameter name]=[parameter value]{#[parameter name]=[parameter value]}</div>\n\ne.g. **ORIGINATOR=Dynmark#SPLIT=TRUE**\n\nThe following optional parameters can be used:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Parameter Name\",\n    \"h-1\": \"Values\",\n    \"h-2\": \"Example\",\n    \"h-3\": \"Description\",\n    \"0-0\": \"<code>DELIVERAFTER</code>\",\n    \"0-1\": \"Date time formatted as follows:<br>DD MMM YYYY hh:mm\",\n    \"0-2\": \"01/01/2014 08:00\",\n    \"0-3\": \"The UTC time to deliver the message after; may only be up to 1 year in the future\",\n    \"1-0\": \"<code>ORIGINATOR</code>\",\n    \"2-0\": \"<code><a name=\\\"split\\\"></a>SPLIT</code>\",\n    \"1-1\": \"The phone number, short code or alpha originator you wish to send from.\",\n    \"1-2\": \"447990123123<br>07990123123<br>CompanyName\",\n    \"1-3\": \"The originator the SMS is sent from. Note you may only use mobile numbers and short codes as originators that are registered to your Dynmark account, such as long numbers bought in the shop.\",\n    \"2-1\": \"TRUE/FALSE\",\n    \"2-2\": \"TRUE\",\n    \"2-3\": \"Indicates whether messages exceeding 160 characters in length can be sent; true = yes\",\n    \"3-0\": \"<code>MESSAGEGUID</code>\",\n    \"3-1\": \"A GUID that uniquely identifies the message for correlation purposes\",\n    \"3-2\": \"cb0d68b2-1707-4886-859e-5613f0e5c6d5\",\n    \"3-3\": \"For correlation purposes you may specify the GUID the message will be identified by, please ensure the GUIDs are unique\",\n    \"4-0\": \"<code>VALIDITYPERIOD</code>\",\n    \"4-1\": \"The period of time the SMS is valid for using expressed as {count}{unit} where unit can be:<ul>w – week</ul><ul>d – day</ul><ul>h – hour</ul><ul>m - minute</ul>\",\n    \"4-2\": \"15m<br>1h<br>1d\",\n    \"4-3\": \"If the SMS is not delivered to the handset within the validity period it won’t be. This feature is useful for time sensitive messages.\",\n    \"5-0\": \"<code><a name=\\\"type\\\"></a>TYPE</code>\",\n    \"5-1\": \"The content type of the message.\",\n    \"5-2\": \"Text.GSM0338<br>Text.UTF8\",\n    \"5-3\": \"**Text.GSM0338** - Indicates that the message content uses the limited character set defined by the GSM default alphabet. Any characters found outside of the GSM alphabet will cause the email to be rejected.<br>**Text.UTF8** - Indicates that the message content uses the UTF8 character set, and therefore supports the full Unicode character set.<br>**Note**: Unicode based messages cost more to send as they hold approximately half the characters per SMS.\",\n    \"6-0\": \"<code>SENDDELIVERYSTATUS</code>\",\n    \"6-1\": \"TRUE/FALSE\",\n    \"6-2\": \"TRUE\",\n    \"6-3\": \"This setting allows you to receive updates via HTTP GET when the message changes status. To use this setting you must also provide a valid URL in the DELIVERYSTATUSURL parameter.\",\n    \"7-0\": \"<code>DELIVERYSTATUSURL</code>\",\n    \"7-1\": \"The URL to send delivery status receipt updates to\",\n    \"7-2\": \"http://<span></span>forwarding.example.com/smsreceipt\",\n    \"7-3\": \"This URL must comply with our <a href=\\\"receipt-handler\\\">HTTP forwarding standards</a>. This setting is used in conjunction with SENDDELIVERYSTATUS\",\n    \"8-0\": \"<code>WAPURL</code>\",\n    \"8-1\": \"The URL to redirect the phone to\",\n    \"8-2\": \"http://<span></span>www.dynmark.com\",\n    \"8-3\": \"Instruct the receiving phone to open the WAP URL specified.\",\n    \"9-0\": \"<code>FILTERSETNAME</code>\",\n    \"9-1\": \"The Intelligent Filtering filter set name to use\",\n    \"9-3\": \"If you have enabled Intelligent Filtering on your account in the user portal you can specify which filter set is applied to this message.\",\n    \"9-2\": \"RemoveDeadNumbers\"\n  },\n  \"cols\": 4,\n  \"rows\": 10\n}\n[/block]\n##Dealing with Email Footers\nIf your email system automatically adds footers to outgoing emails and you don't want these to be included in any SMS set via Email to SMS, add the text **#end#** to your email body to ensure only the characters in the body before this token will be sent as the SMS.\n\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Example\",\n  \"body\": \"This is a test SMS message\\n**#end#**\\n\\nRegards,\\nJoe Bloggs\\n\\n01234 567890\"\n}\n[/block]\n##Unicode / International Character Based Messages\nUnless overridden with the [TYPE](#type) optional subject parameter *TYPE=Text.UTF8*, Email To SMS will reject messages that contain characters that are not within the GSM0338 messaging standard characters, as including these will cause the SMS to be sent in Unicode format, reducing the number of characters significantly e.g. A GSM SMS is 160 characters whereas Unicode is only 70 characters. \n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"A GSM SMS is 160 characters whereas Unicode is only 70 characters\",\n  \"body\": \"See the [Important Knowledge](doc:important-knowledge) section for more information.\"\n}\n[/block]\n##Long Messages\nUnless overridden with the [SPLIT](#split) optional subject parameter *SPLIT=TRUE*, or using the split registered email preference, Email To SMS will reject messages that require more than one SMS segment.","excerpt":"","slug":"composing-an-email","type":"basic","title":"Composing an email"}

Composing an email


## Addressing Email To SMS uses the emails *TO* and *CC* fields to determine what phone numbers the email body content should be sent to as an SMS. *BCC* is ignored. The format of these fields is: <div class="alert alert-success">{International formatted mobile number}@dynmark.net</div> Multiple numbers can be separated using a semicolon or comma, e.g. <span class="c-success">447990123123@dynmark.net;447970321321@dynmark.net</span> [block:callout] { "type": "info", "body": "If you have been sending email to SMS using the *e-txt.co.uk* domain, you may continue to do so." } [/block] ## Subject The subject line within the email may be used to control how Email To SMS processes the email. The optional parameters are separated by the # (hash) character and the value specified using the = (equals) character, therefore the subject line would be composed in the following format: <div class="alert alert-success">[parameter name]=[parameter value]{#[parameter name]=[parameter value]}</div> e.g. **ORIGINATOR=Dynmark#SPLIT=TRUE** The following optional parameters can be used: [block:parameters] { "data": { "h-0": "Parameter Name", "h-1": "Values", "h-2": "Example", "h-3": "Description", "0-0": "<code>DELIVERAFTER</code>", "0-1": "Date time formatted as follows:<br>DD MMM YYYY hh:mm", "0-2": "01/01/2014 08:00", "0-3": "The UTC time to deliver the message after; may only be up to 1 year in the future", "1-0": "<code>ORIGINATOR</code>", "2-0": "<code><a name=\"split\"></a>SPLIT</code>", "1-1": "The phone number, short code or alpha originator you wish to send from.", "1-2": "447990123123<br>07990123123<br>CompanyName", "1-3": "The originator the SMS is sent from. Note you may only use mobile numbers and short codes as originators that are registered to your Dynmark account, such as long numbers bought in the shop.", "2-1": "TRUE/FALSE", "2-2": "TRUE", "2-3": "Indicates whether messages exceeding 160 characters in length can be sent; true = yes", "3-0": "<code>MESSAGEGUID</code>", "3-1": "A GUID that uniquely identifies the message for correlation purposes", "3-2": "cb0d68b2-1707-4886-859e-5613f0e5c6d5", "3-3": "For correlation purposes you may specify the GUID the message will be identified by, please ensure the GUIDs are unique", "4-0": "<code>VALIDITYPERIOD</code>", "4-1": "The period of time the SMS is valid for using expressed as {count}{unit} where unit can be:<ul>w – week</ul><ul>d – day</ul><ul>h – hour</ul><ul>m - minute</ul>", "4-2": "15m<br>1h<br>1d", "4-3": "If the SMS is not delivered to the handset within the validity period it won’t be. This feature is useful for time sensitive messages.", "5-0": "<code><a name=\"type\"></a>TYPE</code>", "5-1": "The content type of the message.", "5-2": "Text.GSM0338<br>Text.UTF8", "5-3": "**Text.GSM0338** - Indicates that the message content uses the limited character set defined by the GSM default alphabet. Any characters found outside of the GSM alphabet will cause the email to be rejected.<br>**Text.UTF8** - Indicates that the message content uses the UTF8 character set, and therefore supports the full Unicode character set.<br>**Note**: Unicode based messages cost more to send as they hold approximately half the characters per SMS.", "6-0": "<code>SENDDELIVERYSTATUS</code>", "6-1": "TRUE/FALSE", "6-2": "TRUE", "6-3": "This setting allows you to receive updates via HTTP GET when the message changes status. To use this setting you must also provide a valid URL in the DELIVERYSTATUSURL parameter.", "7-0": "<code>DELIVERYSTATUSURL</code>", "7-1": "The URL to send delivery status receipt updates to", "7-2": "http://<span></span>forwarding.example.com/smsreceipt", "7-3": "This URL must comply with our <a href=\"receipt-handler\">HTTP forwarding standards</a>. This setting is used in conjunction with SENDDELIVERYSTATUS", "8-0": "<code>WAPURL</code>", "8-1": "The URL to redirect the phone to", "8-2": "http://<span></span>www.dynmark.com", "8-3": "Instruct the receiving phone to open the WAP URL specified.", "9-0": "<code>FILTERSETNAME</code>", "9-1": "The Intelligent Filtering filter set name to use", "9-3": "If you have enabled Intelligent Filtering on your account in the user portal you can specify which filter set is applied to this message.", "9-2": "RemoveDeadNumbers" }, "cols": 4, "rows": 10 } [/block] ##Dealing with Email Footers If your email system automatically adds footers to outgoing emails and you don't want these to be included in any SMS set via Email to SMS, add the text **#end#** to your email body to ensure only the characters in the body before this token will be sent as the SMS. [block:callout] { "type": "success", "title": "Example", "body": "This is a test SMS message\n**#end#**\n\nRegards,\nJoe Bloggs\n\n01234 567890" } [/block] ##Unicode / International Character Based Messages Unless overridden with the [TYPE](#type) optional subject parameter *TYPE=Text.UTF8*, Email To SMS will reject messages that contain characters that are not within the GSM0338 messaging standard characters, as including these will cause the SMS to be sent in Unicode format, reducing the number of characters significantly e.g. A GSM SMS is 160 characters whereas Unicode is only 70 characters. [block:callout] { "type": "info", "title": "A GSM SMS is 160 characters whereas Unicode is only 70 characters", "body": "See the [Important Knowledge](doc:important-knowledge) section for more information." } [/block] ##Long Messages Unless overridden with the [SPLIT](#split) optional subject parameter *SPLIT=TRUE*, or using the split registered email preference, Email To SMS will reject messages that require more than one SMS segment.