similar to: Help with Virtual Plugin

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

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:

> 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

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

# 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

On 1 Oct 2019, at 16.45, Ralf Hildebrandt via dovecot <dovecot at dovecot.org> wrote: > > * Ralf Hildebrandt via dovecot <dovecot at dovecot.org>: > >> But why is that? Why would the index file be updated so often? > > BTW: This post is a followup to my "2.3.7 slower than 2.3.6?" post from back in July. Fixed by

* 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 =

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

On 04/03/18 09:55, Stephan Bosch wrote: > Op 3/4/2018 om 9:07 AM schreef John Fawcett: >> On 03/03/18 22:10, Stephan Bosch wrote: >>> Clearly, the relevant specifications don't allow UTF-8 in the local part >>> without email address internationalization (EAI), which Dovecot does not >>> support nor announce yet (although that should be mended somewhat soon).

>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]:

When starting 2.0.5, I'm getting: # /usr/dovecot-2/sbin/dovecot -F doveconf: Warning: service auth { client_limit=4096 } is lower than required under max. load (12288) doveconf: Fatal: execvp(/usr/dovecot-2/sbin/dovecot) failed: Argument list too long Argument list too long? WTF? -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus

> We'll need the `dovecot -n` output first. Here we go: > # 2.2.devel (933d16f): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.devel (63f9b42) > # OS: Linux 3.13.0-98-generic x86_64 Ubuntu 14.04.5 LTS > default_vsz_limit = 2 G > lmtp_user_concurrency_limit = 10000 > mail_attachment_dir = /home/copymail/attachments > mail_location = mdbox:~/mdbox >

> On June 1, 2017 at 1:42 PM Ralf Hildebrandt <Ralf.Hildebrandt at charite.de> wrote: > > > * Aki Tuomi <aki.tuomi at dovecot.fi>: > > > > > 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

3 years ago (!) I aksed about this and finally I implemented it today: >> # NEW >> passdb { >> driver = passwd >> # firstname.lastname at charite.de:password:uid:gid:(gecos):home:(shell):user=realloginname >> args = /usr/local/etc/dovecot.login_via_email >> } >If you're only using it as a passdb, you don't need the uid/gid/home.

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

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

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)

Hi Aki, could you maybe disable the 'edit on doubleclick' feature on wiki2.dovecot.org? Everytime I try to select a word by double clicking on it, I end up in editing mode. It's just a minor thing, but maybe I'm not the only one who's annoyed by this ;) Thanks! Michael

Hey, I have several thousand email addresses, the vast majority of which are definitely no good, and I want to figure out which are good. So I will send out an email to all the email addresses. By making a list of the ones that bounced, and comparing that list with the full list, I can determine which are still good. This is for a non-profit association -- I am not in the spam business.

Today I was looking for some spam and issued this command: ========================================================== doveadm import -u restore at backup.invalid mdbox:/home/copymail2/mdbox INBOX header Reply-To bixrs.com Then I immediately got a crash: doveadm(restore at backup.invalid): Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset <