<laughs> Yeah, you can bet I'll be more careful with command-line parameters in the future :)
But guys, let's kill this thread.... It's pointless. It's true that Xmail has some less-than-good error messages, but I've got Xmail on three separate networks on eight different servers, and I can tell you that it's an excellent product -- and I'm sure there are lots of folks on this list who have even more experience with it and have even more installs of it, and they would agree with me too. And yes, I also agree that better error messages is really, really low on the priority list -- I said as much in my original post -- and I'm sure that Davide would agree with me that good error messages are a good thing and maybe at some point he'll have the desire or opportunity to go back and take a look at improving some of them. But he can't do that if we, the collective users of the software, don't give him adequate feedback on what error messages need improving, or what error conditions need more or better trapping and handling. The main reason I posted my original note was so that OTHER PEOPLE would know about this very tiny bug -- and that it would hopefully save someone else a few hours of chasing their tail over a similar problem. Anyway, I bet I've accomplished that and all of us will be very careful with formatting command-line parameters in the future :) > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Davide Libenzi > Sent: Thursday, January 23, 2003 4:37 PM > To: XMail mailing list > Subject: [xmail] Re: Bug in command line parsing > > > > On Thu, 23 Jan 2003, Andreas Hansson wrote: > > > > > > However you titled your email "Bug in command line > parsing" and it > > > is NOT > > a "bug". > > > > In my opinion, freezing up due to an invalid command line option > > instead of printing/logging an error message or at least > refusing to > > start IS a bug. It's not what well-behaving software should do. > > Unfortunately there seems to be a lot of cases where xmail will > > proceed and fail in some random and hard to debug way instead of > > printing an error message as soon as the problem can be detected. > > Inside an application like Photoshop, I would have to agree. > This is a server software, meant to be used by ppl that know > what they're doing. After you spent 8 hours because of the > use of a bad parameter, the next time I'm pretty sure you > will be more carefull in touching configurations. Or you will > stop using XMail ( natural selection ). And both are good > things. Different is the validaion of parameters coming from > the clients, that must be strongly validated to avoid security flaws. > > > > - Davide > > - > To unsubscribe from this list: send the line "unsubscribe > xmail" in the body of a message to [EMAIL PROTECTED] > For general help: send the line "help" in the body of a > message to [EMAIL PROTECTED] > > - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
