reply-to header not signed.

Welcome Guest! To enable all features please Login or Register.

Notification

Error

reply-to header not signed. - Is there a reason this is not signed by default?

Options

Previous Topic Next Topic

BrianWiggins		#1 Posted : Friday, June 17, 2022 4:42:51 AM(UTC)
Rank: Newbie Groups: Registered Joined: 6/17/2022(UTC) Posts: 1 Location: UK		I have noticed that the default list of header to be signed are as below. sender, from, to, cc, date, subject, mime-version, content-type, message-id, references, in-reply-to reply-to is missing from the list. Is there a reason this is missing, or just an oversight? reply-to is included in the recommended list within the DKIM RFC Is there any reason I should not add this header into the signed list manually? Brian


User Profile View All Posts by User View Thanks


	Wanna join the discussion?! Login to your EmailArchitect Support forum account or Register a new forum account.

ivan		#2 Posted : Tuesday, June 21, 2022 2:10:43 AM(UTC)
Rank: Administration Groups: Administrators Joined: 11/11/2010(UTC) Posts: 1,154 Thanks: 9 times Was thanked: 55 time(s) in 55 post(s)		No problem, you can add Reply-To in the header list, there is no negative effect. But it is not a MUST, sometimes the transport agent will change the reply-to header based on the user rule, that is why we don't use it by default.


User Profile View All Posts by User View Thanks

Users browsing this topic
Guest

Forum Jump

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Notification

EXPLORE TUTORIALS

Send Email

Read and Parse Email

DKIM Solution