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 th
I didn't think you COULD omit the space -- it was pure human (as
in, me) error
But realistically, I think at some point it would be a good idea to have
stronger parsing of that command-line to either handle this or generate
an error to the user -- whatever makes sense design-wise. The
alter
In Xmail V1.11 (I assume this is so in other versions), I ran across a
minor bug in how Xmail parses its command-line on start-up.
If you DO NOT put in a space after the -Mr flag (which controls the # of
hours it takes the logs to rotate), the Xmail service will die the first
time it tries to wri
I'm new to Xmail, but I do have a functioning evaluation server up and
running and it seems excellent.
I have one question, though, and I suspect the answer might be simple
but I just don't see it in the docs:
How do I implement a subscribe/unsubscribe control mechanism via email
for a mailing
