similar to: trash plugin together with sieve_before ?

It seems we have a few email addresses that are not RFC 5322 compliant, and now that we've started using sieve these are failing. The problem is that we have a few addresses with leading, trailing or double dots in the local part: jan..frode at tanso.net .janfrode at tanso.net janfrode. at tanso.net I believe these has been working fine with everything else in dovecot (lda, lmtp, imap,

I'd like to get the IP-address of the webmail-klient logged in my maillog (for being compliant with coming data retention policies). I've noticed that with login_trusted_networks pointing at my dovecot directors, we get rip=client-ip logged on the backends. How is the proxy providing this to the dovecot backends? Anybody know what magic we need to implement in our webmail-solution to be

We've been collecting some stats to see what kind of benefits UP/SquirrelMail's IMAP Proxy in for our SOGo webmail users. Dovecot is running in High-performance mode http://wiki2.dovecot.org/LoginProcess with authentication caching http://wiki2.dovecot.org/Authentication/Caching During the weekend two servers (webmail3 and webmail4) has been running with local imapproxy and two servers

I now have "mail_home = /srv/mailstore/%256RHu/%d/%n". Is there any way of asking dovecot where a user's home directory is? It's not in "doveadm user": $ doveadm user -f home janfrode at lyse.net $ doveadm user janfrode at tanso.net userdb: janfrode at tanso.net mail : mdbox:~/mdbox quota_rule: *:storage=1048576 Alternatively, is there an easy way

Guess I don't quite get namespaces, but we have the following namespace configured: $ doveconf namespace namespace { hidden = no inbox = yes list = yes location = prefix = INBOX. separator = subscriptions = yes type = private } But when I try running dsync it complains: $ sudo -u atmail dsync -u janfrode at tanso.net mirror mdbox:/tmp/janfrodeboks

I'm in the processes of running our first dsync backup of all users (from maildir to mdbox on remote server), and one problem I'm hitting that dsync will work fine on first run for some users, and then reliably fail whenever I try a new run: $ sudo dsync -u janfrode at example.net backup ssh -q mailbackup at repo1.example.net dsync -u janfrode at example.net $ sudo dsync -u janfrode

I enabled the trash plugin yesterday, adding "trash" to mail_plugins, and configuring the plugin setting "trash = /etc/dovecot/dovecot-trash.conf.ext". But I still see users with lots of files in INBOX.Trash getting bounced because of quota exceeded: postfix/lmtp[26273]:: C89F490061: to=<XXXXXXXXXXXXX at example.no>, relay=loadbalancers.example.net[192.168.42.15]:24,

I have a strange problems with quota on v2.0.14. We have an ldap user directory, and all users should have a mailQuota defined there. My problem is that some users gets the quota enforced, while others don't, and "doveadm user" doesn't seem to agree with "doveadm quota ge gett" Ref: $ doveadm user janfrode at example.net userdb: janfrode at example.net home

On 11/12/13, Jan-Frode Myklebust <janfrode at tanso.net> wrote: > My installation is only serving 1/10 of your size, but long time ago we > migrated off mysql for userdatabase, and over to LDAP. The MySQL data > source had issues (not dovecot related), and didn't seem like the right > tool for the job. A database is a database, a master is a master, and a slave is a slave

Hi This is my first post here so i will be as precise as i can I'm trying to setup a quota system using dovecot postfix and procmail dovecot version 1.2.9 postfix version 2.7.0 I have succesfully modified dovecot config to use fs quota system (so far imap and pop3) It reports correct quotas to imap and pop3 clients (both user and group) What im tryin to do now is to modify

I'm preparing to set up a new set of directors on dovecot-ee-2.1.10.3-1, but would prefer to do this a bit gradually. Will it be OK to set up a ring of directors with 2x dovecot-ee-2.1.10.3-1 and 2x dovecot-2.0.14 ? -jf

I'm having some problems with the sftpserver from yesterdays snapshot. It's working fine on the machine I built it on, but the (supposedly) identical machines I rdisted it to fails (SGI O2, Irix 6.5.11m). The client says: % sftp buskfuru Connecting to buskfuru... Enter passphrase for key '/usr/people/jfm/.ssh/id_dsa': janfrode at buskfuru's password: Received message too

We have both dovecot and a webmail application that are both modifying our users maildirs, so dovecot indexes can be out of sync when the webmail has been messing with the maildirs. We also have a webservice that report how many unread messages a user has in his inbox, which is simply counting files in the maildirs (plus caching the result, and present old values if the directory timestamps hasn?t

We upgraded our two dovecot directors from v2.0.14 to dovecot-ee 2.1.10.3 this week, and after that mail seems to be flowing a lot slower than before. The backend mailstores are untouched, on v2.0.14 still. After the upgrade we've been hitting process_limit for lmtp a lot, and we're struggeling with large queues in the incoming mailservers that are using LMTP virtual transport towards our

I need to migrate 15K users to a new domain name, and plan to use "dsync mirror" in the transition phase. Could someone confirm that this should work: Before giving users access to new-domain do a first sync to get all the stale data over: for user in $old-domain; do dsync mirror $user at old-domain $user at new-domain done Configure sieve vacation filter to forward all messages

I just configured postfix' virtual_transport to point at my dovecot director, but am seeing occational problems like this: Aug 31 11:50:06 smtpgw postfix/lmtp[5339]: 69E2F5410D: to=<email at example.net>, relay=loadbalancers.example.net[192.168.42.17]:24, delay=0.15, delays=0.14/0.01/0/0, dsn=5.5.4, status=bounced (host loadbalancers.example.net[192.168.42.17] said: 501 5.5.4 Invalid

IMHO it would be great if we could both provision and un-provision users without having the provisioning system mess with files in the filesystem. Provisioning new users works fine since dovecot will create all files/directories on first login, but I haven?t found the tools to un-provison them. I see "doveadm mailbox delete" can delete individual mailboxes, but what about indexes,

We have an imap-client (SOGo) that doesn't handle this status output while searching: * OK Searched 76% of the mailbox, ETA 0:50 Is there any way to disable this output on the dovecot-side? -jf

My dovecot directors (v2.0.8) had 3 instances of these yesterday: imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd >= 0) master: Error: service(imap-login): child 17374 killed with signal 6 (core dumps disabled) imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd >= 0) master: Error: service(imap-login): child 1780 killed with signal 6

We have quite a few frontend mail gateways that deliver incoming email trough our dovecot director (lmtp proxy) to the backend lmtp servers, and are seeing this logged on the frontend mail gateways: Sep 5 10:51:56 mailgw1 postfix/lmtp[23443]: 0E2F41C01A: to=<me at example.com>, relay=loadbalancers.example.com[192.168.42.15]:24, delay=61, delays=0.02/0.3/31/30, dsn=4.4.0, status=deferred