Postfix Forwarder - Pending update post pfsense v2.2 or abandoned?
-
Can anyone confirm whether postfix forwarder is going to be updated to function post-pfsense 2.2, or has it been abandoned? This information will help people as they figure out how to address post-pfsense 2.2 problems, especially those that upgraded and then had to revert to 2.1.5 and are now left with partially borked installs.
-
There is a work-around suggested by the package maintainer on another thread. But, he's worried that any future fix will misbehave because of the work around. Seems the pbi thing is causing stress. I certainly think it's reasonable to ask PF leadership to give upgraders a heads up if known working packages won't function after an upgrade.
The upgrade process should be changed in this way: A new flag, ON by default, which causes the dashboard to NOT report 'upgrade available' unless the maintainers of all packages the user has installed have affirmed their package 'has no regressions' for that upgrade. The new stuff doesn't have to work, but the old stuff can't be broken.
-
Snapshots are provided for a reason. I would recommend testing the packages you use prior to a release.
-
There is a work-around suggested by the package maintainer on another thread.
Is this the post you are referring to?
https://forum.pfsense.org/index.php?topic=40622.msg504124#msg504124
So in theory, this would get postfix forwarder running properly on 2.2?
-
You can use the Postfix Forwarder pbi after running the following:
pkg install libspf2 pcre cyrus-saslThere's another way to do it by creating a bunch of symlinks but I think this way is cleaner and easier.
-
Snapshots are provided for a reason. I would recommend testing the packages you use prior to a release.
Well lesson learned there. I wish that reason was mentioned in the release announcement, which read: "As always, you can upgrade from any previous version straight to 2.2.2"
It doesn't say "As always, you can upgrade from any previous version straight to 2.2.2. Note to add-on package users: no packages have been tested, they may or may not start after the upgrade."
I want to be clear that I'm not complaining. After all I could ask for a complete refund of my purchase price of $0. It's a great package overall. All it takes is a tweak to release announcements so folks using packages don't presume they've been tested prior to the release or upgrade. Cost me a bunch of time, worth much more than the incremental value of this upgrade in my particular case.
-
It doesn't say "As always, you can upgrade from any previous version straight to 2.2.2. Note to add-on package users: no packages have been tested, they may or may not start after the upgrade."
It doesn't say that because that isn't true.
We test many of the packages but we can't test them all. We can't be responsible for packages that are contributed/maintained by the community, only the ones we maintain directly. It's up to the package maintainers to keep up with development and testing. If a package like postfix was contributed by a community member and the maintainer disappeared or lost interest, someone else needs to step up and maintain it.
It may be used by a few people but due to the nature of the package running a mail server on a firewall it's not one we have ever supported nor encouraged.
There is a bounty open to get it fixed up, check that board for more.
