Sam Varshavchik wrote:
Is your name Sybil? So far, looks like you're the only one who's having
persistent problems. Last time I checked, there was almost 900 subscribers
to this mailing list. Clearly, most folks can figure things out without
much difficulty.
I've been lurking on this list for a while. Pretty much most of the
posts are from people who are at their wits end trying to figure out
what on earth is going on.
To quote someone else in a discussion on another list:
"FWIW, I've found courier-IMAP to be one of the less friendly open
source packages around. Heh. How 'bout we fork his codebase?"
People can expect anything they want to expect. It is not feasible to
anticipate everyone's expectations, because everyone will have different
expectations. You can't please them all.
"You can't please them all" is a really lame excuse for "you refuse to
please anyone".
So far the only thing you've shown that's not "properly indicated" is that
it's not made explicitly clear that aliasing rewriting happens before the
remaining processing. If you actually asked about it instead of writing
lengthy editorials, you would've had your answer much earlier.
I had no such question - you're mixing me up with someone else. If you'd
paid attention during the thread you would have known that.
What you do then is ponder the likelyhood of designing a relatively
complicated piece of software that attempts to anticipate every possible
kind of a configuration failure, and responds with step-by-step instructions
for repairing the configuration failure.
Nope - all you need to do is wherever in your code you see "return
(error-condition)" you preceed it with a single line of code to return
the reason for the error condition.
Simple.
Regards,
Graham