dovecot - Jul 2015 - Questions about hardlinks, alternate storage and compression

On 14/07/15 08:17, Steffen Kaiser wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Mon, 13 Jul 2015, Gionatan Danti wrote:
>
>> On the other hand, private (per-user) sieve file works without
>> interfering with hardlinks. In a similar manner, disabling sieve also
>> permits dovecot to create multiple hardlinks for a single message.
>>
>> Does someone know if newer dovecot versions change anything in this
>> regard?
>
> LMTP adds Delivered-To header, so all delivered messages are unique and
> you cannot hardlink messages regardless of Sieve.
>
> If Dovecot LDA adds headers, too, I do not know.
>
Mmm... I'm using LMTP, but I can't find the "Delivered-To"
header.
Below you can see an example of successfully hard-linked email [1]

I am missing something?

[1]
Return-Path: <g.danti at assyoma.it>
Received: from mail.gruppocrimi.it
         by mail.gruppocrimi.it (Dovecot) with LMTP id 
VFA8Fj3OmlUStwAA6qgwnw
         ; Mon, 06 Jul 2015 20:51:41 +0200
Received: from localhost (localhost.localdomain [127.0.0.1])
         by mail.gruppocrimi.it (Postfix) with ESMTP id 22AB4A1A85;
         Mon,  6 Jul 2015 20:51:41 +0200 (CEST)
X-Virus-Scanned: amavisd-new at gruppocrimi.it
Received: from mail.gruppocrimi.it ([127.0.0.1])
         by localhost (mail.gruppocrimi.it [127.0.0.1]) (amavisd-new, 
port 10024)
         with LMTP id NC3YcizeDFPO; Mon,  6 Jul 2015 20:51:40 +0200 (CEST)
Received: from mr003msb.fastweb.it (mr003msb.fastweb.it [85.18.95.87])
         by mail.gruppocrimi.it (Postfix) with ESMTP id 4380DA1A7C;
         Mon,  6 Jul 2015 20:51:40 +0200 (CEST)
Received: from ceres.assyoma.it (93.63.55.57) by mr003msb.fastweb.it 
(8.5.140.03)
         id 55501C9F0432631D; Mon, 6 Jul 2015 20:51:40 +0200
Received: by ceres.assyoma.it (Postfix, from userid 48)
         id B7B912643B4; Mon,  6 Jul 2015 20:51:39 +0200 (CEST)
To: gionatan.danti at gruppocrimi.it, g.danti at gruppocrimi.it
Subject: test invio
X-PHP-Originating-Script: 0:rcube.php
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
  format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 06 Jul 2015 20:51:39 +0200
From: Gionatan Danti <g.danti at assyoma.it>
Organization: Assyoma s.r.l.
Message-ID: <ef3149d82ef4350c1c9b6da9c1f03fae at assyoma.it>
X-Sender: g.danti at assyoma.it
User-Agent: Roundcube Webmail/1.0.5


-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti at assyoma.it - info at assyoma.it
GPG public key ID: FF5F32A8

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 14 Jul 2015, Gionatan Danti wrote:
> On 14/07/15 08:17, Steffen Kaiser wrote:
>> On Mon, 13 Jul 2015, Gionatan Danti wrote:
>> 
>>> On the other hand, private (per-user) sieve file works without
>>> interfering with hardlinks. In a similar manner, disabling sieve
also
>>> permits dovecot to create multiple hardlinks for a single message.
>>> 
>>> Does someone know if newer dovecot versions change anything in this
>>> regard?
>> 
>> LMTP adds Delivered-To header, so all delivered messages are unique and
>> you cannot hardlink messages regardless of Sieve.
>> 
>> If Dovecot LDA adds headers, too, I do not know.
>> 
>
> Mmm... I'm using LMTP, but I can't find the
"Delivered-To" header.
> Below you can see an example of successfully hard-linked email [1]
You asked about "newer dovecot versions", v2.2 does so.

- -- 
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVaTjzXz1H7kL/d9rAQK1oAf/fdUuBY8kseVEFa5kyXG01cyUjc3RfBNl
o0EYm+e2hvoz5B4N96pkbmilYjaCtgUw/qlMnGkzFbmJDwrqOiAhxOG71Aewjvbx
q42cXHtw7CsOCr6y+eshNUfU3T20f7wgvyJDqLAOwg/pSP3CjU9m93D2zCqUgDXO
MHuDV1zEEljlrxXmtdG8GI5YlwkBqvWXQuPbXr7PhoQ4HTKhvKHWurGvVkfBlg6k
cpuy40mSWY3ZXwNDcnHP0o82EezGAdgzDE/EoV4fV0JDvANbTjpwwqE4gMW+wOM+
lUJnMyawkVuvfbB85K/tkK+a0lIVnZOwdUy0RaUcJFeZHXdRsixvIg==HzBs
-----END PGP SIGNATURE-----

On 14/07/15 12:26, Steffen Kaiser wrote:
>
> You asked about "newer dovecot versions", v2.2 does so.
>
Fair enough :)

So, with v2.2+ the hardlink approach is irremediably gone, at least with 
LMTP (and without relying to SiS)?

-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti at assyoma.it - info at assyoma.it
GPG public key ID: FF5F32A8

Am Dienstag, den 14.07.2015, 12:26 +0200 schrieb Steffen
Kaiser:
> On Tue, 14 Jul 2015, Gionatan Danti wrote:
> > On 14/07/15 08:17, Steffen Kaiser wrote:
> > > On Mon, 13 Jul 2015, Gionatan Danti wrote:
> > > 
> > > > On the other hand, private (per-user) sieve file works
without
> > > > interfering with hardlinks. In a similar manner, disabling 
> > > > sieve also
> > > > permits dovecot to create multiple hardlinks for a single 
> > > > message.
> > > > 
> > > > Does someone know if newer dovecot versions change anything
in
> > > > this
> > > > regard?
> > > 
> > > LMTP adds Delivered-To header, so all delivered messages are 
> > > unique and
> > > you cannot hardlink messages regardless of Sieve.
> > > 
> > > If Dovecot LDA adds headers, too, I do not know.
> > > 
> > 
> > Mmm... I'm using LMTP, but I can't find the
"Delivered-To" header.
> > Below you can see an example of successfully hard-linked email [1]
> 
> You asked about "newer dovecot versions", v2.2 does so.
> 
I just updated my Dovecot 2.2.13 to the current 2.2.18
This config option was added in the meanwhile:

# Which recipient address to use for Delivered-To: header and Received:
# header. The default is "final", which is the same as the one given
to
# RCPT TO command. "original" uses the address given in RCPT TO's
ORCPT
# parameter, "none" uses nothing. Note that "none" is
currently always
used
# when a mail has multiple recipients.
#lmtp_hdr_delivery_address = final

Doestn't that mean if you set it to none that no Delived-To: header
gets added then?