Configuring email settings for thirdparty

Modified on Thu, 4 Dec at 11:34 AM

Configuring email settings for thirdparty

Email settings control how Hubhus sends emails, including domain configuration for Mailgun integration, default sending domains, and failed delivery notifications.

On this page

Jump to any section using the links below

Email settings control how Hubhus sends emails, including domain configuration for Mailgun integration, default sending domains, and failed delivery notifications. Proper configuration ensures reliable email delivery and helps you monitor delivery issues.


Accessing email settings

Go to Account → Email settings. This page contains three main sections:

  • Email domains: Mailgun domain configuration
  • Default email domain: Select which domain to use for sending
  • Failed delivery notifications: Monitor email delivery issues

Email domains

The Email domains section shows all configured Mailgun domains that can be used for sending emails from Hubhus. The table displays:

  • Domain: The email domain (e.g., mg.hubhus.dk)
  • Domain region: Geographic region (EU, US, etc.)
  • Verified: Verification timestamp
  • Webhooks: Webhook configuration status
  • Edit and Delete buttons

Mailgun integration

Hubhus uses Mailgun as its primary email delivery service. Mailgun provides:

  • Reliable email delivery infrastructure
  • Domain verification and SPF/DKIM authentication
  • Delivery tracking and webhooks
  • Bounce and complaint handling
  • Regional email sending (EU, US regions)

To send emails through your own domain, you need to add and verify the domain in Mailgun.


Adding a Mailgun email domain

Click Add Mailgun email domain to open the configuration dialog. You will need:

Mailgun email domain: The domain you want to send from (e.g., mg.yourdomain.com)

Mailgun API key: Your Mailgun API key for authentication

Mailgun domain region: Choose the geographic region (US, EU, etc.)

The system provides an important security notice: Due to security reasons, you will not be able to access the entered API key through Hubhus at any later time. Store your API key securely before submitting.


Domain verification

After adding a domain, it must be verified through Mailgun. The Verified column shows when the domain was successfully verified. Verification typically involves:

  • Adding DNS records (SPF, DKIM, CNAME) to your domain
  • Waiting for DNS propagation
  • Mailgun confirming the records are correct

Click Edit API key or domain region to update credentials or change the region if needed.


Webhooks configuration

Webhooks allow Hubhus to receive real-time notifications from Mailgun about email events (bounces, complaints, deliveries, opens, clicks).

A warning icon in the Webhooks column indicates webhooks need configuration. Proper webhook setup enables:

  • Failed delivery notifications
  • Email tracking and analytics
  • Bounce and complaint handling
  • Delivery status monitoring

Default email domain

The Default email domain dropdown lets you select which configured domain to use for sending emails. This setting determines:

  • Which domain emails are sent from by default
  • The from-address for automated emails
  • Which Mailgun account handles delivery

The explanation states: "Emails are automatically sent using the domain that matches the email from-address. If the from-email domain is not known the default domain set here will be used."

This means Hubhus intelligently selects the sending domain based on your email templates, but falls back to the default if no match is found.


Alternative email providers

Hubhus supports integration with other email providers beyond Mailgun:

  • SendGrid: Popular email delivery service
  • Mailchimp: Email marketing platform

The page notes: "Contact us if you use another email provider." This indicates custom integrations can be arranged for enterprise customers with specific email provider requirements.


Failed delivery notifications

The Failed delivery notifications section allows you to set up alerts when emails fail to deliver. This helps you quickly identify and resolve delivery issues.


Setting up delivery notifications

Click New delivery status update to configure notifications. You will configure:

Send notification to: Enter recipient email addresses (can use "Me" shortcut or separate multiple addresses by space or comma)

Bcc: Optional blind carbon copy recipients

Notification frequency: How often to receive notifications (e.g., Every 10 minutes)

Notify about these emails: Filter which failed emails trigger notifications:

  • All: All failed emails
  • All emails from specific campaigns: Filter by campaign
  • Emails from specific email templates: Filter by template

Notification frequency

The notification frequency setting determines the maximum rate at which failure reports are sent. Available options typically include intervals like:

  • Every 10 minutes
  • Every 30 minutes
  • Every hour
  • Every 4 hours
  • Daily

The system notes: "This is the maximum allowed notification frequency. If there are no bounced emails, no failure report will be sent."

This prevents notification spam while ensuring timely alerts when issues occur.


Filtering notification scope

The "Notify about these emails" setting provides granular control over which failures trigger notifications:

All: Receive notifications for all failed email deliveries across all campaigns and templates

All emails from specific campaigns: Monitor failures only from selected campaigns, useful for high-priority campaigns

Emails from specific email templates: Track failures from particular email templates, helpful for troubleshooting template-specific issues


Managing delivery notifications

Once configured, delivery status updates appear in the table with options to edit or delete. You can create multiple notification rules to:

  • Send different notifications to different team members
  • Use different frequencies for different campaigns
  • Separate critical notifications from routine monitoring

Refreshing domain status

Click the Refresh button next to the Email domains table to update the verification and webhook status of all configured domains. This is useful after:

  • Adding DNS records
  • Configuring webhooks in Mailgun
  • Troubleshooting domain issues

Best practices for email configuration

When configuring email settings:

Domain setup:

  • Use a subdomain for transactional emails (e.g., mg.yourdomain.com)
  • Verify domains promptly after adding
  • Configure all required DNS records (SPF, DKIM, CNAME)
  • Test email sending after domain verification

API key security:

  • Store API keys securely outside Hubhus
  • Use read-only keys when possible
  • Rotate keys periodically
  • Never share API keys in support tickets or screenshots

Delivery monitoring:

  • Set up failed delivery notifications immediately
  • Use appropriate notification frequency (not too frequent, not too slow)
  • Monitor notifications regularly and investigate failures
  • Create specific notification rules for critical campaigns

Regional considerations:

  • Choose the correct region (EU for European customers, US for American)
  • Ensure region compliance with data protection regulations
  • Consider delivery latency when selecting regions

Troubleshooting email delivery

If emails are not sending:

Check domain verification:

  • Ensure the domain shows as verified
  • Verify all DNS records are correct
  • Wait for DNS propagation (can take up to 48 hours)

Check webhook configuration:

  • Look for warning icons in the Webhooks column
  • Configure webhooks in Mailgun dashboard
  • Test webhook endpoints

Check default domain:

  • Ensure a default domain is selected
  • Verify the from-address matches a configured domain

Monitor failed delivery notifications:

  • Set up notifications to catch issues quickly
  • Review bounce reasons and take corrective action
  • Check Mailgun dashboard for detailed delivery logs

Summary

Email settings provide comprehensive control over email delivery in Hubhus. Add and verify Mailgun domains with API keys and regional selection, configure webhooks for delivery tracking, set a default sending domain, and establish failed delivery notifications with customizable frequency and filtering. Proper configuration ensures reliable email delivery, enables monitoring of delivery issues, and provides alerts when problems occur. For alternative email providers beyond Mailgun, contact Hubhus support for custom integration options.

? Common searches

email setup • send email • email template • automated email

? Also known as

message • notification • mail

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article