Re: cyrus + postfix + lmtpd questions
> I just want to get this straight. Please, someone clarify his to me. > Consider Cyrus and Postifx runing on different servers and having to > communicate with each other through lmtp. > > 1) > Here´s the line we all know from cyrus.conf that is gonna bring lmtp > listening on tcp: > > lmtp cmd="/usr/local/cyrus/bin/lmtpd" listen="lmtp" prefork=1 > maxchild=100 > > Is that enough on the cyrus side ? That look okay, but see below... > > 2) > posfix's main.cf : > > mailbox_transport = inet:[1.2.3.4]:24 Looks also okay. > > 3) > On some previous reply someone wrote about adding the following to > relay_domains : > > example.com lmtp:unix:public/lmtp# for a local LMTP socket > example.com inet:[1.2.3.4]:24# for a remote LMTP socket > > and then to extend transport_maps: > > transport_maps=hash:/etc/postfix/transports,hash:/etc/postfix/relay_domains. > > Cant figure out why this is necesary. Well, using a simple mailbox_transport like shown in 2) is the easiest configuration. Of course you can have very complex postfix configs for example with complicated transport maps but you don't have to make it complex if your environment doesn't enforce it. > > 4) > And last but not least. How postfix authenticates in anyway so Cyrus The question is how you want to communicate. In my case I was using a local trusted network between postfix and cyrus server so I did the easiest thing which is running lmtpd without authentication and configure TCP wrapper to accept only connections from the postfix host. Like so: In /etc/cyrus.conf I had lmtpd listening preauthenticated: lmtp cmd="lmtpd -a" listen="lmtp" prefork=1 In /etc/hosts.deny on the cyrus host I had: # Allow only specific hosts to send mail via LMTP lmtp: ALL EXCEPT mailhub.domain.tld Regards, Simon Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: sieve vacation filter not working for one user
> Can anyone tell me where the file(s) with list of email addresses that > have been sent a vacation reply lives in a debian installation? I can't > seem to find it. Hi, I think what you are looking for is deliver.db in $configdir. Don't know on Debian but on my systems it's /var/lib/imap/deliver.db. Regards, Simon Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Nginx configuration for imap
memcached would certainly be fast, but what sort of authentication rate are you talking about here. My bet is that you've got other bits of system, such as the authentication validation with the target IMAP server, that will be more of a dominant term when it comes to the performance of your system. I deployed an nginix proxy to assist in my migration to Cyrus (once all my users were on Cyrus, murder took over) -- just had it do lookups against our LDAP directory to determine which IMAP provider to redirect to, it worked perfectly fine. -rob On Wed, Mar 17, 2010 at 10:35 PM, Robert Mueller wrote: > > > But I thought a memcache lookup will be much more inexpenisve than > > connecting to a mysql db to do lookup for every cyrus connection > > Probably slightly. But what happens if the value isn't in memcached? > Where do you get the value from? > > Anyway, it's still WAY better than doing: > > > > > $user['user1'] = 10.1.1.1; > > > > $user['user2'] = 10.1.1.2; > > > > > > > > $user[user15000]=10.1.1.1; > > For every lookup. > > Rob > > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ > Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Nginx configuration for imap
> But I thought a memcache lookup will be much more inexpenisve than > connecting to a mysql db to do lookup for every cyrus connection Probably slightly. But what happens if the value isn't in memcached? Where do you get the value from? Anyway, it's still WAY better than doing: > > > $user['user1'] = 10.1.1.1; > > > $user['user2'] = 10.1.1.2; > > > > > > $user[user15000]=10.1.1.1; For every lookup. Rob Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Nginx configuration for imap
On Thu, 2010-03-18 at 14:36 +1100, Robert Mueller wrote: > > > $user['user1'] = 10.1.1.1; > > $user['user2'] = 10.1.1.2; > > > > $user[user15000]=10.1.1.1; > > For 15k users this method becomes very heavy. There are too many httpd > > processes running that suck the resources on the machine. I want to > > store the userlist in a memcache and look it up through nginx.conf > > How do I do this ? > > Don't use memcache, it's a *cache*, you want a *database*. So > just use a database to store the data, and look it up for each > user. eg. > > mysql: http://php.net/manual/en/book.mysql.php > bdb: > http://www.oracle.com/technology/documentation/berkeley-db/db/programmer_reference/ext_php.html > Choose your favourite key/value db here... > But I thought a memcache lookup will be much more inexpenisve than connecting to a mysql db to do lookup for every cyrus connection Is that not true. Thanks Ram Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Nginx configuration for imap
> $user['user1'] = 10.1.1.1; > $user['user2'] = 10.1.1.2; > > $user[user15000]=10.1.1.1; > For 15k users this method becomes very heavy. There are too many httpd > processes running that suck the resources on the machine. I want to > store the userlist in a memcache and look it up through nginx.conf > How do I do this ? Don't use memcache, it's a *cache*, you want a *database*. So just use a database to store the data, and look it up for each user. eg. mysql: http://php.net/manual/en/book.mysql.php bdb: http://www.oracle.com/technology/documentation/berkeley-db/db/programmer_reference/ext_php.html Choose your favourite key/value db here... Rob Rob Mueller r...@fastmail.fm Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Metapartitions
On Wed, Mar 17, 2010 at 09:17:49PM -0300, Diego Ventrice wrote: > Thanks Mark, > > Thats what I guessed. I suppose these files make use of the .seen and > .sub files under also, right ? .seen and .sub files are always in your "configdir" - where the mailboxes.db and related things are. It's actually not quite flexible enough for my liking, and I'm seriously considering a per-file configuration option that will allow things like deliver.db and statuscache.db to be configured on different paths - specifically on tmpfs! We already symlink the proc directory out to tmpfs, but that's harder to do with individual files. ... but that's debate for the future: for now there are basically three locations of interest: 1) the data path, where emails are stored 2) the (optional) metadata path, where you can choose to locate some higher IO rate small files 3) the config directory. In our experience, the size of (2 + 3) with all cyrus.* files except squat on meta is about 5% (20/1) of data. The IO rates around 5/1 meta over data. That makes it a pretty good tradeoff to split the meta onto small fast storage. My rough testing a little while back showed about a 50% split between 2 and 3. So half the IO is to the config directory (databases + .seen and quota files) and half is to cyrus.index and cyrus.cache files. This is on machines with lots of memory, so the majority of "hot" data is in memory - most of the ongoing IO is writes. Bron. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Metapartitions
Thanks Mark, Thats what I guessed. I suppose these files make use of the .seen and .sub files under also, right ? Diego And thanks Dan for the link. > http://cyrusimap.web.cmu.edu/imapd/internal/mailbox-format.html > > -- > Dan White > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: cyrus + postfix + lmtpd questions
I just want to get this straight. Please, someone clarify his to me. Consider Cyrus and Postifx runing on different servers and having to communicate with each other through lmtp. 1) Here´s the line we all know from cyrus.conf that is gonna bring lmtp listening on tcp: lmtp cmd="/usr/local/cyrus/bin/lmtpd" listen="lmtp" prefork=1 maxchild=100 Is that enough on the cyrus side ? 2) posfix's main.cf : mailbox_transport = inet:[1.2.3.4]:24 3) On some previous reply someone wrote about adding the following to relay_domains : example.com lmtp:unix:public/lmtp# for a local LMTP socket example.com inet:[1.2.3.4]:24# for a remote LMTP socket and then to extend transport_maps: transport_maps=hash:/etc/postfix/transports,hash:/etc/postfix/relay_domains. Cant figure out why this is necesary. 4) And last but not least. How postfix authenticates in anyway so Cyrus Thanks for all who answered and for the patience Diego Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
sieve vacation filter not working for one user
Can anyone tell me where the file(s) with list of email addresses that have been sent a vacation reply lives in a debian installation? I can't seem to find it. thanks, maria Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Metapartitions
On 17/03/10 14:45 -0300, Diego Ventrice wrote: >Danke Marc, clearer now. >And sure, I'll take answers from anyone. > >About this: > >>What do you think files named "header", "index", "cache", "expunge" and >>"squat" in this context contain? ;) > >Ich denke this are the cyrus header index and cache files generally >stored on each mailbox folder. >I can imagine what they do but not sure and I wouldnt mind about a >little explanation =) > >About expunge and squat, keine Idee about what they are for and where >they reside >expunge: index file with messages marked for deletion ? http://cyrusimap.web.cmu.edu/imapd/internal/mailbox-format.html -- Dan White Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Metapartitions
Hi, Quoting Diego Ventrice : Danke Marc, clearer now. And sure, I'll take answers from anyone. About this: What do you think files named "header", "index", "cache", "expunge" and "squat" in this context contain? ;) Ich denke this are the cyrus header index and cache files generally stored on each mailbox folder. I can imagine what they do but not sure and I wouldnt mind about a little explanation =) most of the time cyrus does not need to access the message file (.) but uses the cyrus.* files. These files are small compared to the sum of the message files. By defining a metapartition you can use fast but expensiv storage like SSDs for the metadata and other storage for the mails. About expunge and squat, keine Idee about what they are for and where they reside expunge: index file with messages marked for deletion ? Thanks again D. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html M.MengeTel.: (49) 7071/29-70316 Universität Tübingen Fax.: (49) 7071/29-5912 Zentrum für Datenverarbeitung mail: michael.me...@zdv.uni-tuebingen.de Wächterstraße 76 72074 Tübingen smime.p7s Description: S/MIME Signatur Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Metapartitions
Danke Marc, clearer now. And sure, I'll take answers from anyone. About this: >What do you think files named "header", "index", "cache", "expunge" and >"squat" in this context contain? ;) Ich denke this are the cyrus header index and cache files generally stored on each mailbox folder. I can imagine what they do but not sure and I wouldnt mind about a little explanation =) About expunge and squat, keine Idee about what they are for and where they reside expunge: index file with messages marked for deletion ? Thanks again D. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: non-encrypted for local queries
Or, in the event you're only allowing access to port 143 from loopback
and possibly a trusted LAN, you can also use:
imap_allowplaintext: yes
imap_sasl_minimum_layer: 0
in /etc/imapd.conf as port 993 is always protected.
We use
tls_cipher_list: !ADH:MEDIUM:HIGH
in /etc/imapd.conf, so sufficient encryption is required over SSL
connections anyway.
Rafe
Dan White wrote:
> On 17/03/10 10:11 -0500, Raphael Jaffey wrote:
>> Use the following as the only "imapd" command configured in
>> /etc/cyrus.conf to accept connections from localhost only:
>>
>> imap cmd="imapd" listen="[127.0.0.1]:imap" prefork={number}
>>
>> You can restrict access to hosts from the LAN without using the
>> firewall using at least a couple of methods:
>>
>> 1) Assuming cyrus was compiled with libwrap support, you can restrict
>> access to the imap service in /etc/hosts.allow (or /etc/hosts.deny).
>>
>> 2) If the LAN you mentioned below is private (no access from other
>> subnets and networks), you can use the following in /etc/cyrus.conf in
>> addition to the entry I mentioned above:
>>
>> imap cmd="imapd" listen="[{LAN-interface-address}]:imap"
>> prefork={number}
>
> Assuming that you have allowplaintext set to no, to disallow plaintext
> logins externally, then you'll want to add a '-p xxx' to the cyrus.conf
> entry that Raphael suggested (inside the cmd field), which will direct
> imapd to assume there is some protection layer for your local/LAN
> connections. See imapd(8).
>
--
___
Raphael Jaffey E-mail: rjaf...@artic.edu
Director of Network Services
The Art Institute of ChicagoVoice: (312) 629-6543
111 S. Michigan Ave, Chicago, IL 60603 FAX: (312) 641-3406
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: non-encrypted for local queries
On 17/03/10 10:11 -0500, Raphael Jaffey wrote:
>Use the following as the only "imapd" command configured in
>/etc/cyrus.conf to accept connections from localhost only:
>
>imap cmd="imapd" listen="[127.0.0.1]:imap" prefork={number}
>
>You can restrict access to hosts from the LAN without using the firewall
>using at least a couple of methods:
>
>1) Assuming cyrus was compiled with libwrap support, you can restrict
>access to the imap service in /etc/hosts.allow (or /etc/hosts.deny).
>
>2) If the LAN you mentioned below is private (no access from other
>subnets and networks), you can use the following in /etc/cyrus.conf in
>addition to the entry I mentioned above:
>
>imap cmd="imapd" listen="[{LAN-interface-address}]:imap"
>prefork={number}
Assuming that you have allowplaintext set to no, to disallow plaintext
logins externally, then you'll want to add a '-p xxx' to the cyrus.conf
entry that Raphael suggested (inside the cmd field), which will direct
imapd to assume there is some protection layer for your local/LAN
connections. See imapd(8).
--
Dan White
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: non-encrypted for local queries
Hello Raphael,
Of course! and thank you.
Reg.
Wednesday, March 17, 2010, 8:53:08 AM, you wrote:
> Use the following in /etc/cyrus.conf:
> imap cmd="imapd" listen="[127.0.0.1]:imap" prefork={number}
> imaps cmd="imapd -s" listen="imaps" prefork={number}
> That will allow connections to port 143 from localhost only and to port
> 993 from anywhere. That first entry is also required for cyradm to work
> on the local box unless you've got a version with SSL support. We also
> run Horde on separate servers, so that uses port 993. However our
> Luminis portal's email client doesn't support SSL or TLS, so we use a
> dedicated crossover cable between servers in this case and have an imap
> instance bind to the private link's interface in the same manner as the
> localhost example above.
> Rafe
> Nybbles2Byte wrote:
>> Hello Raphael,
>> Thanks but I'm not looking to restrict access just to the LAN. I'm
>> looking to allow unencrypted access via localhost (and as a bonus via
>> the LAN but not necessary) but only encrypted access via the WAN. Which
>> I believe boils down to port 143 for localhost and 993 for the WAN.
>> This allows me to have an application like horde which I can use for web
>> mail to talk with cyrus unencrypted being on the same server while
>> remote users being required to have a secure line. After all, why make
>> the server encrypt communications to talk to itself? That's just chewing
>> up resources for no good reason.
>> Wednesday, March 17, 2010, 8:11:10 AM, you wrote:
>> *> Use the following as the only "imapd" command configured in
>>> /etc/cyrus.conf to accept connections from localhost only:
>>> imap cmd="imapd" listen="[127.0.0.1]:imap" prefork={number}
>>> You can restrict access to hosts from the LAN without using the firewall
>>> using at least a couple of methods:
>>> 1) Assuming cyrus was compiled with libwrap support, you can restrict
>>> access to the imap service in /etc/hosts.allow (or /etc/hosts.deny).
>>> 2) If the LAN you mentioned below is private (no access from other
>>> subnets and networks), you can use the following in /etc/cyrus.conf in
>>> addition to the entry I mentioned above:
>>> imap cmd="imapd" listen="[{LAN-interface-address}]:imap"
>>> prefork={number}
>>> Nybbles2Byte wrote:
>>> > Hello Info-cyrus,
>>> > Is there a way to tell cyrus to accept non-encrypted port 143 queries
>>> > from localhost (and perhaps the LAN) but not remotely? I guess you
>>> > could allow unencrypted requests in cyrus but block 143 in your firewall
>>> > but I am wondering if there is purely cyrus settings solution.
>>> > /--
>>> > Nybbles2Byte mailto:nybbles2b...@gmail.com/
>>> > /
>>> > /
>>> >
>>> > /
>>> >
>>> > Cyrus Home Page: http://cyrusimap.web.cmu.edu/
>>> > Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
>>> > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html/
>> */--
>> Nybbles2Bytemailto:nybbles2b...@gmail.com/
--
Nybbles2Bytemailto:nybbles2b...@gmail.com
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: non-encrypted for local queries
Use the following as the only "imapd" command configured in
/etc/cyrus.conf to accept connections from localhost only:
imap cmd="imapd" listen="[127.0.0.1]:imap" prefork={number}
You can restrict access to hosts from the LAN without using the firewall
using at least a couple of methods:
1) Assuming cyrus was compiled with libwrap support, you can restrict
access to the imap service in /etc/hosts.allow (or /etc/hosts.deny).
2) If the LAN you mentioned below is private (no access from other
subnets and networks), you can use the following in /etc/cyrus.conf in
addition to the entry I mentioned above:
imap cmd="imapd" listen="[{LAN-interface-address}]:imap"
prefork={number}
Nybbles2Byte wrote:
> Hello Info-cyrus,
>
> Is there a way to tell cyrus to accept non-encrypted port 143 queries
> from localhost (and perhaps the LAN) but not remotely? I guess you
> could allow unencrypted requests in cyrus but block 143 in your firewall
> but I am wondering if there is purely cyrus settings solution.
>
> /--
> Nybbles2Byte mailto:nybbles2b...@gmail.com/
>
> /
> /
>
> /
>
> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html/
--
___
Raphael Jaffey E-mail: rjaf...@artic.edu
Director of Network Services
The Art Institute of ChicagoVoice: (312) 629-6543
111 S. Michigan Ave, Chicago, IL 60603 FAX: (312) 641-3406
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: non-encrypted for local queries
> Hello Info-cyrus, > > Is there a way to tell cyrus to accept non-encrypted port 143 queries from > localhost (and perhaps the LAN) but not remotely? I guess you could allow > unencrypted requests in cyrus but block 143 in your firewall but I am > wondering if there is purely cyrus settings solution. You should be able to define a listener on cyrus.conf for imap (port 143) which listens only on localhost. You may find some examples in the list archives. Regards, Simon Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
non-encrypted for local queries
Hello Info-cyrus, Is there a way to tell cyrus to accept non-encrypted port 143 queries from localhost (and perhaps the LAN) but not remotely? I guess you could allow unencrypted requests in cyrus but block 143 in your firewall but I am wondering if there is purely cyrus settings solution. -- Nybbles2Byte mailto:nybbles2b...@gmail.com Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
OT: Nginx configuration for imap
I am using ngnix as a Load balancer for two imap servers. Currently the nginx calls an apache php script that determines if the user is on imap1 or imap2 by looking up a plain text file. which contains entries like $user['user1'] = 10.1.1.1; $user['user2'] = 10.1.1.2; $user[user15000]=10.1.1.1; For 15k users this method becomes very heavy. There are too many httpd processes running that suck the resources on the machine. I want to store the userlist in a memcache and look it up through nginx.conf How do I do this ? Does Nginx support for memcache also include imap protocol Thanks Ram Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Metapartitions
Diego, Diego Ventrice schrieb: > > Andrew, > > Could you just exlplain to me the metapartition ? Don't you want answers from anyone else? ;) > What info is kept there and which is there regular location ? > > metapartition-p1: /var/spool/cyrus/mail/meta1 > metapartition_files: index cache expunge squat So, you found the metapartition_files directive and still want to know what it does? metapartition_files: Space-separated list of metadata files to be stored on a metapartition rather than in the mailbox directory on a spool partition. Allowed values: header, index, cache, expunge, squat metapartition-name: The pathname of the metadata partition name, corresponding to spool partition partition-name. For any mailbox residing in a directory on partition-name, the metadata files listed in metapartition_files will be stored in a corresponding directory on metapartition-name. Note that not every partition-name option is required to have a corresponding metapartition-name option, so that you can selectively choose which spool partitions will have separate metadata partitions. [man imapd.conf] What do you think files named "header", "index", "cache", "expunge" and "squat" in this context contain? ;) Marc Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Metapartitions
Andrew, Could you just exlplain to me the metapartition ? What info is kept there and which is there regular location ? metapartition-p1: /var/spool/cyrus/mail/meta1 metapartition_files: index cache expunge squat Thanks D. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
