# Define custom Return-Path without a dedicated IP

**URL:** <https://community.hubspot.com/t/define-custom-return-path-without-a-dedicated-ip/24409>\
**Category:** HubSpot Ideas\
**Tags:** account-settings, marketing-email\
**Created:** [August 20, 2020, 4:20am UTC](https://community.hubspot.com/t/define-custom-return-path-without-a-dedicated-ip/24409 "2020-08-20T04:20:08Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![wilsontayar](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/wilsontayar/32/98942_2.png) [@wilsontayar](https://community.hubspot.com/u/wilsontayar)\
**Post date:** [August 20, 2020, 4:20am UTC](https://community.hubspot.com/t/define-custom-return-path-without-a-dedicated-ip/24409/1 "2020-08-20T04:20:08Z")

</div>

Currently, if the portal does not have the dedicated IP add-on, all e-mails are sent using a “[hubspotemail.net](http://hubspotemail.net)” domain in the “Return-Path” header.

By doing so HubSpot is breaking SPF Alignment rules. SPF and DKIM alignment are positive indicators and should be considered for the security of users, even those that do not need a dedicated IP setup.

Competitors are already offering this feature with a simple CNAME entry, see: [How do I add a custom return-path? | Postmark Support Center](https://postmarkapp.com/support/article/910-how-do-i-add-a-custom-return-path)

Without proper return-path values, all DMARC reports and Google’s Postm Authentication reports show SPF fails, making it harder to detect problems and postponing companies to fully implement DMARC’s quarantine/reject policies.

---

_[View the full topic](https://community.hubspot.com/t/define-custom-return-path-without-a-dedicated-ip/24409)._