On 7/20/2018 12:06 AM, Stefano Bagnara wrote:
h=from:to:subject:mime-version:sender:list-unsubscribe:content-type:content-transfer-encoding:feedback-id;
I saw some recommendation not to sign "To" but I don't think it is a
good practice (for the generic use case). If you don't sign the To
then an
Hello,
First - Benjamin, Steve's post is not a coincidence - he and I had a
conversation about the specific issue I'm dealing with, which was super
helpful, and I suspect sparked this blog post. I wanted to get a few more
data points, which is why I posted here, but his blog post is indeed very
us
> On Jul 20, 2018, at 9:52 AM, J Orlando Letra via mailop
> wrote:
>
> Hi Email Folks,
>
> recently enom.com stopped showing 'whois' info which used to allow us to
> verify, to some extent, the authenticity of senders.
Enom and everyone else, thanks to (a misunderstanding of?) GDPR.
> An
On 07/19/2018 11:18 PM, Autumn Tyr-Salvia wrote:
Hello Email Folks,
Hi Autumn,
I know signing the From: field is required by spec, but I think
everything else is technically optional. For those of you who have been
in the position of choosing which headers to sign and which not to,
would yo
On Thu, Jul 19, 2018 at 10:18 PM, Autumn Tyr-Salvia
wrote:
>
>
> ... I have lately had some customers with greater-than-usual issues
> relating to ... messages that get forwarded, where the forwarding system is
> changing headers to the point that they break DKIM
>
Aside from this being a great o
Hi,
I am looking for a person that is part of the abuse team of iinet.net.au (or a
form if they cannot be contacted directly). Anyone already had the occasion to
discuss with them ?
Thank you for your help !
Mathieu.
___
mailop mailing list
mail
Here's mine:
h=from:to:subject:mime-version:sender:list-unsubscribe:content-type:content-transfer-encoding:feedback-id;
I saw some recommendation not to sign "To" but I don't think it is a
good practice (for the generic use case). If you don't sign the To
then anyone can "replay" your message to
