| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Patch #1464708 from William McVey: fixed handling of nested comments in mail
addresses. E.g.
"Foo ((Foo Bar)) <foo@example.com>"
Fixes for both rfc822.py and email package.
|
| |
|
|
|
|
|
|
|
|
| |
acceptable to Python 2.4's time.strftime(). This fix mirrors the behavior in
email 3.0. That field is documented as being "not useable" so it might as
well not be buggy too <wink>.
Add a test for this behavior and update a few tests that were expecting a 0 in
this field. After committing I will run the entire Python 2.3 test suite to
ensure this doesn't break any Python tests.
|
| |
|
|
| |
SF #753617. Back port candidate (but low priority).
|
| |
|
|
|
|
|
| |
week. Patch given by Daniel Berlin in SF bug # 732761. Also closes
SF bug # 727719.
Backport candidate.
|
| |
|
|
|
|
|
| |
no address there (perhaps because of invalid characters, it appends
('', '') to the result set.
Closes mimelib SF bug # 697641.
|
| |
|
|
| |
the day in an RFC 2822 date.
|
| | |
|
| |
|
|
|
| |
specifically that dots are allowed in obs-phrase. This fixes parsing
of dots in realnames.
|
|
|
address parsing routines. Closes SF patch #613434.
|