> -----Original Message-----
> From: R. Scott Perry [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 09, 2002 8:53 AM

> So, here's my suggestion.  If you're going to complain, 
> explain WHY you are complaining, and mention the bug that
> is in 7.07 and fixed in 7.1 that affects you.

Here's a filtered list of bugs fixed in 7.1.  I've omitted most
interoperability improvements, reordered the list, and assigned the bugs
series and serial numbers, just to get things rolling.  

Series "A" bugs are the most obvious ones, the ones you'd expect to see just
by using a feature.  Series "B" bugs product symptoms that are more
difficult to spot and explain.  Series "C" bugs might never be noticed
without pretty intense scrutiny and analysis.  And this filtering and
sorting comes with a big "IMHO" all over it...

A.1  Web Calendaring: Recurring events are now all sent as a single instance
representing the first date for that event. Our calendar implementation
didn't handle recurring events sent to it and the ones it sent broke
Outlook.
A.2  Calendar now properly encodes "TEXT" properties -- see RFC 2445.
A.3  Web Calendaring: Accessing days in October from the Yearly view now
sends the user to October, not the current date.
A.4  Web Calendaring: Dates in January with values higher than the last day
in February now go to the correct date in January instead of the last day in
January (ex. Jan 30 sent you to Feb 28)
A.5  Web Messaging: Removed bug that caused crash when users had more than
500 sub-mailboxes.
A.6  SMTP32: The x-rcpt-to line will now be correctly populated.

B.1  SMTP32: Fixed bug causing S: S line to appear in log when a TCP
information message should have been displayed.
B.2  SMTP32: Corrected handling of default maximum mailbox size and maximum
message count when not specified for the user.
B.3  Web Messaging: System admins can now correctly display user attributes.
B.4  IAdmin: Corrected user count display.
B.5  IAdmin: Repaired display of the common name attribute for LDAP.
B.6  IAdmin will no longer allow addition of a duplicate hostname.
B.7  Adduser will no longer add a user to the registry when using NT Domain
and entering an invalid user.

C.1  Corrected DNS queries so MX records would be used in priority order.
C.2  IMAILSRV: Increased size of filename for messages to reduce risk of
name duplication.
C.3  IMail1: Increased size of filename created when sending mail.
C.4  Web Messaging: Sockets which never receive data will timeout rather
than stay open.

Note that I'd be hard pressed to explain how any of the class B or C fixes
really affects me -unless- they're fixed.  I've seen B.1 and wondered if
data was getting lost, but without the missing data I couldn't say how
important it might have been.  I think I've seen B.3 and B.4., but never
when I was relying on it.  The class C fixes would just seem like general
transient mail failures, fixed by time or a reboot - hence my original
wonder at C.1 upon first glancing at the release notes.

Continuing MHO, there's another way to divide these fixes:

Some fixes correct advertised features that I already paid for but never
really got.  I paid for a calendar function, not a calendar function that
doesn't know how to access October.  I paid for a mail server that works
with the norms of the DNS system.  And so on...

Other fixes correct how IMail does what I expected it to do when I bought
it.  I expected that an administrative interface would show me user
attributes, and could count its own users.  I expected the logging features
to log the transactions, not the uninitialized variables.  I expected that
spooled file namespace would be large enough to avoid collisions.  Perhaps
I'm expecting too much?

None of these bugs I listed are anything more than what I've already paid
for in 7.0x, and they're nothing more than what I thought IMail would
deliver.  Since that wasn't the case, I feel I might be due a partial refund
for that purchase, which I'll gladly apply to the purchase of a service
contract extension.

-- 
Dave Salovesh
RAM Associates, Inc.
(800) 543-3635



Please visit http://www.ipswitch.com/support/mailing-lists.html 
to be removed from this list.

An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/

Please visit the Knowledge Base for answers to frequently asked
questions:  http://www.ipswitch.com/support/IMail/

Reply via email to