You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some incoming emails, it could be with header Return-Path: <>. This is possible for auto-replies emails.
This library always throws MimeMessageParseException when parsing those emails.
I just implemented a simple empty check which checks for null, "" and "<>". Did this for Return-Path as well as Return-Receipt-To and Disposition-Notification-To.
Will be in release 6.0.0. Thanks for the bug report!
For some incoming emails, it could be with header Return-Path: <>. This is possible for auto-replies emails.
This library always throws MimeMessageParseException when parsing those emails.
related code
The text was updated successfully, but these errors were encountered: