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.
Look at what happens with HTML between browsers. The big ol IE vs Netscape. Makes web design harder then all hell. Which I do NOT want to get into, just a side point about standards is all :)
/jesse
-------------------------------------------------------
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
