Title: Message

Hi Nick, John, Eric, Fritz, Kevin, Dan, NCL Admin, et al:

>>  This change removes our ability to override ROUTETO in special circumstances. <<

I recommend you sit tight just a little longer. The "new" behavior apparently was not intended and I'm certain, Declude will be made "downward" compatible.

It may help to check your configurations to whether you can company specific (= per domain) actions. If you are using either of these two features:

- \Domain.com\$default$.junkmail
- REDIRECT @domain.com

then this may explain the (unexpected/temporarily) changed handling of DELETE, HOLD and other actions. Again, I believe this will be corrected.

Best Regards
Andy Schmidt

H&M Systems Software, Inc.
600 East Crescent Avenue, Suite 203
Upper Saddle River, NJ 07458-1846

Phone:  +1 201 934-3414 x20 (Business)
Fax:    +1 201 934-9206

http://www.HM-Software.com/

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt
Sent: Friday, March 04, 2005 12:17 PM
To: [email protected]
Subject: Re: [Declude.JunkMail] Declude 2.x

John Tolmachoff (Lists) wrote:
I have not been following the thread in detail, but if some one that is
having the problem would change to WEIGHTRANGE instead of WEIGHT and ensure
there are no overlappings, I have a feeling the at least part of the
"problem" might be resolved.
No, this isn't an appropriate solution.  The change makes ROUTETO the final action, and now it has precedence over DELETE.  If you have a filter called BLACKLIST-NO-MATTER-WHAT set to DELETE, and a message fails that test plus it fails something that has a ROUTETO action, it will not be deleted.  This change removes our ability to override ROUTETO in special circumstances.  While most issues will be fixed by preventing the overlapping of weight ranges and the actions, that only applies to weight based things, and this ties our hands when it comes to taking actions regardless of weight.  That's completely unacceptable, and I also assume that it was unintentional; the result of an oversight.

If DELETE is to be changed in the way that they did, they must make it be able to target a recipient that has already been tagged with ROUTETO.  It makes no sense to use the changed ROUTETO address for determining further actions.  This will also be very difficult to troubleshoot in some circumstances and also difficult to keep track of.

Declude needs to make sure that the actions are not applied based on the ROUTETO address' config, but instead the original recipient's config.  If they did that, all problems would be solved, including the overlapping weight range issue that seemingly has stung so many here.

Matt
-- 
=====================================================
MailPure custom filters for Declude JunkMail Pro.
http://www.mailpure.com/software/
=====================================================

<<attachment: HMSoftSmall.jpg>>

Reply via email to