On 3 Mar 2005 at 16:57, David Franco-Rocha wrote:

Excellent David. Good idea Kevin..

This will help us all -

Thanks

-Nick



> Kevin,
> 
> When was the last time someone granted you a request simply because
> you asked? :-)
> 
> We are currently making changes to the log whereby the debug mode will
> show all actions for all users, so that it will be much easier to see
> exactly what happened to any particular email.
> 
> David
> 
> ----- Original Message ----- 
> From: "Kevin Bilbee" <[EMAIL PROTECTED]>
> To: <Declude.JunkMail@declude.com>
> Sent: Thursday, March 03, 2005 4:51 PM
> Subject: RE: [Declude.JunkMail] Declude 2.x
> 
> 
> > Would it be possible to change the logging to reflect the final
> > action for each user. This would make since and make it easier to
> > know the final disposition of the email.
> >
> > We use a catchall account on Imail and a message that should have
> > been delete the final disposition showed
> >
> > Last action = IGNORE
> >
> > When it should have been deleted.
> > If the message was processed differently for different accounts then
> > I would expect to see
> >
> > Last action = DELETE - [EMAIL PROTECTED]
> > Last action = IGNORE - [EMAIL PROTECTED]
> >
> >
> > Because in all actuality there were multiple final actions.
> >
> >
> >
> > Kevin Bilbee
> >
> >
> >> -----Original Message-----
> >> From: [EMAIL PROTECTED]
> >> [mailto:[EMAIL PROTECTED] Behalf Of David
> >> Franco-Rocha
> >> Sent: Thursday, March 03, 2005 1:19 PM
> >> To: Declude.JunkMail@declude.com
> >> Subject: Re: [Declude.JunkMail] Declude 2.x
> >>
> >>
> >> Nick,
> >>
> >> Prior to 2.0, the DELETE action had the highest priority and
> >> affected all recipients of a message. Even with per-user settings,
> >> if one user triggered the DELETE action, the email was deleted for
> >> everyone.
> >>
> >> A change was made in 2.0 to allow for deletions to be made on a
> >> per-user level: If there are three recipients A, B and C, and at
> >> least one of the recipients (B, for example) triggers the DELETE
> >> action, the envelope is modified and the new recipients are A and
> >> C. That seems to be working fine. The problem arises with DELETE
> >> which has been preceded by another action that has already modified
> >> the recipient. If my per-user cfg indicates that:
> >>
> >> WEIGHT10 ROUTETO [EMAIL PROTECTED]
> >> WEIGHT15 DELETE
> >>
> >> I expect to re-route email that fails WEIGHT10 but to simply delete
> >> email when it fails the higher weight because the probability of
> >> spam there is much higher and I do not want to waste my time
> >> checking it. The problem is that the WEIGHT10 ROUTETO action
> >> removes me as a recipient and replaces me with [EMAIL PROTECTED];
> >> when the DELETE action is triggered, it tries to delete me as a
> >> recipient, but I have already been replaced, so the deletion does
> >> not occur.
> >>
> >> There are several combinations and scenarios that can occur with
> >> multiple recipients and multiple actions, and we are studying and
> >> testing this very carefully. There may be other facets of your
> >> issue that do not apply here, and I will take a very careful look
> >> at it.
> >>
> >> David
> >>
> >> ----- Original Message -----
> >> From: "Nick Hayer" <[EMAIL PROTECTED]>
> >> To: <Declude.JunkMail@declude.com>
> >> Sent: Thursday, March 03, 2005 3:51 PM
> >> Subject: Re: [Declude.JunkMail] Declude 2.x
> >>
> >>
> >> > On 3 Mar 2005 at 15:06, David Franco-Rocha wrote:
> >> > Hi David,
> >> >
> >> > I am having problem with the DELETE action as well; have sent 2
> >> > support requests - would this issue be related to what you
> >> > describe below as well?
> >> >
> >> > Thanks
> >> >
> >> > -Nick Hayer
> >> >
> >> >> We wish to let everyone know that through our own testing,
> >> >> support emails and forum responses, we understand that there is
> >> >> some confusion over Version 2.x actions with regard to per-user
> >> >> setting code changes. We are analyzing and evaluating various
> >> >> options and will soon release procedures to deal with this
> >> >> issue.
> >> >>
> >> >> ---
> >> >> [This E-mail was scanned for viruses by Declude Virus
> >> >> (http://www.declude.com)]
> >> >>
> >> >> ---
> >> >> This E-mail came from the Declude.JunkMail mailing list.  To
> >> >> unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
> >> >> type "unsubscribe Declude.JunkMail".  The archives can be found
> >> >> at http://www.mail-archive.com.
> >> >>
> >> >
> >> >
> >> > ---
> >> > [This E-mail was scanned for viruses by Declude Virus
> >> > (http://www.declude.com)]
> >> >
> >> > ---
> >> > This E-mail came from the Declude.JunkMail mailing list.  To
> >> > unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
> >> > type "unsubscribe Declude.JunkMail".  The archives can be found
> >> > at http://www.mail-archive.com.
> >> >
> >>
> >> ---
> >> [This E-mail was scanned for viruses by Declude Virus
> > (http://www.declude.com)]
> >
> > ---
> > This E-mail came from the Declude.JunkMail mailing list.  To
> > unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
> > type "unsubscribe Declude.JunkMail".  The archives can be found at
> > http://www.mail-archive.com.
> >
> > ---
> > [This E-mail was scanned for viruses by Declude Virus 
> > (http://www.declude.com)]
> >
> > ---
> > This E-mail came from the Declude.JunkMail mailing list.  To
> > unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
> > type "unsubscribe Declude.JunkMail".  The archives can be found at
> > http://www.mail-archive.com.
> > 
> 
> ---
> [This E-mail was scanned for viruses by Declude Virus
> (http://www.declude.com)]
> 
> ---
> This E-mail came from the Declude.JunkMail mailing list.  To
> unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
> type "unsubscribe Declude.JunkMail".  The archives can be found
> at http://www.mail-archive.com.
> 


---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.

Reply via email to