REPLY: 2:221/1.58@fidonet e331cf37
MSGID: 2:310/31 5e8d6b84
CHRS: LATIN-1 2
TZUTC: 0200
TID: hpt/lnx 1.9.0-cur 2019-01-08
Hi August!

07 Apr 2020 20:14, from August Abolins -> Daniel:

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

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

And what should that do??
THEY know what they are doing.
THEY can deal with it nicely.

This is much better, and funnier:
https://www.youtube.com/watch?v=_QdPW8JrYzQ

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

On what basis should they do so??

But there is a really easy and extremely effective way!
Greylisting.

It is extremely simple, and since I use it the spam mails dissappeared.

It simply refuses the first delivery of the mail.
The RFC says you need to retry, but the spambots never do.
In effect that gets rid of them.
The price you pay is a slight delay for every mail that you receive from a new
address.

The other/additional method is to set up SpamAssassin.
It scores the mail and if the score is too high it does not accept it.
But it is much more complicated to set up and maintain.

CU, Ricsi

... All I ask is a chance to prove that money can't make me happy.
--- GoldED+/LNX
 * Origin: Don't cloud the issue with logic. (2:310/31)
SEEN-BY: 1/123 90/1 103/705 154/10 203/0 221/0 226/30 227/114 229/101
SEEN-BY: 229/426 452 1014 240/5832 249/206 317 400 280/464 5003 288/100
SEEN-BY: 292/854 310/31 317/3 322/757 342/200 396/45 423/120 712/848
SEEN-BY: 770/1 2452/250
PATH: 310/31 280/464 229/426