Re: Danga mailing list is an earlytalker?

[Elliot Foster]

For shame, thinking that I sullied Danga.

The root cause appears to have been postfix being configured with a 
(relatively) low timeout on helo/connect.  It was not so much that the 
server was speaking early as much as it was the remote server closing 
the connection.

Perhaps we could put some effort into differentiating an early talker 
from a "quitter before I say hello?"

Elliot

Elliot Foster wrote:

Elliot Foster wrote:

I noticed that I hadn't received any of my danga mailing list content 
in a while, and checked my logs to find:

@4000000044662b4a2f63f34c 28892 D check_earlytalker 
207.7.148.197:56598 216.218.240.174:25   Connecting host started 
transmitting before SMTP greeting

Which appears to be the danga list server.  Is anyone else seeing this?


I sent an email to the list manager of the danga lists, and whipped up 
ye olde plugin.  What are other people using for whitelist purposes?

I would use devin carraway's whitelist plugin, but it appears to be an 
all-or-nothing whitelist, whereas I would like to have different 
levels of whitelist.  Allowing someone to be an earlytalker but still 
perform a spam scan on it, for example.

Have I mentioned lately that I love qpsmtpd?

#!/usr/bin/perl
#

sub hook_connect {
  my ($self, $transaction) = @_;
  my $connection = $self->qp->connection;

  # Check if this IP is whitelisted
  my $client_ip = $self->qp->connection->remote_ip;
  if ( -e "config/whitelist/$client_ip" ) {
    if ( -e "config/whitelist/$client_ip/earlytalker" ) {
      $self->qp->connection->notes('whitelistclient', 'earlytalker');
    }
  }

  return (DECLINED);
}