If you are using external systems like HR software, accounting platforms, or marketing tools that need to send emails using your domain (e.g. @yourcompany.com), here's how to do it while maintaining reliable email delivery through our hosting.

Before setting up, find out whether the third-party system will send emails:

• They are using their own domain (e.g. @thirdpartyservice.com)
• They are using your domain (e.g. @yourcompany.com)

To ensure these emails arrive in your inbox and are not filtered as spam, it is recommended to whitelist the sender domain in your Global Email Rules.

For Example: You're using a payroll system that sends pay slips from @hrsystem.com.
To receive them consistently, add the following line in your Global Email Rules:

  pass *@hrsystem.com

This tells the email server to always accept emails from that domain, even if spam filters might otherwise apply.

This is more sensitive: If the system sends emails using your domain but doesn't follow proper authentication, our server may flag and reject them as spoofed.
Depending on the capabilities of the third-party service, choose from the options below:

If the third-party service allows SMTP setup, configure it using your actual email credentials:

• SMTP Host: vo1.agnx.com / vo2.agnx.com / g1.agnx.com
  IMPORTANT: To confirm which server to be used for your domain, please use the Email Lookup Tool or consult Lookafter Helpdesk.
• Port: 465 (SSL) or 587 (STARTTLS)
• Username: (your email address, e.g. no-mail@yourdomain.com)
• Password: (your email password)

This ensures the email is sent securely from your domain through our mail server, and fully passes SPF check.

If SMTP isn’t available, ask the third-party service for the IP address or domain name of their sending mail server.
You can then update your domain's SPF record via Manage DNS to include their server.

This tells receiving servers (including your mail server) that it's legitimate for that third-party server to send emails on behalf of your domain.

NOTE: Updating your SPF record involves technical steps.
Please do not remove or overwrite your existing SPF record, as this may cause email delivery issues.
If you're unsure how to proceed, feel free to contact our helpdesk for assistance. A one-time service fee may apply for SPF record updates.

If SMTP isn't available and you prefer not to modify your SPF, you can use a subdomain to send from the third party - e.g. notify@mailer.yourdomain.com.

This method helps isolate third-party sending without affecting the deliverability of emails from your main domain.

NOTE: The subdomain must not already exist or be used with any other services.