On Fri, Mar 29, 2013 at 09:15:29AM +0100, Axel Luttgens wrote:
> Le 29 mars 2013 ? 02:43, Viktor Dukhovni a ?crit :
>
> > [...]
> >
> >> ...
> >> S: 354 End data with <CR><LF>.<CR><LF>
> >> C: From: <original-sender@sender-domain>
> >> To: <original-recipient1@recipient-domain1>,
> >> <recipient2@recipient-domain2>
> >> Date: ...same date as original message...
> >> Subject: ...same subject as original message...
> >> MIME-Version: 1.0
> >> Content-Transfer-Encoding: 7bit
> >> Content-Type: Multipart/Mixed;
> >> boundary="unique-boundary-string"
> >
> > The message envelope could be quite large, since a message
> > Can have thousands of recipients after virtual(5) expansion.
> > Putting all envelope recipients in the "To:" header risks
> > running into header length limits that cause header truncation
> > Or parsing problems.
>
> Hello Viktor,
>
> Do you think this should be submitted to expansion?
Yes.
> Wouldn't one then lose the original envelope sender and recipient(s)?
Only if one uses virtual alias expansion. To archive the original
external recipients, expand downstream of the archive copy.
Typically, you want to archive who received the message, more so
than who it was sent to.
Actually, when archiving the message envelope as a message body
part, I used to record both the original and the final recipient
for each recipient.
Original-Sender: <address-if-different>
Sender: <address>
Original-Recipient: <address-if-different>
Recipient: <address>
Original-Recipient: <address-if-different>
Recipient: <address>
...
Various representations are possible, for example best-effort
consolidation of consecutive entries with the same original recipient:
Original-Sender: <address-if-different>
Sender: <address>
Original-Recipient: <address-if-different>
Recipient: <address>
Recipient: <address>
...
Original-Recipient: <address-if-different>
Recipient: <address>
Recipient: <address>
...
...
--
Viktor.
