Re: wiki suggestion: integrated products bundling Cyrus IMAPd
Craig Ringer wrote: Hi folks I thought it might be an idea to start a wiki page tracking products that ship an integrated Cyrus IMAPd. This would be useful in (a) saving people who don't want to roll their own a lot of frustration and (b) potentially saving the mailing list participants a lot of repeat questions and issues. I suggest an entry, possibly on the main wiki page, along the lines of Integrated products including Cyrus. A FAQ entry along the lines of this is too fiddly - isn't there an easier way to make this all just go? that refers to the aforementioned page might be a good idea, too. Sound sensible? Here's my suggested beginning for the product list: [Free] Simon's RPMs - not really integrated mail system, but make setup a bit easier [Commercial] SuSE OpenExchange http://www.suse.de/en/business/products/suse_business/openexchange/ Apple MacOS X Server http://www.apple.com/server/macosx/ Here are some more possible additions.. [Free] Cyrus 2.1 packages for Debian stable. Add the following lines to /etc/apt/sources.list .. deb http://people.debian.org/~hmh/woody/ hmh/cyrus/ deb http://people.debian.org/~hmh/woody/ hmh/misc/ [Commercial] Bynari Insight Server http://www.bynari.net/index.php?id=501 SUSE LINUX Standard Server 8 http://www.suse.com/us/business/products/server/standard/features.html --- Home Page: http://asg.web.cmu.edu/cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Kill this thread, it shouldn't have been one ( was: Re: CYRUS = ....)
Peter P. Benac wrote: The problem with Freeware is that most times the documents that accompany the software severely lack any substance. What needs to be stressed here is that its *free* software. You are more than welcome to donate either efforts (like Ken suggested) or funds to correct the situation you describe. If these solutions were put into print or FAQ format then perhaps David wouldn't have to be so angry and the stupid questions that nobody wants to answer will have a place to be sent. Perhaps but that is no excuse. I rely on opensource software a lot and have often found myself in a similar scenario like that of the original poster of this thread where documentation did not suffice and I didn't receive any replies to my requests for help on mailing lists. Just because we are able to download and use free software does not mean that we are absolutely entitled to free support. Developers and experienced system administrators who donate their time and post to these mailing lists probably have other priorities - it's a little presumptuous to think that they *have* to answer our calls for help within a certain time frame.
Re: BDB or skiplist?
Andreas wrote: I see that the cyrus-imap-2.2 branch already uses skiplist as the default format. Does this recomendation also apply to the 2.1 branch or was this due to some code change between 2.1 and 2.2? Here are some notes which might help you in deciding which database backend to use and why. Recommendations are offered for both 2.1 and 2.2 releases.. http://acs-wiki.andrew.cmu.edu/twiki/bin/view/Cyrus/WhatDatabaseBackend
Re: Is Reiserfs better than ext3
Craig Ringer wrote: Some people swear by XFS - and it /does/ work brilliantly with LVM - but there have been reports of unreliability and FS corruption. Could you please provide some links to these reports? Thanks.
Re: virtual domain and postfix problem
Murat Ergur wrote: Hi, I'm using cyrus-imapd-2.2.1-BETA with postfix 2.0.16. My problem is postfix cannot deliver incoming mails to cyrus virtual domain mail folder. It's complaining with user unknown in virtual alias table. My settings are below: /etc/imapd.conf virtdomains: yes defaultdomain: mail.bar.org /etc/postfix/main.cf mydomain = bar.org myhostname = mail.bar.org myorigin and mydestination not defined local_recipient_maps = virtual_alias_domains = /etc/postfix/domains virtual_alias_maps = /etc/postfix/users mailbox_transport = lmtp:unix:/var/imap/socket/lmtp /etc/postfix/domains foo.org anything The problem is what should I write in RHS of virtual_alias_maps file. Whatever I write, it gives the same error (user unknown in virtual alias table). However when I check it with postmap -q, the database seems OK. What I understand from this is I have to find a way to pass both username and domain part of e-mail to the postfix. Let's assume you have a cyrus user (part of a virtual domain) called [EMAIL PROTECTED]. Remove virtual_alias_domains and virtual_alias_maps from your main.cf file and add these lines instead.. transport_maps = hash:/usr/local/etc/postfix/transport relay_domains = foo.org relay_recipient_maps = hash:/usr/local/etc/postfix/relay_recipients Then add your information in this format to the above mentioned files.. For /usr/local/etc/postfix/transport foo.org lmtp:unix:/var/imap/socket/lmtp For /usr/local/etc/postfix/relay_recipients [EMAIL PROTECTED] accept
Re: Using email address as login name
Gerard Ceraso wrote: I have seen some places where the login name for the email would be [EMAIL PROTECTED] so for example if I wanted to login my login for this account would be [EMAIL PROTECTED] How is this done with cyrus, I tried and it didn't work. Am I missing something? Is it possible with cyrus? It's possible with version 2.2, you can log in using the default domain that Cyrus is configured for ([EMAIL PROTECTED]) or any virtual domain ([EMAIL PROTECTED]).
Re: About mailbox's upper case
Kai wrote: How can I let Cyrus ignore the case of mailbox ? I mean ,I want Cyrus treating the upper case's mailbox and lower case's mailbox as the same recipient if their spelling are same. This might help.. http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrusmsg=25220
Re: lmtp and uppercase email addresses
Igor Brezac wrote: On Tue, 7 Oct 2003, Avtar Gill wrote: Here are the relevant parts of my imapd.conf file, I can provide the entire file if necessary.. sasl_pwcheck_method: auxprop sasl_auxprop_plugin: sasldb sasldb_path: /usr/local/etc/sasldb2 username_tolower: yes You want lmtp_downcase_rcpt: yes Thanks. For anyone's future reference, the solution provided above worked.
lmtp and uppercase email addresses
Hi. I've searched this mailing list and come across some posts which indicate that cyrus 2.2 (I'm running Cyrus-IMAP 2.2.1 with Postfix 2.0.9 on FreeBSD 4.8) is not case sensitive when dealing with user accounts/email addresses. That doesn't appear to be the case with my installation. Whenever the server receives an email where the address is all in uppercase letters I get the following error in my mail log.. host /var/imap/socket/lmtp[/var/imap/socket/lmtp] said: 550-Mailbox unknown. Either there is no mailbox associated with this 550-name or you do not have authorization to see it. 550 5.1.1 User unknown (in reply to RCPT TO command) Mail delivered to the same account gets accepted by cyrus if the address is in lowercase. I'm not sure what I'm doing wrong here so I would appreciate it if someone could point out what I've overlooked. Thanks! Here are the relevant parts of my imapd.conf file, I can provide the entire file if necessary.. sasl_pwcheck_method: auxprop sasl_auxprop_plugin: sasldb sasldb_path: /usr/local/etc/sasldb2 username_tolower: yes # /usr/local/cyrus/bin/deliver -l 220 mail.tdneti.com LMTP Cyrus v2.2.1-BETA ready mail from:[EMAIL PROTECTED] 250 2.1.0 ok rcpt to:[EMAIL PROTECTED] 550-Mailbox unknown. Either there is no mailbox associated with this 550-name or you do not have authorization to see it. 550 5.1.1 User unknown # /usr/local/cyrus/bin/deliver -l 220 mail.tdneti.com LMTP Cyrus v2.2.1-BETA ready mail from:[EMAIL PROTECTED] 250 2.1.0 ok rcpt to:[EMAIL PROTECTED] 250 2.1.5 ok
Re: Outlook 2002 vs. Cyrus 2.1.12
On Tue, 11 Feb 2003, Hasso Meyer-Jordan wrote: (I wouldn't be surprised about brain-dead Microsoft developers! ;-))) Perhaps badly payed immigrants of India [like unskilled worker]. ) I can't speak for the administrators of this list but as a normal user of Cyrus IMAPD I turn to this mailing list for technical help and information, not bigotry. Please take your racist diatribe elsewhere.
Re: clients that notify upon new mail in folders other than INBOX?
On Wed, 5 Feb 2003, Piet Ruyssinck wrote: their inbox, but also a few other (shared) folders, it would be neat if they were notified when new messages arrive in these other folders as well. Any idea which clients support this kind of functionality or how I can implement this ? If your decision isn't only limited to GUI clients then Pine can do this as well with the help of (unofficial) patches.. http://www.math.washington.edu/~chappa/pine/info/incoming.html
Re: DBERROR: archive
On Thu, 9 Jan 2003, Bob Meader wrote: I get these recurring lines in log: Jan 9 15:08:27 tuba ctl_cyrusdb[28368]: checkpointing cyrus databases Jan 9 15:08:27 tuba ctl_cyrusdb[28368]: DBERROR: archive /var/imap/db: cyrusdb error Jan 9 15:08:27 tuba ctl_cyrusdb[28368]: done checkpointing cyrus databases I am running NetBSD 1.6, I installed cyrus-imap-2.1.9 via I kept getting those errors while using Cyrus-IMAP on NetBSD 1.6 too except I was using 2.1.11 instead. Chris Gilbert was kind enough to point me to a new patch in pkgsrc which resolved the problem. You might want to consider updating your pkgsrc tree and upgrading Cyrus-IMAP to 2.1.11 and see if that helps you too. Here are the archived posts.. http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrussearchterm=netbsdmsg=19606 http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrussearchterm=netbsdmsg=19929 http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrussearchterm=netbsdmsg=19935 Good luck.
Re: ctl_cyrusdb DBERROR on NetBSD 1.6
Chris Gilbert [EMAIL PROTECTED] wrote: I'd been meaning to investigate this problem, but hadn't had the time to, but someone may well have beaten me to it. Could you try the latest cyrus from pkgsrc? Thanks Chris, the latest patch did the trick. I haven't seen that error in the logs now.. Jan 8 23:58:59 kompressor master[3079]: process started Jan 8 23:58:59 kompressor ctl_cyrusdb[3081]: recovering cyrus databases Jan 8 23:59:00 kompressor ctl_cyrusdb[3081]: done recovering cyrus databases Jan 8 23:59:01 kompressor master[3079]: ready for work Jan 8 23:59:01 kompressor ctl_cyrusdb[3082]: checkpointing cyrus databases Jan 8 23:59:01 kompressor ctl_cyrusdb[3082]: done checkpointing cyrus databases
ctl_cyrusdb DBERROR on NetBSD 1.6
I'm currently trying to setup cyrus-imapd-2.1.11 on a NetBSD 1.6 server. For some reason I keep seeing errors in the log files whenever the ctl_cyrusdb checkpoint event is issued. This is what I saw in the logs when I first started the master process.. Dec 17 04:15:21 kompressor master[1444]: process started Dec 17 04:15:21 kompressor ctl_cyrusdb[1446]: recovering cyrus databases Dec 17 04:15:23 kompressor ctl_cyrusdb[1446]: done recovering cyrus databases Dec 17 04:15:23 kompressor master[1444]: ready for work Then immediately.. Dec 17 04:15:23 kompressor ctl_cyrusdb[1447]: checkpointing cyrus databases Dec 17 04:15:23 kompressor ctl_cyrusdb[1447]: DBERROR: archive /var/imap/db: cyrusdb error Dec 17 04:15:23 kompressor ctl_cyrusdb[1447]: DBERROR: error archiving log file: /var/imap/db/log.01 Dec 17 04:15:23 kompressor ctl_cyrusdb[1447]: DBERROR: archive /var/imap/db: cyrusdb error Dec 17 04:15:23 kompressor ctl_cyrusdb[1447]: done checkpointing cyrus databases These errors keep showing up in the logs every 30 minutes. Here are the contents of the /var/imap/db directory.. drwxr-xr-x 2 cyrus mail 512 Dec 17 04:21 . drwxr-x--- 10 cyrus mail 512 Dec 17 12:51 .. -rw--- 1 cyrus mail 8192 Dec 17 04:21 __db.001 -rw--- 1 cyrus mail270336 Dec 17 04:21 __db.002 -rw--- 1 cyrus mail 98304 Dec 17 04:21 __db.003 -rw--- 1 cyrus mail 17063936 Dec 17 04:21 __db.004 -rw--- 1 cyrus mail 32768 Dec 17 04:21 __db.005 -rw--- 1 cyrus mail 17497 Dec 17 04:21 log.01 From browsing the mailing list archives I noticed two other people are experiencing this problem. http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrussearchterm=DBERRORmsg=19541 http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrussearchterm=DBERRORmsg=19579 This is a brand new server so no imap user accounts have been created yet. Is there any reason to be concerned about these errors?
