headers
Jason Welsh | 5 Nov 2009 16:40

Re: newbie needin help with sieve server/ingo config.

ok, I wiped out my ingo directory, installed fresh from scratch..
redid my config and my backends.php and tried again.. Looking in my
apache error logs, I see

[Thu Nov 05 10:39:39 2009] [error] [client 192.168.1.55] PHP
Deprecated:  Assigning the return value of new by reference is
deprecated in /usr/local/apache2/htdocs/horde/lib/Horde/Prefs.php on
line 847, referer: https://birdhouse.mydomain.com/horde/ingo/script.php
[Thu Nov 05 10:39:39 2009] [error] [client 192.168.1.55] PHP
Deprecated:  Assigning the return value of new by reference is
deprecated in /usr/local/apache2/htdocs/horde/ingo/lib/Storage.php on
line 272, referer: https://birdhouse.mydomain.com/horde/ingo/script.php
[Thu Nov 05 10:39:39 2009] [error] [client 192.168.1.55] PHP
Deprecated:  Assigning the return value of new by reference is
deprecated in /usr/local/apache2/htdocs/horde/ingo/lib/Storage.php on
line 380, referer: https://birdhouse.mydomain.com/horde/ingo/script.php
[Thu Nov 05 10:39:39 2009] [error] [client 192.168.1.55] PHP
Deprecated:  Assigning the return value of new by reference is
deprecated in /usr/local/apache2/htdocs/horde/ingo/lib/Storage/sql.php
on line 172, referer: https://birdhouse.mydomain.com/horde/ingo/script.php
[Thu Nov 05 10:39:40 2009] [error] [client 192.168.1.55] PHP
Deprecated:  Assigning the return value of new by reference is
deprecated in
/usr/local/apache2/htdocs/horde/ingo/lib/Driver/timsieved.php on line
68, referer: https://birdhouse.mydomain.com/horde/ingo/script.php
[Thu Nov 05 10:39:40 2009] [error] [client 192.168.1.55] PHP
Deprecated:  Assigning the return value of new by reference is
deprecated in /usr/local/lib/php/Net/Sieve.php on line 177, referer:
https://birdhouse.mydomain.com/horde/ingo/script.php
[Thu Nov 05 10:39:40 2009] [error] [client 192.168.1.55] PHP
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jan Schneider | 5 Nov 2009 16:58
Favicon
Gravatar

Re: newbie needin help with sieve server/ingo config.

Zitat von Jason Welsh <jason@...>:

> ok, I wiped out my ingo directory, installed fresh from scratch..
> redid my config and my backends.php and tried again.. Looking in my
> apache error logs, I see
>
> [Thu Nov 05 10:39:39 2009] [error] [client 192.168.1.55] PHP
> Deprecated:  Assigning the return value of new by reference is
> deprecated in /usr/local/apache2/htdocs/horde/lib/Horde/Prefs.php on
> line 847, referer: https://birdhouse.mydomain.com/horde/ingo/script.php
> [Thu Nov 05 10:39:39 2009] [error] [client 192.168.1.55] PHP
> Deprecated:  Assigning the return value of new by reference is
> deprecated in /usr/local/apache2/htdocs/horde/ingo/lib/Storage.php on
> line 272, referer: https://birdhouse.mydomain.com/horde/ingo/script.php
> [Thu Nov 05 10:39:39 2009] [error] [client 192.168.1.55] PHP
> Deprecated:  Assigning the return value of new by reference is
> deprecated in /usr/local/apache2/htdocs/horde/ingo/lib/Storage.php on
> line 380, referer: https://birdhouse.mydomain.com/horde/ingo/script.php
> [Thu Nov 05 10:39:39 2009] [error] [client 192.168.1.55] PHP
> Deprecated:  Assigning the return value of new by reference is
> deprecated in /usr/local/apache2/htdocs/horde/ingo/lib/Storage/sql.php
> on line 172, referer: https://birdhouse.mydomain.com/horde/ingo/script.php
> [Thu Nov 05 10:39:40 2009] [error] [client 192.168.1.55] PHP
> Deprecated:  Assigning the return value of new by reference is
> deprecated in
> /usr/local/apache2/htdocs/horde/ingo/lib/Driver/timsieved.php on line
> 68, referer: https://birdhouse.mydomain.com/horde/ingo/script.php
> [Thu Nov 05 10:39:40 2009] [error] [client 192.168.1.55] PHP
> Deprecated:  Assigning the return value of new by reference is
> deprecated in /usr/local/lib/php/Net/Sieve.php on line 177, referer:
(Continue reading)

Permalink | Reply | 1 comment |
headers
lst_hoe02 | 5 Nov 2009 17:38
Picon
Favicon

Re: newbie needin help with sieve server/ingo config.

Zitat von Jan Schneider <jan@...>:

> Zitat von Jason Welsh <jason@...>:
>
>> ok, I wiped out my ingo directory, installed fresh from scratch..
>> redid my config and my backends.php and tried again.. Looking in my
>> apache error logs, I see
>>
>> [Thu Nov 05 10:39:39 2009] [error] [client 192.168.1.55] PHP
>> Deprecated:  Assigning the return value of new by reference is
>> deprecated in /usr/local/apache2/htdocs/horde/lib/Horde/Prefs.php on
>> line 847, referer: https://birdhouse.mydomain.com/horde/ingo/script.php

As far as i know this is a warning from PHP 5.3 for compatibilty  
problems which may arise in the future. But this has nothing todo with  
your problem.

Regards

Andreas
Permalink | Reply | 0 comments |
headers
Jeff Larsen | 20 Nov 2009 17:32
Picon

Re: Ingo lost the filters

Jan Schneider <jan <at> ...> writes:

> 
> Zitat von Carsten Burghardt <carsten <at> ...>:
> 
> > Hi list,
> >
> > I am using Ingo (1.2.1) as part of a new Kolab installation. I  
> > created some new filter rules and the sieve script was created just  
> > fine and it works. But the strange part is that shortly after the  
> > configuration (maybe the next day) all my custom filters disappeared  
> > from the web frontend, only the "standard" filters such as spam,  
> > white and backlist are listed. The active script is still fine and  
> > still shows in the header that it was created by Ingo. Any idea how  
> > I can restore the configuration that is shown in the web interface,  
> > maybe from the sieve configuration script?
> 
> This is not possible.
> 
> Jan.

Dredging up an old thread... I found it unpleasant to find "This is not
possible" when I was observing identical symptoms.

I did manage to figure out how I created the problem, so I thought I should
share for the benefit of future web searches. 

I am building a new horde installation and was working on setting up default
preferences. During the process, I was deleting all the entries in the SQL
horde_prefs table so I could test my changes in various prefs.php files. Ingo
(Continue reading)

Permalink | Reply | 0 comments |
headers
Shane Williams | 30 Nov 2009 21:53
Picon
Favicon

Rules don't have mail prefix

Running Horde 3.3.4, IMP 4.3.4, Ingo 1.2.2 and Dovecot 1.0.7

Other background:  Due to historical issues with mail folders (that,
no surprise, have to do with UW-IMAP), we've created several
namespaces in dovecot.  The default namespace, with no prefix, points
to "$HOME/mail".  Then there are additional hidden namespaces, one of
which, to provide backward compatibility in certain situations uses
the prefix "mail/" and also points to "$HOME/mail".  So, right now,
when IMP does it's NAMESPACE command, it gets back:
* NAMESPACE (("" "/")) NIL NIL

Problem description
Ingo is set to use the IMP folder api, which appears to work right.
That is, when I go to set up a new rule, and choose "Deliver to
folder..." as the "Do this:" action, up pops a list of target folders
(which live in $HOME/mail).

But then, when I select a folder (cron for instance), and save the
rule, the resulting procmail script shows the destination as only
"cron" when it ought to say "mail/cron".

Interestingly, if I specify a namespace in my IMP servers.php with:
'namespace' => array('mail/')
when I go through ingo action to "Deliver to folder" the drop-down now
shows the list of folders from the default, and then, in the middle
where the "m"s are, there's a greyed out line that says "mail" and all
the folders listed again, but slightly indented.  If I chose the
indented "cron", ingo now points the procmail action toward
"mail/cron", as desired.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jan Schneider | 2 Dec 2009 00:14
Favicon
Gravatar

Re: Rules don't have mail prefix

Zitat von Shane Williams <broot@...>:

> Running Horde 3.3.4, IMP 4.3.4, Ingo 1.2.2 and Dovecot 1.0.7
>
> Other background:  Due to historical issues with mail folders (that,
> no surprise, have to do with UW-IMAP), we've created several
> namespaces in dovecot.  The default namespace, with no prefix, points
> to "$HOME/mail".  Then there are additional hidden namespaces, one of
> which, to provide backward compatibility in certain situations uses
> the prefix "mail/" and also points to "$HOME/mail".  So, right now,
> when IMP does it's NAMESPACE command, it gets back:
> * NAMESPACE (("" "/")) NIL NIL
>
> Problem description
> Ingo is set to use the IMP folder api, which appears to work right.
> That is, when I go to set up a new rule, and choose "Deliver to
> folder..." as the "Do this:" action, up pops a list of target folders
> (which live in $HOME/mail).
>
> But then, when I select a folder (cron for instance), and save the
> rule, the resulting procmail script shows the destination as only
> "cron" when it ought to say "mail/cron".
>
> Interestingly, if I specify a namespace in my IMP servers.php with:
> 'namespace' => array('mail/')
> when I go through ingo action to "Deliver to folder" the drop-down now
> shows the list of folders from the default, and then, in the middle
> where the "m"s are, there's a greyed out line that says "mail" and all
> the folders listed again, but slightly indented.  If I chose the
> indented "cron", ingo now points the procmail action toward
(Continue reading)

Permalink | Reply | 1 comment |

Gmane