Matt Sergeant wrote:
On 25-Feb-08, at 4:35 PM, Jared Johnson wrote:
Using async/check_earlytalker from qp 0.40, I get the following error:
FATAL PLUGIN ERROR: Can't locate object method "AddTimer" via
package "Qpsmtpd::TcpServer" at /usr/share/qpsmtpd/plugins/async/
On 25-Feb-08, at 4:35 PM, Jared Johnson wrote:
Using async/check_earlytalker from qp 0.40, I get the following error:
FATAL PLUGIN ERROR: Can't locate object method "AddTimer" via
package "Qpsmtpd::TcpServer" at /usr/share/qpsmtpd/plugins/async/
check_earlytalker l
On Mon, 2008-02-25 at 17:36 -0500, Guy Hulbert wrote:
> $ find gt -name '*.pm' -exec grep -i AddTimer '{}' \;
Better:
$ find gt -name '*.pm' -exec grep -Hi AddTimer '{}' \;
gt/lib/Danga/TimeoutSocket.pm:Danga::Socket->AddTimer(15,
\&_do_cleanup);
gt/lib/Danga/TimeoutSocket.pm:Danga::Socket->A
On Mon, 2008-02-25 at 16:04 -0600, Jared Johnson wrote:
> > Try: grep -i AddTimer /usr/share/perl5/Qpsmptd/TcpServer.pm
> >
> > the * won't match past the / in the shell. Also try:
> >
> > grep -i add ... | grep -i timer
>
> grep -ri timer /usr/share/perl5/Qpsmtpd/ /usr/share/perl5/Qpsm
Try: grep -i AddTimer /usr/share/perl5/Qpsmptd/TcpServer.pm
the * won't match past the / in the shell. Also try:
grep -i add ... | grep -i timer
grep -ri timer /usr/share/perl5/Qpsmtpd/ /usr/share/perl5/Qpsmtpd.pm
no results there either :/
a quick browse through svn doesn't show an
Hi,
Using async/check_earlytalker from qp 0.40, I get the following error:
FATAL PLUGIN ERROR: Can't locate object method "AddTimer" via package
"Qpsmtpd::TcpServer" at
/usr/share/qpsmtpd/plugins/async/check_earlytalker line 94.
grep can't find AddTimer anywhe
On Thu, 17 Jan 2008 19:59:38 +0100
Hanno Hecker <[EMAIL PROTECTED]> wrote:
> sub connect_handler {
> my ($self, $transaction) = @_;
> my $score = $self->qp->connection->notes("dnswl") || -1;
err, the above line should be:
my $score = self->qp->connection->notes("dnswl");
$score
rted environment (with
hook_skip) ;-) You can easily wrap the earlytalker plugin like shown
below. Don't know if it works, written just here. For apache use
apr_(connect|data)_handler as sub names (and in the SUPER:: calls).
# dnswl_earlytalker, load instead of check_earlytalker with sa
two large email sources for us, apple.com (mac.com) and
> > bellnexxia.net ( Bell Canada / Sympatico ) are now being rejected by
> > check_earlytalker.
> [...]
> > I definitely do not want to turn off check_earlytalker since it
rejects
> > about 30,000 connections a day fo
On Wed, 16 Jan 2008 16:57:31 -0500
"mike.ashton" <[EMAIL PROTECTED]> wrote:
> Issue, two large email sources for us, apple.com (mac.com) and
> bellnexxia.net ( Bell Canada / Sympatico ) are now being rejected by
> check_earlytalker.
[...]
> I definitely do not want t
HI,
New to the list but have been using qpsmtpd for about a year and it has
really been great at getting SPAM under control.
Issue, two large email sources for us, apple.com (mac.com) and
bellnexxia.net ( Bell Canada / Sympatico ) are now being rejected by
check_earlytalker. It appears that have
On Fri, 2007-01-05 at 10:23, Devin Carraway - [EMAIL PROTECTED] wrote:
> Try using the whitelist plugin, and add "182.168.0." to your whitelisthosts
> file. That will bypass the check for that particular subnet.
I don't have a whitelist plugin. I am using the latest tarball.
I do have a dns_whi
On Thu, Jan 04, 2007 at 03:55:46PM +, [EMAIL PROTECTED] wrote:
> Is it possible, currently, to configure check_earlytalker
> to _not_ check particular ip addresses? eg 192.168.0.*
Try using the whitelist plugin, and add "182.168.0." to your whitelisthosts
file. That will
d a little like this:
check_earlytalker:
ip 192.168.0.
auth_secure_conditions:
port 465
ip 192.168.0.
$PLUGIN1:
$skip_condition1
...
$skip_conditionN
...
$PLUGINn:
Are there other circumstances in which chaining things like this for
ip/port/etc. restrictions mig
Lo all,
I have a line in my config for check_earlytalker:
check_earlytalker 1 log 0
I've put it to log because it was rejecting connections from
some internal systems, possibly blat or a java scheduler.
Is it possible, currently, to configure check_earlytalker
to _not_ check particul
On Fri, 17 Nov 2006, John Peacock wrote:
Peter Eisch wrote:
Watercooler chatting got me to learn it. I don't like stumbling onto 'use'
statements inside conditionals but it seems to be necessary to evaluate
->port properly.
Except that unless you wrap that in an eval, or do the equivalent t
Peter Eisch wrote:
Watercooler chatting got me to learn it. I don't like stumbling onto 'use'
statements inside conditionals but it seems to be necessary to evaluate
->port properly.
Except that unless you wrap that in an eval, or do the equivalent thing
using 'require', you are going to brea
ements inside conditionals but it seems to be necessary to evaluate
->port properly.
Patch attached and inline (one line wrapped) below:
--- check_earlytalker.orig 2006-02-26 06:22:16.0 -0600
+++ check_earlytalker 2006-11-17 08:02:18.0 -0600
@@ -89,6 +89,13 @
On 27 Apr 2005, at 19:35, Brian Grossman wrote:
Matt, will the patch to Danga::Socket have any bad side effects? I
haven't
been around Danga::Socket enough to know.
No, it's right. Applying both now.
__
This email has been scanne
In the high_perf branch, check_earlytalker doesn't work for me.
This patch makes check_earlytalker work in high_perf.
There are two parts to this patch. The first patch, to
plugins/check_earlytalker, makes check_earlytalker work when there are
other connections generating events. (For te
20 matches
Mail list logo
