MSGID: 2:221/1.58@fidonet e331cf37
REPLY: 1252.fido_internet@1:340/7 22f16092
PID: OpenXP/5.0.43 (Win32)
CHRS: ASCII 1
TZUTC: -0400
Hello Daniel!

** 07.04.20 - 00:03, Daniel wrote to August Abolins:

 D>Good job. I love doing that on the rare occasion I get an attachment. with
 D>xls I like to save them as zip files, then extract the components and dig
 D>around. It's silly simple how some of these trojans work.

I think the originators deserve a reciprocation of their own medicine.

I have toyed with the idea of replying to the ones that request payment,  
and just send back a message that says, details of payment "are ENCLOSED  
in the attachment. Password is the same as you provided: 1234"  ..and send  
back the file.

Many of these emails are so stupid. I despise those things. There should  
be a away to block them right at the ISP/server side.  I would rather not  
have them delivered to my mailbox in the first place.  Why can't ISP's  
block certain ip addresses right on the spot?

For example, I just received another blatantly stupid email:

====[begin]====

National Publication & Community of Professionals


Dear Valued Candidate,

Congratulations! You have been nominated for a spot in the 2020
Professional Who's Who publication. Starting the New Year with this level
of recognition, branding, and respect will help improve and accelerate
your career.

Please click here to update your professional profile.



Include all your credentials and accomplishments. We want
to be sure we have the most accurate information for our publication team.

====[end]====

Part of the message header is:

Return-Path: 
Delivery-date: Tue, 07 Apr 2020 11:18:35 -0400
Received: from landchimney.icu ([93.177.102.132])
X-EN-OrigIP: 93.177.102.132
From: " Dorothy" 
Date: Tue, 07 Apr 2020 10:14:22 -0500
Subject: "Final steps" to your application approval!


It would be ideal to simply filter 93.177.*.* to the bit-bucket and leave  
my own email program alone.  I simply hate having to waste my own data  
quota to even deal with them.


 D>We don't usually see them at work since I administer our content analysis
 D>system and it soaks everything up.

If I could automate a bit-bucket request to my ISP to "soak up"  
93.177.*.*, that would be something useful for our computers to do.


  ../|ug

--- OpenXP 5.0.43
 * Origin: /|ug's Point, Ont. CANADA (2:221/1.58)
SEEN-BY: 1/123 90/1 103/705 154/10 203/0 221/1 6 360 226/30 227/114
SEEN-BY: 229/101 426 452 1014 240/5832 249/206 317 400 280/464 5003
SEEN-BY: 288/100 292/854 310/31 317/3 322/757 342/200 396/45 423/81
SEEN-BY: 423/120 712/848 770/1 2452/250
PATH: 221/1 280/464 229/426