On 12-05-24 3:06 PM, Peter Peltonen wrote:
Hi,
On Thu, May 24, 2012 at 9:34 PM, Jean Raby wrote:
We could finally reproduce the issue and it should now be fixed in the
nightly builds (sope).
Will there be 1.3.15b or should one install 1.3.15a + updated sope
packages from nightly? And which o
Hi,
On Thu, May 24, 2012 at 9:34 PM, Jean Raby wrote:
> We could finally reproduce the issue and it should now be fixed in the
> nightly builds (sope).
Will there be 1.3.15b or should one install 1.3.15a + updated sope
packages from nightly? And which of the sope packages should be
updated:
sop
On 12-05-19 5:27 AM, Romain LE DISEZ wrote:
Hi all,
Le Vendredi 18 Mai 2012 18:40 CEST, Jean Raby a écrit:
However, if SOGo is _not_ restarted after the upgrade, the client will
see a mostly empty page.
sogod should be automatically restarted after an upgrade. That's how packages
work in RH
On 12-05-19 4:48 AM, Jean-Michel OLTRA wrote:
Bonjour,
Le vendredi 18 mai 2012, Jean Raby a écrit...
After clearing the browser cache, all went well. I had a look to the
mtime timestamp of the files: it was the one of the upgrade.
I've been trying to reproduce this issue for a while
Romain LE DISEZ wrote:
Hi all,
Le Vendredi 18 Mai 2012 18:40 CEST, Jean Raby a écrit:
However, if SOGo is _not_ restarted after the upgrade, the client will
see a mostly empty page.
sogod should be automatically restarted after an upgrade. That's how packages
work in RHEL (eg: httpd, postgre
Hi all,
Le Vendredi 18 Mai 2012 18:40 CEST, Jean Raby a écrit:
> However, if SOGo is _not_ restarted after the upgrade, the client will
> see a mostly empty page.
sogod should be automatically restarted after an upgrade. That's how packages
work in RHEL (eg: httpd, postgresql) and Debian.
A sm
Bonjour,
Le vendredi 18 mai 2012, Jean Raby a écrit...
> >After clearing the browser cache, all went well. I had a look to the
> >mtime timestamp of the files: it was the one of the upgrade.
> I've been trying to reproduce this issue for a while, but it simply
> doesn't happen on my setup
On 12-05-17 1:50 AM, Jean-Michel OLTRA wrote:
Bonjour,
Le mercredi 16 mai 2012, Jean Raby a écrit...
Also, if you can reproduce the problem, can you post the apache logs
where apache returns 304 (Not Modified) responses? (which cause the
client to use its cached version)
Here is one
Bonjour,
Le mercredi 16 mai 2012, Jean Raby a écrit...
> Also, if you can reproduce the problem, can you post the apache logs
> where apache returns 304 (Not Modified) responses? (which cause the
> client to use its cached version)
Here is one of our customers who was not able to view mai
On 12-05-16 1:23 PM, Jeroen Dekkers wrote:
At Wed, 16 May 2012 01:32:51 -0500,
Aaron C Johnson wrote:
On 05/16/2012 01:29 AM, Relu Parfene wrote:
I updated to sogo 1.3.15 and all sope modules. I restarted sogo and
memcached. After these operations in the web interface all mails are
gone (includ
10 matches
Mail list logo