similar to: libtoolize warnings when building

Displaying 20 results from an estimated 4000 matches similar to: "libtoolize warnings when building"

2017 Aug 01
3
configure.ac
Hi, Just a quick mail to mention that I cannot generate a new configure script using autoconf or autoreconf. I had edited the configure.ac and thought ... "oh, that's my fault", but then I tried it on R-patched and R-3.4.1 without touching configure.ac and had the same problems. The "building R packages" documentation seems to suggest that "autoconf" should take
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
2009 May 22
2
"Panic: file client.c: line 354: unreached"
>From my log today: May 22 07:38:48 postamt dovecot: imap-login: Disconnected (no auth attempts): rip=141.42.245.68, lip=141.42.4.250 May 22 07:39:29 postamt dovecot: imap-login: Disconnected (no auth attempts): rip=141.42.245.68, lip=141.42.4.250 May 22 07:39:50 postamt dovecot: imap-login: Disconnected (no auth attempts): rip=141.42.245.68, lip=141.42.4.250 May 22 07:39:50 postamt dovecot:
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:
2018 Mar 05
1
[ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
* Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>: > > From the code in lib-smtp/smtp-address.c function smtp_address_write, it > > looks as though the assertion will happen whenever there is a non ascii > > char that is also non qpair in the local part, ie > > !smtp_char_is_atext(*p) and !smtp_char_is_qpair(*p). > > Could somebody please point me in the
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
0
Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
* Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>: > 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: I was able to determine the last working version: 2:2.2.28-1~auto+6 and the first "broken" version: 2:2.2.28-1~auto+7 -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung
2017 May 31
0
Bug with 2.2.29-1~auto+25 back to haunt me
* 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 /etc/dovecot/conf.d/10-ssl.conf:36: ssl_ca_file has been replaced by ssl_ca = <file > > Gnarf! As you can see I do HAVE ssl_ca in my doveconf -n output! > >
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:
2010 Oct 11
0
AUTOREPLY Re: 2.0.5 masteruser problem with uncached users
Vielen Dank f?r Ihre Email! Ich bin heute leider nicht im B?ro, erhalte Ihre Email aber trotzdem. In dringenden F?llen k?nnen Sie mich auch per Handy erreichen: 0177-7372923. Mit freundlichen Gr??en aus Sarstedt Hauke Hagedorn -- Hagedorn Internet- & Veranstaltungsdienstleistungen Wenderter Str. 37d 31157 Sarstedt Ust-Id DE 256037115 Tel: +49 5066 917 339 1 Fax: +49 5066 917 339 9
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
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
2012 Jan 03
1
Deliver all addresses to the same mdbox:?
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
2018 Mar 05
1
[ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
* A.L.E.C <alec at alec.pl>: > On 03/02/2018 03:32 PM, Ralf Hildebrandt wrote: > > The address causing the error is: > > > > From: =?utf-8?Q?Dorit_M=C3=BCller?= <d.m?ller at JOMEC.de> > > > > Note the "umlaut" in the email address... :) > > This is about SMTPUTF8 (RFC6531). Looks like your only option is to disable >
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
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
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]:
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
2012 Aug 26
4
Recipe for "admin-less restore"
Is there a way for setting up dovecot in such a way that a user can "jump back in time" to an old mailbox "state" in order to retrieve his accidentially deleted mail? -- 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: +49 30 450