## TL;DR

Clean the source: fix the import or the form that produced the bad addresses. For bulk lists, run a validation pass before sending rather than discovering bad addresses one drop at a time.

## Steps

1. Symptom: dropped events with reason 'Invalid Address'.

2. Cause: the address is syntactically invalid (typo, missing domain, stray characters) or came from a bad import or form input.

3. Confirmation: the dropped event names the address. Eyeball it; the defect is usually obvious.

4. Fix:
1. Validate addresses at capture: syntax check in the form, and confirm the domain has an MX record for important flows.
2. Clean the source: fix the import or the form that produced the bad addresses.
3. For bulk lists, run a validation pass before sending rather than discovering bad addresses one drop at a time.

5. Verification: Invalid Address drops fall to zero on the next send to the cleaned list.

## When to use

You are seeing this: Symptom: dropped events with reason 'Invalid Address'. Use this skill when you run into "SendGrid dropped event reason Invalid Address".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
