On Wednesday, 27 January 2010, 23:40:49 +0000,
Christian Ebert <blacktr...@gmx.net> wrote:
> * E. Prom on Wednesday, January 27, 2010 at 18:10:37 +0100
> > On Wednesday, 27 January 2010, 09:39:22 +0000,
> > Christian Ebert <blacktr...@gmx.net> wrote (extract):
> ^^^^^
> >> I just use postfix:
> >
> > Keeping in mind that you delay an already written mail : The Date header
> > has been generated, so the recipient will see the date/time you wrote
> > the message,
>
> Your attribution agrees with this, it doesn't say "sent".
Yes, easier for references :)
That's a choice to do: which time zone? date sent or received? I love
Mutt, it's possible to choose between %(date), %{date}, %[date].
> > not when you decided it should be sent (unless his MUA
> > shows received date/time, which is not common).
>
> Well, I sent it from Mutt, it could have got stuck e.g. at gmx as
> well -- which indeed happened, gmx was down the other day for
> some time.
>
> Mutt also says "sent", when I send it to may mailserver
> (postfix).
You can affirm that in good faith, but sometimes it can be very hard to
explain your boss a mail can get stuck somewhere (I'm used to being
alleged guilty). And if he's not too ignorant, it's easy for him to look
in the headers to find the delay comes from your own mail server.
There's also the sorting issue : the e-mail will appear before other
e-mails that have been received after.
I prefer using date-received in index, because with date-sent there's
always a mail whose date is 3 years in the future that will keep
appearing as most recent, and it eliminates the risk of a fraudly
written Date header... and that's why I curse all the fetchmail-like
programs who add a Received header by default.
Your postfix solution looks quite practical, I will keep it somewhere.
