Paul H Byerly schrieb:
> If I have my computer set
> to 1974 do my posts come through with this date and get lost by folks who
> sort by date?
Of course.
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo
At 7:13 PM -0600 2004/01/14, Paul H Byerly wrote:
and Brad Knowles responded:
You're always free to install Mhonarc, if you prefer.
If it really bothered me I'd do something about it - I just think
it's something to consider tweaking in a future release.
It may be more difficult
I wrote:
> Ultimately a bad guess would be better than something a decade
> or two in the future. Go check out
> http://mail.python.org/pipermail/mailman-users/ and see how things
> like April 2024 and December 2006 make a mess.
and Brad Knowles responded:
You're always free to ins
At 7:04 PM -0600 2004/01/12, Paul H Byerly wrote:
Ultimately a bad guess would be better than something a decade
or two in the future. Go check out
http://mail.python.org/pipermail/mailman-users/ and see how things
like April 2024 and December 2006 make a mess.
You're always free to
I wrote:
> Maybe it would be better to override the
> sending time stamp only when it's, say, 2 days or more away
> from the Mailman server time?
and Brad Knowles wrote:
To really do it properly, you'd have to parse the date/time
stamps on every hop that the message passed through, con
At 12:04 PM -0600 2004/01/12, Paul H Byerly wrote:
That would make a mess of time stamps, especially on an
international list.
Or any list spanning multiple timezones.
Maybe it would be better to override the
sending time stamp only when it's, say, 2 days or more aw
"Andrzej Kasperowicz" wrote:
2
I think that there should be an option allowing to archive mails
according to date of reception of the posts by mailman, and not date set
by user who sends it.
That would make a mess of time stamps, especially on an international
list. Maybe it would be better
