similar to: expunge not removing attachments?

Displaying 20 results from an estimated 2000 matches similar to: "expunge not removing attachments?"

2019 Feb 12
0
[ext] expunge not removing attachments?
* Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>: > I have a large mail backup folder backup at backup.invalid; I'm cleaning > up daily like this: > > infimum=`date -d "-4 day" +"%Y-%m-%d"` > doveadm expunge -u backup at backup.invalid mailbox INBOX SAVEDBEFORE $infimum > doveadm purge -u backup at backup.invalid > > yet I see this:
2019 Feb 12
1
expunge not removing attachments?
On 12 Feb 2019, at 03:45, Ralf Hildebrandt via dovecot <dovecot at dovecot.org> wrote: > 201629 of 301900 (66.7%) files are modified (mtime) more than 5 days ago, although I just purged everything older than 4 days? I had problems with this a few years ago, and resorted to simply using find to remove the files from the file system /usr/bin/find /usr/local/virtual/*/.Junk*/{cur,new}
2009 Feb 05
1
Questions regarding journal replay
Today, I had to uncleanly shutdown one of our machines due to an error in 2.6.28.3. Durin the boot sequence, the ext4 partition /home experienced a journal replay. /home looks like this: /dev/mapper/volg1-logv1 on /home type ext4 (rw,noexec,nodev,noatime,errors=remount-ro) Filesystem Size Used Avail Use% Mounted on /dev/mapper/volg1-logv1 2,4T 1,4T 1022G 58% /home Filesystem
2010 Oct 05
4
2.0.5: deliver crashing
>From my log: Oct 6 00:10:36 postamt kernel: [2353838.557216] deliver[2799]: segfault at 48 ip b77dd649 sp bfcf3b48 error 6 in libdovecot-storage.so.0.0.0[b778e000+b8000] Oct 6 00:14:39 postamt kernel: [2354082.014722] deliver[6399]: segfault at 48 ip b7779649 sp bf9ca028 error 6 in libdovecot-storage.so.0.0.0[b772a000+b8000] Oct 6 00:28:12 postamt kernel: [2354894.551201] deliver[13972]:
2017 Mar 20
4
Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
Hi! I upgraded the 2.2 packages today (from 2:2.2.28-1~auto+5 to 2:2.2.28-1~auto+8) I now I'm getting an error: Mar 20 13:25:58 mproxy dovecot: auth: Error: imapc(email.charite.de:993): Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) I checked, and alas, I had ssl_client_ca_dir = ssl_client_ca_file = So I set:
2016 Oct 17
2
Massive LMTP Problems with dovecot
* Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>: > I attached gdb top a long running LMTP process: > > #0 sha1_loop (ctxt=0x7f3b1a4d7fa0, input=0x7f3b1a524860, len=0) at sha1.c:216 > input_c = 0x7f3b1a524860 "\211PNG\r\n\032\n" > gaplen = <optimized out> > gapstart = <optimized out> > off = 0 > copysiz =
2016 Oct 17
2
Massive LMTP Problems with dovecot
* Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>: > > It seems to loop in sha1_loop & hash_format_loop > > The problem occurs in both 2.3 and 2.2 (I just updated to 2.3 to check). I'm seeing the first occurence of that problem on the 10th of october! I was using (prior to the 10th) : 2.3.0~alpha0-1~auto+371 On the 10th I upgraded (16:04) to:
2010 Oct 28
4
migration 1.1.7 to 2.0.6
I'm thinking of migrating from 1.1.7 (default RPM on SUSE 11.1) to 2.0.6 compiled from source using the default locations. Any Gotchas to expect that are different to an upgrade from 1.2? Any hints from moving from RPM to compiling from source and retaining the default configuration under /usr/local? TIA -- Brian Duffell RiscPC600 | VRPC Sa-Adjust RISC OS 6.10 96Mb Linux PCs
2010 Nov 21
2
dovecot/imap-login TLS?
# ps auxwww|egrep -i imap-login dovenull 11879 1.4 0.9 83484 77656 ? S Nov20 19:12 dovecot/imap-login [822 connections (822 TLS)] What exactly is TLS in this context? All connections from imap -> imap-login? All clients connecting to an imap process? -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin
2010 Nov 05
5
Ongoing performance issues with 2.0.x
Due to the ongoing performance issues with 2.0.x I switched back to 1.2.15 yesterday evening, with no changes to the machine or my users. (I migrated from 1.2.15 to 2.0.x by converting the existing config) Today, we have MUCH LESS load, with the same number of logins/min. I cannot say what exactly causes this immense increase in load, but one observation is that the time spent in system() has
2012 Feb 18
5
Folder name migration when moving from 2.0.x to 2.1.x?
Today I encountered this after upgrading: Feb 18 18:15:40 postamt dovecot: imap(lehnertr): Panic: LIST: Mailbox name not UTF-8: INBOX.Entw?rfe Feb 18 18:15:40 postamt dovecot: imap(lehnertr): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x4104a) [0xb75cc04a] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x410bb) [0xb75cc0bb] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0)
2017 May 31
2
Bug with 2.2.29-1~auto+25 back to haunt me
> On May 31, 2017 at 6:10 PM Ralf Hildebrandt <Ralf.Hildebrandt at charite.de> wrote: > > > * Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>: > > > So I added > > ssl_ca_file = /etc/ssl/certs/ca-certificates.crt > > > > But alas: > > May 31 16:50:24 mproxy dovecot: config: Warning: Obsolete setting in
2010 Oct 06
2
migration 1.2.5 -> 2.0.5 load increased dramatically
During norml operation this morning we're seeing a significantly increased load on the IMAP server (factor 5, from 5 to 25). Does dovecot need to rebuild index files or perform other IO intensive operations after the upgrade? We're using Maildir Our monitoring shows increased "system" time. We're runnign fewer processes, the IO rate ist identical to yesterday, memory usage
2017 May 31
2
Bug with 2.2.29-1~auto+25 back to haunt me
After upgrading from 2.2.28-1~auto+45 to 2.2.29-1~auto+25 I'm gettings this: May 31 16:44:31 mproxy dovecot: auth: Fatal: passdb imap: Cannot verify certificate without ssl_ca_dir or ssl_ca_file setting May 31 16:44:31 mproxy dovecot: master: Error: service(auth): command startup failed, throttling for 8 secs May 31 16:44:31 mproxy dovecot: imap-login: Disconnected: Auth process broken
2012 Feb 17
4
2.0.X -> 2.1 pitfalls?
Hi all, are there any pitfalls known for the migration from 2.0.18 to 2.1? Can I simply stop dovecot, make install and start again? --Frank Elsner
2008 Apr 10
4
GETQUOTAROOT?
All over a sudden the getquota plugin in SquirrelMail doesn't work anymore. I activated debugging an got: IMAP command sent: a001 GETQUOTAROOT "INBOX" IMAP response received: Array ( [0] => * QUOTAROOT "INBOX" "" [1] => * QUOTA "" () ) A manual test results in: . GETQUOTAROOT "INBOX" * QUOTAROOT "INBOX"
2014 Sep 24
2
LMTP proxying
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:
2016 Apr 29
4
Recent update causes segfault in proxy mode
I'm using the auto builds (2:2.2.24-1~auto+3) for Ubuntu/Debian. The recent upgrade to 2.2.24 cause the follwoing error to appear: I can log in to a mailbox via dovecot I can delete emails Upon expunge, dovecot crashes: Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142514, msgid=, size=10086 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX,
2011 Aug 30
5
Message flags
How do I set message flags in sieve rules in such a way that e.g. Thunderbird is displaying the mail as "important"? Is there a list of hwo flags are interpreted by different IMAP clients? -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax:
2008 Feb 27
3
Another 1.1rc1 signal 6 crash (with backtrace)
Core was generated by /usr/local/libexec/dovecot/imap'. Program terminated with signal 6, Aborted. #0 0xb7fb6410 in __kernel_vsyscall () (gdb) bt #0 0xb7fb6410 in __kernel_vsyscall () #1 0xb7e85f15 in raise () from /lib/i686/cmov/libc.so.6 #2 0xb7e87891 in abort () from /lib/i686/cmov/libc.so.6 #3 0x080ce499 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x80e8f54