Whatever the previous setup was seemed to be working fine for us. I guess 
SmarterMail was deleting these automatically? We have well over 10,000 email 
accounts and never saw any spam leakage as discussed here. 

Now I have an error directory that grows 1+ GBs each day. If SmarterMail isn't 
deleting these correctly then I hope this information has been passed to them 
so this can be fixed. SmarterMail has been pretty responsive to our requests. 
It seems odd that Declude would have to hack together a "fix" for something 
that is apparently a SmarterMail issue.

I just don't want to have to deal with thousands of messages in the error 
directory and have to search through them daily to ensure they should all be 
there.  

 Mark Strother
 Pacific Online
 Phone: 604-638-6010 ext. 222
 Fax: 604-638-6020
 Toll Free: 1-877-503-9870
 http://www.pacificonline.com

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Barker
Sent: Wednesday, July 12, 2006 4:33 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.

Reply via email to