Nigel Moore
My feedback
29 results found
-
259th ranked
Nigel Moore shared this idea ·
-
23rd ranked
An error occurred while saving the comment -
471st ranked
Nigel Moore shared this idea ·
-
28th ranked
Nigel Moore supported this idea ·
-
56th ranked
An error occurred while saving the comment Nigel Moore commented
And today we have these exciting new additions - all apparently addresses that are entirely above board and legitimate, and from which I eagerly await an extra ration of spam (although I was completely unaware previously of their existence):
newsletter@pan.iownyour.org (Congratulations GoKeto)
newsletter@evolutionfitness.site (Market Loans)
newsletter@logofrance.site (Fidelity Life Insurance)
newsletter@weischiropractice.site (National Injury Bureau -Lejeune)
newsletter@@resolsingprosoft.site (McAfee@Partner2023)
renter-infonewsletter@gaam.yourtrap.com (Male Solution)Again, one can commend the honesty of intent of iownyour.org.
However, in sum , a classic example of a potentially good idea implemented without any validation checks, and also apparently without any consideration for how easily it might be exploited for malicious purposes.Nigel Moore shared this idea ·
-
1st ranked
Nigel Moore supported this idea ·
-
183rd ranked
Nigel Moore shared this idea ·
-
259th ranked
Nigel Moore shared this idea ·
-
471st ranked
Nigel Moore shared this idea ·
Scott, it would be prudent to check whether the sender of the good emails that end up in your spam folder is a bigger part of the problem than yahoo.
A suggestion for the next time this happens:
Open the mis-categorized email, click on the three little dots in a line (at the top line after Spam)
From the dropdown choose 'View Raw Message'
Near the top of the raw message find the Authentication grouping
Within that grouping check what the value is for dkim.
If dkim = unknown or fail, that will at least contribute to your good email going into your spam folder because it is not actually not quite good enough.
"DKIM is used to verify that no third party has tampered with data within an email." [https://www.proofpoint.com/us/threat-reference/dkim]
"... enables a company to take responsibility for sent messages that can be verified by mailbox providers. Essentially, it allows the outbound domain to digitally sign email to provide legitimacy for the receiver via email headers.
[https://mxtoolbox.com/dmarc/dkim/roi-of-dkim]
Your senders implementing DKIM (DomainKeys Identified Mail) will probably remove the biggest part of the problem.