Skip to main content
Gorelo uses Mailgun for email delivery to ensure reliability, high deliverability, and seamless troubleshooting. Instead of dealing with multiple BYO mail servers, using Mailgun exclusively allows Gorelo to tightly integrate email with its features—providing better tracking, logging, and efficient email issue handling.

​
Why Gorelo uses Mailgun

  • Optimized deliverability – Mailgun is built to ensure transactional emails reach inboxes, reducing the risk of messages being marked as spam.
  • Simplified troubleshooting – Gorelo manages the entire email flow, making it easier to track, diagnose, and resolve any issues quickly.
  • Deeper integration – Full control over email processing lets Gorelo pull error messages, delivery reports, and logs directly into tickets for better visibility.

​
Dedicated IP addresses

Gorelo uses dedicated IPs to ensure better email deliverability and maintain a strong sender reputation. The current IPs are:
  • 198.244.59.82
  • 159.135.238.33
Additional dedicated IPs may be added in the future as needed. If you need to whitelist Gorelo’s email servers, ensure this IP (and any future ones) are added to your email security settings.

​
What about my custom domain

When using Gorelo, emails are sent from a subdomain like gorelo.yourdomain.com, where all necessary DNS records are configured. This setup ensures there’s no impact on your root domain (yourdomain.com), meaning your primary email services remain fully functional and unaffected. Your clients will still see and interact with your root domain for email communication. For example, they’ll receive and reply to emails from support@yourdomain.com, while the subdomain is only used behind the scenes.

​
Stripped domains

Gorelo uses the concept of ‘Stripped Domains’. These are domains that you specify should not be associated with any particular Client or Contact — essentially, stripping the client and contact from them when a ticket is generated. In addition, Gorelo will not send an automatic response to the sender. A great example of this would be for Huntress. If you’ve configured Huntress to email Incident Reports to your help/support address, you likely don’t want everything coming from noreply@huntress.io to be associated with a single client or contact. Instead, you want these fields to be blank so you can easily assign the correct client.