fix(cache): trim <> from email keys (#1190)

Matt Van Horn and Matt Van Horn created 2 months ago

## What?

Add `<` and `>` to the trim cutset in `normalizeContactEmail` so the
cache key is the bare email regardless of whether the input came from a
header or a UI field. Whitespace and commas continue to be trimmed.

## Why?

Email addresses arriving from `From:` headers commonly come wrapped in
angle brackets (`<[e-mail]>`). The previous trim cutset was `,` only,
so the cache stored the literal `<[e-mail]>` and never matched future
lookups against `[e-mail]`.

Resolves #1122.

Co-authored-by: Matt Van Horn <[e-mail]>

Change summary

config/cache.go | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Detailed changes

config/cache.go

@@ -149,7 +149,7 @@ func LoadContactsCache() (*ContactsCache, error) {
 }
 
 func normalizeContactEmail(email string) string {
-	return strings.ToLower(strings.Trim(strings.TrimSpace(email), ","))
+	return strings.ToLower(strings.Trim(strings.TrimSpace(email), ",<>"))
 }
 
 // AddContact adds or updates a contact in the cache.