Il 24/02/2011 21:07, Ludovic Marcotte ha scritto:
On 11-02-24 3:06 PM, Mark Adams wrote:
It's not fixed, lets all comment on the bug report.
Your best bet is to put pressure on the calendar folks through on the bug
report... this might
jeopardize positively their
Wolfgang has closed this bug:
http://www.sogo.nu/bugs/view.php?id=1148
Saying this:
The bug is actually in Thundebird:
https://bugzilla.mozilla.org/show_bug.cgi?id=608041 [^]
It's probably going to be solved around august 2038.
What we do to work around the issue is raise the search timeout
Hello all,
I added following line in .GNUstepDefaults for Sieve
keySOGoSieveScriptsEnabled/key
stringYES/string
keySOGoSieveServer/key
stringsieve://sieveserver/string
Then, restarted the sogo daemon and apache. When I logon with user I do not see
option for sieve filter
On Fri, Feb 25, 2011 at 10:19 PM, fire...@aaryaveda.com wrote:
I currently run v1.3.5a.
It was fixed in 1.3.5/1.3.5a.
Which user are you running that binary (sogo-ealarms-notify) as ? You gotta
run it as the sogo user, through a crontab entry ( or as a separate service
).
Anyway, that's
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
On Fri, Feb 25, 2011 at 11:47 PM, Mohit Chawla
mohit.chawla.bin...@gmail.com wrote:
It was fixed in 1.3.5/1.3.5a.
Which user are you running that binary (sogo-ealarms-notify) as ? You
gotta run it as the sogo user, through a crontab entry ( or as a separate
service ).
Ugh, nevermind,
In order to ease the confusion for some of our users, I'm trying to
configure a system that will accept either the uid or mail LDAP
attributes for login to SOGo. I've setup a test system which seems to
work for this. Here's the SOGoUserSources I'm using:
CNFieldName = cn;
IDFieldName = uid;
Hi, there
I downloaded SOGo-1.3.5a rpm package(include others) from
http://www.sogo.nu/files/downloads/SOGo/RHEL5/i386/RPMS/,
and installed it onto a new installation of RHEL5.3(32bit) on a VirtualBox.
I run sql-update-1.3.3_to_1.3.4-mysql.sh to update MySQL database.
I copy over the old
Allen-
Allen Chen wrote:
... snip ...
and adjust /etc/httpd/conf.d/SOGo.conf file:
RequestHeader set x-webobjects-server-port 80
RequestHeader set x-webobjects-server-name sogo135
RequestHeader set x-webobjects-server-url
http://sogo135.hftinternal.com;
Try setting
Stephen Ingram wrote:
Allen-
Allen Chen wrote:
snip ...
and adjust /etc/httpd/conf.d/SOGo.conf file:
RequestHeader set x-webobjects-server-port 80
RequestHeader set x-webobjects-server-name sogo135
RequestHeader set x-webobjects-server-url
http://sogo135.hftinternal.com;
Try
Allen-
Allen Chen wrote:
Thanks Steve for the quick reply.
I changed SOGo.conf to:
RequestHeader set x-webobjects-server-port 80
RequestHeader set x-webobjects-server-name sogo135.hftinternal.com
RequestHeader set x-webobjects-server-url
http://sogo135.hftinternal.com;
and restart sogod
and restart sogod and httpd. when I access GOGo web interface,
I still got the same error messages in http and sogo:
httpd/error_log shows me this:
[Fri Feb 25 22:11:47 2011] [notice] child pid 4446 exit signal
Segmentation fault (11)
sogo/sogo.log shows me this:
Feb 25 22:11:47 sogod [4426]:
Allen-
Allen Chen wrote:
I am not doing updates on the live server. It's a new test installation
with the SOGo1.3.3 database.
I just copied MySQL(SOGo-1.3.3) database to the new RHEL5.3 server,
and install SOGo-1.3.5a rpms, run sql-update-1.3.3_to_1.3.4-mysql.sh to
update MySQL database.
13 matches
Mail list logo