anchor.diff:  “archive” : [ “archive_email"@corp.com” ], 
   
   "options" : {"open_tracking" : false, "click_tracking" : true},
  -
  +}
   ```
   NOTE:  You may not specify more than a total of 1000 total recipients in those 3 lists.
  +
  +You may also specify name and email keys in the "cc" and "bcc" JSON arrays in order to produce a “friendly Cc or Bcc header”. For example:
  +
  +```
  +X-MSYS-API: {
  +"cc" : [
  +   {
  +    "email" : "cc_recip_1@gmail.com",
  +    "name" : "CC 1"
  +   },
  +   {
  +    "email" : "cc_recip_2@gmail.com",
  +    "name" : "CC 2"
  +   }
  +]
  +"bcc" : [
  +   {
  +    "email" : "bcc_recip_1@gmail.com",
  +    "name" : "BCC 1"
  +   }
  +]
  +}
  +```
   
   SMTP defines a maximum line length of 1000 characters (including CRLF).  If the value of the X-MSYS-API JSON string is
   longer than 998 characters, it will need to be folded across multiple lines before the message is injected.  An example
  
positive.code: |-------|------|-------------|----------|-------|
  | campaign_id | string | Name of the campaign to associate with the SMTP message | no | Maximum length - 64 bytes (same restriction as the REST API) |
  | metadata | JSON object | JSON key value pairs associated with the SMTP message | no | A maximum of 200 bytes of metadata is available during click/open events. |
  | cc | JSON array | Array of recipient addresses that will be included in the CC header | no | A unique message will be generated for each recipient in this list. |
  | bcc | JSON array | Array of recipient addresses. Will not be included in any header | no | A unique message will be generated for each recipient in this list. |
  | archive | JSON array | Array of recipient addresses. Will not be included in any header | no | A unique message will be generated for each recipient in this list. |
  | tags | JSON array | Array of text labels associated with the SMTP message | no | Tags are available in click/open events. Maximum number of tags is 10 per recipient, 100 system wide. |
  | options | JSON object | JSON object in which SMTP API options are defined | no | For a full description, see the Options Attributes. |
  
  
negative.code: 
  Through use of the X-MSYS-API header in a message sent to SparkPost through SMTP 
  (see ["Sending an Email"](https://www.sparkpost.com/docs/sending-email)), you can now specify a campaign id, metadata,
  tags, Cc, Bcc, and archive recipient lists and enable open and/or click tracking.  Note that to use this option you should be familiar with how to encode
  options as JSON strings, as the value of the header field is a JSON object that specifies the relevant options:
  
  ```
  