Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/docs/deliverability/ded-ip-full-circle-dns.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,9 @@ lastUpdated: "02/08/2020"
title: "Dedicated IPs - full-circle reverse DNS and EHLO hostnames on SparkPost"
description: "Dedicated IP addresses issued from SparkPost address ranges automatically have Full Circle Reverse DNS"
---
You may have noticed that recently allocated [dedicated IP addresses](https://docs.sparkpost.com/docs/deliverability/managing-dedicated-ip-pools/) in your SparkPost account come from specific address ranges.
You may have noticed that recently allocated [dedicated IP addresses](/docs/deliverability/managing-dedicated-ip-pools/) in your SparkPost account come from specific address ranges.

Unless you are using our [Bring your Own IP](https://docs.sparkpost.com/docs/tech-resources/bring-your-own-ip/) feature, your dedicated IPs come from a range registered to SparkPost.
Unless you are using our [Bring your Own IP](/docs/tech-resources/bring-your-own-ip/) feature, your dedicated IPs come from a range registered to SparkPost.

```
whois 147.253.215.24
Expand Down
4 changes: 2 additions & 2 deletions content/docs/deliverability/dedicated-ip-pools.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ title: "Dedicated IP Pools"
description: "Dedicated IP addresses are available for any account with the exception of the FREE plan with no credit card details on file Any new dedicated IP address added to your account will have a neutral initial reputation which means that you will be responsible for properly warming up your new..."
---

Dedicated IP addresses are available for any account with the exception of Starter and Test plans. Any new dedicated IP address added to your account will have a neutral initial reputation, which means that you will be responsible for properly warming up your new IP. You can refer to our [IP Warmup Overview](https://docs.sparkpost.com/docs/deliverability/ip-warm-up-overview/) for a comprehensive guide to warming up your new IP.
Dedicated IP addresses are available for any account with the exception of Starter and Test plans. Any new dedicated IP address added to your account will have a neutral initial reputation, which means that you will be responsible for properly warming up your new IP. You can refer to our [IP Warmup Overview](/docs/deliverability/ip-warm-up-overview/) for a comprehensive guide to warming up your new IP.

## Plans with an Included IP

Expand All @@ -28,7 +28,7 @@ You can provision additional dedicated IPs directly to your Account via the UI.

You can view and manage your dedicated IPs and their associated IP Pools in the UI by selecting **Configuration** > **IP Pools**

From here, you can create, delete, or edit IP Pools. You can also move dedicated IPs between pools. Read this article to understand more about __[managing your existing dedicated IP pools](https://docs.sparkpost.com/docs/deliverability/managing-dedicated-ip-pools/)__.
From here, you can create, delete, or edit IP Pools. You can also move dedicated IPs between pools. Read this article to understand more about __[managing your existing dedicated IP pools](/docs/deliverability/managing-dedicated-ip-pools/)__.

## Using Your Dedicated IPs

Expand Down
4 changes: 2 additions & 2 deletions content/docs/deliverability/deliverability-analytics.md
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ The seed list is updated periodically, as we regularly expand our panel coverage

### Getting Started with Panel Data

Panel data associated with a sending domain in your SparkPost account will start flowing into your account immediately. If you already have a sending domain added and verified, no further action is needed! If you do not yet have a sending domain in your SparkPost account, please follow these [Getting Started steps](https://docs.sparkpost.com/docs/getting-started/getting-started-sparkpost/) to set one up and verify it.
Panel data associated with a sending domain in your SparkPost account will start flowing into your account immediately. If you already have a sending domain added and verified, no further action is needed! If you do not yet have a sending domain in your SparkPost account, please follow these [Getting Started steps](/docs/getting-started/getting-started-sparkpost/) to set one up and verify it.

Note: You do *not* need to send emails to the consumer panel *through SparkPost* in order to see the data - we will show you panel data sent through any method. We do require a verified domain in order to display the results to the correct account.

Expand Down Expand Up @@ -111,7 +111,7 @@ SparkPost also provides the following deliverability metrics in the [SparkPost a
| Moved to Spam Count | Number of panel messages delivered to the inbox but then moved to the spam folder. | `count_moved_to_spam`
| Moved to Spam Rate | Percentage of panel messages delivered to the inbox folder but then moved to the spam folder. | `count_moved_to_spam` / (`count_inbox_panel` + `count_inbox_seed`) |

To view the deliverability metrics in the UI, first click “Signals Analytics” in the top menu to be taken to the “Analytics Report”. Click “Add Metrics” and scroll to the “Deliverability Metrics” section to add your desired metrics. All [user roles](https://docs.sparkpost.com/docs/user-guide/managing-users/) can view deliverability metrics in the UI.
To view the deliverability metrics in the UI, first click “Signals Analytics” in the top menu to be taken to the “Analytics Report”. Click “Add Metrics” and scroll to the “Deliverability Metrics” section to add your desired metrics. All [user roles](/docs/user-guide/managing-users/) can view deliverability metrics in the UI.

![](media/deliverability-analytics/02-deliverability-metrics.png)

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,8 @@ In order to get the best deliverability and inbox placement rates, you need to e
* Hide the unsubscribe link or ignore unsubscribe requests
* Buy email lists - especially those from untrustworthy sources
* Sell your list to a third party without permission
8. Set up [custom bounce domain(s)](https://docs.sparkpost.com/docs/tech-resources/custom-bounce-domain/)
9. Set up [custom tracking domain(s)](https://docs.sparkpost.com/docs/tech-resources/enabling-multiple-custom-tracking-domains/)
8. Set up [custom bounce domain(s)](/docs/tech-resources/custom-bounce-domain/)
9. Set up [custom tracking domain(s)](/docs/tech-resources/enabling-multiple-custom-tracking-domains/)

For more detailed information on this topic, please review [MAAWG Sender Best Common Practices](https://www.m3aawg.org/documents/en/m3aawg-sender-best-common-practices-version-30).

Expand Down
2 changes: 1 addition & 1 deletion content/docs/faq/can-i-send-from-any-domain.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: "Domain Ownership And Control You can send mail through Spark Post

## Domain Ownership And Control

You can send mail through SparkPost from any domain *that you or your customers control*. By verifying your sending domains with SparkPost, you're letting us know that you control them and that you authorize delivery from those domains. The DKIM domain verification procedure is the best option here since it also brings deliverability best practice with it. [There are instructions here how to verify your sending domains](https://docs.sparkpost.com/docs/getting-started/getting-started-sparkpost/#step-2-verify-domain).
You can send mail through SparkPost from any domain *that you or your customers control*. By verifying your sending domains with SparkPost, you're letting us know that you control them and that you authorize delivery from those domains. The DKIM domain verification procedure is the best option here since it also brings deliverability best practice with it. [There are instructions here how to verify your sending domains](/docs/getting-started/getting-started-sparkpost/#step-2-verify-domain).

## Why Can't I Just Send From Any Domain?

Expand Down
2 changes: 1 addition & 1 deletion content/docs/faq/cc-bcc-archive-recipients.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ It is possible to specify a list of one or more recipients who will receive a co
### Notes

* The “rcpt_type” field present in webhook/Message Events API data is used to specify whether the recipient is a CC, BCC or Archive recipient.
* If the [REST API is used to send cc or bcc messages](https://docs.sparkpost.com/docs/faq/cc-bcc-with-rest-api/) (please note that archive is **not** supported via the REST API), the "rcpt_type" field **does not appear** in the webhook or Message Events API data. We recommend that you include recipient-level metadata for tracking which type each recipient address belongs to.
* If the [REST API is used to send cc or bcc messages](/docs/faq/cc-bcc-with-rest-api/) (please note that archive is **not** supported via the REST API), the "rcpt_type" field **does not appear** in the webhook or Message Events API data. We recommend that you include recipient-level metadata for tracking which type each recipient address belongs to.
* Each Archive, CC, and BCC recipient is counted in the standard targeted and accepted metrics.
* Archive messages do not include a BCC header.
* The total number of CC, BCC and archive recipients cannot exceed 1000.
Expand Down
2 changes: 1 addition & 1 deletion content/docs/faq/cc-bcc-with-rest-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ title: "Using CC and BCC with the REST API"
description: "Before getting started please read What are the differences between CC BCC and archive recipients Note to use CC BCC and Archiving with SMTP check out our SMTP API reference documentation Note Please be advised that CC and BCC messages count towards your usage What is CC CC is a..."
---

Before getting started please read [What are the differences between CC, BCC, and archive recipients?](https://docs.sparkpost.com/docs/faq/cc-bcc-archive-recipients/)
Before getting started please read [What are the differences between CC, BCC, and archive recipients?](/docs/faq/cc-bcc-archive-recipients/)

Note: to use CC, BCC, and Archiving with SMTP, check out our [SMTP API reference documentation](https://developers.sparkpost.com/api/#/reference/smtp-api).
Note: Please be advised that CC and BCC  messages count towards your usage.
Expand Down
2 changes: 1 addition & 1 deletion content/docs/faq/daily-and-monthly-quota-limits.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,4 +34,4 @@ Daily limits can take up to a week to fully update after you upgrade your plan.

If you need to send more than 50,000 email a day on average throughout a calendar month, SparkPost requires that you have one or more dedicated IPs and custom bounce and tracking domains set up. Please set these up before requesting a limit rise.

**Note:** Please follow our [IP Warm up Guide](https://docs.sparkpost.com/docs/deliverability/ip-warm-up-overview/) to warm up any new IP and correctly establish your sending reputation.
**Note:** Please follow our [IP Warm up Guide](/docs/deliverability/ip-warm-up-overview/) to warm up any new IP and correctly establish your sending reputation.
2 changes: 1 addition & 1 deletion content/docs/faq/dkim-wont-verify.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: "Q Why won't my DKIM record verify A While configuring your Sending

Q: Why won't my DKIM record verify?

A: [While configuring your Sending Domains](https://docs.sparkpost.com/docs/getting-started/getting-started-sparkpost/#prerequisites), you need to "verify" that the DNS entries you have made are available to SparkPost and ESPs for use. The DNS TXT records you create have a TTL (Time To Live) value associated with them. This value is important (in cases where you have been unable to verify your Sending Domain's DNS DKIM record). The TTL is typically measured in seconds. For example a TTL value of 60 = 1 minute.
A: [While configuring your Sending Domains](/docs/getting-started/getting-started-sparkpost/#prerequisites), you need to "verify" that the DNS entries you have made are available to SparkPost and ESPs for use. The DNS TXT records you create have a TTL (Time To Live) value associated with them. This value is important (in cases where you have been unable to verify your Sending Domain's DNS DKIM record). The TTL is typically measured in seconds. For example a TTL value of 60 = 1 minute.

When you click the "verify" link on the Sending Domains configuration page, SparkPost makes a request to DNS to see if that record is available. Sometimes, the TTL may cause changes you've just made to not be "visible" to SparkPost yet. So if you don't see a message saying your DKIM is verified, just wait a bit and refresh the page.

Expand Down
2 changes: 1 addition & 1 deletion content/docs/faq/error-messages-smtp.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,4 +12,4 @@ For error messages that are not listed below, see one of the popular SMTP reply
|:---------------------------------------------------------|:-------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 535 5.7.8 Sorry. *** No authentication type succeeded | There is some problem with the authentication credentials. API key, user name, etc. | Confirm that the API key has the Send via SMTP permission and the user name SMTP_Injection. |
| 550 5.6.0 JSON parsing error in X-MSYS-API | The X-MSYS-API header is malformed in some way | Fix the header's json. The error message usually supplies additional details about the problem. See [the API Docs](https://developers.sparkpost.com/api/smtp-api.html) for more information about the format. |
| 550 5.7.1 Unconfigured Sending Domain <demo.example.com> | The domain part of the "From" address isn't a configured sending domain | Use a "From" address that uses a configured sending domain. See [Creating Sending Domains](https://docs.sparkpost.com/docs/getting-started/getting-started-sparkpost/#preparing-your-from-address) if you need to create a sending domain. |
| 550 5.7.1 Unconfigured Sending Domain <demo.example.com> | The domain part of the "From" address isn't a configured sending domain | Use a "From" address that uses a configured sending domain. See [Creating Sending Domains](/docs/getting-started/getting-started-sparkpost/#preparing-your-from-address) if you need to create a sending domain. |
2 changes: 1 addition & 1 deletion content/docs/faq/gmail-shows-mailing-list.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,4 +10,4 @@ Gmail pulls the 'mailing list' information from the list_unsubscribe header that

## How do I remove this? 

Unfortunately since the header is auto-generated it cannot be changed or removed. For more information about the list_unsubscribe header please see [this article](https://docs.sparkpost.com/docs/user-guide/remove-list-unsubscribe-header/).
Unfortunately since the header is auto-generated it cannot be changed or removed. For more information about the list_unsubscribe header please see [this article](/docs/user-guide/remove-list-unsubscribe-header/).
4 changes: 2 additions & 2 deletions content/docs/faq/inactive-account.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,13 @@ title: “What happens if I don’t use my Free SparkPost account?”
description: “If you never send from your Free account, after 3 months we will close your account, or if you don’t send from your Free SparkPost account for 6 months we will close your account”
---

We love it when customers use SparkPost, but we recognize that things can change, and you might no longer need your account for sending. We strongly recommend that you contact support through the in app support tool to request your account is closed. Details can be found [here](https://docs.sparkpost.com/docs/faq/submit-a-ticket/), but if you don’t, to protect your account’s security and any data we will close your account...
We love it when customers use SparkPost, but we recognize that things can change, and you might no longer need your account for sending. We strongly recommend that you contact support through the in app support tool to request your account is closed. Details can be found [here](/docs/faq/submit-a-ticket/), but if you don’t, to protect your account’s security and any data we will close your account...

<ul>
<li>If you have never sent with your own verified domain your account will be closed after 3 months.</li>
<li>If you have stopped sending we will close your account after 6 months of inactivity.</li>
</ul>

If you would like to start using SparkPost again, you will be asked to set up a new account with one of our current plans. You can find more information on account set up [here](https://docs.sparkpost.com/docs/getting-started/getting-started-sparkpost/).
If you would like to start using SparkPost again, you will be asked to set up a new account with one of our current plans. You can find more information on account set up [here](/docs/getting-started/getting-started-sparkpost/).

**NOTE** For Paid plan customers we recommend you downgrade to the free plan to stop ongoing charges but also contact support as mentioned above if you no longer require your SparkPost account.
2 changes: 1 addition & 1 deletion content/docs/faq/post-to-webhook-target-failed.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,4 +14,4 @@ This error occurs when SparkPost sends a test batch to your webhook endpoint and
* Your receiving HTTP service must return a 200 status code when it successfully receives an event batch.  Any non 200 response is treated as an error.
* For security reasons, SparkPost only supports standard ports 80 (for HTTP traffic) and 443 (for HTTPS traffic). Make sure your webhook endpoint is listening for traffic on at least one of these ports.

For more details on managing your webhooks and handling webhook event data, check out [this support article](https://docs.sparkpost.com/docs/tech-resources/managing-webhook-data/) and [this blog post](https://www.sparkpost.com/blog/webhooks-beyond-the-basics/) on the topic.
For more details on managing your webhooks and handling webhook event data, check out [this support article](/docs/tech-resources/managing-webhook-data/) and [this blog post](https://www.sparkpost.com/blog/webhooks-beyond-the-basics/) on the topic.
Comment thread
danielfsousa marked this conversation as resolved.
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ You can use the API key to view who was on your account's Suppression List, but

You can edit that by visiting this URL and clicking the Edit button for that particular API key and adding the Suppression Lists Read/Write permission: [https://app.sparkpost.com/#/account/credentials](https://app.sparkpost.com/#/account/credentials)

More information regarding the suppression list can be found here: https://docs.sparkpost.com/docs/user-guide/using-suppression-lists/
More information regarding the suppression list can be found [here](/docs/user-guide/using-suppression-lists/).

Some workarounds for this situation are:

Expand Down
Loading
Loading