Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*"
Favorites infavorites:mine
Status closed:yes
Types is:question
Exclude -[tag]
For more details on advanced search visit our help page
Results tagged with Search options user 70406

Related to email protocols, clients, servers, content, and message format.

could send you an email with a self signed PGP public key, claiming it's really the key of the sender. It's as easy to spoof as the email itself. The responsibility of accepting and trusting it is on … recipients side. Building such feature to email clients would create false sense of security. Retrieving keys directly from key servers sounds like a bit better idea, but it doesn't actually give …
answered May 6 '18 by Esa Jokinen
headers added by your own email system do have the actual IP address the message was received from. This is the reason why any server forwarding the message to another should add its own additional … altogether. Email header usually has an ipv4 originating and a ipv6 like this so I would of thought it would be same or similar. X-Originating-IP: [] x-originating-ip: [2a00:23c2 …
answered Oct 24 '18 by Esa Jokinen
You should contact Gmail abuse, if the headers clearly show the message is actually from Gmail and the message is against their policies or terms of use. If the From: address is spoofed, you can use m …
answered May 11 '18 by Esa Jokinen
By default email is like a postcard: anyone delivering it can read all the contents. On the privacy for the connection (putting the card on an envelope): The connection between mail user agent … (client software) and email server should always be encrypted to protect your passwords, and a webmail must be used over HTTPS. In these circumstances, if both the sender and the recipient are on the …
answered Jan 28 by Esa Jokinen
Relaxed in DMARC doesn't mean completely liberated, but has limitations. From RFC 7489, 3.1.2 SPF-Authenticated Identifiers (emphasis is mine): In relaxed mode, the [SPF]-authenticated domain and …
answered May 16 by Esa Jokinen
blocked features, click here. To always show content from this sender, click here. Unless you enabled the harmful content or clicked any links on the email, you should be safe. If you clicked …
answered Mar 14 by Esa Jokinen
Authentication-Results:; dmarc=none (p=none dis=none) The domain doesn't have DMARC protecting it. This means anyone can send on behalf …
answered Mar 7 by Esa Jokinen
unsigned messages. SPF and DKIM protects your email domain against different threats. The only efficient solution against email spoofing is to use SPF+DKIM+DMARC together in a combination that allows all … your own email scenarios and restricts everything else. To answer the new question after the modification: You need SPF record to match the envelope sender. Your SPF record doesn't need to match …
answered Feb 5 by Esa Jokinen
could be found on ANY email client, but the fewer features a client has, the fewer potential security risks, e.g. Mozilla mentions in Security Advisory 2019-12 about critical vulnerabilities: In … general, these flaws cannot be exploited through email in the Thunderbird product because scripting is disabled when reading mail, but are potentially risks in browser or browser-like contexts …
answered Nov 17 by Esa Jokinen