On 16/11/2015 05:00, Ian McMichael wrote:
Yes, confirmed on three separate systems running v2.3.3 here too. No work-around found as yet...
v2.3.3a has just been released with the fix.
Thanks, -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
