ShutdownRadar
Support lifecycle

postfix end of life dates — full support timeline

14 of 18 tracked postfix releases have already reached end of life. The dates below are published support dates, not estimates.

Version support timeline

ReleaseReleasedEnd of lifeLatestStatus
3.112026-03-06not announced3.11.5supported
3.102025-02-16not announced3.10.12supported
3.92024-03-06not announced3.9.13supported
3.82023-04-17not announced3.8.19supported
3.72022-02-062026-03-063.7.21ended
3.62021-04-292025-02-163.6.19ended
3.52020-03-152024-03-063.5.26ended
3.42019-02-272023-04-173.4.29ended
3.32018-02-222022-02-053.3.22ended
3.22017-02-282021-04-293.2.22ended
3.12016-02-242020-03-153.1.15ended
3.02015-02-082019-02-273.0.15ended
2.112014-01-152018-02-212.11.11ended
2.102013-02-112017-02-282.10.10ended
2.92012-02-012016-02-242.9.15ended
2.82011-01-202015-02-082.8.20ended
2.62009-05-122013-02-112.6.19ended
2.52008-01-242012-02-062.5.17ended

Who is affected

Anyone running an unsupported postfix release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.

Source

These dates are maintained by endoflife.date/postfix, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.

Get told before the next postfix deadline

You are reading this because a postfix release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every postfix and related deadline as it is announced, with exact dates and primary sources.

Watch postfix deadlines Team monitoring pilot →

Takes about twenty seconds. No account, no card, no tracking.

All upcoming deadlines · Full archive