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
Hi,
I'm always stucked in configuring a murder cluster for Cyrus HTTP.
Is it possible to disable http on both backend and frontend, and only
use https ?
I have tried with only entries https in cyrus.conf on both
backend/frontend and I notice connexion refused from the frontend.
imap
On 4/2/19 7:15 PM, Ken Murchison wrote:
>
> On 4/2/19 1:02 PM, Jean-Christophe Delaye wrote:
>> Hello,
>>
>> We're testing Cyrus3.0.9 in a murder configuration.
>> It works fine for imap/imaps services. I can access mailboxes from
>> differents fronte
On 4/2/19 1:02 PM, Jean-Christophe Delaye wrote:
Hello,
We're testing Cyrus3.0.9 in a murder configuration.
It works fine for imap/imaps services. I can access mailboxes from
differents frontend, and move mailboxes from on backend to another !
I'm now blocked with the calendar f
Hello,
We're testing Cyrus3.0.9 in a murder configuration.
It works fine for imap/imaps services. I can access mailboxes from
differents frontend, and move mailboxes from on backend to another !
I'm now blocked with the calendar features in this configuration.
It works fine in bot
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
PLAIN mech,
(but e.g. with LOGIN). So as only PLAIN is availble "No worthy mechs
found".
You can try not to set "mupdate_username: murder" in the frontend
imapd.conf.
But keep "mupdate_authname: murder". This should result in normal
PLAIN authentication
as user
Hi,
I suspect, lmtp it trying to proxy auth, which is not possible with
the PLAIN mech,
(but e.g. with LOGIN). So as only PLAIN is availble "No worthy mechs found".
You can try not to set "mupdate_username: murder" in the frontend imapd.conf.
But keep "mupdate_authn
Hello,
I'm stucked in configuring a murder cluster with one frontend and one
backend.
LMTP between frontend and backend doesn't work, the logs says that no
mechanism is available.
I'm using sasl plain.
When turning saslauthd in debug mode, mta connection to frontend is OK,
Hi,
we discovered a bug in cyrus imapd 3.0.8 in murder/aggregator configuration.
We have the following default stucture:
a LIST "" "*"
* LIST (\HasNoChildren) "/" INBOX
* LIST (\HasChildren) "/" Mail
* LIST (\HasNoChildren \Drafts) "/" Mail/dra
Hi all,
we have a set-up with 3 backend servers and one frontend in a murder cluster.
When I move a message to a folder on another backend than the one my inbox is
residing on, I get the following error :
> 1 messages could not be moved to the mailbox “Sha
> I'm currently trying to setup a running murder Cyrus configuration.
>
> I'm using a frontend (which is also the master mupdate) and a backend.
> Imapd process seems ok, i'm able to connect and authenticate.
>
> imap.eurecom.fr> ver
> name : Cyrus IMAP
Hello,
I'm currently trying to setup a running murder Cyrus configuration.
I'm using a frontend (which is also the master mupdate) and a backend.
Imapd process seems ok, i'm able to connect and authenticate.
imap.eurecom.fr> ver
name : Cyrus IMAPD
version: 3.0.6
ve
? They would also have to be using
altnamespace.
Yes, respectively 2 frontend proxys which are also the murder master and
slave. So how can I managed from these proxys that I have backend
servers with different altnamespace settings ? ... if it's possible ?
On 04/11/2018 12:20 PM, Jean-Chris
On 04/11/2018 06:52 PM, Ken Murchison wrote:
> Do you have any frontend proxys? They would also have to be using
> altnamespace.
Yes, respectively 2 frontend proxys which are also the murder master and
slave. So how can I managed from these proxys that I have backend
servers with dif
Do you have any frontend proxys? They would also have to be using
altnamespace.
On 04/11/2018 12:20 PM, Jean-Christophe Delaye wrote:
Hello,
We are currently running cyrus 2.4 in a murder configuration: 2 murder
servers (master and slave) and 5 backend servers.
As in 2.x version, the
Hello,
We are currently running cyrus 2.4 in a murder configuration: 2 murder
servers (master and slave) and 5 backend servers.
As in 2.x version, the altnamespace value is set to its legacy value
:off on all the server's imapd.conf.
We would like to change the altnamespace value to on BUT
> On 30 May 2017, at 22:47, Michael Menge
> wrote:
>
>
> Quoting Tim Piessens <mailto:tim.piess...@icloud.com>>:
>
>> Hi all,
>>
>> I have created a murder cluster containing 1 update server, 1 frontend and 2
>> backends.
>> M
Quoting Tim Piessens :
Hi all,
I have created a murder cluster containing 1 update server, 1
frontend and 2 backends.
Mail reading woks ok, also moving folders between backends.
However when a client creates a new folder, it gets created on the
frontend and not on a backend.
Is this an
Hi all,
I have created a murder cluster containing 1 update server, 1 frontend and 2
backends.
Mail reading woks ok, also moving folders between backends.
However when a client creates a new folder, it gets created on the frontend and
not on a backend.
I am using cyrus-imapd version 2.5.10
gt;/https://cyrusimap.org/docs/cyrus-imapd/2.4.17/install-murder.php />>>>>>>>>>//>>>>>>>>>>>/Configuring the frontends />>>>>>>>>>>/[...] />>>>>>>>>>>/However, because the front
On 03/15/2017 02:02 PM, Patrick Hennessy wrote:
We are looking to migrate from a 2.3.7 server to a 2.4.18 server. I was
hoping to set up the cyrus murder/aggregator and move the existing
server behind that. While doing some reading and research, I came
across the following mailing list
from source.
Thanks,
Pat
On 3/15/2017 2:02 PM, Patrick Hennessy wrote:
> We are looking to migrate from a 2.3.7 server to a 2.4.18 server. I was
> hoping to set up the cyrus murder/aggregator and move the existing
> server behind that. While doing some reading and research, I cam
We are looking to migrate from a 2.3.7 server to a 2.4.18 server. I was
hoping to set up the cyrus murder/aggregator and move the existing
server behind that. While doing some reading and research, I came
across the following mailing list thread. I was wondering if it's still
the case tha
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 to
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
nyway, I should have, better, read the docs :
https://cyrusimap.org/imap/release-notes/2.5/x/2.5.0.html :
" Cyrus IMAP Murder Topologies
Environments that run a Cyrus IMAP Murder topology will want to upgrade
their backends before they upgrade their frontends. See Task #16 for
details. &quo
ost> lam user.morgan
morgan lrswipkxtecda
Andy
On Mon, 6 Jun 2016, Jean Charles Delépine via Info-cyrus wrote:
Hello,
I'm on the way to make a big (late) upgrade.
My murder config is composed of 16 1To backends. I can't upgrade
all of them simultaneously. So I planed to :
\\Deleted from all visibility.
localhost> lam user.mpellieux
mpellieux lrswip*kxte*cda
cyrus kxca
anyone p
Ps: I had a class with you in 2005 (first ISRAD prom)
Regards,
On 06/06/2016 15:49, Jean Charles Delépine via Info-cyrus wrote:
Hello,
I'm on the way to make a big (late) upgrade.
M
Hello,
I'm on the way to make a big (late) upgrade.
My murder config is composed of 16 1To backends. I can't upgrade
all of them simultaneously. So I planed to :
- upgrade mupdate server (make a new one, and update frontend's and
backend's conf)
- replace fro
ldap_bind_dn: uid=cyrus-admin,ou=services,dc=example,dc=org
Case 2
ldap_bind_s: uid=cyrus-admin,ou=special users,dc=example,dc=org
In case 1 both testsaslauthd and mupdatetest can authenticate just
fine, but in case 2 only testsaslauthd will.
2 In a murder deployment like this, should ptloader be
ldap_bind_s: uid=cyrus-admin,ou=special users,dc=example,dc=org
In case 1 both testsaslauthd and mupdatetest can authenticate just fine,
but in case 2 only testsaslauthd will.
2 In a murder deployment like this, should ptloader be running on all
server or just a part of it, backend? frontend? (M
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 11/11/2015 04:33 AM, Khalid Mehmood via Info-cyrus wrote:
Is it possible to enable caldav/carddav support in a murder environment?
Yes. We are running it in our Murder at CMU. I highly recommend that
you use the 3.x code since its much more robust and had more testing
than the 2.4
Is it possible to enable caldav/carddav support in a murder environment? Any
documention available about running caldav/carddav in a murder setup?
Thanks.
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https
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}
>
>>
gured correctly for a murder
>environement. Currently, only using 1 frontend and one backend.
>
>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 follo
gured correctly for a murder
>environement. Currently, only using 1 frontend and one backend.
>
>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 follo
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
On 06/05/2015 07:42 PM, Andrew Morgan wrote:
> On Fri, 5 Jun 2015, Major Csaba wrote:
>
>> There is one more small question: why the proxied LMTP needs to have
>> "admins" permission on the backend? I thought the proxyservers
>> setting is for this, but LMTP doesn't work without adding my proxy
On 06/05/15 16:44 +0200, Major Csaba wrote:
>Hi,
>
>Thanks for the quick answer.
>I managed to get further as I realized I missed a small piece from the
>documentation. My fronted server and master update server is on the
>same machine and I didn't configure the "mupdate_*" parameter. But as
>I
yr_lmtp cyr_proxy
# Only set proxyservers on Standard Murder BACKENDS
proxyservers: cyr_proxy
and on our frontends:
admins: cyrus
lmtp_admins: cyr_lmtp
proxy_authname: cyr_proxy
proxy_password:
Andy
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu
Hi,
Thanks for the quick answer.
I managed to get further as I realized I missed a small piece from the
documentation. My fronted server and master update server is on the same
machine and I didn't configure the "mupdate_*" parameter. But as I can
see, the proxy still has to speak to mupdate w
On 06/05/15 14:38 +0200, Major Csaba wrote:
>Hi,
>
>I'm rying to build a cyrus server with murder frontend/backend. The
>topology is quiet simple at the moment: there is one frontend +
>mupdate master, and there is one backend server.
>(Cyrus version: 2.4.17)
>
>
Hi,
I'm rying to build a cyrus server with murder frontend/backend. The
topology is quiet simple at the moment: there is one frontend + mupdate
master, and there is one backend server.
(Cyrus version: 2.4.17)
Almost everything is working fine:
* The backend populates the folder chang
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
connection between frontend and backend is lost or the frontend
dies during upload of the message.
Yeah, I'm not a fan of this. It happens in non-murder too.
b) "opening index %s: Invalid mailbox name" the mailbox name seem to
be fine in most cases. I haven
Michael,
I'd like to thank you for having written up such a succinct and
reasonable description of a well thought out murder installation. Lot's
of good information here, especially for people who may be considering a
move like yours. This could be the bones of a good Wiki article
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
On 06/05/2014 05:33 AM, Jean-Christophe Delaye wrote:
> Hi,
>
> After successfully tested Cyrus IMAPD v2.4.17-caldav on a "stand-alone"
> Cyrus IMAP server, I wonder how to integrate "CalDAV" features in our
> running Imap systems.
> We're currently
Hi,
After successfully tested Cyrus IMAPD v2.4.17-caldav on a "stand-alone"
Cyrus IMAP server, I wonder how to integrate "CalDAV" features in our
running Imap systems.
We're currently using 2 murder hosts and 4 backend servers, running in a
cluster (Solaris) environ
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
I see in the documentation that it is better to leave trees of mailboxes on
the same server. I'm wondering if this is an absolute requirement and I
will experience problems if I do not follow this, or if it is more of a
housekeeping issue.
The reason I'm asking is that I would like to create an ar
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
hi all,
I've moved a series of maildir from one server to another ... on the
old server are remained the maildir renamed with the old_ prefix, and
now on the murder I've this entries assigned to the old mailserver.
now I want to remove totally this server from murder ... what is the
Bron helped me track it down. Starting in Cyrus v2.4.13, there is a check
to see if we're running on a standard Murder backend. If so, some code to
update the mailbox list is skipped.
The code was identifying a server as a backend server by checking for the
presence of the "pr
I recently upgraded our Cyrus murder cluster from v2.4.12 to v2.4.16.
Since then, I have come across an interesting race condition. When
connected to a frontend server, if I create a mailbox and then immediately
try to select it, I will get an error message.
Frontend IMAP telemetry
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
On Tue, Aug 14, 2012 at 12:16 AM, shabahang elmian wrote:
> Hello,
> I have a problem on murder env.
> Env:
> 1 MTA on postfix (redhat221)
> 1 frontend+Mupdate (redhat101)
> 2 backends (redhat103, redhat112)
>
> if i pont the MTA to backend(mailbox_transport =
> lmtp
Hello,
I have a problem on murder env.
Env:
1 MTA on postfix (redhat221)
1 frontend+Mupdate (redhat101)
2 backends (redhat103, redhat112)
if i pont the MTA to backend(mailbox_transport =
lmtp:redhat101.example.com:2003), it works on the backend mail boxes.
but when pointing MTA to frontend
On 06/29/12 18:13 -0700, Stephen Ingram wrote:
>I'm trying to test an lmtp connection from the MTA using lmtptest. I'm
>connecting to a murder frontend system which then lmtpproxy's to the
>backend.
>
>On the frontend system I have:
>
>lmtp_admins: lmtp-kerbero
I'm trying to test an lmtp connection from the MTA using lmtptest. I'm
connecting to a murder frontend system which then lmtpproxy's to the
backend.
On the frontend system I have:
lmtp_admins: lmtp-kerberos-principal
On the backend system I have:
lmtp_admins: lmtp-kerberos-p
On Sat, Jun 23, 2012 at 10:55 PM, Stephen Ingram wrote:
> On Thu, Jun 14, 2012 at 9:14 PM, Dan White wrote:
>
> ...snip...
>
>> You can control whether clients will get referrals via the
>> proxyd_disable_mailbox_referrals option.
>>
>> When proxying, you would configure the 'cyrus-' user within
On Thu, Jun 14, 2012 at 9:14 PM, Dan White wrote:
...snip...
> You can control whether clients will get referrals via the
> proxyd_disable_mailbox_referrals option.
>
> When proxying, you would configure the 'cyrus-' user within
> the proxyservers option on the backend. When the frontend authent
On Thu, Jun 14, 2012 at 9:14 PM, Dan White wrote:
...snip...
> You can control whether clients will get referrals via the
> proxyd_disable_mailbox_referrals option.
>
> When proxying, you would configure the 'cyrus-' user within
> the proxyservers option on the backend. When the frontend authent
On 06/22/12 11:31 -0700, Stephen Ingram wrote:
>One other question though, how often do you refresh your credential
>cache? From the few examples I've seen, most people seem to refresh
>very frequently (anywhere from 6 minutes to 1 hour). Given that most
>tickets can last up to 10 or 12 hours, I'm
On Wed, Jun 20, 2012 at 6:29 AM, Dan White wrote:
> On 06/19/12 19:04 -0700, Stephen Ingram wrote:
>>
>> Thank you for your continued help with this. I really appreciate it
>> and am determined to get to the end of this.
>>
>> I think I'm getting closer. I have successfully authenticated using
>>
On 06/19/12 19:04 -0700, Stephen Ingram wrote:
>Thank you for your continued help with this. I really appreciate it
>and am determined to get to the end of this.
>
>I think I'm getting closer. I have successfully authenticated using
>mupdatetest from one of the backends to the mupdate server. I'm u
On Sun, Jun 17, 2012 at 8:21 PM, Dan White wrote:
> On 06/17/12 18:04 -0700, Stephen Ingram wrote:
>>
>> On Thu, Jun 14, 2012 at 9:14 PM, Dan White wrote:
>>
>> ...snip...
>>
>>> Another way to keep your principals straight is that you'll need a user
>>> principal where you will run the *test uti
On 06/17/12 18:04 -0700, Stephen Ingram wrote:
>On Thu, Jun 14, 2012 at 9:14 PM, Dan White wrote:
>
>...snip...
>
>> Another way to keep your principals straight is that you'll need a user
>> principal where you will run the *test utilities, and a service principal
>> on the server that the *test
On Thu, Jun 14, 2012 at 9:14 PM, Dan White wrote:
...snip...
> Another way to keep your principals straight is that you'll need a user
> principal where you will run the *test utilities, and a service principal
> on the server that the *test utility will connect to.
>
> The service principals wi
On Wed, 13 Jun 2012, Dan White wrote:
> From: Dan White
> To: Stephen Ingram
> Cc: info-cyrus
> Date: Wed, 13 Jun 2012 21:23:57
> Subject: Re: GSSAPI for various murder component setups
...
> The other issue is that where your systems are acting as clients
> (such as w
nit'd "user"
tgt (or a non-service principal if you will). I actually name these
'cyrus-' instead of 'cyrus/'. There was some case in
libsasl2 where the slash caused me some grief.
>> Every server in your murder, except perhaps your replica server, will
>&g
mail.example.net service ticket
>>> for accepting client imap connections, but then may need a separate
>>> ticket,
>>> such as cyrus/mail.example.net, for backend/mupdate connections. I use
>>> cronjobs, running as the cyrus user, to initialize those crendential
On Thu, Jun 14, 2012 at 6:20 AM, Dave McMurtrie wrote:
> On 06/14/2012 12:02 AM, Stephen Ingram wrote:
>
>> This is exactly the part I'm really confused about. For murder, I see
>> connections from the frontends and backends to the mupdate server. I
>> also see conn
>> such as cyrus/mail.example.net, for backend/mupdate connections. I use
>> cronjobs, running as the cyrus user, to initialize those crendential
>> caches.
>
>This is exactly the part I'm really confused about. For murder, I see
>connections from the frontends and bac
On 06/14/2012 12:02 AM, Stephen Ingram wrote:
> This is exactly the part I'm really confused about. For murder, I see
> connections from the frontends and backends to the mupdate server. I
> also see connections from the frontends to the backends. The
> connections to the mupdate
On Wed, Jun 13, 2012 at 1:23 PM, Dan White wrote:
> On 06/13/12 12:57 -0700, Stephen Ingram wrote:
>>
>> There seems to be quite a bit of information on the Website about
>> setting up a murder configuration. Most of the documentation, however,
>> seems to be centered
On 06/13/12 12:57 -0700, Stephen Ingram wrote:
>There seems to be quite a bit of information on the Website about
>setting up a murder configuration. Most of the documentation, however,
>seems to be centered on basic authentication. Is there a good resource
>somewhere to using Kerbe
On 06/13/2012 03:57 PM, Stephen Ingram wrote:
> There seems to be quite a bit of information on the Website about
> setting up a murder configuration. Most of the documentation, however,
> seems to be centered on basic authentication. Is there a good resource
> somewhere to using Kerbe
There seems to be quite a bit of information on the Website about
setting up a murder configuration. Most of the documentation, however,
seems to be centered on basic authentication. Is there a good resource
somewhere to using Kerberos to setup the communication between the
mupdate, frontend and
On Fri, 11 May 2012, David Mayo wrote:
> We are looking at upgrading from Cyrus IMAP 2.3 to 2.4. We run a Murder
> with one front end server and one back end server. We plan to XFER
> mailboxes from the old back end to a new back end server with more storage.
>
> From the
We are looking at upgrading from Cyrus IMAP 2.3 to 2.4. We run a Murder
with one front end server and one back end server. We plan to XFER
mailboxes from the old back end to a new back end server with more storage.
From the mailing list I understand we should upgrade the front end
server
On 05/10/2012 10:47 AM, Marc Patermann wrote:
> Nic,
>
> Nic Bernstein schrieb (04.05.2012 14:32 Uhr):
>>In trying to bring up a murder with 2.4.10
> just out of curiosity: Why do you start testing with 2.4.10, which is
> 3/4 of a year old, and not 2.4.16?
This is an in-p
Nic,
Nic Bernstein schrieb (04.05.2012 14:32 Uhr):
> In trying to bring up a murder with 2.4.10
just out of curiosity: Why do you start testing with 2.4.10, which is
3/4 of a year old, and not 2.4.16?
Marc
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: h
1 - 100 of 1079 matches
Mail list logo
