IMHO no.
---
Martin Rabl
Am 19.12.2011 um 22:29 schrieb Patrick Ben Koetter :
> * Martin Rabl :
>> The SSL-Bundle error message is very very very ... old and known. It can be
>> ignored.
>
> Are you suggesting it is something else that causes sogod to segfault?
>
> p@rick
>
>
> --
> state
* Ludovic Marcotte :
> On 19/12/11 16:46, Patrick Ben Koetter wrote:
>
> [snip]
> >HTH,
> Install the SOPE debugging packages, as I requested!
Sorry, misunderstood you to install sogo-dbg only.
sogo@mail:~$ gdb --args /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES
-WOPort 2 -WOWorkersCou
On 19/12/11 16:46, Patrick Ben Koetter wrote:
[snip]
HTH,
Install the SOPE debugging packages, as I requested!
--
Ludovic Marcotte
lmarco...@inverse.ca :: +1.514.755.3630 :: www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
--
users@so
* Ludovic Marcotte :
sogo@mail:~$ gdb --args /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES
-WOPort 2 -WOWorkersCount 1 -WOLogFile - -WOPidFile /tmp/sogo.pid
...
done.
(gdb) r
Starting program: /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES -WOPort
2 -WOWorkersCount 1 -WOLogFile -
On 19/12/11 16:39, Patrick Ben Koetter wrote:
sogo@mail:~$ gdb --args /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES
-WOPort 2 -WOWorkersCount 1 -WOLogFile - -WOPidFile /tmp/sogo.pid
...
done.
(gdb) r
Starting program: /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES -WOPort
2 -WO
* Ludovic Marcotte :
> On 19/12/11 16:29, Patrick Ben Koetter wrote:
> >Are you suggesting it is something else that causes sogod to segfault?
> Install the debug packages for SOPE/SOGo and GNUstep and run it inside gdb.
>
> su - sogo
> gdb --args /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES
On 19/12/11 16:29, Patrick Ben Koetter wrote:
Are you suggesting it is something else that causes sogod to segfault?
Install the debug packages for SOPE/SOGo and GNUstep and run it inside gdb.
su - sogo
gdb --args /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES -WOPort
2 -WOWorkersCount
* Martin Rabl :
> The SSL-Bundle error message is very very very ... old and known. It can be
> ignored.
Are you suggesting it is something else that causes sogod to segfault?
p@rick
--
state of mind ()
http://www.state-of-mind.de
Franziskanerstraße 15 Telefon +49 89 3090 4664
81669 Mü
The SSL-Bundle error message is very very very ... old and known. It can be
ignored.
---
Martin Rabl
--
users@sogo.nu
https://inverse.ca/sogo/lists
* Patrick Ben Koetter :
> * oeufd...@gmail.com :
> > Hi,You should try to use tcpdump or tshark to see what's wrong about
> > sieve.Something like that: tshark -i lo -f "port 2000" if sieve
> > run on localhost on the port 2000.RegardsFabrice Durand
>
> Here's a transcript from tcpflow. IIRC Ludo
* oeufd...@gmail.com :
> Hi,You should try to use tcpdump or tshark to see what's wrong about
> sieve.Something like that: tshark -i lo -f "port 2000" if sieve
> run on localhost on the port 2000.RegardsFabrice Durand
Here's a transcript from tcpflow. IIRC Ludovic prefers this tool. The log was
t
Stephen,
* Stephen Ingram :
> On Tue, Dec 13, 2011 at 6:21 AM, Patrick Ben Koetter
> wrote:
> > I'm having problems activating SIEVE rules on my sogo 1.3.11 (I had them on
> > previous versions too) and I am kind of stuck debugging this.
> >
> > Creating a SIEVE rule is no problem. I can add ano
Patrick-
On Tue, Dec 13, 2011 at 6:21 AM, Patrick Ben Koetter
wrote:
> I'm having problems activating SIEVE rules on my sogo 1.3.11 (I had them on
> previous versions too) and I am kind of stuck debugging this.
>
> Creating a SIEVE rule is no problem. I can add another SIEVE rule (currently
> ab
Hi,You should try to use tcpdump or tshark to see what's wrong about sieve.Something like that: tshark -i lo -f "port 2000" if sieve run on localhost on the port 2000.RegardsFabrice Durand-- Envoyé depuis mon HP Pre3Le 19 déc. 2011 21:10, Patrick Ben Koetter a écrit : Would somebody at Inverse be
Would somebody at Inverse be so kind and give a sign of life?
p@rick
* Patrick Ben Koetter :
> I'm having problems activating SIEVE rules on my sogo 1.3.11 (I had them on
> previous versions too) and I am kind of stuck debugging this.
>
> Creating a SIEVE rule is no problem. I can add another S
* Martin Rabl :
> I had a similiar error in 1.3.7 ...
I filed a bug.
p@rick
--
state of mind ()
Digitale Kommunikation
http://www.state-of-mind.de
Franziskanerstraße 15 Telefon +49 89 3090 4664
81669 München Telefax +49 89 3090 4666
Amtsgericht MünchenPartnerschafts
* Martin Rabl :
> I had a similiar error in 1.3.7 ...
I recall this type of error going back to that version, too.
It sucks, also because SOGo SIEVE is a one way road. It can't read in rules
from an existing file. There's no way to edit sieve rules in a different
editor without loosing the edits
Hi,
I had a similiar error in 1.3.7 ...
Martin
Am 13.12.2011 15:21, schrieb Patrick Ben Koetter:
I'm having problems activating SIEVE rules on my sogo 1.3.11 (I had them on
previous versions too) and I am kind of stuck debugging this.
Creating a SIEVE rule is no problem. I can add another SIE
I'm having problems activating SIEVE rules on my sogo 1.3.11 (I had them on
previous versions too) and I am kind of stuck debugging this.
Creating a SIEVE rule is no problem. I can add another SIEVE rule (currently
about 60 rules) and save it. But when I choose to activate the rule and "save
and c
19 matches
Mail list logo
