Harmeet said:
> question: how do you intend to use (String Date) -> (Date object) API.
for comparisons, you might want to have a mailet perform different actions depending
on the date a message was sent, perhaps check if that date is obviously wrong, in the
future for instance, and you want to correct it, or notify someone.
Perhaps you want to close a mailbox to entries posted after x .. or not accept mail
posted before y ..
> The headers often have a format that does not comply with RFC822. 'Date'
> header often does not comply. Part of the 'Recieved' header usu. does, but
> that seems to be a practice not a standard(I think, can anyone confirm)
Date is compulsory and should comply.
Resent-date is optional (primarily for FW messages, obviously.)
Recieved doesn't mention date at all in the message syntax table, but does excuse it
in the description. " time-of-receipt may be specified."
RFC822Date now copes with all of the following cases, are there any more (apart from
the two letter "military" time zones which I'm working on) ..
It doesn't work with the zone in front of the year, b'cos that is not allowed by the
RFC and I haven't found any examples of it (yet), and after all the class is only
claiming to work with dates which *do* comply.
Wed, 3 Oct 2001 06:42:27 GMT+02:10 gets: Wed, 3 Oct 2001 05:32:27
+0100
Wed 3 Oct 2001 06:42:27 GMT+02:10 gets: Wed, 3 Oct 2001 05:32:27
+0100
3 Oct 2001 06:42:27 GMT+02:10 gets: Wed, 3 Oct 2001 05:32:27
+0100
Wed, 3 Oct 2001 06:42:27 PST gets: Wed, 3 Oct 2001 15:42:27
+0100
Wed 3 Oct 2001 06:42:27 PST gets: Wed, 3 Oct 2001 15:42:27
+0100
3 Oct 2001 06:42:27 PST gets: Wed, 3 Oct 2001 15:42:27
+0100
Wed, 3 October 2001 06:42:27 Pacific Standard Time gets: Wed, 3 Oct 2001 15:42:27
+0100
Wed, 3 October 2001 06:42:27 +0100 gets: Wed, 3 Oct 2001 06:42:27
+0100
Wed 3 October 2001 06:42:27 +0100 gets: Wed, 3 Oct 2001 06:42:27
+0100
3 October 2001 06:42:27 +0100 gets: Wed, 3 Oct 2001 06:42:27
+0100
Wed, 3 October 2001 06:42:27 +0100 (BST) gets: Wed, 3 Oct 2001 06:42:27
+0100
d
