[Dovecot] Lifetime of redirect info stored by Sieve in .dovecot.lda-dupes
Hello,
A quick question.
How long are the Message-ID and recipient of forwarded messages (thru the redirect action) kept in .dovecot.lda-dupes?
According to the code, it could be 24 hours; am I right?
TIA, Axel
Axel Luttgens schreef op 8-5-2014 11:29:
Hello,
A quick question.
How long are the Message-ID and recipient of forwarded messages (thru the redirect action) kept in .dovecot.lda-dupes?
According to the code, it could be 24 hours; am I right?
Yes. Why are you asking?
Regards,
Stephan.
Le 8 mai 2014 à 13:14, Stephan Bosch a écrit :
Axel Luttgens schreef op 8-5-2014 11:29:
Hello,
A quick question.
How long are the Message-ID and recipient of forwarded messages (thru the redirect action) kept in .dovecot.lda-dupes?
According to the code, it could be 24 hours; am I right?
Yes. Why are you asking?
Many thanks for your reply, Stephan.
I'm asking because I've been questioned this morning about following scenario.
Let's say one has a "redirect only" mailbox, having address "triplet@example.com" and a sieve script similar to this one:
redirect "user1@example.com";
redirect "user2@example.com";
redirect "user3@example.com";
discard;When retrieving his messages with his MUA, user1 notices a message that should have been sent to user99. He thus decides to forward that message to user99, and puts triplet@example.com in the Cc: field so as to inform the other users (user2 and user3) that they don't need to bother about that message anymore.
So, you sure guess what happened (for my part, I had to look in the log): no redirect action succeeded for the informative message, since its Message-ID was the same as the original one ("discarded duplicate forward to ...").
One thing leading to another, I then came with that lifetime-related question. ;-)
Axel
Axel Luttgens schreef op 8-5-2014 14:22:
Le 8 mai 2014 à 13:14, Stephan Bosch a écrit :
Axel Luttgens schreef op 8-5-2014 11:29:
How long are the Message-ID and recipient of forwarded messages (thru the redirect action) kept in .dovecot.lda-dupes?
According to the code, it could be 24 hours; am I right? Yes. Why are you asking? I'm asking because I've been questioned this morning about following scenario.
Let's say one has a "redirect only" mailbox, having address "triplet@example.com" and a sieve script similar to this one:
redirect "user1@example.com"; redirect "user2@example.com"; redirect "user3@example.com"; discard;
When retrieving his messages with his MUA, user1 notices a message that should have been sent to user99. He thus decides to forward that message to user99, and puts triplet@example.com in the Cc: field so as to inform the other users (user2 and user3) that they don't need to bother about that message anymore.
So, you sure guess what happened (for my part, I had to look in the log): no redirect action succeeded for the informative message, since its Message-ID was the same as the original one ("discarded duplicate forward to ...").
Ehmm, what mail client is doing this? :)
Afaik, forwarding messages should have a new Message-ID. I've tested this with Thunderbird and it does that properly.
Regards,
Stephan.
Le 8 mai 2014 à 14:51, Stephan Bosch a écrit :
[...] Ehmm, what mail client is doing this? :)
Apple's Mail.app.
Afaik, forwarding messages should have a new Message-ID. I've tested this with Thunderbird and it does that properly.
I should perhaps have written "resend that message" instead of "forward that message"? You know, that action of "reintroducing a message into the transport system", as described in section 3.6.6 of RFC 5322.
In that case, Mail.app adds "Resent-From:", "Resent-Date:" and "Resent-To:" fields to the resent message (but it doesn't add a "Resent-Message-ID:" field, even if it SHOULD do so).
On the other hand, forwarding a message indeed builds a message with a new Message-ID.
Best regards, Axel
On 5/8/2014 5:26 PM, Axel Luttgens wrote:
Le 8 mai 2014 à 14:51, Stephan Bosch a écrit :
[...] Ehmm, what mail client is doing this? :) Apple's Mail.app.
Afaik, forwarding messages should have a new Message-ID. I've tested this with Thunderbird and it does that properly. I should perhaps have written "resend that message" instead of "forward that message"? You know, that action of "reintroducing a message into the transport system", as described in section 3.6.6 of RFC 5322.
In that case, Mail.app adds "Resent-From:", "Resent-Date:" and "Resent-To:" fields to the resent message (but it doesn't add a "Resent-Message-ID:" field, even if it SHOULD do so).
Right.
This should help:
http://hg.rename-it.nl/dovecot-2.2-pigeonhole/rev/3b6917a4807c
Regards,
Stephan.
Le 9 mai 2014 à 01:37, Stephan Bosch a écrit :
[...] Right.
This should help:
http://hg.rename-it.nl/dovecot-2.2-pigeonhole/rev/3b6917a4807c
Fine! I'll now try to find another edge case. ;-)
Thanks again, Axel
participants (2)
-
Axel Luttgens
-
Stephan Bosch