Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ReceivedHeader: add parse for Authenticated sender #105

Open
toto4ds opened this issue Jan 18, 2020 · 1 comment
Open

ReceivedHeader: add parse for Authenticated sender #105

toto4ds opened this issue Jan 18, 2020 · 1 comment
Labels

Comments

@toto4ds
Copy link

toto4ds commented Jan 18, 2020

Hi,

Looking at ticket #78, I propose to add parsing "Authenticated sender", example:

Received: from my.mail.host (my.mail.host [193.193.193.193])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
(No client certificate requested)
(Authenticated sender: [email protected])
by my.mail.host (Postfix) with ESMTPSA id 1F2D84BE6E0E
for [email protected]; Tue, 14 Jan 2020 15:48:06 +0700 (+07)

I want to note that the field can be without a domain, example:
(Authenticated sender: postmaster)

Thx

@zbateson
Copy link
Owner

Hi @toto4ds --

I specifically and purposefully left out other parts of a Received header, because there is so much variation and no clear guideline to follow, and because I don't want to chase differences in the wild. You can look at and parse those yourself though by calling $header->getComments() and looking for one that starts with "Authenticated sender:" or something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants