Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-13 23:57 UTC

Message

Re: [milter-greylist] Re: Use real-time black lists *retroactively*!

2005-03-14 by Uriel Wittenberg

>This has to be one of the meanest as well as completely asinine things I've 
>seen someone say to someone who actually makes a good product. A lot of 
>people have trouble spelling.... Now, since you have nothing constructive 
>to say at all

It might help if you'd read a bit more carefully.

I referred to spelling errors PLUS SEMANTIC OBSCURITY.

Is this a quibble?

Not at all. The trouble with you geeks is that you can't explain simple 
ideas simply. And you have no imagination. You assume that the disgusting, 
crappy systems you work with, with all their ludicrous, arbitrary 
limitations and defects, HAVE to be that way. You're incapable of 
comprehending original ideas for doing things a better way.

And your unintelligibility is one of the basic reasons why spam exists at 
all. If you could communicate with human beings, then maybe normal people, 
not just you geeks, would understand the truth: Spam could be ERADICATED. 
Then maybe there'd be hope that the proper legislation would be passed to 
accomplish it.

But I know most techies are happy collecting salaries for jobs that are 
fundamentally a waste of time and wouldn't exist at all if things were set 
up more rationally and efficiently.

You're right, I've never run a mail server. So what? When I was a software 
developer I was always able to make myself coherent to lay people. But most 
techies just can't believe that anyone could fail to know what a DNSRBL is.

Take your own message:

>that computer, which I've allowed to send mail from my mail servers because 
>they're one of my customers, is sending spam messages through my server. My 
>server all of a sudden gets blacklisted.

We were talking about spammers with working return addresses (which get 
blacklisted between send and re-try). So I was thinking of blacklisting a 
spammer's email address, not the whole server he's sending from.

If you run servers that are potential sources of spam, I'd like you to 
explain why you can't have an automatic process that alerts you when a user 
has a high volume of outgoing mail. Why can't you have a bell ring when 
probable spamming is detected -- so someone can promptly look at it and see 
at a glance if it's spam or not? 30,000 users? How often does one of them 
become a spammer? You really can't stop this?

>according to your plan, all other ISPs that use this blacklist must go 
>through and find all the messages....

You seem to have some very labor-intensive procedure in mind, akin to that 
performed by 18'th century clerks. Did I need to spell out that I meant an 
AUTOMATIC process?

>... that are still either in their queue's(not likely) or have been 
>delivered locally on their system.

What can you mean?? If it's been "delivered locally" to the end-user, then 
it's gone, and I absolve the ISP of any responsibility. I merely said the 
ISP should delete PENDING email.

You say "not likely." Your reasons are a mystery. The likelihood is a 
function of the user's frequency in retrieving his email.

>This is also hoping that the messages haven't been downloaded to their 
>MUA(Outlook or OE or Thunderbird).

I'm not "hoping" anything.

>spent the 2-3 hours at least to find the messages that have come from my 
>server

It has always amazed me how techie people accept it as a law of nature when 
their deficient systems require them to perform unbelievably inefficient, 
clerical, time-wasting procedures. They're techies! Yet they can't 
understand which jobs are fit for machines and which for humans.

>they also have to parse each message, take the email address from the From: 
>header, which may or may not be the one that was given in the envelope 
>session, and send that person an email stating that this message has been 
>deleted.

Ditto.

>If my server were blacklisted, then the server that it would be sending to 
>would say "I'm sorry. You're blacklisted. I can't accept mail from you" 
>Then it would be up to my server to say that to the person that sent the 
>email.

So this happens to your 30,000 users when a single one of them gets his 
computer hijacked? I hope you offer good prices.

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.