fix: stop suppressing synthetic@pipeline.com (real customer address)
Paul Wilson (Compound Technologies) signed up with synthetic@pipeline.com, which is a genuine, deliverable EarthLink address (pipeline.com MX -> earthlink-vadesecure.net; he confirmed receipt by phone). Our code had hardcoded pipeline.com + the synthetic@ prefix as a 'non-deliverable FMCSA-census placeholder' and silently suppressed every automated email to him (checkout provisioning, order-creation validation, intake reminders, set-password invites). Nothing in the codebase actually generates that address, so the placeholder rationale was wrong. Removed pipeline.com and the synthetic@ rule from all four suppression sites; only RFC-reserved example.com/test.com/invalid remain blocked.
This commit is contained in:
parent
983c732baf
commit
1ff8b88ac8
4 changed files with 20 additions and 21 deletions
|
|
@ -338,10 +338,10 @@ def _build_portal_onboard_html(pg_order: dict | None) -> str:
|
|||
order_number = pg_order.get("order_number", "")
|
||||
if not email:
|
||||
return ""
|
||||
# Never send a set-password invite to a known placeholder address (e.g. the
|
||||
# FMCSA-census "synthetic@pipeline.com" used when no real email was found).
|
||||
# Never send to RFC-reserved test domains. (pipeline.com is a REAL EarthLink
|
||||
# domain a customer uses -- not a placeholder -- so it is allowed.)
|
||||
em = email.strip().lower()
|
||||
if em.startswith("synthetic@") or em.split("@")[-1] in {"pipeline.com", "example.com", "test.com"}:
|
||||
if em.split("@")[-1] in {"example.com", "test.com", "invalid"}:
|
||||
return ""
|
||||
token = _generate_set_password_token(email, order_number)
|
||||
url = f"{PORTAL_URL.rstrip('/')}/set-password?token={token}"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue