While I don't see the guys at Declude drinking beer, I do see them updating their website and marketing sales. Its a matter or priorities.
3 months may be acceptable for software development, but for a major bug I do not see it as acceptable. And I don't think Scott would have ever let it go this long. IMail has released patches for 8.2 and that may cloud the issue, but that means Declude has to stay focused. It would be better to clearly communicate they have an issue to there client base, which they did not, and then create a fix for a particular version of 8.2, rather than chase IPSwitch and every version they produce over a period of a year. If IPSwitch releases another patch will it delay the Declude fix for several more months while they correct the code for the new version? The people that will have this problem are most likely the ones with current service agreements, at least with IPSwitch, the ones paying money to stay on top of the software. Declude should keep this in mind. ----- Original Message ----- From: "Michael Jaworski" <[EMAIL PROTECTED]> To: <Declude.JunkMail@declude.com> Sent: Tuesday, August 23, 2005 9:56 PM Subject: RE: [Declude.JunkMail] Declude and IMail 8.2 Heimir, You may want to consider using this list as your first line of defense. This is the best place to learn of new issues which are brought to everyone's attention by folks who are in the trenches. Keep in mind not everyone here has the latest version and not everyone is using iMail. I would not expect Declude to keep track of what is going on with my particular e-mail servers. I prefer them to spend all resources keeping up with the spammers. A few have made mention of the delay getting out this fix. It hurts when you are the one who is being impacted by an issue. I have been there but in the end I know they will find a fix and get it implemented as soon as possible. I don't see the folks at Declude sitting around drinking beer and working issues when they feel like it. From my experience in the software developing cycle 3 months for a major change is fast. Keep in mind they need to test and retest all those features we have requested over the years. Add the issue of iMail changing their software and then balance it out with what we pay for maintenance ... I am happy they are still in business constantly working and listening to us to update their product(s). Best to not play victim but actively monitor this anti-spam community created by Scott and driven by a lot of knowledgable, talented and hard working customers. And maintain your maintenance agreement. Small price to pay for what the product does for my customers. Michael Jaworski Puget Sound Network, Inc. (206) 217-0400 (800) 599-9485 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Heimir Eidskrem Sent: Tuesday, August 23, 2005 5:43 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Declude and IMail 8.2 Thank you for the update. It concern me that I can't find the email notifying your customer about this bug. Could you tell me when it was sent so I can find it and make sure I am not holding this type of emails. They are critical to us so I will put some effort in making sure I get them. Its been over 2.5 months. The fix will not be available for some time according your email. This is a very long time and frankly I think it makes Declude look very bad. I think there have been plenty of complaints about Declude lately. It seems that your reputation is getting a little tarnished. [EMAIL PROTECTED] wrote: > Thank you for you posts. > >We understand your frustration; here are the facts so there is no >confusion. > >1. This is NOT a bug in Declude. Ipswitch made changes to their IMail >architecture, making it incompatible with Declude and this requires a >fundamental re-write of Declude not a 10 minute fix. 2. As soon as we >were aware of these changes we began development to modify Declude to >work with IMail 8.2. 3. It has been our priority and focus since we >first identified the problem. > >4. In order to deliver a quality product, sufficient testing needs to >be done to ensure customer satisfaction. Since identification of the >issue additional patches have been released by Ipswitch meaning >additional testing and development has been required. 5. This is not an >issue of interim releases as Declude product architecture has had to >change making it very different from earlier versions of Declude. 6. >This is not an issue of having Scott back as the situation would be no >different from today. We are in regular consultation with Scott and we >all agree as to the product direction and problem resolution. > >If there was an easier, faster, simpler way in which we could achieve a >resolution we would do it. > >Barry > > >--- >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.
