The version of the mail/postfixadmin port is pinned to `GH_TAGNAME= d3bc1551`, which references a commit from 2021. The intention of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258154 was to keep it more current than the newly created mail/postfixadmin33 port, but that was not achieved and the port was never actually updated to point to a more current and stable commit. It's pretty misleading not to have a postfixadmin-devel port for stuff like this and have the mail/postfixadmin use the latest release, which is 3.3.13 from December 2022 Also, there is no version 3.4, not even tagged on Github. Users might misinterpret the 3.4xxx version as more current than 3.3.x. I don't know if it's even possible to make a port follow HEAD on Github.
Later commits in the 3.4-dev branch use Composer, a PHP dependency management tool that is not compatible with the Ports System. 3.3.x doesn't, which is why it continued to update. The reason for mail/postfixadmin being on the dev branch and there being a seperate port for 3.3.x is due to how upstream development and support works. Most people should be using 3.4-dev unless they have a specific reason to use the legacy branch. If there is an engineered release in 3.4, mail/postfixadmin will update to that. Barring that or Composer being fixed, all I can do is change mail/postfixadmin to a metaport with a pkg-message directing people to clone main from Github. Would having mail/postfixadmin be a metaport make more sense to you than the current situation?
Are you still interested in discussing this? Or perhaps someone else would like to offer feedback? Barring further discussion, this PR can be closed without a fix.