Displaying 20 results from an estimated 8000 matches similar to: "Merge multiple doveadm commands"
2017 Jun 01
0
Bug with 2.2.29-1~auto+25 back to haunt me
* 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 in /etc/dovecot/conf.d/10-ssl.conf:36: ssl_ca_file has been replaced by ssl_ca = <file
> > >
> > > Gnarf! As you can
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 =
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
> 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 05
2
Startup error dovecot-2.0.5
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
2017 Jun 02
2
Bug with 2.2.29-1~auto+25 back to haunt me
> 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
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 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 23
2
Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
* Ralf Hildebrandt <r at sys4.de>:
> Mar 20 16:10:17 mproxy dovecot: master: Dovecot v2.2.devel (a39b5b2) starting up for imap
> Mar 20 16:10:26 mproxy dovecot: auth: Error: imapc(exchange-imap.charite.de:993): Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
> Mar 20 16:10:26 mproxy dovecot: auth: Error:
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:
2011 Jan 05
5
Login with firstname.lastname instead of loginname - WORKING
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.
2013 Aug 09
2
Error: Threading lost Message ID?
QUERY: THREAD REFERENCES ISO-8859-1 ALL
RESPONSE: [SERVERBUG] Internal error occurred. Refer to server log for more information. [2013-08-09 15:42:34]
Aug 9 15:41:48 postamt dovecot: imap(username) tTbs7oPjfACNKs4m: Error: Threading lost Message ID
Aug 9 15:42:34 postamt dovecot: imap(username) tTbs7oPjfACNKs4m: Error: Threading lost Message ID
What does that mean? WHY has the Message-Id
2009 Jul 15
2
sieve / managesieve: unknown Sieve capability 'imapflags'
$HOME/.dovecot.sieve.log reports:
main_script: line 8: error: require command: unknown Sieve capability 'imapflags'.
main_script: line 8: error: require command: unknown Sieve capability 'notify'.
main_script: error: validation failed.
I'm using sieve (not cmusieve) and managesieve with dovecot-1.2.
SquirrelMail 1.4 is using the avelsieve plugin to created/edit the
sieve
2010 Apr 16
2
"try MD5-CRYPT scheme instead"?
I'm getting a lot of entries like this in my log:
Apr 16 10:10:18 postamt dovecot: auth(default): shadow(doxxxris,141.42.206.38): CRYPT(wrongpassword) != '$1$qSe71xxx$09MoMqNyll.wPLCdSaFuA0', try MD5-CRYPT scheme instead
It seems that changing the password via SquirrelMail (poppasswd)
breaks the authentication scheme somewhat. Users cannot log in anymore.
--
Ralf Hildebrandt
2011 Jan 04
2
Implications of zlib plugin on search operations
Right now I'm compressing all mails older than 31 days and larger than
100k in size.
But what implications does this compression have on search queries
performed by users (user looking for an old mail containing a certain
string).
--
Ralf Hildebrandt
Gesch?ftsbereich IT | Abteilung Netzwerk
Charit? - Universit?tsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203
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
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
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
2018 May 30
2
expunge not removing attachments?
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:
# find attachments/ -type f -ctime +5 | wc -l
7522
# find attachments/ -type f | wc -l
127579
# find
2014 May 16
1
imapc Proxy to IMAPS Exchangeserver?
I'm trying to adapt http://wiki2.dovecot.org/HowTo/ImapcProxy
to our Exchange Server, which has LOGINDISABLED on Port 143, and I
offering LOGIN on Port 993.
How do I go about this?
Simply changing imapc_port to:
imapc_port = 993
doesnt work:
Connected to localhost.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS