Conversely, it is known, not but not in the official documentation that this is a common problem with the CMDSPACE test and that forcing your own clients to use AUTH and then whitelisting them is the best practice that avoids this problem.
Also, Declude.exe "calls it like it sees it", and doesn't make any exception for known broken software, such as Outlook. Andrew 8) > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Darrell ([EMAIL PROTECTED]) > Sent: Sunday, October 23, 2005 3:18 PM > To: [email protected] > Subject: Re: [Declude.JunkMail] cmdspace command > > Just one bit of clarification - when I used the word "known > issue" it was in the sense that the issue is within the > outlook software and not Declude. > > Darrell > ------------------------------------------- > Check out http://www.invariantsystems.com for utilities for > Declude And Imail. IMail Queue Monitoring, Declude Overflow > Queue Monitoring, SURBL/URI integration, MRTG Integration, > and Log Parsers. > > ----- Original Message ----- > From: "Darrell ([EMAIL PROTECTED])" > <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Sunday, October 23, 2005 6:06 PM > Subject: Re: [Declude.JunkMail] cmdspace command > > > > Travis, > > > > This is a known issue - you should auth / whitelist auth > all of your local > > clients that connect/send email through your mail server. > > > > Darrell > > ------------------------------------------- > > Check out http://www.invariantsystems.com for utilities for > Declude And > > Imail. IMail Queue Monitoring, Declude Overflow Queue Monitoring, > > SURBL/URI integration, MRTG Integration, and Log Parsers. > > > > ----- Original Message ----- > > From: "Travis Sullivan" <[EMAIL PROTECTED]> > > To: <[email protected]> > > Sent: Sunday, October 23, 2005 5:06 PM > > Subject: [Declude.JunkMail] cmdspace command > > > > > >> declude 1.82 > >> ms-outlook express win xp > >> > >> cmdspace scores a hit... here are my headers: > >> > >> > >> ----- Original Message ----- > >> From: "Serge" <[EMAIL PROTECTED]> > >> To: <[email protected]> > >> Sent: Sunday, October 23, 2005 1:50 PM > >> Subject: Re: [Declude.JunkMail] found something new to me > >> > >> > >>> Matt said: > >>> <On the other hand, if you want to tag just two tests in > combination, > >>> this is very easy to do using a different approach. For > instance, if > >>> you wanted to filter for something that failed both > SPAMCOP and XBL (and > >>> anything else), you could do so as follows: > >>> > >>> TESTSFAILED END NOTCONTAINS SPAMCOP > >>> TESTSFAILED 0 CONTAINS XBL> > >>> > >>> why can't this approach be used for any number of tests ? > >>> > >>> TESTSFAILED END NOTCONTAINS SPAMCOP > >>> TESTSFAILED END NOTCONTAINS SBL > >>> TESTSFAILED 0 CONTAINS XBL> > >>> > >>> will tag a message that failed all 3 tests. No ? > >>> > >>> > >>> ----- Original Message ----- > >>> From: "Matt" <[EMAIL PROTECTED]> > >>> To: <[email protected]> > >>> Sent: Saturday, October 22, 2005 9:06 PM > >>> Subject: Re: [Declude.JunkMail] found something new to me > >>> > >>> > >>>> Travis, > >>>> > >>>> Not exactly. The TESTSFAILED string is a space > separated string of > >>>> tests that failed, so if SPAMCOP, SBL and XBL hit, the > string would > >>>> look like the following: > >>>> > >>>> SPAMCOP SBL XBL > >>>> > >>>> If you are looking for more than two tests, it requires > you to have the > >>>> order the same as Declude records them, so for instance > the above > >>>> string would need to be matched exactly like so: > >>>> > >>>> TESTSFAILED 0 CONTAINS SPAMCOP SBL XBL > >>>> > >>>> The following wouldn't hit however because the string > wouldn't match: > >>>> > >>>> TESTSFAILED 0 CONTAINS SBL XBL SPAMCOP > >>>> > >>>> That means that you have to be careful about how you > order your tests > >>>> if you are looking to match more than two, and you also > have to be > >>>> aware of the order in which Declude runs certain types > of tests, for > >>>> instance all blacklists are run before built-in Declude > tests, and > >>>> those are run before External tests, and External tests > are run before > >>>> custom filters. Sometimes you can just make non-scoring > filters to tag > >>>> a certain test in order to guarantee their order just in > case there are > >>>> other tests that can appear in between them. > >>>> > >>>> On the other hand, if you want to tag just two tests in > combination, > >>>> this is very easy to do using a different approach. For > instance, if > >>>> you wanted to filter for something that failed both > SPAMCOP and XBL > >>>> (and anything else), you could do so as follows: > >>>> > >>>> TESTSFAILED END NOTCONTAINS SPAMCOP > >>>> TESTSFAILED 0 CONTAINS XBL > >>>> > >>>> Why is this so difficult? Because it wasn't designed > for combo-ing > >>>> tests...but you can make it do just that with a little > elbow grease. > >>>> Combo-ing tests is a kludge that came about after the TESTFAILED > >>>> variable was introduced for a separate reason. > >>>> > >>>> Matt > >>>> > >>>> > >>>> > >>>> > >>>> Travis Sullivan wrote: > >>>> > >>>>> I think I got it... I am slow, I know :) > >>>>> > >>>>> global.cfg contents: > >>>>> COMBO filter C:\IMail\Declude\lists\combo.txt x 0 0 > >>>>> > >>>>> combo.txt file contents: > >>>>> TESTSFAILED 10 CONTAINS testname1-testname2 > >>>>> > >>>>> ================ > >>>>> > >>>>> So, any test I want to combo script simply take the > testname and > >>>>> seperate them by a hyphen? > >>>>> > >>>>> like: > >>>>> SPAMCOP-SBL > >>>>> > >>>>> ? > >>>>> > >>>>> Thanks, I can definately see how this can further > punish emails... > >>>>> allowing us to lower the scores of the individual tests. > >>>>> > >>>>> Travis > >>>>> --- > >>>>> 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 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 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 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 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 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 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.
