Acceptance helps keep expected findings out of the default attention list. It records a review choice; it does not repair DNS, change the grade or prove that mail passes authentication.

Review and accept

1. Open PD Modules → Deliverability → Needs attention.
2. Review the domain, severity and What it means.
3. Use How to fix to understand the context before deciding the condition is expected.
4. Choose Accept only for the intended finding, then check the list.

For example, a deliberately monitored policy can be an expected result. Treat that as a documented operational choice rather than changing policy solely to remove a warning.

Revisit the result

Choose Show accepted, review any severity filter, then use Un-accept to return the finding to the default attention list. The view contains open findings; it is not an unrestricted resolved-history browser. Its row limit can differ from the summary counts.

Acceptance is retained when the same finding kind is updated and can remain when it is later reopened. Do not assume that a changed severity, detail or recurrence automatically clears the earlier acceptance. Schedule a deliberate staff review of accepted exceptions when your mail configuration changes.

Distinguish closure from a fix

The latest grading resolves kinds it no longer emits. A failed lookup or the no-mail classification can also remove earlier open findings, so disappearance is not independent proof of a successful correction.

Check the actual DNS and sending evidence before closing an investigation. For an unexpected accepted or missing finding, record the reference, checked time, filters and relevant result in your investigation notes. Do not delete monitoring records merely to bring a warning back.

See the PD Email Deliverability Blesta guide for related tasks, or explore PD Email Deliverability.