Hi.. Im trying to understand how qpsmtpd ticks, and have a small problem the plugin: content_log is not working for some reason. my plugins file looks like this check_relay require_resolvable_fromhost rcpt_ok content_log $include /etc/qpsmtpd/debian-queue-method my qpsmtpd install is a ubuntu 7.10 with postfix Thanks in advance Vent
On Sat, 1 Mar 2008, Ventosus wrote: > Hi.. Im trying to understand how qpsmtpd ticks, and have a small problem > > the plugin: content_log is not working for some reason. Unless you define "not working" then nobody is likely to be able to help you. Do you mean, for instance, that it is just lazy, and sits around watching television? > my plugins file looks like this > > check_relay > require_resolvable_fromhost > rcpt_ok > content_log > $include /etc/qpsmtpd/debian-queue-method And what happens? What happens if you remove content_log?
On Feb 29, 2008, at 8:26, Francisco Valladolid wrote: > WARNING: Setting ABSTRACT via file 'README' failed Thanks; fixed in SVN (r850). - ask -- -- http://www.askbjoernhansen.com/
I'm trying to write a plugin that uses hook_helo_parse but am not having
any success. Some debugging shows my function gets called, it returns a
CODE ref, but the ref'd sub never gets called here's a simple example:
sub hook_helo_parse {
my $self = shift;
my $ref = \&parser;
$self->qp->log(LOGALERT, "hook_helo_parse called and returning $ref");
return(OK, $ref);
}
sub parser {
my( $self, $cmd, $line) = <at> _;
$self->qp->log(LOGALERT, "helo parser called for $cmd and $line");
return(OK, $line);
}
When run I see the first alert, but not the second- does anyone else
have a plugin using this hook that's working? I'm using qpsmtpd-0.40 and
the async server if that makes any difference.
This seems like rather an obvious idea: Reject new
connections if the system load is too high. But surprisingly
there seem to be no plugins which I could find implementing it.
So here's mine:
http://mail-scanning.com/qpsmtpd/system-load
This reads /etc/qpsmtpd/max_system_load, and if the system load
is equal or higher than the value contained within it it is rejected.
Comments welcome, and I'm happy for it to be used in the core, or in
contrib if there is any interest.
Steve
--
--
http://mail-scanning.com/
On 3/7/08 3:39 PM, "Steve Kemp" <steve <at> steve.org.uk> wrote: > > This seems like rather an obvious idea: Reject new > connections if the system load is too high. But surprisingly > there seem to be no plugins which I could find implementing it. > I had posted this one to the list back a couple years ago. It works on linux, bsd'en and solaris. Maybe on hpux too. peter #!/usr/bin/perl =head1 NAME loadcheck =head1 DESCRIPTION Only takes email transactions if the system load is at or below a specified level. =head1 CONFIG max_load This is the 1 minute system load where we won't take transactions if our load is higher than this value. (Default: 7)(Continue reading)
Note - you'd be better off using Linux::SysInfo (on Linux, obviously) to save the backtick call. On 7-Mar-08, at 4:39 PM, Steve Kemp wrote: > > This seems like rather an obvious idea: Reject new > connections if the system load is too high. But surprisingly > there seem to be no plugins which I could find implementing it. > > So here's mine: > > http://mail-scanning.com/qpsmtpd/system-load > > This reads /etc/qpsmtpd/max_system_load, and if the system load > is equal or higher than the value contained within it it is rejected. > > > Comments welcome, and I'm happy for it to be used in the core, > or in > contrib if there is any interest. > > Steve > -- > http://mail-scanning.com/ >
On Fri Mar 07, 2008 at 17:48:22 -0500, Matt Sergeant wrote: > Note - you'd be better off using Linux::SysInfo (on Linux, obviously) to > save the backtick call. Noted. I'll update the code to use that where possible. (Right now I figured portability would be a good thing - although I realise my regexp fails there!) Steve -- --
Peter Eisch skribis 2008-03-07 16:17 (-0600):
> $self->{_args}->{uptime} = '/usr/bin/uptime'
> if (! defined $self->{_args}->{uptime});
> (...)
> my $res = `$self->{_args}->{uptime}`;
Especially during high load, forking and executing uptime may not be
such a wise thing to do, depending on how well your platform handles
this under high load.
--
--
Met vriendelijke groet, Kind regards, Korajn salutojn,
Juerd Waalboer: Perl hacker <##### <at> juerd.nl> <http://juerd.nl/sig>
Convolution: ICT solutions and consultancy <sales <at> convolution.nl>
On Sat, 8 Mar 2008 16:08:10 +0100
Juerd Waalboer <juerd <at> convolution.nl> wrote:
> Peter Eisch skribis 2008-03-07 16:17 (-0600):
> > $self->{_args}->{uptime} = '/usr/bin/uptime'
> > if (! defined $self->{_args}->{uptime});
> > (...)
> > my $res = `$self->{_args}->{uptime}`;
>
> Especially during high load, forking and executing uptime may not be
> such a wise thing to do, depending on how well your platform handles
> this under high load.
True. The goal is to avoid swamping the system.
I'm happy to take patches that keep the plugin universal and gather the
stats better.
RSS Feed3 | |
|---|---|
9 | |
1 | |
4 | |
21 | |
5 | |
3 | |
69 | |
199 | |
58 | |
3 | |
1 | |
6 | |
14 | |
19 | |
5 | |
16 | |
26 | |
5 | |
34 | |
27 | |
6 | |
13 | |
30 | |
5 | |
72 | |
9 | |
97 | |
25 | |
21 | |
30 | |
28 | |
14 | |
75 | |
46 | |
19 | |
25 | |
81 | |
59 | |
123 | |
73 | |
42 | |
97 | |
117 | |
55 | |
18 | |
36 | |
59 | |
22 | |
52 | |
38 | |
127 | |
75 | |
65 | |
94 | |
78 | |
116 | |
41 | |
78 | |
158 | |
275 | |
61 | |
142 | |
126 | |
86 | |
63 | |
208 | |
324 | |
78 | |
131 | |
157 | |
123 | |
80 | |
89 | |
123 | |
105 | |
181 | |
174 | |
233 | |
371 | |
85 | |
198 | |
76 | |
50 | |
88 | |
316 | |
133 | |
187 | |
162 | |
200 | |
168 | |
37 | |
66 | |
151 | |
84 | |
273 | |
121 | |
139 |
