|
Home > Archive > Anonymous Servers > November 2006 > Mixmaster references header chopped up....
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Mixmaster references header chopped up....
|
|
| Anonymous 2006-11-29, 1:12 pm |
|
Greets 2 all.
I'm trying to avoid being a NETPORK who posts mixmastered
usenet articles that do not thread properly for some reason.
No problem in the case of originating posts or even first
responder ones, but the effort comes undone when 2nd and
deeper level threading is needed. ???
Always editing with nedit, I use a bash script to invoke
mixmaster (client only) against a prepared source.txt file.
Never did like front-ends. Here's an adapted part sample
#!/bin/bash
# show up to 3 references, NO COMMAS
# show In-Reply-To for directly referenced message-id
# First responder shows same references and inreply2
mixmaster source.txt \
-v --post-to=alt.privacy.anon-server \
--header="Subject: Re: whatever" \
--header="References: <ref1@dom1><ref2@dom2><ref3@dom3>" \
--header="In-Reply-To: <ref3@dom3>"
Mix then produces an asci outfile which I mail as per
normal to the shown remailer after removing the open
data at the top.
From: user@machine
To: mixmaster@mailer.soandso
::
Remailer-Type: Mixmaster 3.0rc1
-----BEGIN REMAILER MESSAGE-----
20480
Ew989bCq3umzsEO55O3K9g== ..etc
But once the post appears on usenet it often does so with
truncated and/or spaced out references like
References: <ref1@dom1> <ref2@ > <ref3@dom3>
In one case the @ in the middle had been replaced by
an O (capital O) followed by abuncha spaces.
I've tried 2.9.1 and 3.0rc1, same results.
What am I messing up?
Can I write headers INTO the text body before mixing?
What syntax to use?
Can I save an originating post as a file and then use
the -fr switch to create a mixed response to it, or
maybe save a response as a draft and then somehow pipe
it to mixmaster?
Is there an open-source Linux front end I could try?
Thanks for all hints & links to read.
| |
|
| On 29 Nov 2006 17:48:58 -0000, Anonymous wrote in
Message-Id: <IZJXW25839050.492337963@anonymous.poster>:
> But once the post appears on usenet it often does so with
> truncated and/or spaced out references like
Not sure if this is a remailer or mail2news problem. To narrow it down,
can you try hardcoding the exit remailer to one that supports Np (direct
usenet posting) rather than Nm (post via mail2news).
--
pub 1024D/8ED57743 2003-07-08 Bananasplit Operator
Key fingerprint = 796F 67E0 E890 A0BB BDAE EBB4 94A6 7A09 8ED5 7743
uid Admin <admin.bananasplit.info>
| |
| Anonymous 2006-11-29, 7:13 pm |
| Zax wrote <ekkkur$65d$1@bananasplit.info>:
> Not sure if this is a remailer or mail2news problem. To narrow it down,
> can you try hardcoding the exit remailer to one that supports Np (direct
> usenet posting) rather than Nm (post via mail2news).
Thanks for responding!
I've just changed to and ISP who does not offer nntp so
I have to work with a free news server to which I cannot
post. This happens to be good mix pratctice but is a little
time consuming :-)
Here goes with banana as last remailer using
--header="References: <IZJXW25839050.492337963@anonymous.poster> <ekkkur$65d$1@bananasplit.info>" \
--header="In-Reply-To: <ekkkur$65d$1@bananasplit.info>" \
BTW I found worse, a potential security problem even. I don't
realy need hard privacy but it may interest others regradless
of whether its fingertrouble or whatever.
Some of the headers that show up may include pieces of the
mixmaster path on my machine as part of References such as
<456d45d3/home/user/etc/mix/etc/scriptname087@news.server.name>
It may happen in this case, i have no way to predict it.
| |
| Nomen Nescio 2006-11-29, 7:13 pm |
| Zax wrote:
> On 29 Nov 2006 17:48:58 -0000, Anonymous wrote in
> Message-Id: <IZJXW25839050.492337963@anonymous.poster>:
>
>
> Not sure if this is a remailer or mail2news problem. To narrow it
> down, can you try hardcoding the exit remailer to one that supports
> Np (direct usenet posting) rather than Nm (post via mail2news).
Has anyone bothered to see it this might be a remnant of a script that
was posted here a while back, then modified by the notorious eelbash?
It was dropping and truncating references headers quite regularly if
I remember correctly.
| |
| Anonymous 2006-11-29, 7:13 pm |
| Nomen Nescio wrote:
> Zax wrote:
>
>
> Has anyone bothered to see it this might be a remnant of a script that
> was posted here a while back, then modified by the notorious eelbash?
> It was dropping and truncating references headers quite regularly if
> I remember correctly.
It's my own, started out with a single command line
that got to be too long (it may well be a poor one).
I'm sending this one through a Nm exit remailer to see if
I could duplicate the problem.
| |
| Stephen K. Gielda 2006-11-29, 7:13 pm |
| nobody@mixmin.net wrote in message news:
<afbe4d8864a54456435150439018450a@anon.mixmaster.mixmin.net> ...
> Zax wrote <ekkkur$65d$1@bananasplit.info>:
>
>
> Thanks for responding!
>
> I've just changed to and ISP who does not offer nntp so
> I have to work with a free news server to which I cannot
> post. This happens to be good mix pratctice but is a little
> time consuming :-)
>
>
> Here goes with banana as last remailer using
>
> --header="References: <IZJXW25839050.492337963@anonymous.poster> <ekkkur$65d$1@bananasplit.info>" \
> --header="In-Reply-To: <ekkkur$65d$1@bananasplit.info>" \
>
> BTW I found worse, a potential security problem even. I don't
> realy need hard privacy but it may interest others regradless
> of whether its fingertrouble or whatever.
>
> Some of the headers that show up may include pieces of the
> mixmaster path on my machine as part of References such as
>
> <456d45d3/home/user/etc/mix/etc/scriptname087@news.server.name>
>
> It may happen in this case, i have no way to predict it.
The references header chopping is due to an 80 character limit. Fold
any headers over 80 char. The other is because you are using a shell
script and not escaping $, it's being read as a variable, escape the $.
/steve
--
Cotse.Net Privacy Service
Advanced e-mail, ssh, proxies, web hosting, and more.
Your Shield From The Internet
http://www.cotse.net
| |
| Anonymous 2006-11-29, 7:13 pm |
| Zax wrote:
> On 29 Nov 2006 17:48:58 -0000, Anonymous wrote in
> Message-Id: <IZJXW25839050.492337963@anonymous.poster>:
>
>
> Not sure if this is a remailer or mail2news problem. To narrow it down,
> can you try hardcoding the exit remailer to one that supports Np (direct
> usenet posting) rather than Nm (post via mail2news).
Still with a Nm exitpoint but according to Stephen's suggeston,
Using:
--header="Subject: Re: Mixmaster references header chopped up...." \
--header="References: <IZJXW25839050.492337963@anonymous.poster> \
<ekkkur\$65d\$1@bananasplit.info>" \
--header="In-Reply-To: <ekkkur\$65d\$1@bananasplit.info>" \
| |
| Nomen Nescio 2006-11-29, 7:13 pm |
| On Wed, 29 Nov 2006 21:19:50 +0000, Anonymous wrote:
> Nomen Nescio wrote:
Let's be fair to eelbash. It was the original script that was dropping and
truncating headers. Eelbash's modification simply did not correct the
original problem, which put there by the script's author, SofaKing.
Eelbash, to his great credit, did correct the problem once he was aware
of it.
[vbcol=seagreen]
>
> It's my own, started out with a single command line
> that got to be too long (it may well be a poor one).
>
> I'm sending this one through a Nm exit remailer to see if
> I could duplicate the problem.
| |
| Anonyma 2006-11-30, 1:14 am |
| Nomen Nescio wrote:
> On Wed, 29 Nov 2006 21:19:50 +0000, Anonymous wrote:
>
>
> Let's be fair to eelbash. It was the original script that was
> dropping and truncating headers. Eelbash's modification simply did
> not correct the original problem, which put there by the script's
> author, SofaKing.
>
> Eelbash, to his great credit, did correct the problem once he was
> aware of it.
No he did not, as we can see from his recent flurry of screwed up
headers. In fact there's been quite a few of those messages posted
here with one thing in common.
You get three guesses.......
>
>
>
>
>
>
>
>
>
>
>
>
>
| |
| Anonyma 2006-11-30, 1:14 am |
| Stephen K. Gielda wrote:
> nobody@mixmin.net wrote in message news:
> <afbe4d8864a54456435150439018450a@anon.mixmaster.mixmin.net> ...
>
> The references header chopping is due to an 80 character limit. Fold
> any headers over 80 char. The other is because you are using a shell
> script and not escaping $, it's being read as a variable, escape the
> $.
>
> /steve
Just to be technically precise, it's a 78 character limit plus a CR/LF
pair (some people may forget about that and count 80 without the CR/LF).
Also the "official" limit is 998 characters, 78 is really a
recommendation given because some clients screw up anything over 78,
not because transports do.
It should also be noted that while header folding is defined as
inserting a single whitespace character after a CR/LF, when those
headers are unfolded RFC dictates that only the CR/LF be removed. If
you're folding with a TAB you might run into the same problems you're
having without folding if any TAB to SPACE conversion takes place.
|
|
|
|
|