On 10/06/2020 20:47, Miguel Mucio Santos Moreira wrote:
> Wolfgang,
>
> If you don't mind, I'd like to know if when you upgraded backend servers
> from 2.4 version to 2.5 version you have an increase, in metadata size.Here
> we had 30% around of increase
Yes, cyrus.* are larger. Not sure about .ca
Miguel,
That's perfectly normal, and I think it's even covered in the release
notes... Nope, I'm wrong, the release notes mention the larger Memory
footprint, due to more data and metadata being cached in memory. But
the on-disk size increases, too, as there is more information being held
in
Wolfgang,
If you don't mind, I'd like to know if when you upgraded backend servers from
2.4 version to 2.5 version you have an increase, in metadata size.Here we had
30% around of increase
Thanks one more time
Greetings
--
Miguel Moreira
DTE/SRE/GRE - Gerência de Redes
+55(31)3339-1401
PRODE
Wolfgang,
I'm sure your help and experience with Cyrus Murder upgrading will save a lot
of time and reduce the possibility of an eventual problem during the upgrade.
Thankful
--
Miguel Moreira
DTE/SRE/GRE - Gerência de Redes
+55(31)3339-1401
PRODEMGE - Companhia de Tecnologia da Infor
Hi!
On 09/06/2020 14:56, Miguel Mucio Santos Moreira wrote:
> Dear Wolfgang,
>
> Firstly thanks for your answer, secondly I have one more doubt, during this
> time where the new Mupdate Master is receiving mailboxes information from
> backend servers, is necessary stopping comunications between fr
Dear Wolfgang,
Firstly thanks for your answer, secondly I have one more doubt, during this
time where the new Mupdate Master is receiving mailboxes information from
backend servers, is necessary stopping comunications between frontend servers
and mupdate master or none action is necessary besi
On 08/06/2020 17:37, Miguel Mucio Santos Moreira wrote:
> Now we're in doubt about how is the best solution to replace the mupdate
> master server for a new one.
> Nowadays we have around 16K mailboxes.
IIRC we simply replaced the mupdate server and did a "ctl_mboxlist -m" on
all backends to fill
Hello guys!
We have a cyrus murder environment with cyrus 2.4 version, according to cyrus
documentation we should upgrade backend servers, mupdate master and for last
frontend servers.
Following this recommendantions we've installed new backend servers, with 2.5
version, joined them t
some
experience in horizontal scaling (backend or mailbox server clustering),
because live moving mailboxes without interruption or in the most possible easy
way (just as examples), are important things to know before writing all the
automation stuff… knowing if a Cyrus Murder could failover from
because it’s really something that
could cause problems to the mailbox (we do it this way always, as a procedure
for avoiding problems, but is it really needed??). I’m in the process of
automating this kind of operation, but reading some info before writing code, I
have seen that Cyrus murder allows
n via Info-cyrus wrote:
> Hi!
>
> Does http proxy work in a cyrus murder environment? I keep getting ""PUT
> /dav/addressbooks/user/testuser/6ecc0a66-74a1412-1581679269354-210887/ef37977290d43113e709f68848aa9a8a5ff8a24f.vcf
> HTTP/1.1" (if-none-match=*) => "H
On 2020-02-17 12:17, Khalid Mehmood Khan via Info-cyrus wrote:
> Hi!
>
> Does http proxy work in a cyrus murder environment? I keep getting ""PUT
> /dav/addressbooks/user/testuser/6ecc0a66-74a1412-1581679269354-210887/ef37977290d43113e709f68848aa9a8a5ff8a24f.vcf
>
Hi!
Does http proxy work in a cyrus murder environment? I keep getting ""PUT
/dav/addressbooks/user/testuser/6ecc0a66-74a1412-1581679269354-210887/ef37977290d43113e709f68848aa9a8a5ff8a24f.vcf
HTTP/1.1" (if-none-match=*) => "HTTP/1.1 403 Forbidden"" on the front
Hello,
we actually use Cyrus2.3.11 with the patch autocreate.
We plan to migrate to Cyrus3.0.8, patch is included, we also plan to use
a murder to share loads between several frontends.
I'm now testing autocreation through a frontend and new mailboxes are
always created on the frontend, not t
mail: />>>>>>>>/michael.menge at zdv.uni-tuebingen.de
<https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus> />>>>>>>>/Wächterstraße 76 />>>>>>>>/72074 Tübingen />>>>>>>//>>>>>>>//>&
Michael Menge via Info-cyrus wrote on 15/11/16 17:08:
> Thanks for the info, we are also still running cyrus 2.4 on our
> production environment.
> But mostly because that was the stable version at the time we migrated
> from stand alone
> to murder setup and the "never touch a running system"
Hi,
Quoting Wolfgang Breyha via Info-cyrus :
Michael Menge via Info-cyrus wrote on 07/11/16 10:30:
Quoting Alberto Cardenas via Info-cyrus :
I'm trying to setup Cyrus Murder for testing and have three virtual
machines for this purpose (frontend, mupdate and backend). The three
machine
convert my existing Cyrus 2.2 ( Debian v6 ) to Cyrus 2.4 ( Debian v8 )
but will be down around 8 ( at least ) for the two debian upgrades and
converting 200gig of Cyrus 2.2 mail to Cyrus 2.4 - indexes and what not.
I was thinking.. maybe another approach would be to setup Cyrus Murder ( 2.2
) on my
( Debian
v8 ) but will be down around 8 ( at least ) for the two debian upgrades
and converting 200gig of Cyrus 2.2 mail to Cyrus 2.4 - indexes and what not.
I was thinking.. maybe another approach would be to setup Cyrus Murder (
2.2 ) on my existing Cyrus 2.2 box and connect it up with a new Cyrus
On 07/28/15 16:37 +, Forster, Gabriel wrote:
>mupdatetest and testsaslauthd checks seem to work fine. But, when trying
>to create a user account using the command-line cyradm tools, from the
>backend, I'm getting the following error:
>
>cyradm -t "" -u kolab -w "${password}" ${cyrus_host}
>
>>
On 07/28/15 16:37 +, Forster, Gabriel wrote:
>Hello,
>
>This was asked in the Kolab list, but they mentioned this list may be more
>appropriate:
>
>Trying to get Kolab 3.4 setup in a distrubuted environment. The last piece of
>the puzzle seems to be getting Cyrus configured correctly for a mu
On 07/28/15 16:37 +, Forster, Gabriel wrote:
>Hello,
>
>This was asked in the Kolab list, but they mentioned this list may be more
>appropriate:
>
>Trying to get Kolab 3.4 setup in a distrubuted environment. The last piece of
>the puzzle seems to be getting Cyrus configured correctly for a mu
Hello,
This was asked in the Kolab list, but they mentioned this list may be more
appropriate:
Trying to get Kolab 3.4 setup in a distrubuted environment. The last piece of
the puzzle seems to be getting Cyrus configured correctly for a murder
environement. Currently, only using 1 frontend and
Quoting Michael Menge :
If you give me some other names, I might be able to see why...
I will send the to you and not to the list, as some names may contain
non public informations.
on closer inspection one other case proved to be a race condition
in sync_client. Sync_client tried to sync a
Quoting Bron Gondwana :
Since the migration we discovered some small issues and some bugs.
1. usually Cyrus is not CPU bound. One exception is the mupdate master
keeping encrypted connection to all frontends and establishing
new encrypted connections from the backend for every mailbox c
.
Cheers,
-nic
On 09/22/2014 06:20 AM, Michael Menge wrote:
Hi,
3 weeks ago we changed our changed cyrus imap servers form stand
alone systems to a cyrus murder cluster. We have ~44000 accounts,
~457000 Mailboxes, and 2x6.5 TB Mails
In our previos setup we had 6 cyrus imap 2.4.17 servers
On Mon, Sep 22, 2014, at 09:20 PM, Michael Menge wrote:
> Hi,
>
> 3 weeks ago we changed our changed cyrus imap servers form stand
> alone systems to a cyrus murder cluster. We have ~44000 accounts,
> ~457000 Mailboxes, and 2x6.5 TB Mails
>
> In our previos setup we ha
Hi,
3 weeks ago we changed our changed cyrus imap servers form stand
alone systems to a cyrus murder cluster. We have ~44000 accounts,
~457000 Mailboxes, and 2x6.5 TB Mails
In our previos setup we had 6 cyrus imap 2.4.17 servers running as KVM
VMs with 8 GB memory and 4 Cores each, on an HP
Hi!
Peter Bücker wrote, on 23/07/13 16:33:
> Hi all,
>
> We're having an issue with our Cyrus Murder environment when moving
> mailboxes from one backend to another backend. Some mails are left
> behind on the source server while we think they should be removed. We
> is
Hi all,
We're having an issue with our Cyrus Murder environment when moving
mailboxes from one backend to another backend. Some mails are left
behind on the source server while we think they should be removed. We
issue the rename by using "cyradm" on the source server with
e end.
When I have setup I have not addede the : and this was the problem.
Best regards.
On 31/08/12 11:00, "[SOLTECSIS] Carles Xavier Munyoz Baldó" wrote:
> Hi,
> I have installed Cyrus and Cyrus Murder using the precompiled packages
> included in Ubuntu 12:
> cyrus-i
Hi,
I have installed Cyrus and Cyrus Murder using the precompiled packages
included in Ubuntu 12:
cyrus-imapd-2.4
cyrus-murder-2.4
I'm trying to setup a Cyrus Murder but when I setup the next
configuration options in my Cyrus backend servers:
mupdate_server
mupdate_port
mupdate_username
I make some tests and find problems moving mailboxes with users online:
( Cyrus 2.4.8 )
Move with
RENAME user/lucas.carraro user/lucas.carraro server2.prevnet!default
In frontends and backends:
.
allowusermoves: 1
disconnect_on_vanished_mailbox: 1
When i move from server1!de
On 5/12/11 7:06 PM, Lucas Zinato Carraro wrote:
>
> I can move mailboxes between servers with a user connected ?
Generally, yes, but I'm not 100% sure that there aren't edge cases.
Actually, I'm going to assume that there are probably edge cases. Also,
newer versions should be somewhat better
I can move mailboxes between servers with a user connected ?
Exist a way to block the connection until the operation finish ?
Regards
Zinato
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Hi,
Quoting Andrew Morgan :
On Tue, 22 Mar 2011, Milos Zupancic wrote:
Hi,
I have a general question if this setup is an option.
We have a cyrus murder setup with 2 backends, 1 mupdate, and 2 frontservers
(servers are within our LAN). Everything is working as it should.
For external mail
On Tue, 22 Mar 2011, Milos Zupancic wrote:
> Hi,
>
> I have a general question if this setup is an option.
> We have a cyrus murder setup with 2 backends, 1 mupdate, and 2 frontservers
> (servers are within our LAN). Everything is working as it should.
> For external mail a
Hi,
I have a general question if this setup is an option.
We have a cyrus murder setup with 2 backends, 1 mupdate, and 2 frontservers
(servers are within our LAN). Everything is working as it should.
For external mail access we atm use a webmail solution.
Some of our employees would still like to
On Wed, Mar 09, 2011 at 02:58:21PM -0300, Lucas Zinato Carraro wrote:
> The parameter "autocreatequota" works in a Murder enviromment ?
> INBOX is created in user logon ?
I believe it should, but I haven't integrated the patches, so you'll need
to test it yourself - it will still be a distro patc
The parameter "autocreatequota" works in a Murder enviromment ?
INBOX is created in user logon ?
My imapd.conf
...
defaultpartition: default
defaultserver: back1.com
serverlist back1.com back2.com back3.com
..
With this configuration INBOX will be created in back1.com!default
Hello,
I have been testing a cyrus murder/aggregator setup on Debian Lenny.
After some ddd debugging sessions I found the need for 3 patches at Debian cyrus
2.3.16 "hmh" branch in order to frontend honor the "serverlist" and
"defaultserver" options when working in a
On Mon, 30 Aug 2010, Andre Felipe Machado wrote:
> I already tried to setup parameters for creating mailboxes on the backend with
> most free available space when no partition is specified, following imapd.conf
> man page.
> The source code uses some conditions to achieve this, like for example:
>
Hello,
I already tried to setup parameters for creating mailboxes on the backend with
most free available space when no partition is specified, following imapd.conf
man page.
The source code uses some conditions to achieve this, like for example:
IMAP_ENUM_MUPDATE_CONFIG_STANDARD (== 0 as enumerate
I need to create a program to manage users in OpenLDAP
and Cyrus Mailboxes ( Aggregation ).
Search in internet i found examples in PHP using IMAP functions and Cyrus.
I find some examples using:
imap_set_quota, imap_mailboxmsginfo, imap_setacl, imap_status,
imap_getacl, imap_get_quota
I dont
ote:
>
> On Fri, Jun 4, 2010 at 3:55 PM, Dan White wrote:
>>
>> On 04/06/10 09:35 +0200, Milos Zupancic wrote:
>>>
>>> Hi,
>>>>
>>>> I'm trying to set up cyrus murder test environment, i have followed
>>>> instructions fr
On Tue, 8 Jun 2010, Milos Zupancic wrote:
> On Fri, Jun 4, 2010 at 3:55 PM, Dan White wrote:
>
>> On 04/06/10 09:35 +0200, Milos Zupancic wrote:
>>
>>> Hi,
>>>
>>> I'm trying to set up cyrus murder test environment, i have followed
>>> i
On Fri, Jun 4, 2010 at 3:55 PM, Dan White wrote:
> On 04/06/10 09:35 +0200, Milos Zupancic wrote:
>
>> Hi,
>>
>> I'm trying to set up cyrus murder test environment, i have followed
>> instructions from http://cyrusimap.web.cmu.edu/imapd/install-murder.html
>
On 04/06/10 09:35 +0200, Milos Zupancic wrote:
>Hi,
>
>I'm trying to set up cyrus murder test environment, i have followed
>instructions from http://cyrusimap.web.cmu.edu/imapd/install-murder.html
>and some web resources.
>
>When i try to start everything up i get the f
gt; >
> > > Milos Zupancic , wrote/schrieb/писав:
> > > > Hi,
> > > >
> > > > I'm trying to set up cyrus murder test environment, i have followed
> > > > instructions from
> http://cyrusimap.web.cmu.edu/imapd/install-murder.html
&g
2010/6/4 Michael Zanin
> Milos Zupancic , wrote/schrieb/писав:
> > Hi,
> >
> > I'm trying to set up cyrus murder test environment, i have followed
> > instructions from http://cyrusimap.web.cmu.edu/imapd/install-murder.html
> > and some web resources.
>
Hi,
I'm trying to set up cyrus murder test environment, i have followed
instructions from http://cyrusimap.web.cmu.edu/imapd/install-murder.html
and some web resources.
When i try to start everything up i get the following errors on backend and
frontend servers.
I can connect to frontend w
Hi Wesley,
Thank you for your info.
It gives me a clearer idea how it works.
The multiple front-ends with the imap aggregator would give a huge
advantage for expanding when more resources are needed, so this is an
option i would like to use.
The only issue i can think of is backups of the mailbox
On 10 Feb 2010, at 16:54, Richard Pijnenburg wrote:
> How do the backends deceide who services which mailbox?
>
The admin decides, more or less, as you provision mailboxes.
> And what happens if one of those backends dies?
>
The mailboxes on that backend are inaccessible. The rest of the
clus
Hi all,
I'm busy thinking about a new mail server setup for my work.
Most of the stuff I've figured out but I don't completely understand Cyrus
murder application.
>From what I understand is that the front-end servers serve the imap/pop3
requests.
These servers conne
--On Wednesday, February 3, 2010 9:26 -0800 Andrew Morgan
wrote:
> On Wed, 3 Feb 2010, Carlos Ricardo Bernal Veiga wrote:
>
>> Ohhh Thank you Dan, this parameter worked really good in our Webmail,
>> and so sorry for my english, We are studying the cyrus murder to deploy
>
On Wed, 3 Feb 2010, Carlos Ricardo Bernal Veiga wrote:
> Ohhh Thank you Dan, this parameter worked really good in our Webmail, and so
> sorry for my english, We are studying the cyrus murder to deploy in our
> company, do you know about some success case with murder?? We have about
Ohhh Thank you Dan, this parameter worked really good in our Webmail, and so
sorry for my english, We are studying the cyrus murder to deploy in our
company, do you know about some success case with murder?? We have about
seventy thousand accounts and we want know more about this project
On 02/02/10 18:30 -0300, Carlos Ricardo Bernal Veiga wrote:
>I am prospecting the Cyrus Murder with 1 frontend, 1 mupdate and 3 backends,
>the environment is almost all in full operation, I already create, alter,
>delete, and modify the mailboxes by the frontend, I have tested it with
&
Good afternoon list
I am prospecting the Cyrus Murder with 1 frontend, 1 mupdate and 3 backends,
the environment is almost all in full operation, I already create, alter,
delete, and modify the mailboxes by the frontend, I have tested it with
Evolution (worked OK), ThunderBird (worked OK too
On 20 Aug 2009, at 19:03, Alexander wrote:
> Also, I see that there is a warning at the beginning of the document
> about "Murder is still relatively young". Is this still the case, or
> is this just a leftover warning from years ago? Can it be considered
> reasonably stable and ready for usage?
Hello All,
I've inherited a working Cyrus installation (a pair of servers behind
a Perdition proxy), and I'd like to modify the existing setup to make
use of the Cyrus Murder.
I've found the following documentation:
http://cyrusimap.web.cmu.edu/imapd/install-murder.html
But
On Mon, 28 Jul 2008, UnlimitedMail.net - Carles Xavier Munyoz Baldó wrote:
Hello,
I'm thinking about to use the Cyrus Murder in order to setup an e-mail IMAP
cluster system. The problem is that I have seen this note on the
install-murder text file:
[...]
Note that Cyrus Murder is
On 28 Jul 2008, at 08:14, UnlimitedMail.net - Carles Xavier Munyoz
Baldó wrote:
> Note that Cyrus Murder is still relatively young in the grand
> scheme of
> things, and if you choose to deploy you are doing so at your
> own risk.
That text is from 2002. Yes, Cyr
On Mon, 28 Jul 2008 08:14:21 -0500 (CDT)
"Chris St. Pierre" <[EMAIL PROTECTED]> wrote:
> On Mon, 28 Jul 2008, UnlimitedMail.net - Carles Xavier Munyoz Bald__ wrote:
> > What I'm losing if I use an IMAP proxy instead of Cyrus Murder?
You are losing a bunch of
On Mon, 28 Jul 2008, UnlimitedMail.net - Carles Xavier Munyoz Baldó wrote:
Then, for a production system, should I use an IMAP proxy solution instead of
Cyrus Murder?
Is there anyone using Cyrus Murder in a hevay loaded production e-mail system?
May you recomend me an IMAP proxy?
What I&#
Hello,
I'm thinking about to use the Cyrus Murder in order to setup an e-mail IMAP
cluster system. The problem is that I have seen this note on the
install-murder text file:
[...]
Note that Cyrus Murder is still relatively young in the grand scheme of
things, and if you choose to d
Hello all.
I must conclude that all "combined" configurations of Cyrus Murder
servers do not work. Or, more exactly, I did not manage to make them
work despite of many hours of tests and meditation.
"frontend+backend" combination (aka "config: unified") seems
Hi,
i transferred my murder installation to x64 machines, I had everything
running in some VM machines!
When I now start my murder, nothing seems to work.
On my mupdate serber it looks like it tries to use pam, but I just
configured it to use
the sasldb
Feb 2 17:21:40 mupdater-A1 saslauthd[25
Hi all
02.01.2008 11:58, Janne Peltonen пишет:
> On Fri, Dec 21, 2007 at 02:04:26PM +0100, Michael Menge wrote:
>> Hi,
>>
>> i don't know if it's possible with Cyrus 2.2, but it is with 2.3,
>> look for unified murder
I met the following fatal problem with "unified" mode: "ctl_mboxlist -m"
is n
i think my mainproblem is that i only can connect with a clientto the server
when i disable digest-md5,
but when I disable digest-md5 the mupdater cant connect anymore to the
master.
how can I solve this?
thx
On Jan 11, 2008 4:37 PM, rupert <[EMAIL PROTECTED]> wrote:
> On Jan 11, 2008 4:12 PM,
On Jan 11, 2008 4:12 PM, Olaf Fraczyk <[EMAIL PROTECTED]> wrote:
> On Fri, 2008-01-11 at 13:27 +, rupert wrote:
> > > > So how can I proceed?
> > > >
> > > Toplevel mailboxes MUST be created on the backend.
> > >
> > >
> > >
> > you mean
On Fri, 2008-01-11 at 13:27 +, rupert wrote:
> > > So how can I proceed?
> > >
> > Toplevel mailboxes MUST be created on the backend.
> >
> >
> >
> you mean like "ralf", well i tried "user.ralf" and it still
> does not wo
If you want to use PAM (via saslauthd), then you shouldn't have to use
saslpasswd2. Like I said earlier, unless your IMAP client can do
referrals, you only need the user credentials on the frontends.
If you're trying to delete a toplevel mailbox, you need to give the
admin the 'c' right before
rupert wrote:
> another questions is:
> does the mysql database have to be on both machines or does the frontend
> cyrus get its data from the backend and doesnt store anything inside its
> local DB?
What MySQL database? For authentication? All user credentials need to
be verified on the front
i followed some howtos on the net and provides wit cyrus,
it uses pam to store some stuff in a mysql 5.1 DB.
i can only login with imtest when i create the user I created with
saslpasswd2 and "cm user.*" also create this user in the DB,
which was installed during the web-cyradmin installation.
Do
-- Forwarded message --
From: rupert <[EMAIL PROTECTED]>
Date: Jan 11, 2008 1:15 PM
Subject: Re: cyrus murder and some unclear things(cant create mailbox from
frontend)
To: Ken Murchison <[EMAIL PROTECTED]>
another questions is:
does the mysql database have to be on b
Hello first,
I was able to set up an murder cluster with one backend and a frontend which
also acts as a mupdate server.
i could get the mailbox accounts from the backend, which was a standalone
before.
I read that now the murder is running i should "only" create accounts on the
frontend and dont d
rupert wrote:
> Hello first,
> I was able to set up an murder cluster with one backend and a frontend
> which also acts as a mupdate server.
> i could get the mailbox accounts from the backend, which was a
> standalone before.
> I read that now the murder is running i should "only" create account
as was copying messages
the other way round. (Copying messages between local folders or between
remote folders did work.)
--Janne Peltonen
University of Helsinki
>
> Quoting Ingo Steuwer <[EMAIL PROTECTED]>:
>
> > Hi
> >
> > I'm evaluating cyrus-murder with
Hi,
i don't know if it's possible with Cyrus 2.2, but it is with 2.3,
look for unified murder
Quoting Ingo Steuwer <[EMAIL PROTECTED]>:
> Hi
>
> I'm evaluating cyrus-murder with cyrus 2.2 (sources from debian etch) using
> the documentation from http://cy
Hi
I'm evaluating cyrus-murder with cyrus 2.2 (sources from debian etch) using
the documentation from http://cyrusimap.web.cmu.edu/imapd/install-murder.html
and the twiki. Thanks to the good documentation the setup of some basic
functionality was straight forward.
I'd like to have t
>> I have installed cyrus-imap-2.2, cyrus_murder-2.2, cyrus-admin-2.2,
>> cyrus-pop3d-2.2, sasl2-bin, libhtml-parser-, cyrus-clients-2.2,
>> libsasl2-modules on a debian etch 32bit.
>>
>> Mupdate works fine and the backend servers too. On the front end I can
login
>> (which is as I understand is d
On Wed, 5 Dec 2007, Frank Purmann wrote:
> I have installed cyrus-imap-2.2, cyrus_murder-2.2, cyrus-admin-2.2,
> cyrus-pop3d-2.2, sasl2-bin, libhtml-parser-, cyrus-clients-2.2,
> libsasl2-modules on a debian etch 32bit.
>
> Mupdate works fine and the backend servers too. On the front end I can log
I have installed cyrus-imap-2.2, cyrus_murder-2.2, cyrus-admin-2.2,
cyrus-pop3d-2.2, sasl2-bin, libhtml-parser-, cyrus-clients-2.2,
libsasl2-modules on a debian etch 32bit.
Mupdate works fine and the backend servers too. On the front end I can login
(which is as I understand is done locally) bu
Hi,
Just testing cyrus-murder in our lab with 1 mc each of frontend, backend, master
when I send mails to the frontend box this is what I get.
Nov 22 17:26:39 location postfix/lmtp[18284]: 2DE2E11E5C6:
to=<[EMAIL PROTECTED]>, relay=none, delay=2.9,
delays=2.9/0.01/0.01/0, dsn=4.4.1,
reply to RCPT TO command))
Now we have cyrus murder configuration and those mails are not bounced
by frontend server, instead they are queued on postfix server with
following error:
relay=xxx:24, delay=259650, delays=259650/0.05/0.02/0, dsn=4.4.2,
status=deferred (lost connection with xxx while
2.3.7 on frontend and one backend (RedHat 5) and 2.3.9 on the other
backend (freebsd 6.1).
Most of errors are between frontend (imap2) and freebsd backend
(imap-old) and protocol is pop3:
Oct 25 20:37:30 imap2 pop3[12945]: connect(imap-old.amis.net) failed:
Connection timed out
Oct 25 20:37:30
On Thu, Oct 25, 2007 at 10:38:01AM -0400, Ken Murchison wrote:
> Vladimir Nikolic wrote:
> >
> > I have questions regarding murder scalability. Untill last week we had
> > one imap server with about 5 users and 2TB mailboxes. Server was
> > overloaded and little slow but there was no trouble
Vladimir Nikolic wrote:
> Hi,
>
> I have questions regarding murder scalability. Untill last week we had
> one imap server with about 5 users and 2TB mailboxes. Server was
> overloaded and little slow but there was no troubles like connections
> drop and repeatedly asking users for password
Hi,
I have questions regarding murder scalability. Untill last week we had
one imap server with about 5 users and 2TB mailboxes. Server was
overloaded and little slow but there was no troubles like connections
drop and repeatedly asking users for password.
Now we have that old server and th
Hi,
I have the following cyrus murder configuration:
frontend - cyrus-2.3.7 on RHEL 5
murder server - cyrus-2.3.8 on FreeBSD 6.2
backends - cyrus-2.3.7 on FreeBSD 6.1 and cyrus-2.3.7 on RHEL 5
There are somewhere about 5 users (4 on FreeBSD and 1 on RHEL).
POP3 users are complaining
Hi,
the main advantages of murder over perdition are the following
1. user can share/access folders across servers
2. you can move users form one server to an other very easy
this comes with the disadvantage that you depend on the mupdate-server
Quoting ram <[EMAIL PROTECTED]>:
> http://cyrus
http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/CyrusCluster
shows different clusters. I have got perdition working , but that is
purely for loadbalancing
I havent tried murder yet , but on the face of it seems same as
perdition in the features
Thanks
Ram
Cyrus Home Page: http://cy
ion is done via
saslauthd->pam->pam_mysql.so.
cyrus.conf looks like that:
SERVICES {
mupdate cmd="/usr/lib/cyrus-imapd/mupdate -m"
listen=3905 prefork=1
}
imapd.conf:
configdirectory: /var/lib/imap
partition-default: /tmp
mupdate_config: standard
mupdate_adm
yrus kxa
setaclmailbox user.seltani cyrus kxa
setaclmailbox user.serre cyrus kxa
setaclmailbox user.solers cyrus kxa
...[400 accounts]...
I then feed the script to cyradm. But after 10 lines, the execution
suddenly slows down to a crawl, and only one "setaclmailbox" every 10 or
20 seconds
setaclmailbox user.solers cyrus kxa
...[400 accounts]...
I then feed the script to cyradm. But after 10 lines, the execution
suddenly slows down to a crawl, and only one "setaclmailbox" every 10 or
20 seconds is executed.
I'm running a unified cyrus murder 2.3.7, with 2 imap server
On Wednesday 14 June 2006 12:31, [EMAIL PROTECTED] wrote:
> Quoting Greg Boug <[EMAIL PROTECTED]>:
> > Hi guys,
> >
> > I'm looking to implement a murder of imap daemons, but not all of
> > them are
> > going to be heavily loaded. I'm attempting to set the system up
> > using
> > multiple servers
Quoting Greg Boug <[EMAIL PROTECTED]>:
> Hi guys,
>
> I'm looking to implement a murder of imap daemons, but not all of
> them are
> going to be heavily loaded. I'm attempting to set the system up
> using
> multiple servers acting as both a front and back end. Ie. they
> are both
> running proxyd
Hi guys,
I'm looking to implement a murder of imap daemons, but not all of them are
going to be heavily loaded. I'm attempting to set the system up using
multiple servers acting as both a front and back end. Ie. they are both
running proxyd and imapd.
My question is, is this possible? I am pu
On Fri, 2006-05-19 at 13:13 +0200, Mirosław Jaworski wrote:
> Problems:
> - mupdate eating cpu
Update: seems that prot.c ( 1.82.2.13 ) patch made the day
for me ( concerning mupdate eating cpu time ).
Still have the problem with synchronizing mailboxes.db
between nodes though.
How often slave m
1 - 100 of 232 matches
Mail list logo
