Steffen Kaiser writes:
My statement is simply my point of view, that the API should be independed
of the backend.
LDAP, Postgresql, Mysql.. I think any of them is fine.
I think anything BUT the initial setup that Timo mentioned. Files in
the mailstore I think is the least scalable option.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 22 Apr 2007, Francisco Reyes wrote:
Well, this statement is true for any backend, incl. LDAP.
Correct.
But many companies do not have a LDAP infrastructure.
It is much easier to setup a Mysql DB and put a table for ACL than it is to
setup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 22 Apr 2007 17:49:52 -0400 [EMAIL PROTECTED] wrote:
> Steffen Kaiser writes:
>
> >> Having ACLs in SQL allows companies to have a centralized place
> >> for all ACLs.
> >
> > Well, this statement is true for any backend, incl. LDAP.
>
> C
Steffen Kaiser writes:
Having ACLs in SQL allows companies to have a centralized place for all ACLs.
Well, this statement is true for any backend, incl. LDAP.
Correct.
But many companies do not have a LDAP infrastructure.
It is much easier to setup a Mysql DB and put a table for ACL than it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 11 Apr 2007, Francisco Reyes wrote:
Having ACLs in SQL allows companies to have a centralized place for all ACLs.
Well, this statement is true for any backend, incl. LDAP.
Bye,
- --
Steffen Kaiser
-BEGIN PGP SIGNATURE-
Version:
Timo Sirainen writes:
Keeping ACLs in SQL is different from keeping the whole mailbox data
in SQL. Currently the ACL plugin supports only vfile backend, but it
wouldn't be too difficult to add support for SQL backend.
Having ACLs in SQL allows companies to have a centralized place for all
Timo Sirainen wrote:
I think I'll also add a check to compare Maildir, new, cur and tmp
directories' permissions and log a warning if they're not the same.
Just as a sanity check, mine differ (for whatever reason - I probably
used 'maildirmake' from Courier) like so:
$ ls -gGld SpamTraining
One more thing:
I think dovecot-shared file is pointless. It can be implemented by
taking the rw-permissions from the Maildir directory (or mbox file).
Only problem that I see is if Maildir unintentionally has too wide
permissions, this change would make the created mails have too wide
permission
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timo Sirainen schrieb:
> On 8.4.2007, at 1.04, Robert Schetterer wrote:
>
>> Timo Sirainen schrieb:
>>> On 7.4.2007, at 14.31, Robert Schetterer wrote:
for acl public folders with virtual domains, wouldnt it be a good idea
to have them in sq
On 8.4.2007, at 1.04, Robert Schetterer wrote:
Timo Sirainen schrieb:
On 7.4.2007, at 14.31, Robert Schetterer wrote:
for acl public folders with virtual domains, wouldnt it be a good
idea
to have them in sql as backend?
Why?
Hi Timo,
as imap clients that are able to edit imap acls are rar
Timo Sirainen schrieb:
On 7.4.2007, at 14.31, Robert Schetterer wrote:
for acl public folders with virtual domains, wouldnt it be a good idea
to have them in sql as backend?
Why?
Hi Timo,
as imap clients that are able to edit imap acls are rare
( thunderbird, Outlook cant do it yet i think )
On 7.4.2007, at 19.02, Troy Engel wrote:
What I was finding with testers is that each person's login process
was rewriting permissions on the subscriptions file and the index
files didn't work out for the same reason; 1 person would drop an
email into a subfolder ("MissedSpam" e.g.), Doveco
Timo Sirainen wrote:
If ACL plugin isn't loaded, I suppose the mailboxes can be accessed if
the process has filesystem permissions to access them.
Kind of, but it doesn't really work in real life. I tried setting it up
initially around... say 1.0rc23 and it runs into permissions problems
wr
On 7.4.2007, at 14.31, Robert Schetterer wrote:
for acl public folders with virtual domains, wouldnt it be a good idea
to have them in sql as backend?
Why?
PGP.sig
Description: This is a digitally signed message part
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timo Sirainen schrieb:
> ** Configuration **
>
> namespace shared {
> prefix = user/%u/
> location = maildir:/home/%u/Maildir:INDEX=~/Maildir/shared-indexes
> }
>
> So the only difference to how it's configured now is that %u is expanded
> to wha
** Configuration **
namespace shared {
prefix = user/%u/
location = maildir:/home/%u/Maildir:INDEX=~/Maildir/shared-indexes
}
So the only difference to how it's configured now is that %u is
expanded to whatever user whose mailboxes we're accessing. ACL plugin
then uses that user as the o
16 matches
Mail list logo
