Re: Reporting My own IP?

Okay, I totally get what you are saying and have adjusted my settings.

On the forum I had registered for it but it apparently required that I check
my eMail and autherize my self and I must have missed where it said that.

So the bottom line from what I have gottem from all of this is the
following...
1. Do not change any thing in the eMail to help the parser.
2. Do not include the spam (use the tracker) and do NOT include eMail as
attachments that are not text.
3. I need to fix my zone file on my IP's or change my eMail servers name to
match what the zone is currently.

My one question I forgot to include earlier is, How do I back out my
mistakes.  How do I cancel out the submissions including my IP's?

Thank you SO much for taking the time to pass all this information to me.  I
really appreciate it..

... Merlin

"Mike Easter" <[email protected]> wrote in message
news:[email protected]...
> Mike Easter wrote:
> > The subject of attachments and uuencoding
> > is another topic that I'll save for later after discussing the
> > problem you are asking about.
>
> You shouldn't be submitting spam as an attachment or any other way into
> any of the newsgroups except spamcop.spam
>
> Even spamcop.spam isn't as good a way to submit spam as a tracking URL
> as demonstrated.
>
> You [probably] shouldn't be configured to make your attachments
> uuencoded, unless you are specifically trying to hop over some hurdle I
> don't know about.  That configuration is here:  OE/ Tools/ Options/ Send
> tab - News sending format - Plain text settings button/ - select MIME
> encoding and None from the menu instead of the other radio button
> Uuencoding.
>
> The problem is, at least in this particular little instance in which
> there is already a relative no-no of posting spam in the wrong group and
> putting an attachment into this group, that if someone is trying to
> 'cope with' your attachment that the 'issue' can't be examined quite as
> easily.  If the original spam had been not uuencoded as an attachment
> instead of mime, it would have been one decoding step more accessible.
> It is possible for someone to handle your post 'as is' insecurely if
> they handle it carelessly.
>
> If someone else's OE is configured insecurely and if you post a
> dangerous .eml attachment and they can't 'see' what is 'inside' your
> attachment because all they see in the Properties is 'begin 666' and
> then the encoding, the careless viewer might decide to click open the
> Solid Financing for the USA!.eml -- and if that eml is a dangerous item
> somehow, then they have become virus infected from the content or
> perhaps by being delivered to a bad website.
>
>
> -- 
> Mike Easter
> kibitzer, not SC admin
>