similar to: Plugin Compatibility

Hi,Using Dovecot 1.2.9 with Maildir and Layout=FS.In a plugin, i'm overriding "update_flags":void my_mail_update_flags(struct mail *_mail, enum modify_type modify_type, enum mail_flags flags)For this email which is having its flags updated, I need to retrieve the physical filename of the message.? I see where using:mail_get_special(_mail, MAIL_FETCH_UIDL_FILE_NAME,? &fname);...I

Hello everyone again..... i try to do a plugin... and i see there is a lot of "hook_*" calls in various places.... There is some documentation about this hooks ? like: hook_mail_storage_created = is calling when the email is.... and go on.... Tks.

We are looking to move to Dovecot from a customized Courier implementation.? Our current format is maildir-like. It's basically a filesystem layout...hierarchies are identified by real directories/subdirectories.? Our folder names do have a leading dot and for reasons related to other systems, we do not want to change our format at all.The Layout=FS is very close to working for us.? The?

For migration possibilities, we're considering whether it's possible to have Dovecot run some users using standard Maildir format, while other users would be using filesystem (LAYOUT=fs) format? We could determine which one's users have, but is there a way to tell Dovecot this information, and is it even part of the Dovecot design to deal with this scenario? Thanks, Tony

Is there a correct way to tell the client we don't want, and don't support Keywords via a configuration option? If there's no configuration option, would I override "allow_new_keywords" to just return FALSE? Thanks, Tony

The subscription files we're migrating from have a "." for folder separation. We will be using Dovecot's maildir with LAYOUT=fs. It's looking for "/" as the separator in the subscription file. So, obviously we could simply write a script to swap the two characters. However, just curious if there are any options for doing this within a plugin (since we're

Using Dovecot 1.2-9 with Maildir and layout=FS. We have our own delivery pushing messages to the /new and then /cur folder eventually. When I have an IMAP client attached, there is apparently some sort of race going on. I believe that Dovecot is moving files from /new to /cur (and renaming them) before our own delivery gets the job done. This is causing a problem for us. Is there a way

For testing purposes, on a small set of users, we've run the courier-dovecot-migrate.pl script. We are converting from Courier 0.43 to Dovecot 1.2.9. For the most part, things seem to be ok. However, an iPhone IMAP client user is reporting a problem where some of her messages don't show up. Even stranger is the fact that these same messages do appear when using Outlook 2k7 for

Hello, i have a problem with the managesieve plugin and a virtual namespace in v2.0. The managesieve plugin complains about an unknown storage driver virtual when i try to log intot the managesieve. I don't know if this is quite a recent problem or if it exists for a while, as i configured the virtual namspace from scratch. (The virtual namespace itself is working.) Jun 28 13:55:54

I am currently running v1.1.20 and was wondering if there is any compelling reason to upgrade to v1.2 or v2.0? For example is there any security updates in v1.2 or v2.0 that aren't included in v1.1.20? The other major thing I would be interested in knowing is there any speed enhancements in the newer versions? I am using basic PAM Auth and Maildir mailboxes on a Linux box. Let me know

On Sat, March 17, 2007 10:51 pm, Timo Sirainen <tss at iki.fi> said: > Oh, and as for when the rewrite is in CVS, I'm not really sure. I'm > still wondering if I should put it there soon and make the release after > v1.0 be v2.0, or if I should first stabilize the current new CVS HEAD > features (which shouldn't take too long), do a v1.2 release and only > then

http://hg.dovecot.org/dovecot-2.0/ I just did the initial commit for master process rewrite, which marks the beginning of Dovecot v2.0. Several things are still missing/broken, but at least I was just able to successfully log in using imap :) I left v1.3 hg tree there for now, but once v2.0 tree is fully usable I'll just delete the v1.3 tree. Note the new dovecot-master-example.conf, which

I forked the wiki to http://wiki1.dovecot.org/ is the old docs for v1.x http://wiki2.dovecot.org/ is the new docs for v2.0 For now wiki.dovecot.org points to wiki1, but once v2.0 is released I'll change it to point to wiki2. I symlinked the user directory, so users should stay synced between the wikis. The main reason for wiki2 is to be able to describe Dovecot v2.0's actual behavior

Dear R colleagues, I am trying to create a new column in a data frame, which converts values and NA's from another column into binary format. Essentially I need the NA's to become 1 and the rest to be 0. The code I wrote is returning the following error message: Error in if (mort[i, 4] != NA) mort[i, 8] <- 0 else if (mort[i, 4] == : missing value where TRUE/FALSE needed

v1.1.0 is finally getting closer, so it's time to start planning what happens after it. Below is a list of some of the larger features I'm planning on implementing. I'm not yet sure in which order, so I think it's time to ask again what features companies would be willing to pay for? Sponsoring Dovecot development gets you: - listed in Credits in www.dovecot.org - listed in

Hello... Currently in the process of upgrading Samba v2.0.10 to Samba v3.0.x, while conducting some minimal testing, it turns-out that Samba v3.0.x is performing slower than Samba v2.0.10. Set-ups: A. Samba v3.0.x --> Same PC client is accessing the samba share running on Red Hat 4.5 (64bit, HP DL380) which in turn has an NFS mount coming from another SAN attached Red Hat 4.5 (64bit, HP

I am looking to migrate my DC V1.2 from mbox to maildir format....and want to do this in stages, user group by user group rather than in one horrendous fell swoop....since I'd rather fell things didn't happen. Since I'm running sendmail/procmail, I can change the ~/.procmailrc to change the writing of the INBOX, but the IMAP mail location access info is knottier when one wants to

Hi, I'm currently running version v2.0.x in production (using Maildir storage) and it's been working well. I'm interested in moving to version 2.2.x and am preparing a test server to do so. As I have been merging the conf file changes between the two versions I noticed syntax changes for the 90-sieve.conf file. There are now 'locations' and presumably to keep referring to

Any thoughts on this: The primary use for "dovecot" user has been for login processes. But people keep misunderstanding this and try to use dovecot for accessing mails. For years I've been wondering about renaming this user to something else like dovelogin, but it never really seemed practical. So now with v2.0 there are a bunch of new processes, and for example anvil and dict are

http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz.sig Just one fix. Maybe the one big thing in Dovecot v2.0.* will be a test suite, which is run before any release. :) - Cache file handling could have crashed rc20 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: