Two regular expressions used for parsing email headers can cause polynomial regular-expression backtracking when processing attacker-controlled input. This occurs during calls to `parse from string()`, `parse from bytes()`, or `parse from file()`, potentially consuming excessive CPU resources and leading to a denial of service for mail gateways, ticketing systems, quarantine UIs, or archiving pipelines.
The issue manifests in two areas:
1. In `src/mailparser/utils.py`, the `get addresses()` function uses a fallback regular expression ` ADDR FALLBACK RE` that overlaps a lazy quantifier with an adjacent `s*`, resulting in quadratic or cubic matching degradation when processing padded address headers.
2. In `src/mailparser/const.py`, the `parse received()` function uses the ` CLAUSE SPLITTER` regular expression, which backtracks quadratically over whitespace runs that are not followed by a clause keyword.