> They are. So far, you have not showed any glaring omissions from the docs.
I thought I did in the last letter about rmbsmtpd -r. I have the same
question now as a poster from Feb 1. The only "docs" I had were the
mail that I saved at that time beccause I knew I would be comeing back
to it.
I came back to it and the mail gives me some insight -- but what is done
in the mail isn't documented anywhere. Oh, show me how it's done and
give me a reference to where multiple -r's is documented in the manual
and I promise I'll unsubscribe from this list and never say another word
to it.
> > Just for curiosity? How would you suggest learning more about qmail and
> > what would be your gauge as to when it would be appropriate for someone
> > who has installed qmail to be able to install the qmail-uce? It's really
> > too bad it's written in c++ and not in a more standard language.
> The qmail-uce patch is not written in C++.
*sigh* Perhaps it's possible to run the qmail-uce without the
dependencies that it has. Perhaps not. But, when I was installing
the dependencies for qmail-uce, I was told that my compiler didn't
create c++ files.
> That right there shows that you do not have a good grasp of what's going
> on.
You're so exactingly clever. You can't see the sun for the light.
> As far as suggestions go, I would suggest that you learn a little bit about
> Unix in general, and how to compile and install software packages.
> Furthermore, it won't hurt to learn a little bit about C programming
> yourself (even C++).
I drive a stick shift, by the way.
Sam, just for sh!ts and giggles, how long have you been writing
software? How long would you guess I have been (writing and compiling?)
Sam, guns don't kill people, bullets do, right?
I'm serious. One poster wrote me and said that you're prone to be
opinionated and capable of rather "rude" messages. That's fine with me
-- I can dish the crap right back. I guess this should be expected
in software now adays.
Scott
