similar to: dsync panic

Displaying 20 results from an estimated 200 matches similar to: "dsync panic"

2018 Jul 13
4
dsync panic
I think I get pretty much the same issue: dsync(support): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(support): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xc9e06) [0x7fba8a348e06] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7fba8a348e4a]
2018 Feb 02
1
Dovecot 2.3.0, Panic: file mailbox-attribute.c: line 362 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL)
Hi at all, I have a RHEL7 server with Dovecot 2.3.0 (new installation). I've a problem when trying to dsync from a Dovecot 2.2.24 server. If I try to sync any user with a folder with ACL, dsycn crash with panic: Source server: dsync-local(USERNAME): Debug: sieve: file storage: sync: Synchronization active dovecot: dsync-local(USERNAME): Debug: acl vfile: reading file
2018 Jul 13
0
dsync panic
On 13 Jul 2018, at 21.39, Wolfgang Rosenauer <wrosenauer at gmail.com <mailto:wrosenauer at gmail.com>> wrote: > > I think I get pretty much the same issue: > > dsync(support): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) > dsync(support): Error: Raw
2018 Apr 09
0
Raw Backtrace Error when backing up specific user
Hi, probably since the update to 2.3.1 I can't backup a specific users mailbox. For backup I use the command 'dsync -o plugin/quota= -f -u user at domain backup dbox:/backup/dir' When I execute this command with the -D option, I get to see (above only Debug messages) dsync(user at domain): Panic: file mailbox-attribute.c: line 362 (mailbox_attribute_get_stream): assertion failed:
2018 Jan 25
3
Aw: Re: problem with lda
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])
2018 Jan 24
3
problem with lda
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
2018 Jan 27
2
2 panics, 1 segmentation fault in dovecot 2.3.0 (fts)
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] and [3] encountered while just playing around, since I did not know of "tokenize" and did not find a
2017 Aug 23
2
Aw: Dovecot - Postfix Calender Synchronisation
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
2015 Jun 12
2
fts_solr Bad Request / BUG: Unknown internal error
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
2020 Jan 08
2
Is it possible to enable push notifications for iOS/macOS mail clients on a stock dovecot?
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
2020 Jan 08
2
Is it possible to enable push notifications for iOS/macOS mail clients on a stock dovecot?
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
2017 Aug 23
5
Dovecot - Postfix Calender Synchronisation
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
2010 Feb 10
1
Get some headers Variables
Hello Everyone again !! I'm putting more functions in my plugin, and would need to access a value of one variable that is going to put in the header, how can I get this value by dovecot? example, I have the header: X-ThereisMy: yes How can I get this value inside a plugin ? There is something like getHeaderVar("X-ThereisMy") ?
2006 Jun 20
1
Group-based filesystem quota
Hello. After using Dovecot for over a year, I have just started experimenting with the filesystem quotas, and I have a suggestion for improvement. On my mail server, I use group-based quotas, and would like to have Dovecot be able to report these quotas. It should be simple to implement, requiring only changes to the quota-fs.c file of the quota plugin. Simply changing USRQUOTA to
2015 Jun 16
3
bug in indexer/indexer-worker
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
2018 Jan 25
1
dovecot Digest, Vol 177, Issue 55
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,
2019 Mar 26
2
v2.2.27 Panic: file rfc822-parser.h: line 23 (rfc822_parser_deinit): assertion failed: (ctx->data <= ctx->end)
After some investigation, it turns out it is non trivial to install dovecot-dbg on debian jessie. Sorry I can't investigate further. Jason Aki Tuomi wrote on 25/3/19 6:12 pm: > Can you install dovecot-dbg and try gdb again? > > Aki > > On 25.3.2019 3.20, Jason Lewis via dovecot wrote: >> Hi, >> >> I've been having an issue with the indexer giving me
2017 Jan 24
1
Quota count does not work with lock_method=dotlock
On 24.01.2017 11:31, Tom Sommer wrote: > On 2017-01-24 10:25, Aki Tuomi wrote: >> On 24.01.2017 11:13, Tom Sommer wrote: >>> On 2017-01-18 15:27, mkliewe at gmx.de wrote: >>> >>>> dovecot crashes when I switch the quota tracking from dict to count. >>> >>> I have the same problem, but I use 'dict:file' as quota backend - >>>
2007 Feb 18
1
Possible Bug in quota-fs.c
Hi, I'm using filesystem quotas with dovecot 1.0rc22 on my Linux 2.4.27 box. The quota limit gets correctly reported in kilobytes to the client but the amount of used space is reported in megabytes. In quota-fs.c I noticed that only the currently used space is divided by 1024: Line 241: *value_r = dqblk.dqb_curblocks / 1024; *limit_r = dqblk.dqb_bsoftlimit; After
2009 Aug 11
1
dovecot-1.2.3 (managesieve) crash with backtrace
>From the log: Aug 11 09:07:23 postamt dovecot: IMAP(zensy): Panic: file mail-index-transaction-view.c: line 106 (tview_apply_flag_updates): assertion failed: (map->hdr.record_size <= tview->record_size) Aug 11 09:07:23 postamt dovecot: IMAP(zensy): Raw backtrace: imap [0x80f0411] -> imap [0x80f0482] -> imap [0x80efe29] -> imap [0x80c839b] -> imap [0x80cea95] -> imap