Editing Merge or update existing SPF records (section)

= How to merge or update existing SPF records =

== Introduction ==
In email authentication, the '''SPF record''' (Sender Policy Framework) specifies which mail servers are authorized to send emails on behalf of a domain. With ActiveCampaign, when you set up your sending domain, this process includes setting up the correct SPF records automatically, which means you often do not need to create or modify an SPF record to work with ActiveCampaign. 

However, manually setting up ActiveCampaign SPF records for your From domain can provide added benefits, particularly regarding enhancing your email deliverability. If you opt to manage your SPF records manually, it is crucial to understand that a domain can only have one valid SPF record. This article explains the process of updating or merging existing SPF records to ensure compliance and maintain email functionality effectively.

== How to access this feature ==
To access and manage your SPF records, you will typically work within your domain's DNS settings. This can be accessed through your domain registrar or hosting provider where DNS records can be modified.

== Step-by-step instructions ==
=== Adding ActiveCampaign’s Include to an Existing SPF Record ===
If you already possess an SPF record and need to add ActiveCampaign as an email sender, you can do this by adding the required include statement to the current record.

1. Retrieve your existing SPF record. For example:
   ```
   v=spf1 include:_spf.google.com -all
   ```

2. Add the include statement for ActiveCampaign:
   ```
   v=spf1 include:_spf.google.com include:emsd1.com -all
   ```
   - Ensure that the new string is placed before the **-all** part.
   - Do not incorporate unnecessary spaces; each string should be separated by a single space.
   - Ensure the recording starts with **v=spf1**.

=== Merging Existing SPF Records ===
If you have multiple SPF records, you will need to merge them into a single record, as having dual or more SPF records is invalid.

1. Identify your existing SPF records:
   ```
   v=spf1 ip4:20.33.1.86/32 include:_spf.google.com -all
   v=spf1 include:emsd1.com -all
   ```

2. Delete one record and modify the other to combine both sets of information:
   ```
   v=spf1 include:emsd1.com ip4:20.33.1.86/32 include:_spf.google.com -all
   ```

=== Important Points to Remember ===
- The SPF record may contain various qualifiers (like **-all**, **~all**, **?all**, or **+all**). It is recommended to use either **~all** (soft fail) or **-all** (fail).
- Merging SPF records offers a perfect chance to tidy the list. Remove outdated includes or strings.
- Since SPF records are processed from left to right, place the most frequently used includes at the top.
- Do note that SPF records have a limit of 10 DNS lookups; thus, you may need to optimize accordingly.

== Configuration options and settings ==
While modifying SPF records, it is crucial to pay attention to the following '''configuration options''':
- **include**: Specifies other domains that are allowed to send emails on your behalf.
- **ip4**: Designates valid IP addresses that can send emails for your domain.
- **-all**: Indicates that emails not matching the previous mechanisms should be rejected (hard fail).
- **~all**: Soft fail, indicating emails not matching should be treated with caution but still accepted.

== Best practices and tips ==
- Always have a single SPF record per domain to avoid email delivery issues.
- Regularly review and update your SPF record to remove any outdated or unused includes.
- Utilize the '''include''' directive wisely to aggregate services you use for email sending.
- Test your SPF records after modifying them using online SPF record testers to confirm they are valid.

== Troubleshooting ==
If issues arise with email delivery following SPF record updates, check the following:
- Ensure there are no conflicting SPF records for your domain.
- Validate your SPF record with an online tool to ensure it adheres to SPF standards.
- Confirm that all necessary senders and services are included in your SPF record.

== Related features ==
- For more on authenticating your emails, check out the [[Email Authentication]] page.
- Understand the overall impact of SPF on your mail deliverability through our guide on '''Understanding SPF and how it impacts email deliverability'''.

== FAQ ==
=== 1. What happens if I have multiple SPF records for the same domain? ===
Having multiple SPF records will lead to email delivery failures. It is critical to consolidate them into one valid record.

=== 2. What is the recommended SPF record format? ===
The standard format should start with **v=spf1** followed by all includes and IPs, and it typically ends with either **-all** or **~all**.

=== 3. Can I include other services in my SPF record? ===
Yes, you can include multiple services by using the **include** directive followed by their respective SPF addresses.

=== 4. How often should I check my SPF records? ===
It is a good practice to review your SPF records at least once every quarter and after significant changes regarding your email sending sources.

=== 5. What tools can I use to validate my SPF records? ===
There are several online SPF validation tools available, which can check the accuracy and functionality of your SPF record.

=== 6. What should I do if my emails are not being delivered? ===
Check your SPF record for any misconfigurations, ensure it is valid, and that all necessary includes are present.

=== 7. Will using ActiveCampaign automatically set my SPF records? ===
While ActiveCampaign sets up SPF records for you during domain setup, managing them manually can enhance control and optimization.

By following the instructions outlined in this article, you can effectively manage your SPF records, thereby optimizing your email authentication and overall deliverability.
```