Bug #4508
closedMailscanner does not work on pfSense 2.2.
0%
Description
As documented in the forum, mailscanner does not work at all in pfSense 2.2.
[[https://forum.pfsense.org/index.php?topic=87385.msg479828#msg479828]]
The purpose of reporting this is to track the issue so that those who depend on mailscanner will know when it is safe to update.
Updated by Marcello Silva Coutinho about 9 years ago
Soren Stoutner wrote:
As documented in the forum, mailscanner does not work at all in pfSense 2.2.
[[https://forum.pfsense.org/index.php?topic=87385.msg479828#msg479828]]
The purpose of reporting this is to track the issue so that those who depend on mailscanner will know when it is safe to update.
It's related to pbi. Once 2.3 is out it will work again.
For now, just a pbi remove and pkg install will workaround this issue.
Updated by Chris Buechler about 9 years ago
- Category set to Mailscanner
- Status changed from New to Confirmed
- Affected Version changed from 2.2 to 2.2.x
Updated by Harry Coin about 9 years ago
Neither postfix nor mailscanner even begin running in 2.2. The maintainer has offered a 'sort of' workaround for postfix, but the online instructions are guidance, not step by step 'known working' pathway. Note the '-r' should be '-rf' in the guidance, and the sequence of what to do in the gui and what to do on the command line and in what order is important and unstated.
The maintainer suggests a similar strategy to get mailscanner working, but whatever was involved, was more involved than the two instructions mentioned as those alone failed.
The maintainer wrote that there is no possibility of either postfix nor mailscanner working in 2.2. He writes that the package's inherent inner structure and pbi will never work over time. Only in 2.3 when 'pbi goes away' might they once again work, he writes.
Those who need either postfix or mailscanner to work should either wait until 2.3 (?? date ??), stay with 2.1, or consider greater design changes.
I'd welcome any corrections or comments from those who understand this situation better. I've tried to upgrade twice from 2.1 to 2.2 following various pathways over the past few months, only to lose a half day on this issue both times and revert to 2.1 for production.
Updated by Chris Buechler almost 9 years ago
- Status changed from Confirmed to Needs Patch