On 11-02-25 1:17 PM, Mohit Chawla wrote:
It was fixed in 1.3.5/1.3.5a.No you're wrong. From the error he had, it was fixed AFTER v1.3.5a. He can use the sogo-ealarms-notify from the nightly builds if he wants, or just wait for 1.3.6 to be released.
Regards, -- Ludovic Marcotte [email protected] :: +1.514.755.3630 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) -- [email protected] https://inverse.ca/sogo/lists
