Me three! Is it done yet? No? Darn.
Frankly, David, if the Declude app is going to have to rewrite the whole message anyway to insert headers, make it an optional *feature* to fix up the line terminators. Then market it as a unique feature; I understand that Venture Capitalists love their "startups" to have innovative features that differentiate their product in the marketplace. Meanwhile, just fix the Declude app so that inserts the header correctly as befits our reasonable expectations as set by all the other products in the marketplace. Andrew. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Darin Cox > Sent: Wednesday, November 08, 2006 10:41 AM > To: declude.junkmail@declude.com > Subject: Re: [Declude.JunkMail] declude not modifying subject line > > Agreed. Put the headers where they need to be. Don't worry > about "fixing" > the message. > > Having this additional test could be worthwhile as well, to > identify and report on mailers that are broken in this fashion. > > Darin. > > > ----- Original Message ----- > From: "Andy Schmidt" <[EMAIL PROTECTED]> > To: <declude.junkmail@declude.com> > Sent: Wednesday, November 08, 2006 12:03 PM > Subject: RE: [Declude.JunkMail] declude not modifying subject line > > > Hi Dave: > > >> 1. This is currently being worked on, there are several > other things that > need to be taken into account when doing this, for example if > Declude has to > rewrite all me messages in order to correct this problem > there will be a hit > on performance. We are also looking at some other alternatives. Any > suggestions are welcome. << > > Although I know this had been suggested - I personally don't feel that > Declude needs (or even SHOULD) rewrite the message. If the message is > "readable" by Imail, Outlook, etc. - then the sender is "in > luck". If not, > then the fact that other software can't read the message will > motivate the > sender to use RFC compliant formatting. > > I feel all that's necessary is that Declude's end-of-line > parsing should be > made intelligent enough so that it DOES detect various CR > CR/LF LF LF/CR > combinations and treat them as "end-of-line", so that it can > properly detect > the "intended" last header. > > This way, Declude can: > > A) append it's own header at the proper location (not append > it below the > message body.) > > B) determining where the message content starts (so that the > content can be > properly scanned for Viruses) > > > I get the feeling this issue of end-of-line detection is > being made overly > complicated. > > Declude is not a "message-fixer-upper". I have enough > problems with people > using CISCO "SMTP FIXUP" that breaks everything. Declude's job is to > correctly determine the header vs. content and then subject > the header and > content to appropriate "analysis". > > If a message is found to be malformed, then Declude can make it fail a > "Test" so that the mail admin can decide to accept or reject > those messages > - but it's not Declude's job to artificially make an > incompatible message > compatible with email clients. > > > Best Regards > Andy Schmidt > > Phone: +1 201 934-3414 x20 (Business) > Fax: +1 201 934-9206 > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of David > Barker > Sent: Wednesday, November 08, 2006 11:38 AM > To: declude.junkmail@declude.com > Subject: RE: [Declude.JunkMail] declude not modifying subject line > > Herb, > > 1. This is currently being worked on, there are several other > things that > need to be taken into account when doing this, for example if > Declude has to > rewrite all me messages in order to correct this problem > there will be a hit > on performance. We are also looking at some other alternatives. Any > suggestions are welcome. > > 2. This is not as simple as having these type of messages > fail a test as > there are too many variables in play wrt line terminators. > > 3. In your \Declude folder there should be a \Resources > folder which has the > latest config files. > > David B > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Herb > Guenther > Sent: Wednesday, November 08, 2006 11:22 AM > To: declude.junkmail@declude.com > Subject: Re: [Declude.JunkMail] declude not modifying subject line > > Hi David; > > In an earlier message (below) you mentioned that you were > working on adding > the ability to handle these malformed messages. > > A couple questions. > > 1. When will this happen as it has been a problem for quite a > while now? > > 2. The messages themselves are not failing any of the tests > that I am using. > Shouldn't we at least be able to have them fail a test and > then take an > action based on that? > > Also, I want to make sure that all of my config files are > correct, and that > I do not have any depreciated tests in them. When I go to the online > manuals on your site, the links to the "tests" are broken, > and I cannot find > samples of the config files. Can you tell me where they are, > and perhaps > update the links in the KB so that they do point to them? > > Thanks, > > Herb > > David Barker wrote: > > Agreed Andy. > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > > Andy Schmidt > > Sent: Wednesday, November 01, 2006 10:31 AM > > To: declude.junkmail@declude.com > > Subject: RE: [Declude.JunkMail] declude not modifying subject line > > > > Hi David: > > > > Pardon me - but lets not forget that we choose to pay > Declude license > > and maintenance fees, precisely because of its claim of > being superior > > in detecting viruses, vulnerabilities and RFC violations that other > > components are known to letting through. > > > > When your business model is based on the premise that you will be > > closing the holes that other components leave, then Declude cannot > > retreat behind an argument that you are "only as defect as the other > guys". > > > > Clearly, if Imail/Smartermail did act appropriately and offered all > > the features it should, then you wouldn't have a customer > base in the > > first place. > > > > Best Regards > > Andy Schmidt > > > > Phone: +1 201 934-3414 x20 (Business) > > Fax: +1 201 934-9206 > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > > David Barker > > Sent: Wednesday, November 01, 2006 10:02 AM > > To: declude.junkmail@declude.com > > Subject: RE: [Declude.JunkMail] declude not modifying subject line > > > > Herb, > > > > I need to clarify something here. This source of this > problem is that > > these messages do not conform to the RFC's and are extremely broken > > and should not be accepted by the mail server in the first > place. That > > is the source of the problem, Declude is showing the > symptom. Have you > > approached SmarterMail/Imail and asked them to fix this > issue, either > > not accept the message or apply message standardization ? What was > > their > response ? > > > > With that said, we are working on correcting this problem because > > clearly the Mail server is not doing it. > > > > Secondly, there are alternatives to marking the Subject line and > > having the mail server take action based on the headers. > You could use > actions like. > > > > # MAILBOX will move the E-mail to a user's folder (no, not > a Windows > > directory) > > # ROUTETO will re-route the E-mail to an alternate address > # HOLD will > > hold the message in the spool\spam directory. > > > > David B > > > > > > > > > > --- > > 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. > > > > > > -- > Herb Guenther > Lanex, LLC > www.lanex.com > (262)789-0966x102 Office > (262)780-0424 Direct > > > This e-mail is confidential and is for the use of the intended > recipient(s)only. If you are not an intended recipient please > advise us of > our error by return e-mail then delete this e-mail and any > attached files. > You may not copy, disclose or use the contents in any way. > > > > > > --- > 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.
