similar to: Retrieve Physical Message Filename

Hi Timo... I Try to get the name from the saved email, you said to me, to get this with the get_special, ok... thats work. I get the name with this: mail_get_special(t->save_ctx->dest_mail, MAIL_FETCH_UIDL_FILE_NAME, &fname); By i got some mistake... when i save a email that exist in the same directory, the email is rewrited with another name, but the get_special give me the old one

Hi, My setup: Solaris 9, mbox format, mailboxes NFS mounted from another S9 system, imap. I got the following assert yesterday: Jan 30 19:57:15 emerald dovecot: [ID 107833 mail.error] imap(user): file index-mail-headers.c: line 258 (index_mail_parse_header): assertion failed: (part != NULL) Jan 30 19:57:16 emerald dovecot: [ID 107833 mail.error] imap(user): file index-mail-headers.c: line

We've had another random imap process crash. This is with the original 1.2.5 imap (I haven't applied the patch for two processes creating an index simultaneously): > Oct 03 13:24:56 imap-login: Info: Login: user=<xxxxxxxx>, method=PLAIN, rip=134.225.1.46, lip=134.225.16.6 > Oct 03 13:25:59 IMAP 6067 xxxxxxxx 134.225.1.46 : Info: delete: uid=483, msgid=<xxxxxxxx> > Oct

>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

> > Is this behavior cured, or do you continue to see it? > No, the behavior isn't cured. We still continue to see it with various clients. I have posted a couple of truss outputs, but so far no resolution. Sorry for the slow response. I've been "fighting other fires". Jackie > Jackie Hunt wrote: > >> On Mon, 2007-09-03 at 12:37 +0200, Robert

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

I've been seeing lots of index cache file errors (using mbox on Solaris 8 sparc 64-bit, but with 32-bit Dovecot) since I switched my account to Dovecot 1.2.0 (we're still on 1.0.15 mostly, but I'm hoping to upgrade to 1.1.17+ this summer, or 1.2.x if it's stable enough). e.g. Error: Corrupted index cache file <path>/.imap/INBOX/dovecot.index.cache: field index too large (47

I just noticed one instance of this in the current CVS version: dovecot: Jul 18 15:25:48 Error: 5962 IMAP(mailuser): mbox sync: Expunged message reappeared in mailbox /mailhome/new/o/h/mailuser/mbox (UID 2834 < 2872) dovecot: Jul 18 15:25:48 Error: 5962 IMAP(mailuser): file mail-index-transaction.c: line 129 (mail_index_buffer_convert_to_uids): assertion failed: (*seq != 0) dovecot: Jul

Saw the following in the log after shutting down my client. Feb 22 20:44:47 sbh16 dovecot: imap(mark): Disconnected: Logged out bytes=1755/9765 Feb 22 20:44:47 sbh16 dovecot: imap(mark): Panic: file istream-raw-mbox.c: line503 (istream_raw_mbox_get_start_offset): assertion failed: (rstream->seeked) Feb 22 20:44:47 sbh16 dovecot: imap(mark): Raw backtrace:

http://dovecot.org/test/ - vpopmail authentication fix - many mmap_disable=yes fixes and a few optimizations - pop3 hang fix - mbox fix for "last-uid lost" error (hopefully last one) - mbox fix for losing dirty flag, causing lost message flags mmap_disable=yes seems to be finally working pretty well. There should be no more cache file related errors with it enabled. I'm still

Implements more verbose imap logging (when client exits). Similar to existing logging in POP3. Due to the nature of imap and my incomplete understanding (of the dovecot code) the session statistics reported have varying accuracy. Much better than nothing IMO. Cheers, Jens ----------------------------------------------------------------------- 'This mail automatically becomes portable

100% reproducible. User is using alpine to write an email. Continue postponed composition (answering "No" won't erase it)? y -> [>Empty folder! No messages really postponed!<] Can't delete {mproxy.charite.de/ssl/novalidate-cert/user=theusername}postponed-msgs Setup: ====== http://wiki2.dovecot.org/HowTo/ImapcProxy coredump available for further inspection Full

Hi, I've been having an issue with the indexer giving me errors on mailbox in dovecot. I managed to narrow it down to a specific email in that mailbox. Various dovecot functions have issues with this email. The email itself is just spam. I can email it to you if you want to analyse it. I did run it through mbox-anonymize but its not clear to me that that would be of any use. Happy to email

On 04/11/2015 02:39 AM, Hardy Flor wrote: > I had been on 3/12/2015 pointed to the lack of documentation of "doveadm > save". It was in the changelog of 2.2.16. Unfortunately this is not unique. Dovecot's documentation is at all times significantly lagging behind the code, this is the MO for this project. I guess someone will say "contributions are welcome". There

Hi, I'm testing Dovecot v2.3.9.2. So, I found a problem that a Dovecot process termed with Panic, like below: Feb 10 08:50:09 imap(user1 at example.com)<38440><p9ec0zSeSIQKEAIK>: Panic: file message-snippet.c: line 71 (snippet_add_content): assertion failed: (*count_r <= size) Feb 10 08:50:09 imap(user1 at example.com)<38440><p9ec0zSeSIQKEAIK>: Error: Raw

Hello, Latest HG assert crashes with imap(user): Panic: file mail-storage.c: line 1836 (mailbox_transaction_begin): assertion failed: (box->opened) Full backtrace is attached. Thanks, e-frog -------------- next part -------------- Core was generated by `dovecot/imap'. Program terminated with signal SIGABRT, Aborted. #0 0xb775d424 in __kernel_vsyscall () (gdb) bt full #0 0xb775d424 in

Hi, I'm running 2.2.36 (as provided by openSUSE in their server:mail repository) and at least at one of my systems LMTP is crashing regularly on certain messages (apparently a lot of them). Sometimes (but not always a backtrace is posted to the logs: 2018-07-11T07:34:56.741848+02:00 saruman dovecot: lmtp(14690): Fatal: master: service(lmtp): child 14690 killed with signal 11 (core dumps

I downloaded and installed dovecot 1.1 nightly build yesterday. Here is a the errors I collected from the log file. dovecot: Aug 15 14:19:29 Error: IMAP(use at doamin): Log synchronization error at seq=7,offset=24 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 2 dovecot: Aug 15 14:19:29 Error: IMAP(use at doamin): Log synchronization error at

Can you help me maybe? I don't see the bug. QUOTA=maildir QUOTA_RULE='*:storage=100M' MAIL_PLUGINS="antispam quota" MAIL_PLUGIN_DIR=/home/johannes/Projects/dovecot/antispam gdb --args /home/johannes/Projects/dovecot/dovecot-1.1/src/imap/imap GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Hi Timo !! I rewrite the copy function from mailbox (using a plugin) My rewrite is like this: static int emexis_antispam_copy(struct mail_save_context *ctx, struct mail *mail){ struct mailbox *box = ctx->transaction->box; union mailbox_module_context *zbox = EMEXIS_CONTEXT(box); struct mail_private *_mail = (struct mail_private *)mail; union mail_module_context *zmail =