[SOGo] Lightning calendar auto refresh closes reminder dialog
It seems that Lightning and SOGo calendar refresh mechanism have a bug, or certainly behave badly. When the calendar refreshes against the server, subject to preference 'calendar.autorefresh.timeout', the reminder dialog closes, never to open again. This is a problem because if you go away for a few minutes and come back to your desk, you may miss the reminder. It seems that when the preference 'calendar.alarms.showmissed' is set to 'true', the problem is alleviated. It's as if it springs back after the refresh. But with it set to 'false' the reminder notification dialog disappears forever, no opertunity to snooze either. It's hard to beleive this has gone unnoticed or fixed, it's pretty fundemental to SOGo calendar users. Also, the default for 'calendar.alarms.showmissed' is 'false'. So it should effect most users. I stumbled upon it when I was forcing my users prefs to 'false' for the said setting, then the problem showed up very quickly under testing. The reason I switched to 'false' was because some are experiencing problems with ghost reminder popups. They keep coming back. Now I will have to test if there really is an issue with dismiss reminder when 'calendar.alarms.showmissed' is 'true'. It may be a case of which is the lesser evil. I suspect past events with reminders could be the cause. SOGo 2.0.4b Thunderbird 24.0.5 Lightning 2.6.6 (same case with 2.6.5) Sogo Connector/ Integrator 24.0.7 (same case with 24.0.4) -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] rekonq browser - compose window not closing
When using rekonq v2.3.2 (a KDE browser) on Linux, the compose window will not close after sending the email. It just stays open as if it's indefinetely trying to send it. Meanwhile the email is already in my sent folder. This is not the case on other browsers. I correspond to the developer so I can ask him to add support if I knew what function needed to be added to support this. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGo on FreeBSD
Your problem with multi-domain setup appears to be the 'id' key. Each domain needs a different id. For example: for domainA.net use id = public_domaina , for domainB.net use id = public_domainb. I made the same mistake myself, easy to overlook, not much in logs to indicate the problem. -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Webmin module for FreeBSD?
I have a fully functioning SOGo setup on FreeBSD,... purrs like a kitten. Just need to do some testing and plan a migration strategy. SOGo is truly great, after looking around quite a bit, it has the best set of features for us. Only one thing I can't do yet on FreeBSD; install the webmin module. I get a message saying it's doesn't support my OS. Is there anything in the webmin module that is really LInux specific? If not I could hack it to fool it into thinking FreeBSD is supported. I guess the paths (e.g to GNUstep defaults) are all I can think of, if so they could easily be changed. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] FreeBSD installation guide.
Very nice guide Jose, much appreciated by a fellow FreeBSD advocate. Thanks for mentioning my work on the service script, but it wasn't all mine, I got some help from another forum post but I can't remember where or who posted it. FYI, this still works on FreeBSD 8.2 with latest ports tree and SOGo 1.3.9 I just wanted to point out a possible mistake: In the NGINX configuration you have this line: proxy_set_header x-webobjects-server-url http://sogo.example.com:; It does not work for me, the port seems strange. However without the : it does work for me: proxy_set_header x-webobjects-server-url http://sogo.example.com; Also, you refer to Apache at the end of the guide, yet you have switched it to NGINX. Otherwise, everything else was pretty smooth sailing. I use LDAP for user lookup / authentication. And PostgreSQL for sogo database. I'm curious, why did you switch to NGINX from Apache? I never heard og NGINX until I read your instructions, it sounds interesting, will have to read up on it. -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] FreeBSD startup script
I got SOGo 1.3.4 to compile and install on FreeBSD 8.1, wohoo!
I will write up my procedure and post it somewhere when I have the time, It was
quite easy though. However, making a startup script was a bit harder, so I
thought I'd share it. Maybe it could go in the source code bundle for other
FreeBSD users.
For reference; GNUstep is installed in /usr/local/GNUstep on FreeBSD, this
needs changing in the SOGo.conf file for apache.
# cp /usr/local/src/SOGo/SOGo-1.3.4/Apache/SOGo.conf
/usr/local/etc/apache22/Includes/
# nano /usr/local/etc/apache22/Includes/SOGo.conf
change /usr/GNUstep to /usr/local/GNUstep
then add 'sogod_enable=YES' to /etc/rc.conf
then add rc script for sogod:
# nano /usr/local/etc/rc.d/sogod
#!/bin/sh
#
#
# PROVIDE: sogod
# REQUIRE: memcached
#
# Add the following lines to /etc/rc.conf to enable sogod:
#
# sogod_enable (bool): Set it to YES to enable sogod.
# Default is NO
#
#
. /etc/rc.subr
name=sogod
rcvar=`set_rcvar`
load_rc_config ${name}
: ${sogod_enable=NO}
: ${sogod_user=sogo}
: ${sogod_group=sogo}
: ${sogod_workers=-WOWorkersCount 1}
: ${sogod_command=/usr/local/GNUstep/Local/Tools/Admin/sogod}
: ${sogod_logfile=/var/log/sogo/sogo.log}
pidfile=/var/run/sogo/sogo.pid
command=/usr/sbin/daemon
command_args=-p ${pidfile} -u ${sogod_user} ${sogod_command} ${sogod_workers}
-WOPidFile ${pidfile} -WOLogFile ${sogod_logfile}
start_precmd=sogod_prestart
start_cmd=sogod_start
stop_cmd=sogod_stop
status_cmd=sogod_status
sogod_prestart() {
if [ ! -d `dirname ${pidfile}` ]; then
mkdir `dirname ${pidfile}` chown ${sogod_user}:${sogod_group} `dirname
${pidfile}`
fi
if [ ! -d `dirname ${sogod_logfile}` ]; then
mkdir `dirname ${sogod_logfile}`
touch ${sogod_logfile} chown ${sogod_user}:${sogod_group}
${sogod_logfile}
fi
if [ -z ${GNUSTEP_SYSTEM_ROOT} ]; then
. /usr/local/GNUstep/System/Library/Makefiles/GNUstep.sh
fi
}
sogod_start () {
${command} ${command_args}
}
sogod_stop () {
kill `cat ${pidfile}`
}
sogod_status () {
if [ -f ${pidfile} ]; then
echo ${name} is running as pid `cat ${pidfile}`
else
echo ${name} is not running
fi
}
run_rc_command $1
omitting the and of course!
then assuming a user called sogo with matching group name has been created, and
ht e'defaults' are set, it's just:
# service start sogod
/etc/passwd for me looks like this:
#cat /etc/passwd | grep sogo
sogo:*:1002:1002:SOGo Admin:/home/sogo:/usr/local/bin/bash
Hope this helps someone.
--
users@sogo.nu
https://inverse.ca/sogo/lists
