SmarterMail was not deleting these files and were handing them to Declude. That is what was causing the problem. Yes you are correct they should not have been handing these messages to Declude in the first place.
David B www.declude.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John T (Lists) Sent: Wednesday, July 12, 2006 5:36 PM To: [email protected] Subject: RE: [Declude.JunkMail] 4.2 build 20 Released 6 July 2006 So SmarterMail says they were deleting them. My question is when? Files related to an incomplete e-mail session should be deleted right away at the close of the session, not left lying around for another program to pick them up. Could that be what is happening, SmarterMail was deleting them on a cycle or time basis rather than properly at the close of the "failed" session? John T eServices For You "Seek, and ye shall find!" > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Gary Steiner > Sent: Wednesday, July 12, 2006 1:04 PM > To: [email protected] > Subject: RE: [Declude.JunkMail] 4.2 build 20 Released 6 July 2006 > > I don't know. I'm still trying to understand the "problem". Declude added a "fix" to > 4.2.20 that moves files to the error directory that they say were > coming through as > spam leakage. SmarterTools says these files are normally deleted by SmarterMail, > and and the only reason I see them in the error directory is that > Declude puts them > there before SmarterMail has a chance to delete them. Now these two statements > contradict each other. Either SmarterMail was deleting these files or > it was not. Since > I never saw them before 4.23.20, I have to assume that SmarterMail was deleting > them. So if SmarterMail was deleting the files, then why did Declude decide to > intercept them in 4.2.20 and prevent SmarterMail from deleting them? > > Hopefully, since as you say Declude is working with SmarterTools "to resolve this > between us" we will see a new fix soon that will make this issue moot. > > > > -------- Original Message -------- > > From: "David Barker" <[EMAIL PROTECTED]> > > Sent: Wednesday, July 12, 2006 7:48 AM > > To: [email protected] > > Subject: RE: [Declude.JunkMail] 4.2 build 20 Released 6 July 2006 > > > > Gary, > > > > If we gave you the option to delete these messages (as SmarterMail should be > > doing) rather than move them to the \error directory would that > > solve your > > problem ? > > > > David B > > www.declude.com > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > > Gary Steiner > > Sent: Wednesday, July 12, 2006 3:41 AM > > To: [email protected] > > Subject: RE: [Declude.JunkMail] 4.2 build 20 Released 6 July 2006 > > > > As far as I'm concerned it's not a solution. SmarterMail deleting > > these messages was not a problem for me, Declude dumping them into > > the error folder is. I wasn't having a problem before 4.2.20, now I am. > > > > Everyone in support has their stint as the piñada. My users don't > > know who > > SmarterTools or Declude are, they just know when they don't get > > their messages or messages they send don't reach their destination. > > But they know > > who I am, so I have to hold their hands and hear their cries and > > then take > > it back to SmarterTools and Declude. And believe me, my users > > really know > > how to hit a piñada because most of them are Spanish. :) > > > > Another interesting thing is, before the decision was made to put > > this "fix" > > in a release version, didn't anyone foresee that dumping all these > > previously deleted files into the error folder would cause a problem? As > > soon as all those messages started showing up in my error directory > > it became pretty obvious. Seems that this work you mention that > > Declude is doing with SmarterMail to resolve this problem should > > have been done before > > the "fix" was put into 4.2.20. > > > > > > -------- Original Message -------- > > > From: "David Barker" <[EMAIL PROTECTED]> > > > Sent: Tuesday, July 11, 2006 5:49 PM > > > To: [email protected] > > > Subject: RE: [Declude.JunkMail] 4.2 build 20 Released 6 July 2006 > > > > > > Gary, > > > > > > From time to time I feel like the Declude pinyada but in this > > > instance we have provided a solution for what is happening in SM. > > > And as I have said we are working with them to resolve this between us. > > > > > > David B > > > www.declude.com > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > > > Of Gary Steiner > > > Sent: Tuesday, July 11, 2006 5:31 PM > > > To: [email protected] > > > Subject: RE: [Declude.JunkMail] 4.2 build 20 Released 6 July 2006 > > > > > > I don't have an answer to this question. I just know that it is a > > problem. > > > > > > > > > But what I find amusing is, here is another instance of two > > > vendors of interacting software products who point the finger at > > > each other, both saying "it's the other guy's fault." > > > > > > > > > > > > -------- Original Message -------- > > > > From: "John T \(Lists\)" <[EMAIL PROTECTED]> > > > > Sent: Tuesday, July 11, 2006 5:21 PM > > > > To: [email protected] > > > > Subject: RE: [Declude.JunkMail] 4.2 build 20 Released 6 July > > > > 2006 > > > > > > > > Although I do not use SmarterMail, my take is these are like T > > > > files in Imail where it is not a complete message, but for some > > > > reason SmarterMail is allowing Declude to have them even though > > > > they are not > > > complete. > > > > > > > > John T > > > > eServices For You > > > > > > > > "Seek, and ye shall find!" > > > > > > > > > -----Original Message----- > > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > > > > > Behalf Of Gary Steiner > > > > > Sent: Tuesday, July 11, 2006 12: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. > > > > > > > > --- > > 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.
