fix: decode RFC2047 subjects, OR TO/FROM in to-mode query, tz-aware Date, drop LIST completion line (v0.1.7)
Subject headers were matched/scanned raw (never RFC2047-decoded), so any provider that base64/quoted-printable encodes non-ASCII subjects silently failed subject filtering and code extraction. match_field='to' only server-queried TO, so an older TO-matching message permanently hid a forwarded-From match the client-side check was documented to accept. _age_seconds treated a naive datetime (from a "-0000" Date header) as local time instead of UTC, corrupting max_age freshness on non-UTC hosts. get_folders appended aioimaplib's tagged LIST completion text as a phantom folder name on every call against any RFC-compliant server. Also corrects __init__.py's __version__, which was left at 0.1.5 through the 0.1.6 release. Signed-off-by: disqualifier <dev@disqualifier.me>
This commit is contained in:
+1
-1
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
|
||||
|
||||
[project]
|
||||
name = "aiomail"
|
||||
version = "0.1.6"
|
||||
version = "0.1.7"
|
||||
description = "async IMAP one-time-code retrieval with password/OAuth2 auth and dynamic matching"
|
||||
requires-python = ">=3.10"
|
||||
dependencies = [
|
||||
|
||||
Reference in New Issue
Block a user