public:emai:senderverify

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		 Previous revision
Last revisionBoth sides next revision
public:emai:senderverify [2023-07-11 14:35] – created marppublic:emai:senderverify [2023-07-11 15:08] – marp
Line 1: Line 1:
 ====== Verify the real sender ====== ====== Verify the real sender ======
  
-**Better safe, than sorry.** See guide [[public:emai:spam|Spam, Phishing and Malware]] and [[public:emai:malware|Dealing with malware, spam, suspicious content]]+**Better safe, than sorry.** See guide [[:public:emai:spam|Spam, Phishing and Malware]] and [[:public:emai:malware|Dealing with malware, spam, suspicious content]]
  
 Everytime you receive any email, verify the true sender. Regardless of detecting email as a suspicious by the spamfilter. How difficult it is and how to do it exactly depend on the email client. But shortly saying: Everytime you receive any email, verify the true sender. Regardless of detecting email as a suspicious by the spamfilter. How difficult it is and how to do it exactly depend on the email client. But shortly saying:
Line 7: Line 7:
   - See the complete address in the form of somebody@somewhere.domain We do not allow outside sender to spoof @cerge-ei.cz domain.   - See the complete address in the form of somebody@somewhere.domain We do not allow outside sender to spoof @cerge-ei.cz domain.
   - In case of any doubt, doublecheck it by call or email ask.   - In case of any doubt, doublecheck it by call or email ask.
-  - Read the next articles as an example how to check real sender. The last article helps you to analyze the complete message path protocol, if you need it.\\ Do not worry, it seems difficult, but in fact the quick proof can be simple. Is the header too complex, too long and with server addresses from outside of cerge-ei domain? Then it could not be the true cerge-ei message.+  - Read the next articles as an example how to check real sender. The last article helps you to analyze the complete message path protocol, if you need it. \\ Do not worry, it seems difficult, but in fact the quick proof can be simple. Is the header too complex, too long and with server addresses from outside of cerge-ei domain? Then it could not be the true cerge-ei message.
  
-[[https://ithelp.brown.edu/kb/articles/view-a-sender-s-email-address-in-gmail | How to see the real email sender in Gmail]] +[[https://ithelp.brown.edu/kb/articles/view-a-sender-s-email-address-in-gmail|How to see the real email sender in Gmail]]
- +
-[[https://lifehacker.com/how-can-i-find-out-where-an-email-really-came-from-1190061668 | How to find the true sender in the message header]]+
  
 +[[https://lifehacker.com/how-can-i-find-out-where-an-email-really-came-from-1190061668 |How to find the true sender in the message header]]
  
  
  • /var/www/html/dokuwiki/data/pages/public/emai/senderverify.txt
  • Last modified: 2024-01-12 15:09
  • by marp