An automated "your message has been delivered" reply is not the same as a contracting officer opening your proposal, and the U.S. Court of Federal Claims made that distinction painfully concrete for one fuel supplier. In an opinion issued June 17, 2026 in Rick Aviation, Inc. v. United States, the court dismissed a protest of a Defense Logistics Agency petroleum-fuel award after the offeror's emailed proposal was silently quarantined by a government email firewall and never reached DLA's inbox. The court held the firm's bid was late under the Federal Acquisition Regulation, and none of the regulatory exceptions rescued it.
Background
DLA Energy issued a solicitation for petroleum fuel with a proposal deadline of 1 p.m. on May 23, 2025. Rick Aviation, Inc. moved early. The company emailed its proposal to DLA's designated address on May 22 at 1:27 p.m. — nearly a full day before the cutoff — and received an automated delivery confirmation in return. On the strength of that confirmation, the firm reasonably believed its offer was in the agency's hands.
It was not. The email traversed the Defense Information Systems Agency, which operates DLA's email infrastructure, and DISA's security systems quarantined the message because of a Sender Policy Framework (SPF) authentication configuration error on the sender's side. SPF is a standard anti-spoofing check that lets receiving mail servers confirm a message actually came from a server authorized to send for the sender's domain. When a domain's SPF record is misconfigured, legitimate mail can fail the check and get treated as suspicious — exactly what happened here. The proposal was trapped in the firewall and never delivered to DLA's inbox.
Unaware of the problem, DLA proceeded to evaluate the offers it had actually received and, on August 19, 2025, awarded the contract to competitor Avfuel. Rick Aviation learned it had lost, filed a protest in September, and only during that process discovered the deeper problem: the agency had never received its proposal at all. What the company thought was a competitive loss was in fact a bid that vanished before anyone at DLA could read it.
Key Details
The court analyzed the dispute under the FAR's well-worn "late is late" rule, which governs proposals not received at the designated office by the exact time set for receipt. The central question was whether delivery to DISA's server counted as receipt by DLA. The court said it did not: "receipt by DISA's server did not satisfy the receipt-by-the-agency requirement." Because the proposal was quarantined in transit, it never reached the office designated in the solicitation before the award, and the timing rule treated it as late.
Rick Aviation invoked the government-control exception, the narrow carve-out that can excuse lateness when a proposal is received at the government installation and then, while under the government's control, is delayed or misplaced through no fault of the offeror. The court rejected that path. The exception presumes the proposal actually arrived at the designated office; here it never did. A message stuck in a security quarantine at an intermediate server had not been received by DLA in the sense the regulation requires, so the government-control exception could not apply.
The automated delivery confirmation, the court reasoned, proved only that the message hit DISA's mail infrastructure — not that it reached the contracting activity. An automated response is a machine acknowledging receipt of network traffic; it is not the government confirming possession of a readable proposal. On that record, the firm bore the consequence of a deadline it had, in a technical sense, missed, even though it hit "send" almost 24 hours early. The court denied the protest.
The outcome is unforgiving, and the opinion does not pretend otherwise. The offeror did nothing careless in the ordinary sense — it submitted early, kept its confirmation, and had no way to see inside DISA's firewall. But the "late is late" framework is deliberately bright-line. It exists so contracting officers are not forced to adjudicate case-by-case claims about who really submitted what and when, and the court declined to bend it around an SPF misconfiguration, wherever the blame for that misconfiguration ultimately sat.
What It Means for Contractors
The practical lesson is blunt: confirm actual receipt with a human at the contracting office before the deadline, every time. An automated delivery response is not proof the agency has your proposal. Nothing in this record suggests Rick Aviation would have lost had it phoned or emailed the contracting officer on the morning of May 22 to verify the proposal was in hand — the extra day it built in gave it ample time to catch a non-delivery, if only it had checked with a person rather than trusting the auto-reply.
Second, treat email as the fragile transport it is. Government security stacks quarantine, strip, and bounce messages routinely, and offerors rarely get visibility into it. Firms should verify their own domain's SPF, DKIM, and DMARC records are correctly configured well before a submission, because an authentication failure on the sender's side can doom an otherwise timely bid. Where a solicitation allows a portal upload or a physical copy, that channel can provide a cleaner receipt trail than email alone.
Third, build margin and a verification step into the submission plan. Submitting early is worthwhile only if the early submission is paired with an affirmative confirmation that the proposal landed. The offeror here did the first half and skipped the second, and the gap was fatal. A short checklist — send, request read confirmation from the CO, and get a human acknowledgment before the clock runs out — costs little and closes exactly the hole that sank this bid.
Finally, understand how narrow the exceptions are. The government-control exception is not a general fairness valve; it requires the proposal to have actually reached the designated office. A proposal caught in transit, however blameless the offeror, generally falls outside it. In a "late is late" world, the burden of confirming receipt sits squarely with the contractor, and the Court of Federal Claims just underscored that no automated acknowledgment will shift it.
