| Anonymous 2007-04-22, 7:12 pm |
| admin@eelbash.yi.org wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I took the word of the gentleman who said there was a problem with our
> mail server, and switched the remailer to a new account. The new key and
You mean you FINALLY figured out that Mercury/Wine under Suse just
don't get it?
If only that were the end of, or even your biggest, problems. 
> capstring are below. This is somewhat abrupt, but I have the feeling it
> will not be disruptive and trust it will solve the problem that he
Of course it won't be disruptive. You can't disrupt what you have no
influence over in the first place.
> described. My tests (from outside accounts, naturally) indicate there is
> no problem.
You mean you FINALLY figured out that mail servers behave differently
from local and remote locations?
If only that were the end of, or even your biggest, problems
> I also added the inflate directive to the remailer's capabilities, as
You're not running a remailer, you're running a crippled copy of
remailer software inappropriately (still) and trying to compensate for
your technical incompetence with scripts written in a language you
don't understand at all.
> well as enabling it to remove garbage on input, i.e., input that was
> created with an inflate directive from the remailer which sent the
> message to Eelbash.
>
> This was done in place of using remix, which wasn't a good idea, and it
> should provide adequate obfuscation.
>
> Questions? Comments? Don't be afraid to post them here.
Thanks. I'm not.
You'll never be a useful member of the remailer network. Not only are
you unable to run a proper remailer in spite of your self avowed
"superior intellect", you're such a flake only a handful of operators
will ever acknowledge your existence, and most of those won't
acknowledge you for very long.
Welcome to the bed you've made for yourself....
|