Skip to content

[bug] Addresses passed as string are not always interpreted correctly #484

@piu130

Description

@piu130

When parsing msg with valid Disposition-Notification-To or Return-Receipt-To the Recipient is not filled correctly. I assume the same applies to Return-Path.

Sample header: Disposition-Notification-To: Fname Lname <fname.lname@domain.ch>
Expected: Recipient{name='Fname Lname', address='fname.lname@domain.ch', type=null}
Actual: Recipient{name='null', address='Fname Lname <fname.lname@domain.ch>', type=null}

The problem happens in OutlookEmailConverter.parseHeader(String headerName, String headerValue, EmailPopulatingBuilder builder) where the header value is passed to EmailPopulatingBuilder.withDispositionNotificationTo(String address).

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions