.png){kind=logo}
SMTP Configuration and Email Forwarding for Custom Email Domains
Goal & Context
We're updating how emails are sent from the Engagement Hub (EH) so that you can send emails from your own domain instead of the default system email.
Currently, all Nexus communications — including emails, invitations, user registrations, and password resets — are sent from s17@briefingedge.com. With this update, you'll be able to use your own email alias, such as EBC@yourdomain.com, improving trust and deliverability to your customers.
Why this matters:
- Emails will come from your domain instead of @briefingedge.com
- You maintain control over branding and reply handling.
- Replies will be sent to an inbox you control.
If you prefer not to use a custom domain, you can continue using s17@briefingedge.com — no changes needed.
Please follow the steps below or share them with your IT team:
Step 1: Gather SMTP Credentials
To allow our system to send emails on your behalf, please provide the following SMTP configuration:
- SMTP Server Address
- SMTP Port (587 for TLS or 465 for SSL preferred)
- Username (usually the email address or a designated SMTP user)
- Password (or an app-specific password if needed)
- Security Protocol (SSL or TLS)
Step 2: Create the Sending Email Address
Set up a dedicated email address to be used by the Engagement Hub — for example: EBC@yourdomain.com.
Make sure this address:
- Is active and operational
- Has permissions to send via SMTP
Step 3: Configure Email Forwarding
Set up automatic forwarding so that any replies to the sending email address are forwarded to:
This ensures responses from speaker/attendees are captured and routed appropriately.
Step 4: Confirm Setup Completion
Once everything is in place:
- Share the SMTP credentials with us via a secure channel (step 1)
- Confirm that email forwarding is working as expected