If you configure Stacks to use an email address linked to your organization's domain as the 'from address,' you may face difficulties receiving emails generated by your Stacks site. This issue arises because Stacks uses a technique called "Spoofing," which makes it appear that emails from the platform come from a different source. Many organizations are adept at identifying and blocking such spoofed sender addresses, and some enforce strict rules against emails not originating from their designated email service.
To address these challenges without compromising security, Stacks recommends two solutions:
-
Use an External Email Provider as a Forwarding Service: Configure a forwarding mechanism so that incoming emails generated within Stacks are automatically redirected through an external email provider. This process removes the 'spoofed' email header, significantly reducing the likelihood of interception by organizations with strict security policies.
-
Configure SMTP in Stacks to Use Your Email Service: If exceptions to organizational email policies cannot be made, Stacks offers an alternative solution. You can configure Stacks to use your organization's email service for outbound emails through Simple Mail Transfer Protocol (SMTP). This approach maintains the integrity of your organization's security policies while allowing Stacks to seamlessly use the established email infrastructure.
Changes are coming to how emails are generated on your Stacks site:
We are currently upgrading sites to use a new email service that is less likely to be blocked by email providers. As part of this upgrade, you will be notified of verification emails that will be sent to authorize each email addresses used as the "from" address. These emails will require your approval. This step ensures that emails generated by Stacks are recognized as legitimate by your organization's email service, enhancing deliverability and compliance with security policies.