How to set up Hubspot ticketing with Mimecast.
Setting up a mailflow incorporating auto-forwarding and special relay rules serves various purposes, one prominent example being the integration of ticketing systems like Hubspot. When employing such systems, Hubspot typically assigns an email address that is intended for use with mail auto-forwarding. For example, you might want customer inquiries sent to support@domain.com to seamlessly feed into your Hubspot ticketing system.
However, default configurations in both Office 365 and Mimecast prohibit this functionality. You may encounter rejection messages such as:
From Office 365: "Remote server returned '550 5.7.520 Access denied, Your organization does not allow external forwarding. Please contact your administrator for further assistance. AS(7555)'"
From Mimecast: "451 Open Relay not allowed"
To overcome these rejections, you'll need to establish specific rules within both Office 365 and Mimecast.
In Office 365, this involves creating a new anti-spam rule specifying the permitted mailbox for auto-forwarding (e.g., support@domain.com). You may also want to create an external mail contact ( the Hubspot email address ).
Subsequently, in Mimecast, you'll add the Hubspot email address to the relay Profile Group.
If you get stuck or need help please reach out!
