I'm curious as to who was experiencing this deluge. As far as I can tell, 99.9% of the messages now ending up in the error folder are ones that SmarterMail (previous to Declude 4.2.20) would have deleted, and both the user and the system administrator (me) would never have seen them, let alone known that they had even existed. So the only deluge I can see (previous to Declude 4.2.20) would have been in the bit bucket.
Sandy hit it right on the nose in stating that this should have been a configurable option. Previously, the only held spam was that which the system administrator had configured as being held. Now Declude has arbitrarily turned the error folder into a new hold folder completely out of the system administrator's control. And if this is indeed a SmarterMail problem, what is Declude going to do if and when SmarterMail fixes it? Rip the bandaid off and put things back to the way they were? -------- Original Message -------- > From: "David Barker" <[EMAIL PROTECTED]> > Sent: Tuesday, July 11, 2006 4:10 PM > To: [email protected] > Subject: RE: [Declude.JunkMail] 4.2 build 20 Released 6 July 2006 > > That is exactly what was happening prior to the fix and it created a deluge > of spam ending up in SmarterMail inboxes. > > David B > www.declude.com > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin > Bilbee > Sent: Tuesday, July 11, 2006 3:49 PM > To: [email protected] > Subject: RE: [Declude.JunkMail] 4.2 build 20 Released 6 July 2006 > > How about if the message has failed in the .hdr file declude just ignores > the file to let SmarterMail process it as it see fit??? > > > Kevin Bilbee > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > > David Barker > > Sent: Tuesday, July 11, 2006 12:26 PM > > To: [email protected] > > Subject: RE: [Declude.JunkMail] 4.2 build 20 Released 6 July 2006 > > > > Not sure who you spoke to at SmarterTools but I do NOT believe this is > > true. > > > > > > Declude will not pick up a message until it is completed writing both > > the .hdr and .eml files, that is the reason why SmarterMail while > > writing the header will have the .eml file as .em_ (while writing) so > > that when the .hdr is complete ie. Written then and only then will > > Declude pick up the file to process it. Also you will see clearly, > > that the SM logs indicate a problem long before we receive the message. > > > > This was a new problem introduced by SmarterMail - 4.2.20 provided a > > fix for this. Again coming back to a previous post I made talking > > about the effects of the Mail server on Declude. The question always > > comes back to who should provide the fix, in this case we did as it > > was causing messages not being scanned by Declude for spam. > > > > I am trying to get a better understanding to the problem from SM and > > as soon as I have some answers from them I will post to the lists. > > > > David B > > www.declude.com > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > > Gary Steiner > > Sent: Tuesday, July 11, 2006 3:13 PM > > To: [email protected] > > Subject: RE: [Declude.JunkMail] 4.2 build 20 Released 6 July 2006 > > > > Here is SmarterTools take on the problem: > > > > > Failed is written to the .hdr if the message was not succesfully > > > recieved via SMTP. For instance, if the connection is closed mid > > > transmission. These(and corresponding .emls) are normally just > > deleted > > > by SmarterMail. The only reason you are noticing them is because of > > Declude storing them in the error folder. > > > > The implication is that Declude is interrupting part of SmarterMail's > > normail process. Now I know this is essentially what Declude does > > anyway, but shouldn't Declude know the difference between a message > > that has finished SMTP and SmarterMail is ready to deliver, and a > > message that is incomplete in the SMTP process and an SMTP retry is > > occurring so this failed message should be ignored? Otherwise we are > > going to get thousands of unneccessary incomplete messages dumped into > > the error folder that is going to do nothing other than to take up > > disk space. Not to mention that if some other type of error occurs > > that puts a message in the error folder, we'll never find it because > > its buried under all these other superfluous messages. > > Before 4.2.20, this wasn't a problem. > > > > > > > > -------- Original Message -------- > > > From: "David Barker" <[EMAIL PROTECTED]> > > > Sent: Monday, July 10, 2006 3:24 PM > > > To: [email protected] > > > Subject: RE: [Declude.JunkMail] 4.2 build 20 Released 6 July 2006 > > > > > > Gary, > > > > > > This is a SmarterMail issue. When they fail to complete the .hdr > > > file they write "Failed" in the .hdr as this was causing major spam > > leakage > > > for declude we decided to move incomplete messages to the \error > > > folder. You could try changing the "Failed" to Written and drop the > > > messages in the \spool. > > > > > > David B > > > www.declude.com > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > > > Gary Steiner > > > Sent: Monday, July 10, 2006 2:52 PM > > > To: [email protected] > > > Subject: re: [Declude.JunkMail] 4.2 build 20 Released 6 July 2006 > > > > > > Now that I've installed 4.2.20, I'm getting a lot of messages in the > > > error folder (I'm running SmarterMail 3.3.2369). Most of them seem > > to > > > be spam, but there are some good messages in there. Am I now going > > to > > > have to scan this folder for false positives just like the held spam > > folder? > > > > > > Here is an example of the .hdr file for a message that was good: > > > > > > Failed > > > [EMAIL PROTECTED] > > > [EMAIL PROTECTED] > > > cmdspc: false > > > helo: ivmail1.fcc.es > > > > > > What does "Failed" mean? Is there something I can look for in the > > > headers of the message (in the .eml file) that would indicate this? > > > Is there any way to requeue this message? > > > > > > > > > -------- Original Message -------- > > > > From: "David Barker" <[EMAIL PROTECTED]> > > > > Sent: Friday, July 07, 2006 11:01 AM > > > > To: [email protected]>, <[email protected] > > > > Subject: [Declude.JunkMail] 4.2 build 20 Released 6 July 2006 > > > > > > > > EVA ADD New NONSTANDARDHDR vulnerability test. Messages > > found to > > > > have broken headers are moved to the \virus folder > > > > > > > > EVA FIX ALLOWVULNERABILITIESFROM (for user) > > > > > > > > EVA FIX BANEXT buffer overflow > > > > > > > > SM ADD When an error is found in the envelope (.hdr) file > > the > > > > message is moved to the \error folder > > > > > > > > SM ADD Decludeproc will not start without a valid > > domainlist.xml > > > > > > > > SM FIX QUEUEFILE_SAVEFILE the log is showing the correct > > directory > > > > path > > > > > > > > SM FIX Allows admin to set VIRDIR to any directory path in > > the > > > > virus.cfg > > > > > > > > David Barker > > > > Product Manager > > > > Your Email security is our businessT > > > > 978.499.2933 office > > > > 978.988.1311 fax > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > --- > > > > 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. --- 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.
