On 2007-08-29 16:02:14 -0500, Chris Garrigues wrote: > I'm trying to write a plugin which will sit in front of the greylisting > plugin > and keep it from greylisting messages to certain addresses. > > I thought from my initial reading of the code that if I put a note on > 'whitelistrcpt' in my hook_rcpt it would do this, but clearly I didn't (and > still don't) understand the code. > > What is the proper way to get this effect? > > It actually seems like putting a note on 'whitelisthost', it might work, but > that doesn't seem to be the intent of these hooks. > > Is there a document somewhere I should be looking at to understand the > whitelisting protocol between plugins?
There is no whitelisting protocol between plugins. Period.
Some plugins (typically written by the same author) play well together.
For example, if you use my version of the greylisting plugin[1], you can
use my aliases plugin[2] for per-recipient whitelisting and my
client_options plugin[3] for per-client whitelisting. These plugins can
also set notes used by most of other plugins written by me. But AFAIK
nobody else has ever adopted my framework, and I wasn't happy with what
others did.
hp
[1] http://www.hjp.at/projekte/qpsmtpd/denysoft_greylist/
http://svn.perl.org/viewcvs/qpsmtpd/contrib/hjp/denysoft_greylist/
[2] http://www.hjp.at/projekte/qpsmtpd/aliases/
http://svn.perl.org/viewcvs/qpsmtpd/contrib/hjp/aliases/
[3] http://www.hjp.at/projekte/qpsmtpd/client_options/
http://svn.perl.org/viewcvs/qpsmtpd/contrib/hjp/client_options/
--
_ | Peter J. Holzer | I know I'd be respectful of a pirate
|_|_) | Sysadmin WSR | with an emu on his shoulder.
| | | [EMAIL PROTECTED] |
__/ | http://www.hjp.at/ | -- Sam in "Freefall"
signature.asc
Description: Digital signature
