Can I receive attachments through Inbound Parsing?

A. Yes. Netcore Email API is capable of receiving and forwarding attachments included in the replies. These are typically sent as part of the JSON payload to your configured Webhook URL.

Why do I need to change my MX records?

A. MX (Mail Exchange) records tell the internet which server is responsible for accepting emails on behalf of your domain. To "catch" the replies your customers send, those replies must be routed to Netcore’s servers first so they can be parsed.

Can I use my main company domain for Inbound Parsing?**

A. While possible, it is a best practice to use a subdomain (e.g., replies.yourdomain.com). Since you must point the MX records to Netcore, using your primary domain would result in your corporate emails (like [email protected]) being sent to Netcore instead of your office inbox.

How do I verify my Webhook URL?

A. Once you enter your Webhook URL in the Inbound Parse settings, click the 'Verify' button. Netcore will send a test request to your server. Your server must respond successfully to authenticate the connection and activate the parse.

What is Conditional Parsing?

A. Conditional Parsing allows you to create "If-Then" rules for incoming emails. For example, you can route emails with the subject line "Support" to one URL and emails containing "Sales" to another. You can filter based on:

• Subject line
• Recipient domain
• Email headers

What happens if an incoming email doesn't match any of my conditions?

A. If a reply doesn't meet any of the specific criteria you've set, it will be processed under the Global Condition. Think of this as your "catch-all" rule that ensures no reply is lost.

My Inbound Parse status says "Unverified." Is it working?

A. No, an unverified parse is inactive. This status typically indicates that you have selected "Webhook" as an action but haven't successfully completed the URL authentication step. Ensure your endpoint is live and click 'Verify' in the dashboard.

I updated my MX records, but Netcore says "Not Verified." Why?

A. DNS changes can take anywhere from a few minutes to 48 hours to "propagate" across the internet. If you are sure the records are correct, wait a short while and try clicking the verify button again.