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
postconf mail_version
mail_version = 3.7.3
perldoc Mail::Milter::Authentication | grep version
version 3.20221006
perldoc Mail::AuthenticationResults | grep version
version 2.20210915
In order to know if this is a known issue, It would be useful if you could provide a sample of the authentication header that is actually been parsed and it is trggering this error.
An existing Authentication-Results header could not be parsed, It will be present in the resulting message with a modified header name.
I think the best change here is to update the logging to show the header that could not be parsed.
running,
where authentication_milter runs in SMTP mode,
i notice in logs lots of these "unexpected token" errors,
where,
seems to be involved.
Known issue?
Or, what add'l info/tests are needed here to track it down?
The text was updated successfully, but these errors were encountered: