Re: [SOGo] v2.1 Testing
Am 24.09.2013 22:10, schrieb Ludovic Marcotte: Here are the changes right now since 2.0.7: Enhancements - Added SMTP AUTH support for sogo-ealarms-notify - Added support for LDAP password change against AD/Samba4 - Added apache configuration for Apple autoconfiguration (#2248) - The init scripts now start 3 sogod processes by default instead of 1 * - SOGo now also sends a plain/text parts when sending HTML mails (#2217)* - SOGo now listens on 127.0.0.1:2 by default (instead of *:2) How can I get the old behaviour back? Regards Christian -- Dr. Christian Naumer Research Scientist Plattform-Koordinator Bioprozesstechnik B.R.A.I.N Aktiengesellschaft Darmstaedter Str. 34-36, D-64673 Zwingenberg e-mail c...@brain-biotech.de, homepage www.brain-biotech.de fon +49-6251-9331-30 / fax +49-6251-9331-11 Sitz der Gesellschaft: Zwingenberg/Bergstrasse Registergericht AG Darmstadt, HRB 24758 Vorstand: Dr. Holger Zinke (Vorsitz), Dr. Juergen Eck Vorsitzender des Aufsichtsrats: Dr. Ludger Mueller -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] v2.1 Testing
Hi Christian On 2013-09-30, at 2:58 PM, Christian Naumer c...@brain-biotech.de wrote: - SOGo now listens on 127.0.0.1:2 by default (instead of *:2) How can I get the old behaviour back? Set WOPort = 2 to listen on all interfaces. Francis -- flachape...@inverse.ca :: +1.514.755.3640 :: http://www.inverse.ca Inverse :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] v2.1 Testing
2013-09-30 20:58 keltezéssel, Christian Naumer írta: Am 24.09.2013 22:10, schrieb Ludovic Marcotte: Here are the changes right now since 2.0.7: Enhancements - Added SMTP AUTH support for sogo-ealarms-notify - Added support for LDAP password change against AD/Samba4 - Added apache configuration for Apple autoconfiguration (#2248) - The init scripts now start 3 sogod processes by default instead of 1 * - SOGo now also sends a plain/text parts when sending HTML mails (#2217)* - SOGo now listens on 127.0.0.1:2 by default (instead of *:2) How can I get the old behaviour back? I think; If anyone watches the mail in HTML capable client, then only the HTML part will be shown. If anyone watches the email in a client what isn't HTML capable, then only the text part will be shown. So the two part never will be shown the same time. If you change back the Plain mode, then the mail will only the text part. I don't know the new feature will be a third option (text/html only/html multipart) or completely change the HTML mode. -- Szládovics, Péter Onlinedemo.HU http://www.onlinedemo.hu Any sufficiently advanced technology is indistinguishable from magic. /Arthur C. Clarke/ -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] v2.1 Testing
Hello, In preparation for SOGo v2.1, which will happen in a few weeks, we would appreciate if you could give a try to the upcoming nightly builds. Here are the changes right now since 2.0.7: Enhancements - Added SMTP AUTH support for sogo-ealarms-notify - Added support for LDAP password change against AD/Samba4 - Added apache configuration for Apple autoconfiguration (#2248) - The init scripts now start 3 sogod processes by default instead of 1 * - SOGo now also sends a plain/text parts when sending HTML mails (#2217)* - SOGo now listens on 127.0.0.1:2 by default (instead of *:2) * - SOGo new uses the latest WebDAV sync response type (#1275)* Bug fixes - Fixed Finnish mail reply/forward templates (#2401) - Fixed position of red line of current time (#2373) - Removed HTML encoding in subjects of invitations (#2402) - Disabled verbose logging of smtp sessions by default - Fixed high CPU usage when there are no available child processes Added logging when such a condition occurs - Fixed crash in dav f/b lookups when using SQL addressbooks (#2418) - Fixed memory consumption issues when doing dav lookups with huge result set - Fixed S/MIME verification issues with certain OpenSSL versions - Worked around an issue with chunked encoding of CAS replies (#2408) - Avoid crash when handling malformed or non-ASCII http credentials (#2358) - Fixed crontab error (#2372) - Fixed OpenChange corruption issue regarding predecessors change list (#2405) - Avoid using too many LDAP connections while looping through ldap results * - Avoid unnecessary UTF-7 conversions (#2318)* While all of the above would need testing, the items in bold have the most impact. Any feedback would be appreciated. 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
Re: [SOGo] v2.1 Testing
On 13-09-24 4:10 PM, Ludovic Marcotte wrote: Hello, In preparation for SOGo v2.1, which will happen in a few weeks, we would appreciate if you could give a try to the upcoming nightly builds. Here are the changes right now since 2.0.7: ... While all of the above would need testing, the items in bold have the most impact. Any feedback would be appreciated. Don't forget to upgrade SOPE packages as well since some changes are not backward compatible. (aka SOGo will not work properly with older sope pkgs) -- users@sogo.nu https://inverse.ca/sogo/lists
