----- Original Message -----
From: "Jesse Cablek" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 12, 2003 10:10 AM
Subject: Re: [courier-users] RFC compliance: goodbye to courier MTA
> Gregor Lawatscheck wrote:
> [...]
> > an ISP should have to hack it to get full compatibility with all the
> > flawed clients around.
> >
> [...]
>
> As good as this may be, it only promotes the flawed clients to not be
> fixed, because what they use, works. I wouldn't want any software that
> promotes the use of non-standard protocol, and would expect it to be
> hacked to gain (or should I say lose) the functionality.
>
> If there are flawed clients out there, get them fixed. Get the company
> to issue a patch for the product instead of releasing a whole new
> version, then notify your users in a monthly email that they should
> patch their clients for best functionality.
>
> While that also sounds good in theory, it also is not the most feasible,
> but i'd prefer it over allowing broken clients to stay broken, which
> breaks SMTP more than it already is.
>
this seems to be the general opinion here. standards are there to be
followed and to enable compatibility. one cannot plan ahead for all the
quirks would-be developpers introduces in their software. if you can't
follow the standard, then you deserve to die (not literally :P)
the original author pointed something about a broken italian OE 5.5, and it
being "too complicated to get every users to upgrade"
well tell you what, we did just that. when we moved to courier, many of our
users were using OE 4.0 which was completly broken. and we still managed to
guide them through upgrading to the lastest (5.5 at the time). your argument
against not upgrading is one of lazyness, not a technical problem at all.
you're asking for the wrong fix
the process involves giving users a link to the microsoft site and telling
them to get the new version, sometimes guiding them a bit along the way (as
much help as you can give in a 3-step process). surely your tech support can
handle that, can they? if not... i suggest you fire them and hire better
tech support guys.
there is not even an issue of stability, i can see wanting to keep a server
in a "stable" state (as stable as a windows server can get). but windows on
the desktop is already so unstable, you probably wouldn't notice a
difference upgrading
oh by the way, making threats of "quitting" is really the lamest thing one
can do. if you're not happy, then by all mean go away. makes the world (or
in this case, mailing list) a better place for those of us who are.
(sorry jesse, didn't mean to post this in reply to you, just reading the
whole discussion at once)
--
Daniel Higgins
Administrateur Syst�me / System Administrator
Netcommunications Inc.
Tel: (450) 346-3401 (st-jean)
(514) 871-1844 (montr�al)
Fax: (450) 346-3587
http://www.netc.net
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
