--- Jim Levie <[EMAIL PROTECTED]> wrote:
> I'd agree with that in ordinary mail environment,
> but not necessarily at
> an ISP. In my experience there's significantly more
> work & training
> involved with the account management part than just
> server setup.
> Changing from a single server to an
--- Rob Siemborski <[EMAIL PROTECTED]> wrote:
> At the time that the document to which you refer was
> written, it had
> also received substantially more testing, this is
> not really the case any
> longer.
You mean that documentation is a bit outdated nowadays
?
> 200 mailboxes is nothing.
--- Earl R Shannon <[EMAIL PROTECTED]> wrote:
> Well, the uniform name space means a couple of
> things. First, each
> user's account has a unique name. Not just on the
> IMAP server where
> their account resides, but across all the IMAP
> servers that are part
> of the MURDER. This allows the a
Hi there,
I was reading the latest Cyrus IMAPd 2.2.6 documentation especially this page:
http://asg.web.cmu.edu/cyrus/download/imapd/install-murder.html
Now I saw the following phrase:
"Sites which think they need the Murder functionality but do not need a uniform namespace (no shared mailb
--- Rob Siemborski <[EMAIL PROTECTED]> wrote:
> That, and it ensures that you have exactly the same
> configuration running
> on all the systems.
Speaking about configuration, I was wondering if there
is any sample configuration files (cyrus.conf and
imapd.conf) for a basic or recommended Cyrus I
--- Rob Siemborski <[EMAIL PROTECTED]> wrote:
> Again, I think you should only build it once per
> architechure you are
> running on, not once per server.
Is there any special reasons for that except the
administrative hassle to compile cyrus again and again
?
So you would suggest me to simply
--- Ken Murchison <[EMAIL PROTECTED]> wrote:
> Greg Pulfer wrote:
> Hmm. The Wiki needs to be updated to discuss 2.2.3
> and later.
That's always good to know ;)
> Depends on the Cyrus version. If using 2.2.3 or
> later, the database
> backends are configured at
--- Rob Siemborski <[EMAIL PROTECTED]> wrote:
> This is definately the way to go. It also means you
> only need to build
> cyrus once (per architechure).
Hmm now I was wondering what about all the
--with-duplcate-db, --with-mboxlist-db,
--with-seen-db, --with-subs-db and such which are
recommend
Hello,
I would like to install a frontend server for our
future Cyrus MURDER mail architecture. If I understood
correctly the Cyrus MURDER/Aggregation , I will need
to compile Cyrus also on my frontend server... Now I
think I don't need the full blown with all options
Cyrus IMAP on the frontend se
