similar to: quota for subfolder with prefix=INBOX.

Hi all, I start this on in a new thread. I setup the deny-user setting to temporarily prevent users from logging in and (that would be great) also stop mail delivery for said user. All this is because of our upcoming migration. Now it seems that lmtp is ignoring this setting. This is from the logfile: Aug 21 13:01:00 klee dovecot: lmtp(pid): Connect from IP Aug 21 13:01:00 klee dovecot:

Am 2015-04-02 um 17:49 schrieb Reindl Harald: > Am 02.04.2015 um 14:30 schrieb Edwardo Garcia: >> On 4/1/15, Reindl Harald <h.reindl at thelounge.net> wrote: >>> Am 01.04.2015 um 14:33 schrieb Bernd Petrovitsch: >>>> On Mit, 2015-04-01 at 13:07 +0200, Reindl Harald wrote: >>>>> Am 01.04.2015 um 13:04 schrieb Bernd Petrovitsch: >>>>>

Dear all, Despite all the progress we are making in our attempt to make the migration as smooth and transparent for our users there are still some important unsolved issues. One thing that I can't figure out is how to preserve a user's flags that s/he has for mail in a shared mailbox. So far we tried 'doveadm backup -R' as well as the cyrus2dovecot script from here [1]. Both

Am 2015-04-02 um 18:24 schrieb Reindl Harald: > Am 02.04.2015 um 18:19 schrieb Jogi Hofm?ller: >> Am 2015-04-02 um 17:49 schrieb Reindl Harald: >>> Am 02.04.2015 um 14:30 schrieb Edwardo Garcia: >>>> On 4/1/15, Reindl Harald <h.reindl at thelounge.net> wrote: >>>>> Am 01.04.2015 um 14:33 schrieb Bernd Petrovitsch: >>>>>> On Mit,

Hi all, Another question regarding migration. While migrating a mailbox with dsync is it safe to deliver mail via LMTP to the new (target) mailbox or is it wiser to deactivate LMTP delivery to this mailbox until it's fully migrated? And what methods could I use to stop delivery to a mailbox during migration? Our user data is stored on an LDAP server. Cheers, -- j.hofm?ller

Folks, Several questions packed into one email ;) Can dovecot use TLS/SSL on LTMP inet socket? Can I configure dovecot to only let an authenticated user deliver mail via LMTP? Can I tell dovecot to use a user/password for proxying LMTP connections? All this is related to my quest to move from cyrus to dovecot transparently to our users. And if any of the above questions can be answered

Dear list, We are finally back to our task of migrating from cyrus to dovecot. dovecot mostly does what we want in terms of POP3/IMAP server. Now we are preparing for migration. The plan is to use dovecot as proxy for not-yet migrated accounts. This works wonderfully for IMAP but not for LMTP. Here's what I find in the logs when I try to deliver e-mail to the dovecot lmtp port: Jun 25

Dear all, We're slowly progressing towards migration, and now run into dscyn dumping core when trying to sync mailboxes from the old imap server. Needless to say that not one byte get's transferred. On the old.server all I see is a correct login. This is what we get for one example user: server:~# doveadm -v -D backup -R -u USER imapc: doveadm(root): Debug: Loading modules from

Hello, unfortunatly, TLS doesn't seem to work on LMTP, anyway, not by simply put ssl=yet to the lmtp inet_listener. I've tried and when I *openssl s_client -connect* to the lmtp listener I've got the following response : CONNECTED(00000003) 34379118248:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown

Hi all, We face a problem migrating shared mailboxes from an old cyrus server to dovecot. Whereas migrating regular users works like a charm, the shared mailboxes cannot be migrated. dsync/doveadm states: "Error: Failed to access mailbox INBOX: Mailbox does not exist". This is somehow true since the shared mailboxes live not under user.mailbox but rather under shared.mailbox (cyrus

Hi all, We are facing quite large mailboxes (>10GB) in our migration from cyrus to dovecot. I did a test on one mailbox and repeated the sync a couple of times with the expected result that the second, third, etc. sync took only seconds compared to minutes for the first sync. We use this command to sync a mailbox: doveadm backup -R -u USER imapc: Are there any problems to be expected

Hi, I'm trying to migrate IMAP mails from dovecot 1.1.20apple0.5 (osx) to dovecot 2.2.33.2 (ubuntu). I'm using "doveadm backup" to migrate my data. It works fine for all subfolders, but the root INBOX stay empty on the new server. I suspect a problem related with hierarchy separator ("." on previous server, "/" on new) or with the namespace prefix (set to

Hallo, I try to migrate existing imap server to dovecot 1.2 in debian squeeze if I connect to imap://user at host/INBOX Inbox works as expected and I get the content of Maildir/{cur,new,tmp} Maildir/.subfolder already exists if I connect to imap://user at host/INBOX.subfolder I get "folder not found" if I do a imap directory listing (raw mutt config, no subscriptions)

Hi, I upgraded from Dovecot v2.0.16 to v2.1.7 over night and I noticed this morning that one of my daily reports which lists summarised mailbox sizes per user has started listing nonsense for vsizes. The reporting script at its core calls : doveadm -f flow mailbox status -A -t 'messages vsize' '*' It appears that Dovecot 2.1.7 is not resetting the vsize after collating the sum

all, below command not reporting the actual usage report on dovecot 2.2.13. please share your suggestion to how to fix this issue doveadm -f flow mailbox status -A -t 'messages vsize' '*' is just showing rkreddy messages=0 vsize=0 jcplho messages=0 vsize=0 planning messages=0 vsize=0 accounts messages=0 vsize=0 spam.notify messages=0 vsize=0 jsraju messages=0 vsize=0 amarnath

Hi, I was wondering if this is a normal behavior (test was made using Dovecot v2.2.9). In my config, quotas are configured as follows: plugin { quota = dict:Userquota::file:%h/dovecot-quota quota_rule = *:storage=1G quota_rule2 = Trash:ignore } # doveadm mailbox status -u my_user "messages vsize" '*' Trash messages=4997 vsize=229535631 Drafts messages=0 vsize=0 Sent

My group is working with datasets between 100 Mb and 1 GB in size, using multiple log ins. From the documentation, it appears that vsize is limited to 2^30-1, which tends to prove too restrictive for our use. When we drop that restriction (set vsize = NA) we end up hanging the server, which requires a restart. Is there any way to increase the memory limits on R while keeping our jobs from

Hi, my nut version is 2.2.2-6.4, debian lenny The ups we use is a tripplite OMNIVS1000 USB The drivers i tried are tripplite_usb and usbhid-ups, googled very long about the problems, but didn't get it to run. Does someone has experiences or similar problems? lsusb and lsmod are all right in /etc/udev/rules.d/52_nut-usbups.rules I found one line according to the modell ---- # Tripp Lite -

My group is working with datasets between 100 Mb and 1 GB in size, using multiple log ins. From the documentation, it appears that vsize is limited to 2^30-1, which tends to prove too restrictive for our use. When we drop that restriction (set vsize = NA) we end up hanging the server, which requires a restart. Is there any way to increase the memory limits on R while keeping our jobs from

Hello, I'm using a 64bit Linux with 16GB of RAM. I'd like to limit the memory that the R process can use so I'm trying to use --max-vsize switch. However, it is seems that I can't enforce a limit above 2GB. shlomo at hippo:~$ uname -a Linux hippo 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux This WORKS: -------------------- shlomo at hippo:~$ R