RE: Outlook does notdelete but displays deleted messages asstrike-trough
Is this considered to be good UI design by anyone? Or, is IMAP support just crippled in Outlook? BTW, the Mac version of Outlook (Entourage or whatever its called) also seems to have this behavior also. wt IMAP support (in my experience) is pretty bad in Outlook - it still has to have PST files on the local machine to house it's special directories and is VERY slow in comparison to more... open alternatives (Mozilla Thunderbird for me). I think this is partly because it insists on downloading attachments before displaying a message, but mostly because (inexplicably) it operates really slowly over the network (~100kb/s over 100Mb switched). Wait, it gets better: the PST file(s) in Outlook 2003 can be of two types: Old, 95/98/200 format (*up to 2GB*) and newer format no file size limits. Supposedly you can chose what type of PST you want to use when you create your profile. Except... If you read the fine print you'll find out that if you chose IMAP, Outlook chooses for you the old type of PST file, guess what the choice will be. Which means, for a 6GB IMAP store with a lot of folders and stuff your local PST file will get to 2GB. IMO the best IMAP client from Microsoft was Outlook 2000, ever since they've done everything they could to limit IMAP usage in Outlook. Now, if only Thunderbird will have Sieve support and ACLs... And have the Sieve implementation compatible with Squirrel mail now THAT will be the day! Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
lmtp delivery - headers missing
Hi, I am having a problem with Cyrus and message delivery... I have tried Exim and sendmail and both are showing pretty much the same issue Mails are arriving without some headers. In the case of Sendmail which is the one I currently have active and am working with, the To: header is not visible in my mailer (have checked with thunderbird and outlook). I have spotted one or two others with this problem but noone seems to have posted a solution. This is running on a RHAS 4 box. Sendmail v 8.13.1 Cyrus v2.2.10 Any pointers really appreciated. Regards Rafe Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Outlook does not delete but displays deleted messages asstrike-trough
James Yale wrote: There is an option (I believe under Edit) to 'Purge deleted messages' which permanently deletes messages marked as to be deleted - is this what you were after? Well, I'm looking for something server-side, best would be something to be run from cyrmaster, like squatter, to expunge all deleted mail from all mailboxes over the night before the backup. Most of the users here use Seamonkey :) Outlook is totally unsuited for handling mail and was kicked out some years ago because it was too troublesome, but now it leaks back in because other software relies on it. GH Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
2.2 murder backend authentication problems
I've been wrestling with a new cyrus murder setup. At this point, edits made to a backend server are properly propigated through the master and frontends. Now, i'm trying to test administration through the frontend servers. For example, when i connect to a frontend server and issue a `CREATE user.testuser imap-backend` the frontend logs show the following: May 18 10:00:28 imap-frontend imap[24327]: accepted connection May 18 10:00:28 imap-frontend imap[24327]: mystore: starting txn 2147483656 May 18 10:00:28 imap-frontend imap[24327]: mystore: committing txn 2147483656 May 18 10:00:28 imap-frontend imap[24327]: starttls: TLSv1 with cipher AES256-SHA (256/256 bits new) no authentication May 18 10:00:28 imap-frontend imap[24327]: login: client [128.113.124.76] cyrusadmin PLAIN+TLS User logged in May 18 10:00:28 imap-frontend imap[24327]: Doing a peer verify May 18 10:00:28 imap-frontend imap[24327]: Doing a peer verify May 18 10:00:28 imap-frontend imap[24327]: received server certificate May 18 10:00:28 imap-frontend imap[24327]: starttls: TLSv1 with cipher AES256-SHA (256/256 bits new) no authentication May 18 10:00:28 imap-frontend imap[24327]: couldn't authenticate to backend server: no mechanism available May 18 10:00:28 imap-frontend imap[24327]: PROTERR: end of file reached -- and the backend: -- May 18 10:00:28 imap-backend imap[5517]: accepted connection May 18 10:00:28 imap-backend imap[5517]: mystore: starting txn 2147483674 May 18 10:00:28 imap-backend imap[5517]: mystore: committing txn 2147483674 May 18 10:00:28 imap-backend imap[5517]: starttls: TLSv1 with cipher AES256-SHA (256/256 bits new) no authentication --- Network dumps show that its using TLS, but i can't tell what the traffic looks like after TLS starts. I've manually logged in with LOGIN to verify that the cyrusproxy,proxypasswd combo is valid on the backend server Here are the pertainant pieces of my frontend imapd.conf... --- configdirectory: /var/lib/imap partition-default: /tmp admins: cyrusadmin proxy_authname: cyrusproxy imap-backend_passwd: proxypass postuser: sharedfolders allowplaintext: 1 sasl_pwcheck_method: saslauthd sasl_mech_list: PLAIN LOGIN GSSAPI sasl_minimum_layer: 0 tls_key_file: /etc/ssl/cert.key tls_cert_file: /etc/ssl/cert.cert tls_ca_file: /etc/ssl/CA.cert # Murder mupdate_username: cyrusproxy mupdate_authname: cyrusproxy mupdate_password: proxypass mupdate_server: imap-master.domain.tld - And the relivant parts of the backend config: - admins: cyrusadmin cyrusbackend postuser: sharedfolders allowplaintext: 1 sasl_pwcheck_method: saslauthd sasl_mech_list: PLAIN LOGIN GSSAPI sasl_minimum_layer: 0 # SSL tls_key_file: /etc/ssl/cert.key tls_cert_file: /etc/ssl/cert.cert tls_ca_file: /etc/ssl/CA.cert # Murder mupdate_username: cyrusbackend mupdate_authname: cyrusbackend mupdate_password: backendpasswd mupdate_server: imap-master.domain.tld proxyservers: cyrusbackend cyrusproxy allowusermoves: 1 - If anyone has suggestions it would be very much appreciated. Thanks. -- Brenden Conte System Programmer, CMT.CIO Rensselaer Polytechnic Institute (518)276-4264 Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Some imapd processes getting permission denied setting flags
This one is really strange. I've just recently upgraded
one of our old Redhat 7.3 servers from Cyrus 2.2.something CVS
to Cyrus 2.3.3.
We're getting lots of users unable to mark messages read or
deleted. Now, our code works by adding the 'selected' flag
to whatever messages it wishes to act upon, then using a search
on that flag to do the action. Convoluted, but it allows us to
act on messages from multiple pages of a web interface.
The symptom - from one server I can log in just fine and do
things. From another server I get no messages selected
from the web interface. I found the matching processid on
the server as follows (username rewritten to protect the user:
[EMAIL PROTECTED] imapproc]$ grep *
27285:web3.internal [10.202.2.212] user.
27827:heartbeat2.internal [10.202.2.161]user.
28773:web1.internal [10.202.2.210] user.
6342:web2.internal [10.202.2.211] user.
[EMAIL PROTECTED] imapproc]$ strace -p 6342 -s 5
select(1, [0], NULL, NULL, {3583, 423000}) = 1 (in [0], left {3575, 302000})
time(NULL) = 1147961382
time(NULL) = 1147961382
select(1, [0], NULL, NULL, {3575, 0}) = 1 (in [0], left {3575, 0})
time(NULL) = 1147961382
time(NULL) = 1147961382
read(0, 1 noop\r\n, 4096) = 8
stat64(/var/spool/imap4/k/user//cyrus.index, {st_mode=S_IFREG|0600, st_siz
e=1012, ...}) = 0
fstat64(16, {st_mode=S_IFREG|0600, st_size=18860, ...}) = 0
fcntl64(14, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = 0
fstat64(14, {st_mode=S_IFREG|0600, st_size=15068, ...}) = 0
stat64(/var/imap/user/k/.seen, {st_mode=S_IFREG|0600, st_size=15068, ...})
= 0
fcntl64(14, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0
write(1, 1 OK Completed\r\n, 16) = 16
open(/var/imap/msg/shutdown, O_RDONLY) = -1 ENOENT (No such file or directory)
time(NULL) = 1147961382
select(1, [0], NULL, NULL, {3600, 0}) = 1 (in [0], left {3599, 997000})
time(NULL) = 1147961382
time(NULL) = 1147961382
select(1, [0], NULL, NULL, {3600, 0}) = 1 (in [0], left {3600, 0})
time(NULL) = 1147961382
time(NULL) = 1147961382
read(0, 2 uid store 11735 +flags.silent (selected)\r\n, 4096) = 44
fcntl64(6, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}) = 0
fstat64(6, {st_mode=S_IFREG|0600, st_size=76253908, ...}) = 0
stat64(/var/imap/mailboxes.db, {st_mode=S_IFREG|0600, st_size=76253908, ...})
= 0
fcntl64(6, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0
stat64(/var/spool/imap4/k/user//cyrus.index, {st_mode=S_IFREG|0600, st_siz
e=1012, ...}) = 0
fstat64(16, {st_mode=S_IFREG|0600, st_size=18860, ...}) = 0
write(1, 2 NO Permission denied\r\n, 24) = 24
But then from web3 I get:
[EMAIL PROTECTED] imapproc]$ strace -p 27285 -s 5
select(1, [0], NULL, NULL, {3525, 417000}) = 1 (in [0], left {3467, 635000})
time(NULL) = 1147962178
time(NULL) = 1147962178
select(1, [0], NULL, NULL, {3468, 0}) = 1 (in [0], left {3468, 0})
time(NULL) = 1147962178
time(NULL) = 1147962178
read(0, 1 noop\r\n, 4096) = 8
stat64(/var/spool/imap4/k/user//cyrus.index, {st_mode=S_IFREG|0600,
st_size=1084, ...}) = 0
fstat64(15, {st_mode=S_IFREG|0600, st_size=1084, ...}) = 0
fstat64(16, {st_mode=S_IFREG|0600, st_size=19740, ...}) = 0
fcntl64(13, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = 0
fstat64(13, {st_mode=S_IFREG|0600, st_size=16508, ...}) = 0
stat64(/var/imap/user/k/.seen, {st_mode=S_IFREG|0600, st_size=16508,
...}) = 0
fcntl64(13, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0
write(1, * 13 FETCH (FLAGS (\\Seen hasnoatt))\r\n1 OK Completed\r\n, 53) = 53
open(/var/imap/msg/shutdown, O_RDONLY) = -1 ENOENT (No such file or directory)
time(NULL) = 1147962178
select(1, [0], NULL, NULL, {3600, 0}) = 1 (in [0], left {3599, 994000})
time(NULL) = 1147962178
time(NULL) = 1147962178
select(1, [0], NULL, NULL, {3600, 0}) = 1 (in [0], left {3600, 0})
time(NULL) = 1147962178
time(NULL) = 1147962178
read(0, 2 uid store 11735 +flags.silent (selected)\r\n, 4096) = 44
fcntl64(6, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}) = 0
fstat64(6, {st_mode=S_IFREG|0600, st_size=76254588, ...}) = 0
stat64(/var/imap/mailboxes.db, {st_mode=S_IFREG|0600, st_size=76254588, ...})
= 0
fcntl64(6, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0
time(NULL) = 1147962178
fcntl64(15, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0,
Re: listmailbox problem
patrick wrote: Thanks, that worked for me. I guess it's not possible to list all users in all domains, but I can work around that. Have a look at the thread saslpasswd and virtual domains from a few days ago. You can also have a look at http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/CyrusVirtualDomains -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert e-mail: [EMAIL PROTECTED] Directie ICT, Afdeling Infrastructuur Groep Systemen tel: +32 9 264 4734 Universiteit Gent / Ghent Universityfax: +32 9 264 4994 Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: 2.2 murder backend authentication problems
On Thu, 18 May 2006, Brenden Conte wrote: I've been wrestling with a new cyrus murder setup. At this point, edits made to a backend server are properly propigated through the master and frontends. Now, i'm trying to test administration through the frontend servers. For example, when i connect to a frontend server and issue a `CREATE user.testuser imap-backend` the frontend logs show the following: In my testing, I had to create mailboxes on the backend. Maybe someone else can confirm this, but I don't think you can create mailboxes from a frontend. Andy Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: mailboxes.db backend comparison
On Wed, 17 May 2006, Wesley Craig wrote: On 17 May 2006, at 14:21, Andrew Morgan wrote: My most recent test was to rebuild the mupdate master mailboxes.db from my backend server. skiplist - 20-25 minutes berkeley - 3 minutes How long does it take to LIST the contents of each database? I don't know of a way to test this on the mupdate master, so instead I converted one of my frontends from skiplist to berkeley. A simple lm command in cyradm took approximately 15 seconds for both formats. Andy Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
cyrus 2.3.3 change + solved: permission denied setting flags
Ok, we've tracked down the permissions problem. It has to do with what I believe is a change in behaviour between 2.3 CVS 6 months ago and 2.3.3. Cyrus 2.3 from CVS about 6 months ago... . select user.xyz ... . OK [READ-WRITE] Completed . examine user.xyz ... . OK [READ-ONLY] Completed Cyrus 2.3.3 . select user.xyz ... . OK [READ-WRITE] Completed . examine user.xyz ... . OK [READ-WRITE] Completed Ok that last one is saying that it's in [READ-WRITE] mode on an examine while previously it used to say [READ-ONLY]. Is that an expected behaviour change, or a bug? Rob Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: cyrus 2.3.3 change + solved: permission denied setting flags
Robert Mueller wrote: Ok, we've tracked down the permissions problem. It has to do with what I believe is a change in behaviour between 2.3 CVS 6 months ago and 2.3.3. Cyrus 2.3 from CVS about 6 months ago... . select user.xyz ... . OK [READ-WRITE] Completed . examine user.xyz ... . OK [READ-ONLY] Completed Cyrus 2.3.3 . select user.xyz ... . OK [READ-WRITE] Completed . examine user.xyz ... . OK [READ-WRITE] Completed Ok that last one is saying that it's in [READ-WRITE] mode on an examine while previously it used to say [READ-ONLY]. Is that an expected behaviour change, or a bug? Its a bug. This make have creeped in with the updated ACL code. What is the ACL on user.xyz for the authorized user? -- Kenneth Murchison Systems Programmer Project Cyrus Developer/Maintainer Carnegie Mellon University Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: cyrus 2.3.3 change + solved: permission denied setting flags
On Fri, May 19, 2006 at 02:40:11AM +1000, Robert Mueller wrote: [...] saying that it's in [READ-WRITE] mode on an examine while previously it used to say [READ-ONLY]. Is that an expected behaviour change, or a bug? And if it's expected, then why was it saying Permission denied when our code took it at its word and tried to set flags on a message! Our solution is to be conservative in what we believe, and storing 'read-only' in our internal connection state data if we asked for an examine rather than a select - regardless of the server's response. This feels like a good idea that will keep working just fine when the bug is fixed, and protect us against any future regressions! Bron. Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: 2.2 murder backend authentication problems
True, and i perhaps used a bad example - this occurs anytime i try to connect to the backend, not just on CREATE. for example, i can successfully, log in with a valid account, but if i try to `SELECT INBOX`, I get the same error. Thanks. -Brenden Andrew Morgan wrote: On Thu, 18 May 2006, Brenden Conte wrote: I've been wrestling with a new cyrus murder setup. At this point, edits made to a backend server are properly propigated through the master and frontends. Now, i'm trying to test administration through the frontend servers. For example, when i connect to a frontend server and issue a `CREATE user.testuser imap-backend` the frontend logs show the following: In my testing, I had to create mailboxes on the backend. Maybe someone else can confirm this, but I don't think you can create mailboxes from a frontend. Andy -- Brenden Conte System Programmer, CMT.CIO Rensselaer Polytechnic Institute (518)276-4264 Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: 2.2 murder backend authentication problems
Am Donnerstag, 18. Mai 2006 17:57 schrieb Andrew Morgan: On Thu, 18 May 2006, Brenden Conte wrote: I've been wrestling with a new cyrus murder setup. At this point, edits made to a backend server are properly propigated through the master and frontends. Now, i'm trying to test administration through the frontend servers. For example, when i connect to a frontend server and issue a `CREATE user.testuser imap-backend` the frontend logs show the following: In my testing, I had to create mailboxes on the backend. Maybe someone else can confirm this, but I don't think you can create mailboxes from a frontend. I'm experiencing something very similar using 2.3.3. When I try to create a mailbox from the frontend it starts to connect to the backend but the connection fails with a no worthy mechs error on the frontend. So it seems it is indeed possible create may be issued from one of the frontends (however I tried a unified setup). If you find anything new, please post it. I'd be very interested in resolving this too. Regards, Michael Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: cyrus 2.3.3 change + solved: permission denied setting flags
Robert Mueller wrote: Ok, we've tracked down the permissions problem. It has to do with what I believe is a change in behaviour between 2.3 CVS 6 months ago and 2.3.3. Cyrus 2.3 from CVS about 6 months ago... . select user.xyz ... . OK [READ-WRITE] Completed . examine user.xyz ... . OK [READ-ONLY] Completed Cyrus 2.3.3 . select user.xyz ... . OK [READ-WRITE] Completed . examine user.xyz ... . OK [READ-WRITE] Completed Ok that last one is saying that it's in [READ-WRITE] mode on an examine while previously it used to say [READ-ONLY]. Is that an expected behaviour change, or a bug? Fixed in CVS (lib/acl.h and imap/imapd.c) -- Kenneth Murchison Systems Programmer Project Cyrus Developer/Maintainer Carnegie Mellon University Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: 2.2 murder backend authentication problems
On Thu, 18 May 2006, Brenden Conte wrote: True, and i perhaps used a bad example - this occurs anytime i try to connect to the backend, not just on CREATE. for example, i can successfully, log in with a valid account, but if i try to `SELECT INBOX`, I get the same error. I don't know enough about the sasl authentication details to debug your problem directly, but here are the relevant parts of my frontend and backend configs for comparison. Frontend servername: imap.onid.oregonstate.edu admins: cyrus allowanonymouslogin: 0 allowplaintext: 1 lmtp_admins: cyr_lmtp sasl_mech_list: PLAIN sasl_minimum_layer: 0 #sasl_maximum_layer: 256 sasl_pwcheck_method: saslauthd mupdate_server: cyrus-mm.onid.oregonstate.edu mupdate_port: 3905 mupdate_authname: cyr_mupdate mupdate_username: cyr_mupdate mupdate_password: XXX proxyservers: cyr_proxy proxy_authname: cyr_proxy proxy_password: XXX Backend --- servername: mail1.onid.oregonstate.edu admins: cyrus cyr_proxy allowanonymouslogin: 0 allowplaintext: 1 lmtp_admins: cyr_lmtp cyr_proxy sasl_mech_list: PLAIN sasl_minimum_layer: 0 #sasl_maximum_layer: 256 sasl_pwcheck_method: saslauthd mupdate_server: cyrus-mm.onid.oregonstate.edu mupdate_port: 3905 mupdate_authname: cyr_mupdate mupdate_username: cyr_mupdate mupdate_password: XXX proxyservers: cyr_proxy proxy_authname: cyr_proxy proxy_password: XXX Btw, LOGIN is not a sasl mech. It is an IMAP login method. Andy Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: 2.2 murder backend authentication problems
Am Donnerstag, 18. Mai 2006 21:26 schrieb Andrew Morgan: On Thu, 18 May 2006, Brenden Conte wrote: True, and i perhaps used a bad example - this occurs anytime i try to connect to the backend, not just on CREATE. for example, i can successfully, log in with a valid account, but if i try to `SELECT INBOX`, I get the same error. I don't know enough about the sasl authentication details to debug your problem directly, but here are the relevant parts of my frontend and backend configs for comparison. Your config looks pretty much like mine. I'm using PLAIN+TLS with an ldap backend. However this may be due to some sasl-subtleties used (and not understood). The part I don't understand is that my client outputs it isn't able to authenticate because it found no worthy mechs. Testing connections with imtest -t gives me an AUTH=PLAIN though. Do you know of any way to get more debug output from either cyrus or sasl? Regards, Michael Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: mailboxes.db backend comparison
On 18 May 2006, at 12:11, Andrew Morgan wrote: On Wed, 17 May 2006, Wesley Craig wrote: On 17 May 2006, at 14:21, Andrew Morgan wrote: My most recent test was to rebuild the mupdate master mailboxes.db from my backend server. skiplist - 20-25 minutes berkeley - 3 minutes How long does it take to LIST the contents of each database? I don't know of a way to test this on the mupdate master, so instead I converted one of my frontends from skiplist to berkeley. A simple lm command in cyradm took approximately 15 seconds for both formats. Any difference in the resources (CPU, disk IO) consumed? Perhaps do lm 10-20 times to get enough data to demonstrate a difference. :wes Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: 2.2 murder backend authentication problems
Quoting Michael Leupold [EMAIL PROTECTED]: Am Donnerstag, 18. Mai 2006 21:26 schrieb Andrew Morgan: On Thu, 18 May 2006, Brenden Conte wrote: True, and i perhaps used a bad example - this occurs anytime i try to connect to the backend, not just on CREATE. for example, i can successfully, log in with a valid account, but if i try to `SELECT INBOX`, I get the same error. I don't know enough about the sasl authentication details to debug your problem directly, but here are the relevant parts of my frontend and backend configs for comparison. Your config looks pretty much like mine. I'm using PLAIN+TLS with an ldap backend. However this may be due to some sasl-subtleties used (and not understood). The part I don't understand is that my client outputs it isn't able to authenticate because it found no worthy mechs. Testing connections with imtest -t gives me an AUTH=PLAIN though. Do you know of any way to get more debug output from either cyrus or sasl? Regards, Michael Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html Your problem is 'what mechanism is your frontend using to connect to your backend'? Generally, there are a couple to choose from, and if you don't specify it, the frontend is just going to choose one (generally GSSAPI). Generally, if you backend has anything other then 'sasl_mech_list: PLAIN', then the frontend will choose a different mechanism (at least in my experience) to use. You can force a frontend to use a specific mechanism, but this currently doesn't work with PLAIN due to a bug (I believe). Anyhow if you are able to, set 'sasl_mech_list: PLAIN' in your backend and see if the connection works from the frontend to the backend. -Patrick Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
