I think what Jaded is suggesting, is that you get the sending mail servers IP address and submit it here:https://www.spamcop.net/bl.shtml
Thing is, SpamCop deals specifically with unsolicited bulk email senders, not phishing emails per se. You can check a mail server's IP/fully qualified domain name against: https://mxtoolbox.com/blacklists.aspx
. That means it's evaluated against over 100 real time block lists, some of which will now doubt including known
The sending mail server's fully qualified domain name/IP address will be available in the email headers. Within the header there will be a line like this:
Received: from mail-out.spamhaus.org (mail-out.spamhaus.org
[220.127.116.11]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested) by blah.com (Postfix) with
ESMTPS id 94BC0174073C for <email@example.com>; Thu, 24 Dec 2015 14:55:06
In this instance, the mail server's fully qualified domain name is mail-out.spamhaus.org and it's IP address is 18.104.22.168. Your email client should let you view the headers/source/raw email. Even Microsoft Live Mail/Outlook365/Gmail let you do this in their webmail clients, although the option is often half hidden away on a 'Other actions' menu, usually accessed by clicking '...' next to the reply/reply all/forward/spam/delete options.
A mail server administrator might use spamcop and other real time block lists to prevent a mail server from accepting email from known
spammers/phishers etc.. As an email user, your options are a bit more limited. Some on-line security products include anti-phishing tools that support some mail clients, like Outlook and some will even work with on-line webmail - Avast for example stops me downloading executable files from within Roundcube web mail when I'm using Edge or Explorer. Some research will be needed into the security product to ensure it works in your use case*.
I've italicised the word known
because new spam/phishing sources crop up daily in large numbers. There are other tools that analyse email content to determine whether the email is ham or spam, but with some education these are evaded. These tools are implemented by the big email providers and they are also used on lots of mail servers. There are some tools you can get to work with email clients too - I think a classic old school tool is MailWasher - I'm not even sure it's still a thing.
So in summary, you can dig some information out of the email headers and determine whether or not the email in question has come from a known
spam source. Or you can install an on-line security product that may or may not do this for you, depending on your actual use case.
*Combination of operating system, mail client/browser/webmail service etc. etc.