similar to: doveadm import - strange warning

Am 27.07.2015 um 10:51 schrieb Ralf Hildebrandt: > Anybody seen this before? > Seems easy to reproduce... > > * Ralf Hildebrandt <r at sys4.de>: >> I'm using the doveadm import command to extract mails from my backup: >> >> % doveadm import -u restore at backup.invalid mdbox:/home/copymail/mdbox "" \ >> mailbox INBOX header Delivered-To

Currently I'm having massive problems with LMTP delivery into dovcot. dovecot/lmtp processes are piling up, eas using considerable amounts of CPU: # ps auxwww|fgrep dove root 20537 0.0 0.0 18124 1196 ? Ss 15:18 0:00 /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf dovecot 20541 0.0 0.0 9620 1084 ? S 15:18 0:00 dovecot/anvil root 20542 0.0 0.0 9752

Anybody seen this before? Seems easy to reproduce... * Ralf Hildebrandt <r at sys4.de>: > I'm using the doveadm import command to extract mails from my backup: > > % doveadm import -u restore at backup.invalid mdbox:/home/copymail/mdbox "" \ > mailbox INBOX header Delivered-To backup+$SEARCHPATTERN at backup.invalid > > This works like a charm, I'm

On a 2.4.15-pre5 system with a 3ware-Escalade-68000 IDE RAID (mode 1) we had the follwing "dmesg" output today: EXT3-fs error (device sd(8,38)): ext3_free_blocks: Freeing blocks in system zones - Block = 16, count = 1 EXT3-fs error (device sd(8,38)): ext3_free_blocks: bit already cleared for block 1052672 EXT3-fs error (device sd(8,38)): ext3_free_blocks: Freeing blocks not in datazone

My users say that "greetings of the day" occurs in academic spam a lot. Since I don't trust my users, I opted to verify this bold claim. But how do I search for a sequence of multiple words? doveadm import -u restore at backup.invalid mdbox:/home/copymail/mdbox "" mailbox INBOX BODY "Greetings of the day" doveadm import -u restore at backup.invalid

Which disk is it? /dev/sda6 or /dev/sdb8 or /dev/sdc6? >From my log: Jun 10 21:25:39 postamt1 kernel: attempt to access beyond end of device Jun 10 21:25:39 postamt1 kernel: 08:06: rw=0, want=1680353324, limit=59954548 Jun 10 21:25:39 postamt1 kernel: EXT3-fs error (device sd(8,6)): ext3_readdir: directory #3473659 contains a hole at offset 1852399616 $ mount /dev/sdb6 on / type auto (rw)

For archiving purposes I'm delivering all addresses to the same mdbox: like this: passdb { driver = passwd-file args = username_format=%u /etc/dovecot/passwd } userdb { driver = static args = uid=1000 gid=1000 home=/home/copymail allow_all_users=yes } Yet I'm getting this: Jan 3 19:03:27 mail postfix/lmtp[29378]: 3THjg02wfWzFvmL: to=<firstname.lastname at

Hi, I had enabled an option in dovecot. mail_attachment_dir = /var/mail/virtual/copymail/attachments After a while I checked /var/mail/virtual and did some cleanup. I did not remember that copymail was specified in dovecot and erased it. Oct 30 10:56:05 mx0 dovecot: imap(hidden): Error:

On 24 Apr 2015, at 13:54, Ralf Hildebrandt <r at sys4.de> wrote: > > * Ralf Hildebrandt <r at sys4.de>: >> I don't find "fts_languages" in the documentation... What should I add >> there anbd where? > > fts_languages = de,en > seems to do the trick. But I wonder if there's something like "all" > and what exactly this setting

I updated dovecot today and all over a sudden I'm getting: Mar 6 14:40:46 mail postfix/lmtp[3150]: 3kz95y3nX3zCtTS: to=<recipient at backup.invalid>, relay=127.0.0.1[private/dovecot-lmtp], delay=88, delays=87/0.94/0.01/0.01, dsn=4.3.0, status=deferred (host 127.0.0.1[private/dovecot-lmtp] said: 451 4.3.0 <recipient at backup.invalid> Too many concurrent deliveries for user (in

How exactly is LMTP proxying supposed to work? According to the example on http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy I'm only seeing "proxy" in the password_query statements. But LMTP never sends a password. IMAP Proxying is working OK: Sep 24 12:51:09 imap-login: Info: proxy(ralf.hildebrandt at charite.de): started proxying to dovecot.charite.de:993:

We would like to provide a self-service restore function to our users using their IMAP client of choice.. Our idea was to use a snapshot (under ZFS, btrfs, whatever) and have it available to the user in a namespace. Unfortunately, but understandably, dovecot doesn't like the mdbox structure to be read-only. Is there any chance to change that? In the meantime, we could use a read-write

I don't find "fts_languages" in the documentation... What should I add there anbd where? doveadm(restore): Error: fts-dovecot: fts_languages setting is missing - disabling -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer

Hi, I use dovecot 2.2.9 on Gentoo Linux and I get lots of these erors in my log file: Dec 4 08:53:37 mx dovecot: auth: Error: close failed in file object destructor: Dec 4 08:53:37 mx dovecot: auth: Error: IOError: [Errno 9] Bad file descriptor What could cause these error messages? My mailboxes are stored on an ext4 filesystem: /dev/vdb1 on /srv/mail type ext4 (rw,noatime) doveconf -n: #

* Edgar Pettijohn <edgar at pettijohn-web.com>: > > Only /etc/dovecot/local.conf should be changed. > > > So you want the standard files to remain unchanged from default settings and override them with your settings in local.conf? Exactly (he said that in his initial mail). -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schlei?heimer Stra?e 26/MG, 80333 M?nchen

We're using dovecot (via LMTP) as a backup for all incoming mail. I upgraded from 2.3.6 to 2.3.7 on the 12th: 2019-07-12 14:35:44 upgrade dovecot-imapd:amd64 2:2.3.6-2~bionic 2:2.3.7-8~bionic and it seems that 2.3.7 is slower than 2.3.6 -- mail to the backup IMAP box is suddenly taking quite some time to get delivered and is piling up in the queue. doveconf -n: ============

I'm using "/usr/bin/doveadm purge -A" to purge the mdboxes of my users. Unfortunately this command terminates prematurely once it reaches a defective mdbox! Is there a workaround for this? Like using doveadm to get a list of valid users and then run "doveadm purge -u" on each of those? -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669

I'm preparing a migration of several mailboxes to another machine. The different useraccounts are distributed to different backend machines by means of a dovecot LMTP/IMAP/POP proxy. Proxying is working really well (now that the kernel does as it should). But how can I "lock" a user during migration? The plan is: ============ * lock the user * kick the user (doveadm kick) *

* Aki Tuomi <aki.tuomi at dovecot.fi>: > Could you send us the gdb bt full backtrace for the core file? Currently I can't get it to create coredumps doveconf -n: # 2.2.devel (3f97702): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (023f391) # OS: Linux 4.4.0-65-generic x86_64 Ubuntu 16.04.2 LTS auth_mechanisms = plain login default_vsz_limit = 1 G imapc_host =

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 10 Jun 2014, Charles Marcus wrote: > On 6/9/2014 5:44 PM, Ralf Hildebrandt <r at sys4.de> wrote: >> That's probably the problem here. The user had LOTS of (duplicate!) >> mails in his inbox. > > Anyone ever found a reliable way to do this? > > It sure would be nice if dovecot could perform this on a per