![]() The SMTP DATA command follows the MAIL and RCPT commands in an SMTP transaction. These addresses are not designated as carbon copy (CC), BCC, or another type of recipient-they are all just recipients. In addition to the sender, which is set with SMTP's MAIL command, these RCPT addresses can be thought of as part of the message envelope-they instruct sending email servers where to deliver the message. When sending email with SMTP, all recipients are listed using SMTP's RCPT (recipient) command. The concept of BCC exists outside of SMTP as defined by RFC 5321. It is possible to simulate blind carbon copy (BCC) behavior using SMTP with or without the X-SMTPAPI header. For example, the Unicode á character will look like this: \u00E1.įor more information, see our scheduling parameters documentation. When sending Unicode characters via the SMTP API, you should escape these characters using the \u escape character.The MAIL FROM address is re-written when we send the email for final delivery, so it is safe to set the MAIL FROM to an address that can receive the bounces and alert you to any errors. When using the X-SMTPAPI header, if our system encounters a parsing error, the message will be bounced to the address specified in the MAIL FROM portion of the SMTP session.If your email is going through another MTA before reaching SendGrid, it is likely that the other MTA will have an even lower setting for maximum header length and may truncate the header. Failure to do this can cause intermediate Mail Transfer Agents (MTAs) to split the header on non-space boundaries, which causes inserted spaces in the final email. Ensure that the header is limited to a maximum total line length of 1,000 characters.Doing so can generate duplicate messages to the addresses listed in both the X-SMTPAPI "to" field and the RCPT list. When using the X-SMTPAPI header to send to multiple recipients, you cannot use SMTP's standard RCPT TO command to also send to multiple recipients.If you have a large number of additional substitutions or sections in the headers, it is best to split the send into even smaller groups. ![]() However, the best practice is to split large jobs into separate transactions of approximately 1,000 recipients, which allows better processing load distribution. There is a hard limit of 10,000 addresses in a multiple recipient email.For any request received with multiple X-SMTPAPI headers on the same request, Twilio SendGrid will adhere to the first X-SMTPAPI header instance on each request. Ensure that you are sending just ONE X-SMTPAPI header per SMTP transaction.However, there are several things to keep in mind when using the header. The X-SMTPAPI is a powerful way to modify your SMTP messages. This page provides instructions for using the X-SMTPAPI to modify and control your mail send. This functionality is made possible by including a header named X-SMTPAPI. The Twilio SendGrid SMTP service allows you to pass SendGrid a JSON string with as many SMTP objects as you want. Now that you've sent a test SMTP email with Telnet, and integrated with SendGrid, it's time to build content.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |