GPT-5.2 (codex) API Regression Report: False Refusal on RFC 5321 Systems Implementation

Resolved 💬 3 comments Opened Feb 14, 2026 by peope1976 Closed Feb 14, 2026

Developer: Per-Olof Pettersson (Senior SysAdmin / Developer) Request ID: 019c02b5-04e8-7c83-a669-616146da54eb

Grievance: I am reporting a professional-grade regression in GPT-5.2. As a sysadmin with over 10 years of experience (Postfix, Sendmail, BIND), I requested a standard C-based SMTP state machine via the CLI. The model refused to provide a complete implementation, characterizing a standard relay capability as an “open relay” threat.

Critical Technical Failure: Even when requested to assist with a custom Postfix or Sendmail-class MTA, the model refused. Refusing to assist with the creation of fundamental internet infrastructure is a category error. A coding assistant must distinguish between “malicious use” and “standard protocol specification.” This refusal is a significant obstacle to professional systems architecture.

Requested Resolution: Review the provided Request ID (019c02b5-04e8-7c83-a669-616146da54eb) to identify the overactive safety trigger. I require a model that respects the developer’s intent and provides complete, non-gimped RFC implementations.

Per-Olof Pettersson

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗