faq:email:integrating_email_with_third_party_services
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| faq:email:integrating_email_with_third_party_services [2025/08/07 16:08] – [Integrating Email with Third-Party Services] vikki | faq:email:integrating_email_with_third_party_services [2025/08/07 16:53] (current) – [1) If They Are Using Their Own Domain (e.g. @thirdpartyservice.com)] vikki | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| Before setting up, find out whether the third-party system will send emails: | Before setting up, find out whether the third-party system will send emails: | ||
| - | * [[faq: | + | * [[faq: |
| - | * [[faq: | + | * [[faq: |
| ---- | ---- | ||
| ===== 1) If They Are Using Their Own Domain (e.g. @thirdpartyservice.com) ===== | ===== 1) If They Are Using Their Own Domain (e.g. @thirdpartyservice.com) ===== | ||
| + | Some third-party systems send emails using their own domain. To ensure these emails arrive in your inbox and are not filtered as spam, it is recommended to **whitelist the sender domain in your [[faq: | ||
| + | For Example: You're using a payroll system that sends pay slips from @hrsystem.com.\\ | ||
| + | To receive them consistently, | ||
| + | |||
| + | This tells the email server to always accept emails from that domain, even if spam filters might otherwise apply. | ||
| + | |||
| + | <fc # | ||
| + | If they do not, their emails may still be rejected by our server for failing anti-spoofing checks - even if whitelisted.\\ | ||
| + | We recommend confirming this with the third-party provider if you encounter any delivery issues. | ||
| ---- | ---- | ||
| ===== 2) If They Are Using Your Domain (e.g. @yourcompany.com) ===== | ===== 2) If They Are Using Your Domain (e.g. @yourcompany.com) ===== | ||
| + | |||
| + | This is more sensitive: If the system sends emails using your domain but doesn' | ||
| + | Depending on the capabilities of the third-party service, choose from the options below: | ||
| + | |||
| + | ==== ✅ Best Option: Use SMTP Authentication ==== | ||
| + | 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\\ <color # | ||
| + | * **Port:** 465 (SSL) or 587 (STARTTLS) | ||
| + | * **Username: | ||
| + | * **Password: | ||
| + | |||
| + | This ensures the email is sent securely from your domain through our mail server, and fully passes SPF check. | ||
| + | |||
| + | ==== ⚙️ Alternative Option: Add the Third Party’s Server to Your SPF Record ==== | ||
| + | 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' | ||
| + | |||
| + | 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. | ||
| + | |||
| + | <color # | ||
| + | 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 None of the Above Options Are Available ==== | ||
| + | |||
| + | If the third-party service does not support SMTP and you prefer not to change your SPF record, please contact our helpdesk for further advice.\\ We’ll review your situation and help recommend the most suitable workaround. | ||
| + | |||
| + | |||
faq/email/integrating_email_with_third_party_services.1754554098.txt.gz · Last modified: 2025/08/07 16:08 by vikki
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
