Re: virtdomains: userid?
Nope Bill, sorry. As was noted in my thread, it looks to be a SASL issue. Because some SASL plugins require a hostname, rather than IP, SASL apparently does a reverse DNS on every connecting IP. Maybe I'll move a request over to the SASL list to look into whether the reverse DNS can be on a per-enabled-plugin basis (thus if I only have enabled plugins that don't require reverse DNS, it doesn't occur). But my personal problem with it was resolved - I kicked my ISP in the rear and got them to fix their DNS setup. Being a local cable operator, they actually do respond to customers' technical requests (*gasp*). :D --Scott Bill Kearney wrote: Would this help your reverse DNS lookup trouble? Or will using the unqualified name still trigger a reverse lookup? It doesn't appear to help my situation, in that I'd like logins without a qualified name to use just the bare username and NOT append a realm onto it. Is this possible? -Bill Configuring Virtual Domains Introduction Virtual domains is the practice of hosting a service for more than one domain on one server. Cyrus IMAP has the ability to host IMAP/POP mailboxes for multiple domains (e.g. [EMAIL PROTECTED] and [EMAIL PROTECTED]) on a single server or Murder. In order to accomplish this, Cyrus needs to know which domain to look in when a mailbox is accessed. There are two ways in which Cyrus can determine the domain: * Fully qualified userid - the client logs in with a userid containing the domain in which the user belongs (e.g [EMAIL PROTECTED] or test%example.net) * IP address - the server looks up the domain based on the IP address of the receiving interface (useful for servers with multiple NICs or using IP aliasing) Both of these methods are active if the virtdomains option is set to on (or yes, 1, true) and can be used in conjunction with one another. If the virtdomains option is set to userid, then only the first method is used. Note that a fully qualified userid takes precedence over a domain obtained from the IP address. 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: improving concurrency/performance
At Mon, 7 Nov 2005 09:00:08 -0500 (EST), John Madden wrote: Have you tried running something like postmark http://packages.debian.org/stable/utils/postmark to benchmark your filesystem? The disks are quite fast. bonnie++, for example, shows writes at over 300MB/s. What I'm finding though is that the processes aren't ever pegging them out -- nothing ever goes into iowait. The bottleneck is elsewhere... The question was though: Have you tried running PostMark? The distinction is extremely important. PostMark can reliably and repeatably provide very good benchmark measurements to compare filesystem tunings and hardware configurations and it does so in ways that mimic very well such real-world multi-user applications such as Cyrus IMAPd. Bonnie and Bonnie++ are very simplistic in comparison and rather useless for determining the cause of bottlenecks in real-world applications that may open many files at a time (unless you script frameworks to wrap them with, in which case you are simply re-inventing something like PostMark). -- Greg A. Woods H:+1 416 218-0098 W:+1 416 489-5852 x122 VE3TCP RoboHack [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED] Secrets of the Weird [EMAIL PROTECTED] 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: Importing MBOX-formatted mailboxes into Cyrus?
At Wed, 16 Nov 2005 11:01:57 -0500, Matt Singerman wrote: Are there any tools available that will take MBOX mailboxes and insert them into Cyrus? Of course there are! Sadly the simplest, the AWK script I've attached, is not included in the Cyrus IMAPd sources I wrote this script for my own use to migrate several largish mail servers, and so far it has served me very well. -- Greg A. Woods H:+1 416 218-0098 W:+1 416 489-5852 x122 VE3TCP RoboHack [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED] Secrets of the Weird [EMAIL PROTECTED] unix2cyrus Description: Binary data 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: handling unqualified names?
Have you tried virtdomains: userid ? This will disable the reverse lookup. Yes, it doesn't reverse but it also tacks on the domain.tld of the server. Or, more accurately, it tacks on the domain.tld of the interface on which the connection was made. So if 192.168.12.2 is 'mail.domain2.tld' then connections into it would be from '[EMAIL PROTECTED]'. Equally true if there are other IP addresses configured to respond to mail then their domain.tld will be used. It does work in cyrus and I think it also does work with SASL auxprop LDAP. It does not work with auxprop SQL where this auxprop plugin will always append the servername as a realm to unqualified userids. Ah, that explains it. I'll have to compare the source between the sql.c plugin and the others. you set virtdomains: userid and login with an unqualified userid the auxprop plugin will always append the servername. The 'auxprop' concept itself? Or the SQL plugin that's called via auxprop? I may be wrong here, but the defaultdomain setting is there to unqualify qualified userids. So if you login with [EMAIL PROTECTED] as in your example above the defaultdomain is stripped and the userid becomes joe. SASL auxprop plugin SQL will then append the servername as a realm leading to a lookup of [EMAIL PROTECTED] So the answer is that auxprop plugin SQL does not support unqualified userids, I think. Unfortunately you may be correct. Which may lead me back to using pam_mysql via saslauthd. Six steps forward, eight steps back, it seems. Here I was thinking it'd be more efficient to call SQL directly, but n! Yeesh. Of course by using PAM I get stuck not being able to use challenge-response, correct? -Bill Kearney 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
