Yes I'm looking for Bug# 2806, mupdate process fix. I
have checked Bugzilla and its says this has been
fixed, so I'm just waiting for the release which
contains this bug fix.
Thanks
KMK
--- Ken Murchison [EMAIL PROTECTED] wrote:
Khalid Mehmood wrote:
What is the expected release date of
Am Mittwoch, 19. April 2006 18:27 schrieb Andrew Morgan:
On Wed, 19 Apr 2006, Dr. Harry Knitter wrote:
Am Mittwoch, 19. April 2006 15:27 schrieb [EMAIL PROTECTED]:
Hello,
we have a problem to restore Cyrus mailboxes from an installation of
SuSE
9.2
which we want to transfer do a
Ken,
Using Internal namespaces and 2.3.3-2 gives following results.
If I create user.jbasile and NO INBOX, I can deliver an email and it
appears at user.jbasile
If I then create user.jbasile.INBOX, I can deliver an email and it appears
at user.jbasile, not at the INBOX
Mailbox is
user.jbasile
Marc G. Fournier wrote:
On Wed, 19 Apr 2006, John Hampton wrote:
barsalou wrote:
What I was wondering iscan someone help list the pro's and cons
of skiplist and Bdb?
I found the following link to be very helpful
http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/WhatDatabaseBackend
Perry Brown wrote:
Thanks for the imtest idea.
It looks like I can log in OK.
server1.sub1% /opt/mail/cyrus-imapd/bin/imtest -m login -p imap
server2.sub2.domain.com
Force imtest to use one of the SASL mechanisms that are listed. The
backends *only* use SASL, not protocol specific login
John Hampton wrote:
barsalou wrote:
What I was wondering iscan someone help list the pro's and cons of
skiplist and Bdb?
I found the following link to be very helpful
http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/WhatDatabaseBackend
Yes, this is a good place to look. One thing
I did not see a reply to Martijn's inquiry. I am particularly interested in
question #2and #4 below, but in my case it's on a Solaris 5.8 (Cyrus 2.1.11)
platform migrating to Linux AS 3.0 (Cyrus 2.2.12).
2.1.11 does not have the xfer command, 2.2.12 does. Which release of 2.1.XX
was the
Create a sieve script for a user mailbox is simple.
But I want to create a sieve script for a shared mailbox (seen by a users
group).
A user foo has a mailbox /var/spool/cyrus/f/user/foo/ and sieve
/var/spool/sieve/f/foo/ .
But a shared mailbox [EMAIL PROTECTED] has a /var/spool/cyrus/i/info
On Thu, 20 Apr 2006, Dr. Harry Knitter wrote:
Could you please give me a hint what you mean with configdirectory?
In my case (SuSE 10.0 as well as 9.2) I found a subdirectory db
in /var/lib/imap the directory where the database seems to be located.
There is a directory deliverdb with a
On Thu, 20 Apr 2006, John Basile wrote:
Ken,
Using Internal namespaces and 2.3.3-2 gives following results.
If I create user.jbasile and NO INBOX, I can deliver an email and it
appears at user.jbasile
If I then create user.jbasile.INBOX, I can deliver an email and it appears
at user.jbasile,
On Thu, Apr 20, 2006 at 06:06:21PM +0200, Etienne ETOURNAY wrote:
Create a sieve script for a user mailbox is simple.
But I want to create a sieve script for a shared mailbox (seen by a users
group).
A user foo has a mailbox /var/spool/cyrus/f/user/foo/ and sieve
/var/spool/sieve/f/foo/ .
Am Donnerstag, 20. April 2006 18:31 schrieb Andrew Morgan:
On Thu, 20 Apr 2006, Dr. Harry Knitter wrote:
Could you please give me a hint what you mean with configdirectory?
In my case (SuSE 10.0 as well as 9.2) I found a subdirectory db
in /var/lib/imap the directory where the database
On Thu, 20 Apr 2006, Ken Murchison wrote:
Marc G. Fournier wrote:
On Wed, 19 Apr 2006, John Hampton wrote:
barsalou wrote:
What I was wondering iscan someone help list the pro's and cons of
skiplist and Bdb?
I found the following link to be very helpful
Marc G. Fournier wrote:
On Thu, 20 Apr 2006, Ken Murchison wrote:
Marc G. Fournier wrote:
On Wed, 19 Apr 2006, John Hampton wrote:
barsalou wrote:
What I was wondering iscan someone help list the pro's and cons
of skiplist and Bdb?
I found the following link to be very helpful
On Thu, 20 Apr 2006, Ken Murchison wrote:
Marc G. Fournier wrote:
On Thu, 20 Apr 2006, Ken Murchison wrote:
Marc G. Fournier wrote:
On Wed, 19 Apr 2006, John Hampton wrote:
barsalou wrote:
What I was wondering iscan someone help list the pro's and cons of
skiplist and Bdb?
I found
Am Mittwoch, 19. April 2006 18:27 schrieb Andrew Morgan:
You could also try deleting the files in the configdirectory/db/ directory
(make a copy to be safe). Those are the transaction logs, etc, for
BerkeleyDB and skiplist. They should be safe to delete because the actual
information is in
Perry Brown wrote:
Thanks for the imtest idea.
It looks like I can log in OK.
server1.sub1% /opt/mail/cyrus-imapd/bin/imtest -m login -p imap
server2.sub2.domain.com
Force imtest to use one of the SASL mechanisms that are listed. The
backends *only* use SASL, not protocol specific
This is a stupid question i had.I just saw in the documentation
Note that you can have the MUPDATE master be one of your frontend
machines, just do not configure a slave mupdate process on this
machine.
excuse me for asking pointless questions :)
simon.
--
http://www.fastmail.fm - Access your
On Thu, 20 Apr 2006, Ken Murchison wrote:
Marc G. Fournier wrote:
'k ... just to make sure that I fully understand though ... as long as I
use Berkeley DB for *anything*, that directory needs to exist ... ? For
instance, if duplicate_db == db3?
Yes. I you use BDB for any of the
On Thu, 20 Apr 2006, Dr. Harry Knitter wrote:
Am Donnerstag, 20. April 2006 18:31 schrieb Andrew Morgan:
On Thu, 20 Apr 2006, Dr. Harry Knitter wrote:
Could you please give me a hint what you mean with configdirectory?
In my case (SuSE 10.0 as well as 9.2) I found a subdirectory db
in
On Thu, 20 Apr 2006, Perry Brown wrote:
I'm sorry I got my dounce cap on today or something.
Should I change the -m login to -m and one of the AUTH= values from the
CAPABILITY output?
ie -m GSSAPI? or digest-md5 etc...
Maybe -m plain?
Andy
Cyrus Home Page:
Perry Brown wrote:
Thanks for the imtest idea.
It looks like I can log in OK.
server1.sub1% /opt/mail/cyrus-imapd/bin/imtest -m login -p imap
server2.sub2.domain.com
Force imtest to use one of the SASL mechanisms that are listed. The
backends *only* use SASL, not protocol
On Apr 20, 2006, at 5:16 PM, Andrew Morgan wrote:
On Thu, 20 Apr 2006, Patrick Radtke wrote:
I'm not sure if its to clear from the documentation (or if its in
there) but you can also configure lmtpproxyd on each frontend to
query the slave mupdate process on the localhost. On a busy
I'm testing out cyrus murder with v2.2.12 and I noticed that lmtpproxyd
doesn't seem to support the -a (preauth) option that the regular lmtpd
does.
On my standalone cyrus system, I use lmtpd -a to accept mail from our
campus mail relays running postfix, and I use tcpwrappers to block all
You need to use tls as well for PLAIN to work. add -t to your
arguments
What mechanism do you want to use for connecting between backends? If
its PLAIN then you want
force_sasl_client_mech: PLAIN
in your imapd.conf file.
Otherwise, the machines will see GSSAPI advertised and will try
I tried with plain: /opt/mail/cyrus-imapd/bin/imtest -m plain -p imap
And it got rejected.
C: A01 AUTHENTICATE PLAIN Y3lyaW1hcABjeXJpbWFwAGpTdXZTMTFz
S: A01 NO no mechanism available
Authentication failed. generic failure
Security strength factor: 0
I can not find a tls conf file so I do not
26 matches
Mail list logo
