similar to: Enabling SIS (single instance storage)

Hi everyone, I am currently trying to setup our next dovecot server (2.2.18) with SIS enabled, but I have enconutered 1 problem and 1 question: *1) Same attachment, different filenames* I have a feeling a misconfigured something (or forgot to do something) because SIS almost works, but not quite since 3 identical attachment take 3x the space (see end of email for my SIS config). For 3 the

Hi, I've been working with dovecot SiS for a long time without any problem. This is my configuration for SiS: mail_attachment_dir = /mail/users/attachments mail_attachment_fs = sis posix mail_attachment_hash = %{sha1} mail_attachment_min_size = 128 k With this configuration, I have, for example: # ls -l /mail/users/attachments/27/d1/27d1904ac9947945bf48ea545ec278940d840ed1* -rw-------

Sorry, I have checked before I wrote first post. Based on docs - the path should be in /etc/dovecot/dovecot.conf or /etc/dovecot/conf.d/10-mail.conf (I have Ubuntu 16.04 LTS). I have some familiar lines in 10-mail.conf: #mail_attachment_dir = #mail_attachment_min_size = 128k #mail_attachment_fs = sis posix #mail_attachment_hash = %{sha1} but all these lines are commented out. So - in theory -

Hi there ! I?m using dovecot 2.3.10 (manually compiled on Centos 8 x86_64 - fully updated), XFS filesystem, with mdbox and a separated compressed attachment directory: mail_attachment_fs = sis compress:lz4:6:posix mail_attachment_hash = %{sha256} mail_attachment_dir = /ATTACHMENTS I'm using dovecot LDA (for mail delivery). Everything works fine with the delivery and compression. The

We will be deploying a replacement Dovecot server soon, and we are planning to use maildir for the primary storage, but with an archive namespace using mdbox (or perhaps sdbox), and SIS. Our backup servers and (luke)warm spare server need to obtain full copies of the mail store. For the maildirs I know I can simply use rsync (we already use it here). I'm a little wary of using rsync with

Hello, I'm using dovecot 2.1.16 with SiS configured as: mail_attachment_dir = <mypath> mail_attachment_min_size = 128 k mail_attachment_fs = sis posix mail_attachment_hash = %{sha1} I'm having a few errors like: Sep 18 15:46:32 myotis51 dovecot: imap(igd): Error: Attachment file

Hi I migrated my dovecot server from Maildir to mdbox with saving attachments to external files and enabled SIS a few days ago. Everything works fine except one issue. I have both virtual and system users. Dovecot saves attachments with mode 0600. So I catch such errors for system users: dovecot: lda(wasya): Error: fs-sis: Couldn't read hash file

I'm seeing this: ./17/3c/173c81da2aab91f225f8eb5e8fcc87119be4eff0-b38d990442316a54a90c00008f4649af: SecuriteInfo.com.TR.Kryptik.180736.5155.16748.22498.UNOFFICIAL FOUND ./17/3c/173c81da2aab91f225f8eb5e8fcc87119be4eff0-bc70851b03216a54483f00008f4649af: SecuriteInfo.com.TR.Kryptik.180736.5155.16748.22498.UNOFFICIAL FOUND When scanning the "attachments" directory of my mdbox. How can

Hi, Anyone else experiencing this (Dovecot 2.2.4, attachments stored separately): dovecot: imap(user at kamdha.com): Error: file_istream.open(/home/ example.com/user/attachments/f5/f0/f5f0f2c08c4311fa404d090a703c3b492f2ea718-a52388285a04eb51820c0000d485234e-c92f64f79f0d1ed01e6d5b314f04886c-42501) failed: No such file or directory dovecot: imap(user at example.com): Error: read(BODY[]) failed: No

http://hg.dovecot.org/dovecot-2.0-sis contains the code for it. Otherwise it's the latest (as of writing this) dovecot-2.0 hg tree. Please test if you're interested in SIS. :) Once there's at least some testing, I'll probably add this to v2.0.x since very little of this new code is used when SIS is disabled (which is the default of course). SIS works pretty much like explained in

Sure, I can provide. What is SIS? How did you determine I don't use it (I still learn)? :) These links: https://www.dovecot.org/tools/maildir-obfuscate.pl https://www.dovecot.org/tools/dbox-anonymize.pl gives 403. How to run mbox-anonymize.pl? I suppose I should download it to mailserver. 2018-08-29 7:45 GMT+02:00 Aki Tuomi <aki.tuomi at dovecot.fi>: > Based on this you are not

Based on this you are not using SIS, so I wonder if those are some old emails when you were using SIS? Can you provide an example corpus of such mail? You can use e.g. https://www.dovecot.org/tools/dbox-anonymize.pl https://www.dovecot.org/tools/maildir-obfuscate.pl https://www.dovecot.org/tools/mbox-anonymize.pl https://www.dovecot.org/tools/mdbox-obfuscate.pl to obfuscate the mail. Aki On

Hello, We are migrating our dovecot servers from 2.1.9 to 2.1.15 (or 2.2 if there is a stable version soon) and maildir format to mdbox. Looking for mdbox options I have found options: * mail_attachment_dir * mail_attachement_min_size * mail_attachment_fs * mail_attachment_hash but this options are described with the message: # WARNING: This feature hasn't been tested much yet. Use at

I have read most of the doc on the dovecot website, and couldn't find any info on the single instance storage feature, so I'm posting my questions here. - Are these 3 parameters the only one necessary for single instance storage? I cannot find any doc on this feature on the website; is there anything specific I need to know about them? (the last one isn't exactly self-explanatory). -

Hi all, I'm using dovecot v2.0.11 on fedora14 with postfix. This system was migrated from an old UW mbox system, so users already have ~/mail/INBOX.* files. Now for some reason, dovecot is creating ~/mail/mail/INBOX.* files and somehow not seeing the mail_location properly. I've set mail_location to "mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u", which has worked on a

Hello, I received an e-mail, this includes 9 forwarding, each with a file. These files are not removed from the e-mail and stored in the attachments-directory, although they are larger than 16 KB. For all files the "Content-Transfer-Encoding: base64" is set. The email is stored in completely in "m.00000034" ------------------------------------- doveconf: # 2.2.12:

Hi all, I'm receiving a reproducible dsync backup panic for some of my users. The error message is as follows: dsync-remote(user@<removed>): Panic: file dsync-brain-mailbox-tree-sync.c: line 111 (dsync_brain_mailbox_tree_sync_change): assertion failed: (brain->no_backup_overwrite) dsync-remote(user@<removed>): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x69b70)

Hi Timo, Upgraded to 2.0.14 last night for the director-related features and I noticed an oddity in the logs: Sep 28 09:53:21 director2 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:53:56 director1 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:54:23 director2 dovecot:

Hi, User's mailbox is failing to sync. Log: Error: read(attachments-connector(/path/storage/m.217)) failed: read(/path/attachments/a5/b0/a5b01f595205522593c27457ea51094872f1f2b42b01e90d27d3f9237bc8a2ab-dbf7460d4778b152ec6e00000d189396[base64:18 b/l]) failed: Stream is larger than expected (256088 > 256087, eof=1) (FETCH BODY[] for mailbox INBOX UID 29925) Sounds like issue here:

Hi, I switched from dovecot 1.2.* to 2.0.* for a mail proxy. I try to play with the new cool utility doveadm, but I don't manage to get results from it. # /usr/local/dovecot-2.0.15/bin/doveadm proxy list username proto src ip dest ip port # As 'proxy list'