Kenneth,
Thanks for the reply. That was helpful. I guess what I don't understand is
how to know where to put information, and lookup information. I'm not really a
PHP programmer, so its not always easy for me to look and see what is going on
easily. So you just modified the SmartSieve.lib ins
On Fri, May 15, 2009 at 10:05:06AM -0400, Gottschalk, David wrote:
> I'm in the process of setting up smartsieve now, but I'm wondering how to
> write a hook for login details.
>
> I see the sample in the conf.php, but I don't entirely understand what is
> going on or how to write my own. I'd li
I'm in the process of setting up smartsieve now, but I'm wondering how to write
a hook for login details.
I see the sample in the conf.php, but I don't entirely understand what is going
on or how to write my own. I'd like to have a hook that authenticates username
and password against ldap, and
On Fri, May 15, 2009 1:15 pm, John McMonagle wrote:
> Did a test and it appears that the acls are defined in the cyrus.header
> files.
>
> For example:
> Cyrus mailbox header
> "The best thing about this system was that it had lots of goals."
> --Jim Morris on Andrew
> advocap.org!user.test 151
Working on migrating our debian sarge cyrus mail to kolab 2.2.1.
That would be cyrus 2.1.18 to cyrus 2.3.13.
The problem is in the old cyrus users are specified as userid the new is
use...@domain.
I'll summarize what I have done.
With new cyrus stopped.
I copied the mail spool over to the corr
