Re: 0.31 release candidate 2
On 2005-08-20 20:59:10 -0700, Devin Carraway wrote: On Sat, Aug 20, 2005 at 07:38:24PM +0200, Peter J. Holzer wrote: * My patch for a configurable plugin_dir (needed for the RPMs directory structure). I ship a similar patch with Debian's qpsmtpd, for FHS compliance. It varies from Peter's original in allowing multiple values in plugin_dirs and checking for plugins in each -- this helps provide sysadmins with a safe spot to drop their own plugins or override the distributed ones without worrying about interfering with the package management. Ah, that's even better, of course. hp -- _ | Peter J. Holzer| Ich sehe nun ein, dass Computer wenig |_|_) | Sysadmin WSR | geeignet sind, um sich was zu merken. | | | [EMAIL PROTECTED] | __/ | http://www.hjp.at/ |-- Holger Lembke in dan-am pgphs6s6UmnoO.pgp Description: PGP signature
Extension of smtp-forward
Hi, I wrote an extension of the smtp-forward plugin which selects the smtp server from a list by the senders address or the senders domain. Since I use Net::SMTP_auth instead of Net::SMTP SMTP-Auth may be used. Is someone interested in it? Nils
Re: 0.31 release candidate 2
On 21 Aug 2005, at 05:22, Peter J. Holzer wrote: On 2005-08-20 20:59:10 -0700, Devin Carraway wrote: On Sat, Aug 20, 2005 at 07:38:24PM +0200, Peter J. Holzer wrote: * My patch for a configurable plugin_dir (needed for the RPMs directory structure). I ship a similar patch with Debian's qpsmtpd, for FHS compliance. It varies from Peter's original in allowing multiple values in plugin_dirs and checking for plugins in each -- this helps provide sysadmins with a safe spot to drop their own plugins or override the distributed ones without worrying about interfering with the package management. Ah, that's even better, of course. Note this is why I implemented $Include.
Re: 0.31 release candidate 2
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 ;-).
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, I removed support for { cache = 0 } from this patch.
AFAICS it wasn't used anywhere)
Peter, it's used by my per_user_config plugin. It's use to allow the
cache to be selectively disabled e.g. if you're running per-user configs
with 1000s of users and don't want to tradeoff the RAM. So I think it
should stay.
I pinged Ask about this too - he asked me to send the patches to
[EMAIL PROTECTED] so they make it into the bug tracker and don't get
overlooked again - that's probably the right thing to do with yours too.
Cheers,
Gavin
Re: Greylisting and dns_whitelist_soft
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. For example, you could create whitelist.bittwiddlers.com with a zone file like this: $TTL 1h @ SOA abuse.bittwiddlers.com 1 10800 3600 604800 86400 151.116.65.216 TXT John 53.103.143.216 TXT GD AIS 240.56.239.216 TXT gmail mproxy 241.56.239.216 TXT gmail mproxy 242.56.239.216 TXT gmail mproxy The whitelist_zones file then only contains the single line whitelist.bittwiddlers.com, which will cause the plugin to query 151.116.65.216.whitelist.bittwiddlers.com if John is connecting. Ah, ok. That helps and I didn't realize that was the intent. I'll give that a try The whitelist_soft plugin will do what you want with your current configs: http://www.openfusion.com.au/labs/qpsmtpd/whitelist_soft Cheers, Gavin
