Bugzilla Bug 199330

Current versions in portage are 2.3.8 and 2.4.5.

--8<--
Postfix stable release 2.4.6 etc. fix minor problems in the SMTP
client, and work around "noatime" mail queues. Note: stable releases
do not change except for bugfixes and emergencies. New features are
introduced via the experimental release (currently, Postfix 2.5).

- A remote SMTP client TLS certificate with an unparsable canonical
  name triggered a panic error in the Postfix SMTP server (attempt
  to allocate zero-length memory) while sending a request to an
  SMTPD policy server.

- On backup MX servers where the queue file system is mounted with
  "atime" (file read/execute access time) updates disabled, the
  flush daemon would trigger mail delivery attempts once every 1000
  seconds, thus rendering the maximal_backoff_time setting useless
  for backup MX service.
--8<--
(2.3.8 => 2.3.13 has even more interesting changes)

As latest and greatest 2.5.1 is already in the tree, it's
not that much important for me to have the latest 2.3 and
2.4 versions in portage...

I agree with not bumping 2.3.x each time a new version exists, since 2.4 is
stable and the upgrade is easy.

I bumped 2.4.7 since 2.5.x is still ~keyworded and 2.4.x is stable.