Displaying 20 results from an estimated 9000 matches similar to: "How do I search for "greetings of the day""
2016 Oct 17
2
Massive LMTP Problems with dovecot
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
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
2019 Jul 15
2
2.3.7 slower than 2.3.6?
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:
============
2019 Oct 01
4
dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp
I set up system copying all mails to a backup system.
This used to work without a hitch - now in the last few days mails
would pile up in the Postfix Queue, waiting to be delivered using the
lmtp transport into dovecot.
So dovecot was being slow, but why? After all, nothing changed.
After reading some articles on stackoverflow I found a way of finding
out which file gets the most IO:
% sysdig
2016 Oct 17
2
Massive LMTP Problems with dovecot
> 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
>
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
2017 Apr 23
1
How to query for headers by regexp?
I need to find all mails with a certain numerical range in my quarantine:
X-Spam-Status: No, score=4.5 tagged_above=2 required=4.6 ...
Assume I'd be looking for 4.5-6.0; so I tried searching for
doveadm import -u restore mdbox:/home/quarantine/mdbox "" \
mailbox INBOX header X-Spam-Status "No, score=4.5"
doveadm import -u restore mdbox:/home/quarantine/mdbox
2012 Jan 06
4
Deduplication active - but how good does it perform?
I have deduplication active in my first mdbox: type mailbox, but how
do I find out how well the deduplication works? Is there a way of
finding out how much disk space I saved (if I saved some :) )?
--
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:
2014 May 07
1
Corrupted mailbox, how to fix?
>From my log:
May 06 16:26:49 imap(loginname): Error: zlib.read(/var/mail/loginname/mdbox/storage/m.94): gz trailer has wrong CRC value at 2412347
May 06 16:26:49 imap(loginname): Error: read() failed: Invalid argument (FETCH for mailbox INBOX UID 3434)
How do I fix that?
--
Ralf Hildebrandt
Gesch?ftsbereich IT | Abteilung Netzwerk
Charit? - Universit?tsmedizin Berlin
Campus Benjamin
2001 Dec 03
2
ext3_free_blocks
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
2020 Jul 27
2
Crash during "doveadm import"
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 <
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
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 =
2019 Oct 16
2
[ext] dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp
* Ralf Hildebrandt via dovecot <dovecot at dovecot.org>:
> * Timo Sirainen <timo at sirainen.com>:
>
> > > BTW: This post is a followup to my "2.3.7 slower than 2.3.6?" post from back in July.
> >
> > Fixed by https://github.com/dovecot/core/commit/5e9e09a041b318025fd52db2df25052b60d0fc98 and will be in the soon-to-be-released v2.3.8.
>
> I
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:
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:
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 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
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