Re: [SOGo] Unable to update to sogo 3.1.4
Hi, > sogo-openchange : Dépend: sogo (= 3.1.3-1) mais 3.1.4-1 devra être > installé > What's going on ? For all distributions of SOGo except Ubuntu Xenial, OpenChange support is being dropped. So please `apt-get remove sogo-openchange` then proceed to the upgrade. If you still need OpenChange support, please consider installing SOGo on Ubuntu Xenial. (OpenChange support has been a hot topic on this list in the last weeks, but to give a quick explanation, current OpenChange needs Samba >= 4.4 and from the set of distributions Inverse supports, only Xenial currently ships with Samba >= 4.4.) -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
Re: [SOGo] Debian Wheezy Repo issue...
>> Looks like there's a redirect? >> W: Failed to fetch >> http://inverse.ca/debian/dists/wheezy/wheezy/binary-amd64/Packages 301 >> Moved Permanently [IP: 2607:5300:60:37b8::2:1 80] > Yes there is now. > You may need to install apt-transport-https package. > Problem might be with IPv6 though, let me get back to you. Redirection was just changed to HTTP (instead of HTTPS). Can you please retry and let us know if you're again able to access our repository? Thanks, -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
Re: [SOGo] Debian Wheezy Repo issue...
> Looks like there's a redirect? > > Ign http://inverse.ca wheezy/wheezy Translation-en_US > Ign http://inverse.ca wheezy/wheezy Translation-en > Err http://inverse.ca wheezy/wheezy amd64 Packages > 301 Moved Permanently [IP: 2607:5300:60:37b8::2:1 80] > W: Failed to fetch > http://inverse.ca/debian/dists/wheezy/wheezy/binary-amd64/Packages 301 > Moved Permanently [IP: 2607:5300:60:37b8::2:1 80] Yes there is now. You may need to install apt-transport-https package. AFAIK apt should follow redirects since about 2009. Problem might be with IPv6 though, let me get back to you. -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
Re: [SOGo] Samba conflict on Debian Jessie
> Which sources of Openchange must be used, last stable (2.3) or current > git? Current OpenChange shipped with Xenial is Zentyal's OpenChange fork version 2.4-zentyal22 — see https://github.com/zentyal/openchange -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
Re: [SOGo] Samba conflict on Debian Jessie
> So, using the pre-compiled sernet samba 4.4 packages > (https://samba.plus/) will not work on jessie/wheezy with sogo? Odds are it will work (I don't see why it wouldn't if samba.plus also ships development headers, but this is obviously not an endorsement!); you will still need to compile/install OpenChange and SOGo yourself though. -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
Re: [SOGo] Samba conflict on Debian Jessie
> What is the best way to have the SOGo / Samba / OpenChange environment > working on Debian Jessie? Compilation; see below. > Why there is no sogo-openchange package with sogo 3.1.3? Is SOGo still > working with OpenChange? SOGo still works with OpenChange when hooked to Samba 4.4. Of all the distributions Inverse currently supports (Debian, Ubuntu, RHEL), only Ubuntu Xenial ships with Samba 4.4. But of course nothing prevents you from compiling and installing Samba 4.4 out-of-band on Jessie, then compiling and installing SOGo/OpenChange yourself. -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
Re: [SOGo] Samba conflict on Debian Jessie
> Is openchange working well with the Jessie samba packages 4.2.10 ? Current OpenChange only works with Samba 4.4.x. Older OpenChange worked with Samba 4.1.x. (and both are now EOL'ed). -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
Re: [SOGo] openSuSE Leap
> Do you know which file should I look in the SOGo installation that > mentions where is expecting the sogo.conf file to be? System defaults handling is described in the source, inside the prepareUserDefaults() method: https://github.com/inverse-inc/sogo/blob/master/SoObjects/SOGo/SOGoSystemDefaults.m -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
Re: [SOGo] Package gnustep-base-libs-1.24.6-6.el7.centos.x86_64.rpm is not signed - CentOS 7
> i wanted to try out SOGo V3 on CentOS 7, but yum denies the install > with above error. Just updated the CentOS 7 repo, adding signatures; let me know if the newer packages still complain. (I would suggest a `yum clean all` first, to ensure local copies of packages fetched pre-signatures are not playing tricks on you.) -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
Re: [SOGo] Samba conflict on Debian Jessie
> I'm trying to install SOGo and Samba on a fresh install of Debian > Jessie but I have a conflict when I try to install samba from the > Inverse SOGo v3 repository. > The Inverse package samba-libs depend of libldb1 < 2:1.1.18 but there > is only 2:1.1.20 in Jessie repository. How can I solve this? Jessie samba packages supersede Inverse's (4.2.10 vs. 4.1.18) and very soon Inverse will stop shipping samba packages for Jessie. Hence, I suggest you install Jessie's samba packages. -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
Re: [SOGo] Updating...
> It seems a critical bug : if this is the result expected, a big > warning should be printed before the execution, otherwise a patch is > needed to keep user data safe. For each of those “combined” migration scripts I just added a big fat warning that prompts the user, to ensure nobody runs them by mistake again. Let me restate, the “combined” data model is *optional* and is not part of any standard upgrade routine. -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
Re: [SOGo] ANN: SOGo v3.1 released!
> This is probably a silly question... but why would we rather have a > 9-tables-total database? Just that it makes mysql look less crowded, > or are there also actual benefits? Two things on top of my head: 1) MySQL table metadata operations get sluggish when the server hits a couple of thousands tables. All table metadata is stored in a non-transactional engine (MyISAM) so full-table locks cannot be avoided; 2) Control of schema creation; if you currently want to use table compression, partitions or get complete Unicode coverage with SOGo, you need to pre-create the schema; letting SOGo automatically create a random number of tables defeats that. -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
Re: [SOGo] META: Mailing list configuration change
>> You may be aware of modern spam protection mechanisms like SPF, DKIM >> and DMARC. > Yes and they are broken by design because they cause problems for > mailing lists and they do not test whether a message is spam. No silver bullet exists AFAIK that deals with all e-mail problems. At least, these try to address the e-mail forgeries that plague e-mail systems, and in some way, make phishing easier when aimed at non-technical users; especially nowadays when spammers steal addressbooks and make it appear that mail comes from a contact. > Is it not serious that it's no longer possible to sort list emails by > sender, or to use the "Reply To Author" commands/buttons in email > clients to reply to the author? You've noticed the textual part from the “From:” header still points to the username; your mail client should be able to sort properly. I guess most mailing lists will proceed as Sympa does, by adding a “X-Original-From” header. It wouldn't be *that* hard for MUA to adjust to this, and still offer users the possibility to reply to the original poster. Then again, I'm not holding my breath; how many years since the adoption of standard mailing-list headers for subscription management, and how many mail clients support it? :) -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
[SOGo] META: Mailing list configuration change
Hi, You may be aware of modern spam protection mechanisms like SPF, DKIM and DMARC. In order to comply with those mechanisms, this mailing list is now replacing the “From:” header with its own address; you may have noticed the change earlier today. As far as I know, this should not create serious issues for subscribers — don't hesitate to report though if this assumption turns out to be false. Thanks for your understanding, -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
Re: [SOGo] FYI nightly 3.0.1.20160225-1
> More of an FYI - next nightly will probably work anyway...! Thanks for the report. A fix was pushed yesterday to ensure proper rebuilding of js/css files before nightly builds — should solve a bunch of problems that broke some user interface components for the last week or so. -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
Re: [SOGo] DMARC and mailing list (offtopic)
> Is there a way to handle incoming messages to the list from the > SPF/DKIM protected mails with DMARC/ADSP policy? Some users cannot > get mails from similar senders (e.g. me). Thanks for pointing it out. We just setup the mailing list software to specially handle e-mail received from such senders. Please let us know if you encounter other related issues. So as far as I know, there should not be any need for subscribers to whitelist posts coming from this list. Cheers, -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
Re: [SOGo] repo zips and xml need a rebuild
>> Upgrading from yum isn't working as these are out-of-date now that >> sogo is 3.0.0-1 Invers promised an FAQ about this. Sadly not here >> till now. The FAQ is now updated: http://sogo.nu/nc/support/faq/article/how-to-install-sogo-and-sope-through-yum-2.html The repositories' metadata has also just been rebuilt. Please retry the "yum clean all"/"yum update" cycle again, this time the update should happen painlessly. -- Patrice Levesque pleves...@inverse.ca :: +1.514.447.4918 *140 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) signature.asc Description: Digital signature
