What exactly is the problem with the catchall account, and when is a fix expected?
We haven't yet upgraded to 2.0 because of the periodic mention of problems with it on this list, but would like to as soon as all known issues are resolved. We don't have many nobody aliases, but we haven't been able to convince a couple of customers to remove them yet. Darin. ----- Original Message ----- From: "Erik" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, March 01, 2005 8:54 AM Subject: RE: [Declude.JunkMail] Declude 2 and DELETE Fritz, We've experienced the same problem as you and for us, it was narrowed down to the catchall account in Imail. If you have a "catchall" account in the Imail setup, Declude will not work correctly. After many emails to Declude about this, they confirmed to me this IS a problem and one of not a high priority to fix. We've reverted back to 1.82 until it's fixed. Also, Decludes' "COMFIRM.CFG" does not work correctly either when there is a "catchall" account. The local Declude will "intercept" any confirmation email that going to another Imail/Declude Confirm system (thus the email never reaches it's intended source. Again, response from Declude was: "it's not a high priority". Erik -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fritz Squib Sent: Tuesday, March 01, 2005 2:42 PM To: [email protected] Subject: [Declude.JunkMail] Declude 2 and DELETE Apparently I missing something bloody obvious, but with 2.0 running it seems like my delete action doesn't work as expected any more. Running the latest 2.x release downloaded last night. --Global Config-- WEIGHT20 weight x x 20 0 WEIGHT30 weight x x 32 0 --Default.junkmail-- WEIGHT20 HOLD WEIGHT30 DELETE In a brief conversation with Declude the response I got was: "The problem is probably the change in the way the DELETE action works. In the past, it would delete the E-mail for all recipients. Now, it only deletes the E-mail for recipients that use the DELETE action." It still seems like the HOLD action is taking precedence over the DELETE action since mail with weight over my WEIGHT30 test winds up in the hold folder even though the log file says: > 02/01/2005 12:25:06 Qbb6c48770128853b Msg failed WEIGHT30 (Weight of > 44 reaches or exceeds the limit of 32.). Action=DELETE. I has sent Scott debug log files but I still haven't figure out what I'm missing. Yes there are a *few* per user .junkmail files, with an action of WARN, but most of the held mail is either not for them (nor are they CC'd or BCC'd as far as I can tell) and/or (may or may not be related) in the spam review application there is no To: field reported. I have also tried changing 'weight' to 'weightrange' with the appropriate scores, and still see the same results Anyone else ? Fritz Frederick P. Squib, Jr. Network Operations/Mail Administrator Citizens Telephone Company of Kecksburg http://www.wpa.net () ascii ribbon campaign - against html email /\ - against microsoft attachments --- [This E-mail scanned by Citizens Internet Services with Declude Virus.] --- [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.
