RFCs 2822 and 822 specify date formats to be used by email. This module parses and emits such dates.
RFC2822 (April 2001) introduces a slightly different format of date than that used by RFC822 (August 1982). The main correction is that the preferred format is more limited, and thus easier to parse programmatically.
Despite the ease of generating and parsing perfectly valid RFC822 and RFC2822 people still get it wrong. So this module provides four things for those handling mail dates:
A strict parser that will only accept RFC2822 dates, so you can see where you're right.
A strict formatter, so you can generate the right stuff to begin with.
A loose parser, so you can take the misbegotten output from other programs and turn it into something useful. This includes various minor errors as well as some somewhat more bizarre mistakes. The file t/sample_dates in this module's distribution should give you an idea of what's valid, while t/invalid.t should do the same for what's not. Those regarded as invalid are just a bit too strange to allow.
Interoperation with the rest of the DateTime suite. These are a collection of modules to handle dates in a modern and accurate fashion. In particular, they make it trivial to parse, manipulate and then format dates. Shifting timezones is a doddle, and converting between formats is a cinch.
As a future direction, I'm contemplating an even stricter parser that will only accept dates with no obsolete elements.
Package Version | Update ID | Released | Package Hub Version | Platforms | Subpackages |
---|---|---|---|---|---|
0.403-bp156.3.1 info | GA Release | 2023-07-22 | 15 SP6 |
|
|
0.403-bp155.2.10 info | GA Release | 2023-05-17 | 15 SP5 |
|
|
0.403-bp154.1.17 info | GA Release | 2022-05-09 | 15 SP4 |
|
|
0.403-bp153.1.14 info | GA Release | 2021-03-06 | 15 SP3 |
|
|
0.403-bp152.1.9 info | GA Release | 2020-04-16 | 15 SP2 |
|
|