[ingo] use whitelist/blacklist

[Jan Schneider]

Zitat von "John H. Bennett III" <bennettj at thebennetthome.com>:

> Quoting Jan Schneider <jan at horde.org>:
>
>> Zitat von Philippe Trolliet <p.trolliet at novatec-gmbh.de>:
>>
>>> hello,
>>> i´m new to horde. i want to use the blacklist and whitelist feature of
>>> horde. to test it i added a test-mail address to the blacklist in horde.
>>> when i send a mail from that address it´s not rejected or blocked.
>>> which prerequesites are needed to use the blacklist/whitelist feature of
>>> horde? what and how do i need to configure?
>>> i´m using cyrus-imapd with sieve and postfix as MTA on Fedora Core 4.
>>> please help. thank you.
>>
>> This is a bug in Ingo's IMAP driver that has just been fixed in CVS.
>>
>> Jan.
>>
>
> Would you let me know if you think this bug is also related to my  
> ingo issue that I sent out a few days ago?

No, it's not.

> I am using the latest stable horde products and am running into an issue
> with ingo filters.  Here are my scenarios.  I have an or rule setup that
> states if from doesn't contain domaina.com or from doesn't contain
> domainb.com or from doesn't contain domainc.com delete message completely.
> Whitelist and blacklist are not enabled.  In this scenario, only things
> matching domainc.com are being delivered to the inbox.  domainc.com by the
> way is the last entry in the rule.  If I switch the order, move domaina.com
> to the bottom and domainc.com to the top, then the email from domainc.com
> will be deleted, but email from domaina.com will be accepted.
>
> Scenario 2, I have the same or rule set up, but above the rule, I have
> whitelist enabled with domaina, domainc, and domainb.  Now with these two
> rules, mail is accepted from domainb and domainc only.  If I switch the
> order in the whitelist, then mail is accepted from the last entry in the
> list.
>
> I am currently running php 4.3.9 (cgi) on CentOS 4.4.  I don't understand
> what is going on, but this is repeatable.  I have this same rule on my boys'
> accounts.  The other point is, this rule had been working for over a year on
> the previous horde 3.0.x components.  Only when I upgraded to the horde
> 3.1.x components did I notice that the rules were no longer working.
>
> Thanks,
>
> John
>
>
> -- 
> Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: ingo-unsubscribe at lists.horde.org
>



Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/