search for: 026632

I would like to develop a new mailbox format for a very specialized application. Can anyone point me in the appropriate direction to get started writing a plugin? More detail for anyone interested: I need to store mail in a format that's quickly accessible and modifiable to an external process. This is for a very low-volume mail system (averaging less than 50 messages stored at any one

Hello It's any chanse to make support dovecot for dbmail? Maybe in some future, or U working on it? ------------------------ Pozdrawiam / Best regards / Cordialement / S pozdravem Wiktor ?yczywek

Hi, folks. I was wondering if anyone has some sort of guide or reference on plugin development. We are trying to develop a non-filesystem backing store. So basically we do not store mailboxes for users in local filesystem. We do RPC call to fetch from fileservers. Thank you in advance. Chang

Hi I intend to write a new virtual backend for dovecot. Are there any hacking docs describing how the code is organized, eventually also important structs and how to hook myself into the system, or do I have to go the classical way? Thanks --Flavius

Hello, I am researching using dovecot with an SQL database as the storage backend. From what I've read, dovecot only supports mbox style file storage, but I'd like to investigate the possibility of using a database instead. According to http://dovecot.org/pipermail/dovecot/2006-June/013818.html, this possibility has been explored before and has generally been accepted that Dovecot

I'm exploring adding a new storage backend to dovecot, storing mail in some sort of database, and had a few questions. Hoping someone here might be able to help :) -Is all of the 'storage' specific code in housed in lib-storage/index? Would adding a new storage backend be as simple as recreating all of the public functions of the current /mbox or /maildir code such as they pertain to