Re: [Dovecot] (no subject)

2007-10-12 Thread Christian Schmidt
Hello LDB,

LDB, 12.10.2007 (d.m.y):

> Version: 1.0.beta8

Well, 1.0 has been released "long time ago"...

> Is it possible to listen on just specific IP addresses
> as opposed a single IP or just all IPs on the same server?

It is. Take a look at your configuration file. Search for "listen".

Gruss/Regards,
Christian Schmidt

-- 
You will be audited by the Internal Revenue Service.


Re: [Dovecot] dovecot 1.1beta2 and dovecot-sieve 1.1.2 - crash in LDA

2007-10-12 Thread Bernhard Schmidt
Bernhard Schmidt <[EMAIL PROTECTED]> wrote:

> I've upgraded to dovecot 1.1beta2 and the latest dovecot-sieve release
> yesterday and have one single mail that cannot be delivered repeatedly.

Screw that, fixed already in the latest hg version, probably with
changeset 58d9f94b9919.

Thanks,
Bernhard



Re: [Dovecot] Spliting Folders for Efficiency

2007-10-12 Thread Daniel Watts

Chris Laif wrote:

On 10/11/07, Daniel Watts <[EMAIL PROTECTED]> wrote:

Dear Timo,

Would there be any sense in giving Dovecot the option to split folders
into multiple subfolders when they reached a specified size (probably
message count) limit?



Many modern file systems offer the possibility to use optimized
directory indexes. Listing these directories scales very well.
Splitting files into subdirectories would have a negative effect: You
have to walk through every directory and merge all file names into one
data table.

Chris



That is true. But it still leaves the motivation of being able to store 
rarely accessed 'old' mail in a separate, perhaps remote, location which 
I can see as valuable. Even though storage is pretty cheap, expensive 
disks...are not cheap =)




Re: [Dovecot] Spliting Folders for Efficiency

2007-10-12 Thread Daniel Watts



Curtis Maloney wrote:

Daniel Watts wrote:

Dear Timo,

Would there be any sense in giving Dovecot the option to split 
folders into multiple subfolders when they reached a specified size 
(probably message count) limit?


My understanding is this is partially covered in Timo's "dbox" format, 
which tries to take the best features of mbox and Maildir.

Is dbox production ready? It looks interesting.
http://wiki.dovecot.org/MailboxFormat/dbox this page says it is not 
finished.


What actually ARE the advantages of a 'one file per folder' format?? We 
switched to Maildir because mbox was killing our server. I wouldn't ever 
switch back.
The only thing perhaps is faster Search since you don't have to open 
lots of files. But for this I reckon it would be best to keep a separate 
index of content. Dreams of offering a 'google like' imap-search 
function anyone? =) Are there any (preferably open source) products out 
there for this?



.Folder.new
.Folder.cur
.Folder.tmp

could become:

.Folder__1.new
.Folder__1.cur
.Folder__1.tmp
and
.Folder__2.new
.Folder__2.cur
.Folder__2.tmp


You would only need to split "cur", unless you expect someone to get 
over 10,000 new message waiting.  "tmp" is only used _whilst_ message 
are being delivered, so mail clients don't see a partially written 
message.

Ah yes this is true.


This could be further extended so that Dovecot could be configured to 
store 'old' message folders in a separate location. We could then 
have slower+cheaper+larger storage mounted so that 'old mail' does 
not take up the expensive local SCSI disks on the machine. Mail from 
2 years ago is much less likely to be accessed than mail from the 
last week.


Also, instead of __N, you could try a different path, so 
/foo/bar/User/ is for new mail, and /old/slow/disk/User is for older 
stuff.
ah yes - and if it is on the same disk it could just be 
$HOME/Maildir/cur and $HOME/Maildir/old/cur



This would provide very neat behind-the-scenes archiving functionality.


There's really two ideas here... one is the mechanism of 
multi-directory folders, the other is the policy of separating by age.

Ideally there would be a few limits set by the system admin:
Min Age of mail
Max Age of mail
Min number of messages.
Max number of messages.

You can then split by either volume or age and control how many emails 
to keep in 'fast' storage as a minimum - eg always have the most recent 
50 emails in local storage, regardless of age.


Dan


Re: [Dovecot] Spliting Folders for Efficiency

2007-10-12 Thread Chris Laif
On 10/11/07, Daniel Watts <[EMAIL PROTECTED]> wrote:
> Dear Timo,
>
> Would there be any sense in giving Dovecot the option to split folders
> into multiple subfolders when they reached a specified size (probably
> message count) limit?
>

Many modern file systems offer the possibility to use optimized
directory indexes. Listing these directories scales very well.
Splitting files into subdirectories would have a negative effect: You
have to walk through every directory and merge all file names into one
data table.

Chris


[Dovecot] (no subject)

2007-10-12 Thread LDB
Version: 1.0.beta8

Is it possible to listen on just specific IP addresses
as opposed a single IP or just all IPs on the same server?

Thanks,

LDB


[Dovecot] dovecot 1.1beta2 and dovecot-sieve 1.1.2 - crash in LDA

2007-10-12 Thread Bernhard Schmidt
Hi,

I've upgraded to dovecot 1.1beta2 and the latest dovecot-sieve release
yesterday and have one single mail that cannot be delivered repeatedly.

Log (reformatted):
Oct 12 15:19:19 vs02 deliver(bernilrz): pool_data_stack_realloc(): stack frame 
changed
Oct 12 15:19:19 vs02 deliver(bernilrz): Raw backtrace: 
/usr/local/libexec/dovecot/deliver(i_syslog_panic_handler+0x1e) [0x47117e] -> 
/usr/local/libexec/dovecot/deliver [0x470eac] -> 
/usr/local/libexec/dovecot/deliver [0x47929b] -> 
/usr/local/libexec/dovecot/deliver [0x46f3e3] -> 
/usr/local/libexec/dovecot/deliver(buffer_write+0x9d) [0x46f70d] ->
/usr/local/libexec/dovecot/deliver [0x469aaf] ->
/usr/local/libexec/dovecot/deliver(message_header_decode+0x104) [0x469c14] ->
/usr/local/libexec/dovecot/deliver(message_header_decode_utf8+0x4b) [0x469d4b] 
-> 
/usr/local/libexec/dovecot/deliver [0x43f3eb] ->
/usr/local /libexec/dovecot/deliver(index_mail_get_headers+0x42) [0x4401c2] ->
/usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0x2b662df67d87] ->
/usr/local/lib /dovecot/lda/lib90_cmusieve_plugin.so [0x2b662df716e8] ->
/usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_eval_bc+0x395) 
[0x2b662df72665] ->
/usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0xfa)
 [0x2b662df77daa] ->
/usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x318) 
[0x2b662df689b8] ->
/usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0x2b662df66d96] ->
/usr/local/libexec/dovecot/deliver(main+0xe74) [0x417d24] -> 
/lib/libc.so.6(__libc_start_main+0xf4) [0x2b662da15b44] ->
/usr/local/libexec/dovecot/deliver [0x416079]

All other mails work fine, so there is probably something corner case
here.

Timo, I'll send you the mail in private.

Regards,
Bernhard Schmidt



[Dovecot] verbose_proctitle for proxy processes?

2007-10-12 Thread Onno Molenkamp
Hi,

We're using Dovecot to proxy incoming POP3 and IMAP connections to the right 
server. We'd like to be able to see what connections are currently open on 
the proxy servers, without having the parse the log file.

For normal mail processes it's possible to use verbose_proctitle for this 
purpose, but this setting doesn't work for proxy/login processes. Is it 
possible to do something similar for proxy processes? Even without displaying 
the username and IP address, it would be useful to be able to see the 
difference between normal (idle/active) login processes, and proxy processes.

Onno


signature.asc
Description: This is a digitally signed message part.


Re: [Dovecot] (no subject)

2007-10-12 Thread Charles Marcus

On 10/12/2007, LDB ([EMAIL PROTECTED]) wrote:

Version: 1.0.beta8


Upgrade... this is way too old...


Re: [Dovecot] Spliting Folders for Efficiency

2007-10-12 Thread Kyle Wheeler

On Friday, October 12 at 11:06 AM, quoth Daniel Watts:
What actually ARE the advantages of a 'one file per folder' format?? 


It depends on the environment. It's exceedingly efficient at storage: 
on a filesystem with 4k blocks, three 1k messages take up 1 block 
(4k), where in a one-file-per-message format they take up 3 blocks 
(12k). Some filesystems have mechanisms of coping with files that only 
occupy a partial block, but those mechanisms tend to be expensive, and  
are often only employed when strapped for space. The 
one-file-per-folder arrangement also helps when doing sequential reads 
(i.e. searches, or loading it into memory, or processing it with a 
filter, or whatever else): when the OS spools the file from disk, it 
loads it up a block at a time, which in a one-file-per-folder format 
is several messages, but in a one-file-per-message format is only ever 
a single message.


I've often contemplated setting up a separate mbox-based namespace in 
my Dovecot setup (e.g. everything in the Archive folder is saved as an 
mbox), just for the space savings.


~Kyle
--
Only the fool hopes to repeat an experience; the wise man knows that 
every experience is to be viewed as a blessing.

   -- Henry Miller


pgpn7Yd1yyMdC.pgp
Description: PGP signature