Unless you want to change the semantics of how the "un" commands work and what they mean, so you could do:
blacklist_from [EMAIL PROTECTED]
unblacklist_from_rcvd [EMAIL PROTECTED] mailserver.example.com
I'd strongly vote against such a feature, since it violates the manner in which un*list commands currently work.
Currently they strictly remove an exactly matching entry in the white/blacklists.. kinda line an "rm" command works.. They do not have any kind of 'subset' ability, and I think to add such an ability opens a giant can of worms for both the code and server admins. So even if there was currently an "unblacklist_from_rcvd", that command in the above example should have no effect.
I'd instead rather see that implemented that as a whole separate command, along the lines of:
require_rcvd_for_from [EMAIL PROTECTED] mailserver.example.com
Which would effectively blacklist any email coming in that had a from of [EMAIL PROTECTED] that didn't pass through mailserver.example.com. Looking at the single-command it is clear what it does, and doesn't necessitate the code tracking both a blacklist, and a separate list of "exceptions" to the blacklist in memory.
At 11:24 AM 12/17/2002 +0100, you wrote:
But unblacklist_from_rcvd would make sense. Please?
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
