similar to: 2 panics, 1 segmentation fault in dovecot 2.3.0 (fts)

> On January 27, 2018 at 4:19 PM Infoomatic <infoomatic at gmx.at> wrote: > > > Hi, > > While testing our migration to dovecot 2.3.0, we encountered 2 panics, 1 segmentation fault while we wanted to rebuild the solr indizes. Problem [1] was encountered while rebuilding the indizes, and now I don't know how many mails/documents are indexed or where it got stuck. [2]

thanks for your input. Bill: deliver is just a symlink to dovecot-lda Stephan: I don't know, and and it even does not work when I use deliver -f "postmaster at ourdomain.internal" - I get the same error message. A part of the mail I got when using 2.2.23: Return-Path: <MAILER-DAEMON> Delivered-To: user1 at ourdomain.internal Received: from localhost (localhost [127.0.0.1])

Hi, I just upgraded from dovecot 2.2.19 to 2.3.2. "doveadm backup" worked fine in v 2.2.19, but now panics (user with shared folder): /opt/dovecot/bin/doveadm backup -u testuser -1 sdbox:/tmp/testuser dsync(standl2): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(standl2):

Hello, I am currently testing the upgrade from our dovecot v2.2.23 to 2.3.0. I have a strange problem with lda. We use bounce mails for internal users if they try to send virus/spammails. The exact same config works with 2.2.23, but not with 2.3.0. The relevant postfix/master.cf part: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail

I still find impediments to the adoption of any of those "solutions". Too many software dependencies, like PHP, DB, python, and a virtual machine. --- There are two portable file formats for calendar and contacts that work across applications and systems, but no server that can use them, and use them safely. Sent from ProtonMail Mobile On Wed, Aug 23, 2017 at 10:41 AM, Infoomatic

Hi, yesterday I created a new mailbox; ever since (and only for the new mailbox) I am getting these errors: 2015-06-12T00:00:29.808526+02:00 mail dovecot: indexer-worker(xxx at example.com): Error: fts_solr: Lookup failed: Bad Request 2015-06-12T00:00:29.808560+02:00 mail dovecot: indexer-worker(xxx at example.com): Error: Mailbox INBOX: Status lookup failed: BUG: Unknown internal error Is

https://github.com/st3fan/dovecot-xaps-daemon Works PERFECTLY. I use it on CentOS 6 and 7. Thanks, Steffan Cline steffan at hldns.com 602-793-0014 > On Jan 8, 2020, at 2:39 PM, infoomatic <infoomatic at gmx.at> wrote: > > ?I have no idea about that Mac proprietary stuff ... however, > https://doc.dovecot.org/configuration_manual/push_notification/ might be > a

Now that Apple has abandoned mail server capabilities in macOS Server.app we have to move to an open source solution. I have done this using Macports and it works well (no thanks to Apple as it never published the in 2018 promised migration info for mail services). The MacPorts Apple Push Notification variant based on a patch written a few years ago for dovecot supports APNS but it requires you

Hello Together Please witch add-on possibilities exist to synchronize the Calednar with Dovecot and Postfix. Can give me here any a possible direction ? thanks regards Mauri

Hi, I have already mentioned this in http://www.dovecot.org/pipermail/dovecot/2014-November/098592.html I could reproduce the errors above in a self-compiled v2.2.18 and the prebuilt packages from xi.rename-it.nl (in addition to version 2.2.15 mentioned in the link) The problem occurs when enabling fts_tika in the plugins (tried tika 1.6, 1.7 and 1.8). I tried to move a folder of my mailbox

No reason to tell me about security, I just need chmod for my tests. Where to change it ? On Thu, Jan 25, 2018 at 12:00 PM, <dovecot-request at dovecot.org> wrote: > Send dovecot mailing list submissions to > dovecot at dovecot.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://dovecot.org/mailman/listinfo/dovecot > or, via email,

When performing an imap search, I hit the following assertion failure: imap(vmail): Panic: file unichar.c: line 128 (uni_ucs4_to_utf8_c): assertion failed: (chr <= 0x40000000) imap(vmail): Error: Raw backtrace: /usr/lib/dovecot/imap [0x80c7f7f] -> /usr/lib/dovecot/imap [0x80c7d6a] -> /usr/lib/dovecot/imap [0x80d8616] -> /usr/lib/dovecot/imap(uni_utf8_to_decomposed_titlecase+0x9f)

Hello, I have some mailbox with error on index-worker process on dovecot 2.3.0 If I move the same mailbox to dovecot 2.2.33.2 this problem dos not happen. See below the backtrace: May 18 10:33:55 Error: imap(xxxxx)<249924><Xpj77npscpYKAQMQ>: indexer failed to index mailbox INBOX May 18 10:33:55 Fatal:

Hi list, ? After spending quite some time to figure out how users can share folders I now hope someone of you could help me out. I am quite sure its just a stupid mistake/misunderstanding?... I am using Ubuntu 12.04 LTS with the shipped dovecot 2.0.19 When I login via telnet as user1 I get the following: 1 create folder1 1 OK Create completed. 2 setacl folder1 user2 rli 2 OK Setacl complete. 3

Hello! I'm moving Dovecot from a FreeBSD Jail (on ZFS using Maildir) to an Amazon EC2 Debian host. 1) I was on Dovecot 2.1 on my FreeBSD system but upgraded it to 2.2 so I could use dsync for the transfers. Is dsync the best way to migrate my data? 2) On the new Debian host, is there a better filesystem than EXT4 that I should use for the mail storage? 3) On the new host, is mdbox

Hi, did you have time to investigate about 'Panic: file unichar.c' bug ? Because I have the same problem with a 2.3.0 installation without virtual plugin. Thanks, Marco On 2018-01-03 16:52, Aki Tuomi wrote: > This is not a bug in virtual plugin, but in some email which contains invalid unicode sequence somehow. Can you send me a core file? This should not have occured ofc but

Hi there! I compiled dovecot 2.3 from git. Because there is already a bug in virtual-plugin, and i hoped, it get fixed... but it doesn't. So this is the error-message from the log J?n 03 16:27:08 aldebaran dovecot[26460]: indexer-worker(jakob)<26476><qQ6g1+BhIJvAqAAO:sjYhMTH2TFpsZwAAk1Mx3g>: Panic: file unichar.c: line 160 (uni_ucs4_to_utf8_c): assertion failed:

Hi, I'm working with dovecot 1.0.beta2 for pop3 only and have set index=memory, so no indizes are created on the disk. pop3_uidl_format is set to %f. The maildirs are located on an nfs-share. So generally, this setup is very similar to what qmail-popup and qmail-pop3d does. However, everytime I'm switching from qmail-pop3d to dovecot, the system load increases from less than 2 to more

Hi, I played around a bit and tried to get tika to run with dovecot. In the end I was at least a bit successful. However, when I tried to index my inbox with "doveadm index -A '*'" I get: doveadm(infoomatic): Error: fts_tika: PUT http://localhost:8081/tika failed: 500 Server Error doveadm(infoomatic): Warning: I/O leak: 0x7f4f697bb170 (line 127, fd 24) doveadm(infoomatic):

On 08/23/2017 07:07 PM, Rupert Gallagher wrote: > I still find impediments to the adoption of any of those "solutions". Too many software dependencies, like PHP, DB, python, and a virtual machine. --- There are two portable file formats for calendar and contacts that work across applications and systems, but no server that can use them, and use them safely. You will need however a