similar to: dovecot-2 new notify plugin

Hello list, After upgrade to dovecot version 1.2.6 I have noticed some quota malfunctions(users become often overquota). Looking at logs closely I have found that quota value resets to general dovecot-config( quota = maildir:Mailbox quota quota_rule = *:storage=500M quota_rule2 = Trash:storage=10%% ), after dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool.sh command. The problem that

Hello list, I have noticed strange dovecot behavior with exim system-filter. I'm using exim+dovecot setup. My exim configuration have system filter enable, which restrict some attachments, like exe, vbs etc. When message with forbidden attachment received, exim accept the message, then construct bounce-message(Reject reason + original message) and returns it to sender. Trying to deliver such

Hello list, We are using virtual plugin for to provide users two additional folders: Company/all - it contains all messages in user's mailbox Company/favorites - here is flagged messages. Here is namespace part of config file: namespace private { prefix = Company/ separator = / location = virtual:/var/mail/virtual:INDEX=MEMORY:LAYOUT=maildir++ subscriptions = no }

Hello list, My dovecot setup have expire plugin enabled. It is working fine: new records added to database(sqlite), expire-tool successfully expunges old mail, but when expire-tool try to update database record for processed user, I get error in logs: root at mail dovecot 0:0 # /usr/sbin/dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool.sh --test Info: koshikov.n at domain.com/Spam:

Hello list, I have noticed that sieve vacation action breaks some non-english letters in the subject. I tested with russian language, if subject contains letters from specific diapason russian alphabet, the message received with unreadable subject, but text in the body with the same letters looks ok. Here is example of full subject header, it contains russian alphabet: Subject:

Hello list, After enabling virtual plugin in dovecot config, I got imap segmentation faults from time to time. I can't say what event trigs this behavior, but in logs I see: Jul 22 13:55:01 dovecot: Error: child 20908 (imap) killed with signal 11 (core dumped) Jul 22 13:56:43 dovecot: Error: child 19466 (imap) killed with signal 11 (core dumped) Jul 22 14:06:16 dovecot: Error: child 22629

Hello Dovecot users, Relatively many bugs and problems were reported recently in a short period of time. Apparently, now that Dovecot v1.2 is finally stable, the new Sieve plugin is also starting to get used much more. No known bugs remain. Let's hope I didn't spawn any new ones. Apart from the bugfixes I made the deprecated notify plugin implementation compatible with CMUSieve. You

Hello Dovecot users, Relatively many bugs and problems were reported recently in a short period of time. Apparently, now that Dovecot v1.2 is finally stable, the new Sieve plugin is also starting to get used much more. No known bugs remain. Let's hope I didn't spawn any new ones. Apart from the bugfixes I made the deprecated notify plugin implementation compatible with CMUSieve. You

Hi there, I'm running dovecot 2.2.13 on my debian jessie server. When installing my own dovecot plugin, I noticed that there are no notifications coming from the notify plugin. I checked back with the mail_log plugin, but also this plugin doesn't log any notifications when a new mailbox is created; the mail is saved to the new inbox never the less. I ran dovecot 2.2.9 before on my

Hello list, Sorry, if it has been asked, but searching throught list not give possitive answers. After upgrade to dovecot version 1.2.1 expire-tool stoped working. I have changed database format and config file to appropriative 1.2 version but: expire-tool.sh fails with: # dovecot -c /etc/dovecot/dovecot.conf --exec-mail ext /usr/libexec/dovecot/expire-tool.sh Info: Loading modules from

On Tue, 03 Aug 2010 23:16:38 +0200 Leander S. wrote: > Hi Nikita Koshikov, > > when I googled for my SERVERBUG which I'm having right now I found your > configuration. > I'm trying to make use of the antispam plugin as you do. Unfortunately > I'm always getting a [SERVERBUG] error mesage with my MTC when I try > moving mails. The antispam debug.log

Hello Stephan, First of all, thanks for time you spent implementing this useful extension. I have found some ugly behavior with such config: sieve_extensions = +notify +spamtest sieve_spamtest_status_type = score sieve_spamtest_status_header = X-Spam-Scan-Score: (-?[[:digit:]]+\.[[:digit:]]) sieve_spamtest_max_value = 10 Sieve: require

Hello list, How can I compile sieve script under new 0.2.2 version from comandline? Under root: #sievec default-before.sieve sievec(root): Error: user root: Initialization failed: Namespace '': mkdir(/root/data) failed: Permission denied (euid=8(mail) egid=12(mail) missing +w perm: /root, euid is not dir owner) sievec(root): Fatal: Invalid user settings. Refer to server log for more

Hello list, Here is the problem: I have few: passdb { #1 } passdb { #2 } And relative userdb sections. If user not found in 1) section it fallbacks to next one - it's expected and right, IMHO. But when the user exists in both section and password verification fails on 1) database it successfully authenticated on next one. I think this behaviour should be configured. The main goal of 1)

Hello list, My question: is sieve support some kind of "continue" action, to explicit tell server processing rules below current one(if current has triged)? Situation: I have few rules, which fileinto's to different directories. All is working fine, but if I want redirect all my mail for some period of time to another mailbox, I'm adding rule like this, to be processing first.

Hello list, In my dovecot-ldap.ext I have: uris = ldaps://host1 ldaps://host2 ldaps://host2 Today host1 hangs and new connections can't be established with mail server. Connected users worked fine (auth_cache_size = 5 k auth_cache_ttl = 15 mins). At this time - host2 and host3 are working fine, but switching to them was not happen. Why ? In logs I got: Feb 09 10:20:36 imap-login: Error:

Hello list, Today, my users have noticed, that delivery to folders with non-english names is broken. For example, if I create russian directory, it correct encoded and display into mail-client program and my webmail: Encoded: Normal view .INBOX.&BEIENQRBBEI- ???? This is part of sieve script, which routing delivery to russian folder. .... elsif allof (header :contains "Subject"

Hello All! I`m using dovecot 1.2.6 I have folder named in russian "????", and when in filter i wrote: fileinto "????"; all works well. Now i find 2 web applications to manage sieve filters (horde-ingo and squirrelmail/avelsieve) - then creates filter like this: if header :contains "Subject" "????" { fileinto "&BCEEEAQfBB8-"; stop; }

Hello Stephan, First of all, thank you for dovecot-sieve implementation. I see that you are adding X-Sieve header to all outgoing e-mail in cmd-redirect.c /* Prepend sieve version header (should not affect signatures) */ rfc2822_header_field_write(f, "X-Sieve", SIEVE_IMPLEMENTATION); How do you look at adding one more header, for example X-Sieve-Forward-From: Now, when redirect

Hello list, I have found imap_allowed option in dovecot which do exactly what I need, for imap. Is there something similar for pop3 protocol? The main goal for it - is to enable pop3 access to specific users. Or maybe dovecot have some 'pop3=yes' or 'imap=no' args to userdb/passdb sections ? I know future dovecot 2.* versions will support rewriting for protocols, but this is