On Tue, Feb 12, 2008 at 10:47:28PM +, Jim Murray wrote:
> Can anyone shed some light on what might be causing this?
>
> @400047b212e52378779c Use of uninitialized value in pattern match
> (m//) at ./plugins/greylisting line 209, line 3.
>
> I'm running QPSMTPD 0.40 release, no tweaks an
On Sat, Sep 15, 2007 at 08:27:19AM +0200, Hanno Hecker wrote:
> I'm not really happy with the all or nothing approach of whitelisting /
> blacklisting. There should be a score based whitelist, which can be
> fine tuned by the admin.
Blacklisting and whitelisting _are_ all or nothing, by definitio
On Fri, Sep 07, 2007 at 02:10:34PM -0500, Chris Garrigues wrote:
> It was very curious. I could see in the logs lines like this:
>
> 2007-09-06 15:04:18.705745500 13257 greylisting plugin: key
> 68.180.197.125:[EMAIL PROTECTED]:[EMAIL PROTECTED] initial DENYSOFT, unknown
>
> but when I looked i
Hi Ernesto,
On Fri, Aug 31, 2007 at 04:10:30AM +0200, Ernesto wrote:
> trying to inherit from a plugin I ran into a problem:
>
> Plugin: /usr/share/qpsmtpd/plugins/extended_rcpt_to
>
> sub init
> {
> my $self = shift;
> print STDERR __PACKAGE__, "::init...\n";
> $self->isa_plug
On Tue, Aug 21, 2007 at 08:56:00AM -0700, JT Moree wrote:
> Peter J. Holzer wrote:
> > Clearly this is useless and each plugin needs to decide what it wants to
> > do with the information that the message is whitelisted.
> >
> > (And since I haven't climbed that particular soap-box for some time I
On Thu, Aug 16, 2007 at 01:02:52PM -0700, JT Moree wrote:
> Shouldn't the documentation for the whitelist_soft module mention that
> it requires modifying the rest of the plugins?
Yes, probably. My current dev version does say:
=head1 BUGS/NOTES
Cross-hook whitelisting must be specifically sup
On Wed, Aug 15, 2007 at 01:50:32PM -0700, JT Moree wrote:
> m. allan noah wrote:
> >> Thank you, I'll experiment with this but I'm still not sure why the
> >> whitelistsenders from whitelist_soft does not work? is it only supposed
> >> to work on senders outside my domain that send mail to my dom
On Tue, Aug 14, 2007 at 02:33:10PM -0700, JT Moree wrote:
> I upgraded to 0.40 over the weekend. Everything seemed to work fine but
> I think I missed some key issues. On Monday qpsmtpd would not relay for
> our offsite users. They could send to addresses in our domain but not
> anything outside
On Wed, May 23, 2007 at 09:50:41AM -0700, JT Moree wrote:
> I'm looking for an archive plugin. Since we send all mail through
> qpsmtpd anyway it seems like a viable place to archive emails. Ignoring
> spam for a moment I'd like a plugin which archives emails to a database
> or just sends the ema
On Sun, Feb 25, 2007 at 05:20:34PM -0500, m. allan noah wrote:
> I have been using greylisting for a little while, and find that
> managing the whitelist is sort of annoying. so, i updated my copy of
> the plugin to use the query object that the SPF plugin squirrels away.
> if the host is a valid s
On Sun, Feb 25, 2007 at 10:39:50PM +0100, Hans Salvisberg wrote:
> I run some of my domains with a catch-all address (i.e. no recipient
> checking), and I have a considerable number of retired addresses there.
> Many were never in actual use but have been invented by spammers! With
> this setup
On Fri, Feb 23, 2007 at 09:51:27PM -0500, m. allan noah wrote:
> i have been running qpsmtpd for a little while now, and love it. but,
> i am getting questions from users about missing email. no one is
> actually able to point at any specific problem, they are just jumpy
> now that there is no spam
Hi all,
I'm beginning to get some time for messing around with qpsmtpd again after
some time away. I have a couple of procedural questions:
- what's the current procedure for submitting patches to the core? Discuss and
submit via the mailing list, or discuss on list and submit via the bug
tra
On Thu, Feb 22, 2007 at 02:19:54PM -0700, Brian Grossman wrote:
> Here it is as two attachments. One attachment is a patch to
> trunk/lib/Qpsmtpd.pm. The other is a file explaining how to use
> the new feature.
>
> What do you think of it conceptually? Is there anything you'd like me to
> chang
er from NZ - skipping");
return DECLINED;
}
$self->SUPER::mail_handler( @_ );
}
and then use 'greylisting_nz' in your config/plugins file instead
of 'greylisting'.
Cheers,
Gavin
--
Gavin Carr
- http://www.openfusion.com.au - Linux, Perl, and Web Consul
anger, available
here:
http://www.openfusion.com.au/labs/qpsmtpd/
I'm still way back on qpsmtpd 0.28 though, so it may well need some
tweaking to use it on current.
Cheers,
Gavin
--
Gavin Carr
- http://www.openfusion.com.au - Linux, Perl, and Web Consulting
- http://www.xool.com.au - Xool, Australi
Hi Max,
On Mon, Apr 10, 2006 at 12:39:27PM -0700, Max Clark wrote:
> I need to share my greylisting data across multiple machines - does a
> patch exist to read/write this data to a mysql database? I'm assuming
> this will add _some_ load to the server - is there a better way to
> implement this?
On Thu, Apr 06, 2006 at 10:54:50AM -0700, Max Clark wrote:
> From the documentation I understand that the order the plugins are
> listed in the configuration will impact the effectiveness of them. Is
> this really the case?
It depends what you mean by "will impact the effectiveness of".
Plugins
On Tue, Mar 28, 2006 at 02:32:29PM -0700, Bryan Scott wrote:
> As a side note, I'm really leaning towards Gavin's per-user setup too, as
> too many of my users are complaining that my rules are either too strict or
> not strict enough. Any gotchas with 0.32x?
I'm still back in the dark ages run
Hi Charles,
On Mon, Mar 13, 2006 at 11:00:33AM +1100, Charles Butcher wrote:
> I have had in the past very good results from greylisting, over 30% of
> first-time rejections never come back. With it turned off we see a
> major increase in spam hitting the queue. Occasionally someone says
> th
On Mon, Jan 23, 2006 at 09:05:13PM +1100, Gordon Rowell wrote:
> Johan Almqvist wrote:
> >
> >On Jan 23, 2006, at 10:48, Gordon Rowell wrote:
> >
> >>check_goodrcptto extn -
> >
> >
> >I don't have this, it wasn't in the distro.
>
> I'll submit it on Gavin Carr's behalf unless he's listening. Gav
On Mon, Aug 22, 2005 at 09:36:01AM +0200, Peter J. Holzer wrote:
> > > The RPM still contains five patches:
> > >
> > > * Gavins patch for an optional hashref argument to config. This is
> > > needed for the greylisting plugin, and it stops an endless recursion
> > > somewhere.
> > > (Gavin,
On Sat, Aug 20, 2005 at 07:09:42PM -0400, Matthew Harrell wrote:
> > Yes, I think you are (I agree that the doc could be clearer).
> >
> > You are supposed to create a DNS whitelist, i.e., a domain which
> > contains information about IP adresses in a similar way to the
> > in-addr.arpa. domain. Fo
On Sat, Aug 20, 2005 at 07:38:24PM +0200, Peter J. Holzer wrote:
> I just updated my RPMs[0] to this version and deployed them on my private
> mail server. Unless I notice any problems I will deploy it on the WSR
> mail server tomorrow, so any serious problems should be noticable by
> Monday ;-).
>
> >> >Replying to self - nope, that won't work. SRS rewriting has to be done
> >> >_after_ rcpt_ok, of course, because our local domain is probably only
> >> >on the un-rewritten recipient. But it really should still be at RCPT
> >> >time because we need to be able to deny individual recipients whe
On Thu, Aug 18, 2005 at 08:35:26AM -0400, Matt Sergeant wrote:
> On 18 Aug 2005, at 03:30, Gavin Carr wrote:
> >On Thu, Aug 18, 2005 at 11:44:06AM +1000, Gavin Carr wrote:
> >>Just wondering if anyone has written a Reverse SRS plugin? I think
> >>this
> >>w
On Thu, Aug 18, 2005 at 12:41:21PM -0400, Bob Dodds wrote:
> If using SRS, recipient not being an SRS alias is fine
> unless what?
Recipient not being an SRS alias is fine. Recipient being an SRS
alias is fine unless the SRS rewrite fails. That means either it's
a bogus alias (isn't hashed with yo
On Thu, Aug 18, 2005 at 11:44:06AM +1000, Gavin Carr wrote:
> Just wondering if anyone has written a Reverse SRS plugin? I think this
> would just be a recipient plugin that rewrites SRS recipient addresses
> early during RCPT? (before rcpt checks, specifically)
Replying to self - n
Just wondering if anyone has written a Reverse SRS plugin? I think this
would just be a recipient plugin that rewrites SRS recipient addresses
early during RCPT? (before rcpt checks, specifically)
Cheers,
Gavin
On Sun, Jul 17, 2005 at 04:48:39PM +0200, Peter J. Holzer wrote:
> Yep, it was. BTW, the greylisting plugin calls config with a second
> parameter { rcpt => $rcpt }, so there is at least one plugin in the
> standard distribution which makes use of an interface which doesn't yet
> exist :-).
Gueril
Attached is the patch to Qpsmptd.pm required by my per_user_config
plugin. It basically just adds argument passing to config plugins,
and tweaks the caching code to be per-config-file rather per-config-name
(and adds a 'cache' named argument to config to allow caching to be
turned off, since #co
On Wed, Jul 06, 2005 at 03:26:08PM -0400, Matt Sergeant wrote:
> This patch creates a circular loop with pluggable logging. My guess is
> you haven't tested it with latest SVN :-)
>
> My suggested change is something like this:
>
> sub get_qmail_config {
>my ($self, $config, $type) = @_;
> -
There's a minor bug in Qpsmtpd::config first reported by Peter Holzer
back around 0.26, such that an empty config loaded via a config plugin
isn't used, and processing falls through to the standard config loading.
A patch is attached. It was included in my per_user_config patch, but
I've split it
Hi Hans,
On Mon, Jun 27, 2005 at 12:43:44PM +0200, Hans Sandsdalen wrote:
> # Check greylisting
> my $sender = $transaction->sender;
> my ($status, $msg) = $self->denysoft_greylist($transaction, $sender,
> $rcpt, $c
> onfig);
> my $connection = $self->qp->connection; #
On Mon, Jun 06, 2005 at 04:50:34PM -0700, Devin Carraway wrote:
> On Mon, Jun 06, 2005 at 04:48:51PM +0200, Peter J. Holzer wrote:
> > The RPMs were built for RH 7.3, but it should be possible to simply
> > rebuild the source rpm. If you use apt, you can add
>
> Ah, cool. I filed an ITP to inclu
On Thu, May 12, 2005 at 09:31:44PM +0200, Peter J. Holzer wrote:
> On 2005-05-12 12:28:09 -0600, Bryan Scott wrote:
> According to their different filter settings, alice and charlie want the
> mail rejected, bob wants it to be marked up as possible spam, and debbie
> wants to receive it unaltered.
On Wed, Apr 13, 2005 at 09:52:02AM -0400, John Peacock wrote:
> I'd rather rewrite the core to not support the "map" interface at all
> (and Ask has already expressed he is happy to see that happen) and just
> have config() take a hashref all the time for option handling. You can
> use it for t
On Mon, Apr 11, 2005 at 06:59:03PM +0100, Tim Meadowcroft wrote:
> On Friday 08 Apr 2005 15:14, John Peacock wrote:
> > > - a single qpsmtpd setup, but use tcprules with tcpserver to set an
> > > environment variable which could point at a different config folder in
> > > Qpsmtpd::get_qmail_config
On Tue, Apr 12, 2005 at 04:37:23PM -0400, John Peacock wrote:
> >5) Options to the config thing should be a hashref; how the map/cdb
> >option is implemented now is bad and ugly.
>
> If I add a config extension as a hashref, should I rewrite the current
> usage of "map" at the same time? It onl
On Wed, Feb 02, 2005 at 04:40:17PM -0600, David Nicol wrote:
> http://www.greylisting.org/
>
>
> the idea is, reject any unseen source the first time it is seen, for an hour
> or two. This cuts down on bot-sent messages at the small price of
> delaying (!!! not requiring a full c/r) the first me
On Fri, Nov 19, 2004 at 09:24:51PM +0100, Michael Holzt wrote:
> > You might try my per_user_config plugin available here:
> > http://www.openfusion.com.au/labs/qpsmtpd/
>
> Some time ago i tried to get it running with the latest CVS version but had
> no lock. Has this changed?
I've updated the
Been meaning to announce this for a while ...
I've written a generic 'handler' plugin to handle the disposition of
an email based on a numeric score. It can reject, drop, redirect, or munge
subjects, and combinations thereof. The idea is to factor out this kind
of disposition code from the vari
Hi Ed,
On Mon, Nov 15, 2004 at 03:06:19PM -0600, Ed McLain wrote:
> I've had alot of my customers ask me about being able to change what tests
> and so forth are run on the mail that comes in for there domains. I saw
> that there was some discussion about this a while back, but haven't heard
> an
On Tue, Oct 05, 2004 at 05:41:38PM -0500, Ed McLain wrote:
> I'm wanting to use the full power of SpamAssassin at the SMTP level, e.g.
> reports, user preferences, etc.. I modded the stock spamassassin plugin
> to pass spamd the recipient of the email, however, subject line changing
> and inclusio
On Mon, Sep 20, 2004 at 09:56:10PM -0400, John Peacock wrote:
> OK, this is what I have working and I think I will check it in tomorrow
> morning after some more testing:
>
> 1) plugins/check_relay is now a check plugin and should run just after
> early_talker (or so); it sets the $connection->{
On Sun, Sep 12, 2004 at 11:27:20PM -0700, Robert Spier wrote:
> > Anyone done any work (or thinking) about supporting hashcash [1] support
> > to qpsmtpd? Validation is included in SpamAssassin 3 - is there any value
> > in a qpsmtpd validation plugin as well? An outward minting plugin would
> >
Anyone done any work (or thinking) about supporting hashcash [1] support
to qpsmtpd? Validation is included in SpamAssassin 3 - is there any value
in a qpsmtpd validation plugin as well? An outward minting plugin would
also be nice, at least for small-medium sites.
Cheers,
Gavin
[1] http://www.
On Thu, Sep 02, 2004 at 11:47:42PM +0200, Michael Holzt wrote:
> Short question: Why has the 'require_resolvable_fromhost' a config file in
> which one needs to put '1' for enable and '0' for disable? It can be
> enabled or disabled by putting it into the plugins-configuration or leaving
> it out.
On Thu, Sep 02, 2004 at 12:25:52PM +0200, Hans Sandsdalen wrote:
> How du I permitt a host even if SPF failes?
One way is via whitelisting. Get a whitelisting plugin e.g.
http://www.openfusion.com.au/labs/qpsmtpd/whitelist_soft
add the hosts you want to permit to a 'whitelisthosts' config file
On Wed, Sep 01, 2004 at 09:53:32PM +1000, Gavin Carr wrote:
> On Wed, Sep 01, 2004 at 02:20:59AM -0700, Ask Bj?rn Hansen wrote:
> > I can see how it'd be useful though, so suggestions are welcome and I'm
> > open for patches.
>
> Okay, I'll come up with somet
On Wed, Sep 01, 2004 at 09:01:41AM -0400, Keith C. Ivey wrote:
> I wonder if the SMTP RCPT addresses and the addresses the
> message will be queued for should be separated into two
> separate properties. Changing the delivery address shouldn't
> destroy the information about what address was gi
On Wed, Sep 01, 2004 at 08:57:27AM +0100, Matt Sergeant wrote:
> > - add body_replace(), allowing mail bodies to be munged and replaced
> > wholesale - rationale: allows body sanitisation (e.g. evil HTML),
> > attachment stripping, etc. Yes, violates MTAs-should-transfer-only
> > dictum; som
On Wed, Sep 01, 2004 at 02:20:59AM -0700, Ask Bj?rn Hansen wrote:
> On Wed, 1 Sep 2004, Gavin Carr wrote:
> > - make recipients() a mutator - rationale: to allow email redirection e.g.
> > for virus or spam scanners, allowing another option than outright denial
> > or m
I know I will be beaten by the email-purists with large pointy objects, but -
I'm wanting to add/extend some methods in Qpsmtpd::Transaction to allow
greater message manipulation by plugins. Specifically:
- make recipients() a mutator - rationale: to allow email redirection e.g.
for virus or s
On Wed, Aug 25, 2004 at 08:23:31AM +0200, Hans Sandsdalen wrote:
> It says "non-multipart mail - skipping" int the log, and executables are
> not blocked?
Are you sending it as an attachment or directly as the mail body? The
current version of exe_filter only scans MIME multipart mails, so the
l
etc.), or an arbitrary string.
=item qpstats_queue_replace
This note can be used to increment a counter instead of the standard
queue counter in a queue hook. Useful if you want to split a 'queue'
up into categories (e.g. splitting out spam redirects).
The format is ':'. Code can b
Qpsmtpd::Plugin seems to be missing the 'deny' hook in the new %hooks hash
introduced in 0.28. Can it be added please (assuming its omission wasn't
intentional)?
Cheers,
Gavin
On Thu, Jul 08, 2004 at 03:54:40PM -0600, Brian Grossman wrote:
> On Wed, 7 Jul 2004 15:51:37 +1000
> Gavin Carr <[EMAIL PROTECTED]> wrote:
>
> > So it depends what you want, but you might try exe_filter at
> > http://www.openfusion.com.au/labs/qpsmtpd/, which do
On Sat, Jul 10, 2004 at 01:41:11AM -0500, Peter Eisch wrote:
> A month or two ago I was getting annoyed with the from email addr using my
> domain when there is no reason that any email should come to me with a from
> addr of my domain. Well, then there is fedex, walmart, ebay and a load of
> othe
On Tue, Jul 06, 2004 at 03:00:20PM +0200, Hans Sandsdalen wrote:
> I have used qmail-scanner with qmail-smtpd for a long time, but now I
> want to try qpsmtpd. Are there any way to reject any executable
> attatchments (for example *.exe) like in qmail-scanner?
Reject them based on what - filename?
On Wed, Jun 30, 2004 at 02:54:26PM -0400, Ted Zlatanov wrote:
> I'm interested in using qpsmtpd with the qmail-ldap patch. Does
> anyone use that? Any positive or negative experiences?
Works fine, since qpsmtpd doesn't really interact with qmail at all - it
just wants something that looks like q
On Wed, May 19, 2004 at 11:57:34AM -0400, Tim Wesemann wrote:
> I'm trying to figure out how to get a variable (or array, hash --
> anything!!) containing the envelope recipient(s) of a given message into the
> check_spam sub within the stock spamassassin plugin... Any help?
Available via the tra
On Tue, May 04, 2004 at 12:05:28AM +0200, Timo T. Rajala wrote:
> Ok, I suspected it could be a bug. But note that the bug is in the perl
> plugin here:
> http://www.hjp.at/projekte/qpsmtpd/denysoft_greylist/denysoft_greylist
>
> That is your plugin modified by Peter J. Holzer if I understand cor
Hi Timo,
On Mon, May 03, 2004 at 08:59:26PM +0200, Timo T. Rajala wrote:
> May 3rd 2004:
> From http://www.openfusion.com.au/labs/qpsmtpd/ :
>
> "per_user_config - a config plugin allowing per-recipient or per-sender
> config files to be defined in subdirectories of the standard
> qpsmtpd/confi
Hi Timo,
On Mon, May 03, 2004 at 08:59:26PM +0200, Timo T. Rajala wrote:
> May 3rd 2004:
> From http://www.openfusion.com.au/labs/qpsmtpd/ :
>
> "per_user_config - a config plugin allowing per-recipient or per-sender
> config files to be defined in subdirectories of the standard
> qpsmtpd/confi
Hi Timo,
On Mon, May 03, 2004 at 07:56:16PM +0200, Timo T. Rajala wrote:
> Is denysoft_greylist really supposed to accept mail if:
>
> 1. remote_ip is in the initial black_timeout period
> and
> 2. sender is <>
>
> ?
Nope - that looks like a bug. Thanks for the report - I'll try and look
at it
On Tue, Apr 27, 2004 at 09:49:41PM +0200, Peter J. Holzer wrote:
> On 2004-04-27 14:37:18 +, [EMAIL PROTECTED] wrote:
> > A frequent occurence is where a connection has a single message
> > bound for multiple recipients. It is possible that one copy may be
> > deliverable, and one copy may
Hi Martin,
On Thu, Apr 08, 2004 at 12:36:10AM +, martin martin wrote:
> qmail + some patches (tarpit, qmailqueue) + vpopmail.
>
> I have been looking for alternatives to spamassasin and I found qpsmtpd
> wich seems to be very good. I read the instalation instructions but, at
> least for me,
On Mon, Mar 29, 2004 at 09:18:41PM +, Tim Meadowcroft wrote:
> On Monday 29 March 2004 16:11, Bryan Scott wrote:
> > There are some portions of the thread that suggest doing a little more
> > damage by using up bandwidth and letting the remote end send the entire
> > payload (with multiple rese
On Mon, Mar 29, 2004 at 03:48:42PM -0500, Russell P. Sutherland wrote:
> Is there a module for limiting the number of
> recipients in a smtp session?
Do you mean "limit to N recipients" or "limit to 1 recipient (or 1
domain)"? The 'denysoft_multi_rcpt' plugin at
http://www.openfusion.com.au/labs/
On Wed, Mar 24, 2004 at 10:31:21PM +, Matt Sergeant wrote:
> FWIW I've had very "weird" stability issues with db files of all
> varieties (even DB_File). Especially under extreme load.
Eeerk - not really the answer I was looking for. :-)
> I've had much better success with SQLite.
Yeah, I
Hi Tim,
On Wed, Mar 24, 2004 at 09:38:24PM +, Tim Meadowcroft wrote:
> I started off thinking that I'd suggest adding basic tar-pitting
> (http://www.gordano.com/kb.htm?q=1112) to selected plugins (such as SPF) that
> are detecting blatant abuse - the idea being that if a spammer has recruit
Hi Sam,
On Tue, Mar 23, 2004 at 01:46:24PM -0600, Sam Laffere wrote:
> Here is a paste of parts of my log, edited for space considerations. On
> message 16306, I left in about anything somebody might want to see, and just
> show the relevant lines on the following messages. You can see that it
>
Hi Sam,
On Mon, Mar 22, 2004 at 07:12:29PM -0600, Sam Laffere wrote:
> I implemented this plugin on a test domain, and it seemed great, but after
> implementing on my production server, I had too many customers not getting
> their email because of the 'no reverse lookup' part. For now I have
> r
On Mon, Mar 22, 2004 at 05:13:43PM -0500, Charlie Brady wrote:
> On Mon, 22 Mar 2004, Matt Sergeant wrote:
>
> > It probably has to be re-written with locking (though I haven't read
> > the code for the plugin - does it lock?)
>
> Yes, it does lock. I didn't check that it will always remove the
used. Note that because spamhandle is a post_data plugin, it is
required and assumed that all recipients are using the same config
definitions (see e.g. the denysoft_multi_rcpt plugin).
=back
=head1 AUTHOR
Gavin Carr <[EMAIL PROTECTED]>.
=cut
use Mail::Address;
my $VERSION = 0.01;
my
On Sun, Feb 22, 2004 at 04:52:53PM +, Matt Sergeant wrote:
> Sorry to take so long to get back to you on this...
>
> My take on this is that the second parameter is already taken, and so we
> should just pass on extra params, not change the existing API.
>
> So I'm happy to apply this patch,
On Sun, Feb 22, 2004 at 09:01:27AM -0600, Peter Eisch wrote:
> sub rewrite {
> my $self = shift;
> my $was = shift;
> my $qacct = $self->{_args}->{redirect_addr} || 'spamq';
>
> return $qacct
> if $qacct =~ /\@/;
>
> $was =~ s/([\w\.\-\_]+)\@/$qacct\@/g;
> return
On Sat, Feb 21, 2004 at 06:18:05PM -0800, Ask Bj?rn Hansen wrote:
> On Jan 31, 2004, at 11:36 AM, Peter J. Holzer wrote:
>
> >The patch below is against 0.26, and includes my previous patch (since
> >it partially overlaps).
>
> I've put it in CVS now. I still miss the Spam: headers with the
> e
Hi Chris,
On Tue, Feb 17, 2004 at 05:37:06PM -0700, Chris Stone wrote:
> Got things setup and fired qpsmtpd up with per_user_config and one domain
> setup with it's own configs for dnsbl - empty file. The log showed getting
> errors in per_user_config as follows:
>
> 2004-02-17 16:52:51.493350500
On Tue, Feb 17, 2004 at 02:51:09PM -0700, Chris Stone wrote:
> Anyone know, if possible, what needs to be changed in the dnsbl and rhsbl
> plugins for supporting per_user_config?
The basic approach is this:
- add a config/plugins 'per_recipient' argument to turn per_recipient
functionality on
Hi Chris,
On Tue, Feb 17, 2004 at 01:19:58PM -0700, Chris Stone wrote:
> Think that I was thinking something incorrectly - there can only be the one
> config/plugin file, right? And then, via config/plugin, I set
>
> spamassassin_spamc per_recipient 1 filter 0/1
Correct.
> And then in the /conf
On Tue, Feb 17, 2004 at 07:20:31PM +1100, Gavin Carr wrote:
> On Mon, Feb 16, 2004 at 06:39:28PM -0700, Chris Stone wrote:
> > Yes, I am trying to setup the per_user_config plugin
> > (http://www.nntp.perl.org/group/perl.qpsmtpd/963 - followup from the link
> > you noted). It&
Hi Chris,
On Mon, Feb 16, 2004 at 06:39:28PM -0700, Chris Stone wrote:
> Yes, I am trying to setup the per_user_config plugin
> (http://www.nntp.perl.org/group/perl.qpsmtpd/963 - followup from the link
> you noted). It's all setup, but I am to the point now of trying to figure
> out how to now poi
7;per_sender_configdir')
transaction note records the most-specific config directory found for
the most recent user.
No caching of results is done by default, since the number of config
files involved might be huge.
=head1 AUTHOR
Written by Gavin Carr <[EMAIL PROTECTED]>.
=cut
On Thu, Feb 05, 2004 at 02:13:14PM -0600, David Dyer-Bennet wrote:
> I'm getting this logged fairly often. Not always after the same
> plugin is run, and the plugins that it comes after sometimes actually
> produce results.
>
> Looking at the source code didn't help much this time; so little re
I haven't been following the various spamassassin plugins that have been
mentioned off and on recently - can someone point me to a recommended one
for use with the latest SAs? Is the current cvs one fairly out of date?
Cheers,
Gavin
On Mon, Jan 19, 2004 at 07:44:20PM +0100, Peter J. Holzer wrote:
> I modified the rhsbl plugin to use per recipient configs (attached) and
> found the first problem:
>
> If the configuration returned by run_hooks is empty, Qpsmtpd::config
> will call get_qmail_config even if run_hooks returned OK.
Sometimes it's presumably better to merge?
No caching of results is done yet. Does not support CDB (map) config
files yet.
=head1 AUTHOR
Written by Gavin Carr <[EMAIL PROTECTED]>.
=cut
my %EXCLUDE = map { $_ => 1 } qw(me timeout);
my $VERSION = 0.01;
sub register {
my ($self
On Fri, Jan 09, 2004 at 10:13:36AM +0100, Fiorenza Meini wrote:
> I'm trying to use the denysoft_greylist with qpsmtpd, but I see this error in the
> log file:
>
> Variable "$self" will not stay shared at ./plugins/denysoft_greylist line 165
>
> What does it mean?
What version of denysoft_greyl
Hi Peter,
On Sun, Dec 21, 2003 at 12:23:52AM +0100, Peter J. Holzer wrote:
[ per_recipient patches to denysoft_greylist ]
A few comments:
a. the per_recipient and recipient_options checks look fine and I'd
be happy to include them
b. I won't be removing the whitelist checks just yet, since I
On Mon, Dec 22, 2003 at 01:57:13PM -0700, Bryan Scott wrote:
> Gavin Carr wrote:
> >Just to throw another approach into the pot for discussion, I've been
> >thinking about approaching this by adding subdirectories to the 'config'
> >directory by RCPT domain, a
On Sat, Dec 20, 2003 at 01:32:12PM +0100, Peter J. Holzer wrote:
> On 2003-12-20 22:16:52 +1100, Gavin Carr wrote:
>
> Yup. In my modified denysoft_greylist plugin, support for recipient
> options has to be explicitely turned on.
So what does that look like in the plugin?
> >
On Wed, Dec 17, 2003 at 02:11:26PM -0700, Bryan Scott wrote:
> I've been thinking for the past little bit (a dangerous habit, I know), and
> came up with an idea that should fit seamlessly into qpsmtpd, vpopmail,
> spamassassin, etc. I'm curious if other developers have already done
> somethin
On Fri, Dec 19, 2003 at 04:53:58PM +0100, Peter J. Holzer wrote:
> On 2003-12-17 14:11:26 -0700, Bryan Scott wrote:
> > To solve this problem one would need per-user and/or per domain
> > controls.
> >
> > My thought is to create a suite of scripts that uses a user database (such
> > as vpopmail
On Fri, Dec 19, 2003 at 09:34:28PM +0100, Peter J. Holzer wrote:
> On 2003-12-19 08:11:15 +, Matt Sergeant wrote:
> > As always the hard thing with doing per-recipient configs is when
> > @recipients > 1.
>
> I had an evil idea a few days ago how to solve this problem:
>
> A plugin which ret
>From the masochism department: anyone tried getting qpsmtpd up on Windows
platform (presumably in smtp-proxy mode rather than qmail mode)? Any
thoughts on how easy or difficult this might be?
Cheers,
Gavin
On Tue, Nov 04, 2003 at 08:33:22AM +, Matt Sergeant wrote:
> On 4 Nov 2003, at 2:06, Gavin Carr wrote:
> >Agreed, and simpler to implement as well. That's a vote for, then; any
> >other comments?
>
> My only other comment would be to check out qmail-users(5), which
On Mon, Nov 03, 2003 at 09:14:50PM +, Matt Sergeant wrote:
> On 3 Nov 2003, at 20:05, Gavin Carr wrote:
> >We seem to be seeing a bit of duplication lately - do we need a webpage
> >or something where announced plugins (and patches and forks) can be
> >registered (a
On Tue, Nov 04, 2003 at 01:39:53AM +0100, Peter J. Holzer wrote:
> On 2003-11-04 08:21:10 +1100, Gavin Carr wrote:
> > Can we get Transaction::recipients made into a mutator? i.e. replacing
> > the current recipient list instead of appending via add_recipients. I
> > know t
1 - 100 of 114 matches
Mail list logo
