[Cleanfeed] Usenet Spam encoded in Base64
Steve Crook
Over the past few months I've noticed Spam being posted to Usenet using
Base64 encoding. That's to say, with a header of:
Content-Transfer-Encoding: base64
A couple of examples:
<b717951a-a78a-480c...@m16g2000yqc.googlegroups.com>
<1746ffd7-6cd8-4687...@m26g2000yqb.googlegroups.com>
As most decent newsreaders decode base64 more or less transparently to
the user, it's a neat way to circumvent all the current regex based
filtering in Cleanfeed, (which has no base64 decode functionality). If
the post is too long, then it gets tagged as misplaced binary but the
limits on base64 are currently quite relaxed to allow for PGP key
exchange on Usenet.
I'd be interested to hear opinions on how people think base64 content
should be handled.
Should all base64 be considered binary?
Should Cleanfeed decode and examine the content?
Should base64 be limited to binary groups, (plus exceptions)?
Should it be ignored and left to the reader to choose how to handle it?
Kathy Morgan
> Should all base64 be considered binary?
That seems reasonable to me. Would it be difficult on the server side
to filter based on base64 in the header?
> Should Cleanfeed decode and examine the content?
> Should base64 be limited to binary groups, (plus exceptions)?
> Should it be ignored and left to the reader to choose how to handle it?
Not the last choice; if it's spam and possible to filter, I as a user
don't want to see it.
--
Kathy
Xavier Roche
> Over the past few months I've noticed Spam being posted to Usenet using
> Base64 encoding.
Yep, and also specially-crafted UTF-7 messages time to time.
> Should all base64 be considered binary?
I've never seen a decent client encoding text parts in base64, hence
this is probably safe. The cleanest way would be to decode parts, of course.
Frank Slootweg
Result: Recipient names must be specified
Steve Crook <st...@mixmin.net> wrote:
> Hi all,
>
> Over the past few months I've noticed Spam being posted to Usenet using
> Base64 encoding. That's to say, with a header of:
> Content-Transfer-Encoding: base64
>
> A couple of examples:
> <b717951a-a78a-480c...@m16g2000yqc.googlegroups.com>
> <1746ffd7-6cd8-4687...@m26g2000yqb.googlegroups.com>
>
> As most decent newsreaders decode base64 more or less transparently to
> the user, it's a neat way to circumvent all the current regex based
> filtering in Cleanfeed, (which has no base64 decode functionality). If
> the post is too long, then it gets tagged as misplaced binary but the
> limits on base64 are currently quite relaxed to allow for PGP key
> exchange on Usenet.
>
> I'd be interested to hear opinions on how people think base64 content
> should be handled.
>
> Should all base64 be considered binary?
No.
> Should Cleanfeed decode and examine the content?
Yes. Your examples are examples of *text* messages. I.e. the
"Content-Transfer-Encoding: base64" by itself is not the point, because,
as it says, that only specifies the *encoding* used. What is (also)
relevant, is if there is (also) a "Content-Type: text/..." header,
preferably a "Content-Type: text/plain" one. I your examples, that's the
case, because they say:
> Content-Type: text/plain; charset=windows-1256
So your examples are perfectly valid *text* articles. That they are in
a 'special' character set doesn't make them any less text. That - as you
say - they are *spam*, is quite another matter.
> Should base64 be limited to binary groups, (plus exceptions)?
The Content-Type etc. should determine whether or not they are
binaries, not the encoding.
> Should it be ignored and left to the reader to choose how to handle it?
If you can determine that something *is* binary, and not just some
encoded text, then your server your rules. If you can't determine that
with sufficient certainty, then you should leave them alone.
Frank Slootweg
It depends what you call "a decent client", but Outlook Express and
Windows Mail can do this [1], and I assume that their replacement
Windows Live Mail can do it as well.
You and I may not consider these clients to be "decent" clients, but
they *do* have a very large user-base.
[1] In Windows Mail: Tools -> Options... -> Send tab -> News Sending
Format => Plain Text Settings... -> Message format -> MIME -> Encode
text using: -> Base 64 (other choices are "None" (default?) and "Quoted
Printable").
Frank Slootweg
> [Hamster: archive-copy of rejected article (news.admin.net-abuse.policy)]
> Result: Recipient names must be specified
Oops! Please ignore that. Forget to strip that from an earlier failed
attempt.
[...]
Peter J Ross
Steve Crook <st...@mixmin.net> wrote:
> Hi all,
>
> Over the past few months I've noticed Spam being posted to Usenet using
> Base64 encoding. That's to say, with a header of:
> Content-Transfer-Encoding: base64
>
> A couple of examples:
> <b717951a-a78a-480c...@m16g2000yqc.googlegroups.com>
> <1746ffd7-6cd8-4687...@m26g2000yqb.googlegroups.com>
How much of this kind of stuff is there? Is it already a significant
problem, likely to become a significant problem, or is it just one or
two spammers whose brain cell has started firing?
> As most decent newsreaders decode base64 more or less transparently to
> the user, it's a neat way to circumvent all the current regex based
> filtering in Cleanfeed, (which has no base64 decode functionality). If
> the post is too long, then it gets tagged as misplaced binary but the
> limits on base64 are currently quite relaxed to allow for PGP key
> exchange on Usenet.
>
> I'd be interested to hear opinions on how people think base64 content
> should be handled.
>
> Should all base64 be considered binary?
No. It's no more binary than Quoted Printable.
As long as non-spammers continue to use software that can use these
encoding methods, filtering either or both of them would produce too
many false positives to be useful.
> Should Cleanfeed decode and examine the content?
Yes. This is the only solution that would be sure to work.
> Should base64 be limited to binary groups, (plus exceptions)?
Not until non-spammers in text groups stop using it.
> Should it be ignored and left to the reader to choose how to handle it?
Filtering on Content-Transfer-Encoding is impossible for most readers,
and "expensive" for the rest of us, since C-T-E isn't included in the
overview data. So the "do nothing" option isn't a very good one.
--
PJR :-)
slrn newsreader v0.9.9p1: http://slrn.sourceforge.net/
extra slrn documentation: http://slrn-doc.sourceforge.net/
newsgroup name validator: http://pjr.lasnobberia.net/usenet/validator
Peter J Ross
Frank Slootweg <th...@ddress.is.invalid> wrote:
> Xavier Roche <xro...@free.fr.nospam.invalid> wrote:
>
>> I've never seen a decent client encoding text parts in base64, hence
>> this is probably safe. The cleanest way would be to decode parts, of course.
>
> It depends what you call "a decent client", but Outlook Express and
> Windows Mail can do this [1], and I assume that their replacement
> Windows Live Mail can do it as well.
That's a significant assumption. If Windows Live Mail has stopped
offering this annoying option, the likelihood of legitimate Base64
articles appearing will gradually be reduced. Maybe somebody who has
access to WLM can enlighten us.
> You and I may not consider these clients to be "decent" clients, but
> they *do* have a very large user-base.
>
> [1] In Windows Mail: Tools -> Options... -> Send tab -> News Sending
> Format => Plain Text Settings... -> Message format -> MIME -> Encode
> text using: -> Base 64 (other choices are "None" (default?) and "Quoted
> Printable").
Unless "None" means "8bit", that's a depressing set of three bad
choices.
D. Stussy
news:slrnhelthe...@news.mixmin.net...
Since plain text (or even HTML; yuck) needs NO encoding while binary does,
it makes sense that all base64 encodings are binary. However, see
"alt.anonymous.messages" - where the encoding seems to be encryption. I
have recently chosen not to carry that group because I cannot tell what is
being passed in them and I don't want my server to be involved (even as a
neutral carrier) in passing potentially terrorist messages internationally.
Therefore:
My recommendations:
1) ALL base64 should be considered binary.
2) Cleanfeed doesn't have to examine its content.
3) As binary, it should be limited to binary groups.
No exception groups; not even a.a.m (above).
4) Shouldn't PGP be using its own MIME type?
Steve Crook
Message-Id: <7l0thkF...@mid.individual.net>:
>> Should Cleanfeed decode and examine the content?
>
> Yes. Your examples are examples of *text* messages. I.e. the
> "Content-Transfer-Encoding: base64" by itself is not the point, because,
> as it says, that only specifies the *encoding* used. What is (also)
> relevant, is if there is (also) a "Content-Type: text/..." header,
> preferably a "Content-Type: text/plain" one. I your examples, that's the
> case, because they say:
>
>> Content-Type: text/plain; charset=windows-1256
>
> So your examples are perfectly valid *text* articles. That they are in
> a 'special' character set doesn't make them any less text. That - as you
> say - they are *spam*, is quite another matter.
Hi Frank,
Thanks for the feedback. Unfortunately in many respects this further
complicates matters. For example, current Cleanfeed tags all base64
content (exceeding max_base64_lines, default: 200) as binary. I've
always felt this is a poor check as the method of encoding doesn't
relate to the nature of the content.
So what's the correct behaviour?
if payload contains base64
and not Content-Transfer-Encoding: base64
tag as binary
if payload contains base64
and Content-Transfer-Encoding: base64
and Content-Type: text/
decode payload and process as text
if payload contains base64
and Content-Transfer-Encoding: base64
and not Content-Type: text/
tag as binary
There are other conditionals to satisfy all permutations but I think
those are the key ones.
>> Should it be ignored and left to the reader to choose how to handle it?
>
> If you can determine that something *is* binary, and not just some
> encoded text, then your server your rules. If you can't determine that
> with sufficient certainty, then you should leave them alone.
I agree that when the content cannot be reliably identified, it has to
be accepted. Every effort should be made to identify the content
though, providing the processing overhead doesn't impact the server
performance to an unacceptable degree.
My server, my rules doesn't really apply. I want Cleanfeed to be
functional for any news service that elects to run it. The operator
should be able to select the filter behaviour from a local config file
without having to dig into the code.
Thanks again,
Steve
Steve Crook
Message-Id: <slrnhen1b...@pjr.gotdns.org>:
> How much of this kind of stuff is there? Is it already a significant
> problem, likely to become a significant problem, or is it just one or
> two spammers whose brain cell has started firing?
Currently there are about 200 posts per day being encoded in this
manner. As a spam problem, that's relatively minor but I suspect it
will catch on. There's also the issue that due to the current Cleanfeed
behaviour, *any* base64 content is treated as binary if it exceeds a
defined number of lines. Spam getting through is less of an issue than
the good content being refused but one solution should address both
issues.
> Filtering on Content-Transfer-Encoding is impossible for most readers,
> and "expensive" for the rest of us, since C-T-E isn't included in the
> overview data. So the "do nothing" option isn't a very good one.
Excellent. If nothing else, the response in this thread seems to agree
that leaving it to the reader is generally a poor solution. :)
Thanks
Peter J Ross
Stussy <spam+ne...@bde-arc.ampr.org> wrote:
> "Steve Crook" <st...@mixmin.net> wrote in message
> news:slrnhelthe...@news.mixmin.net...
>> Over the past few months I've noticed Spam being posted to Usenet using
>> Base64 encoding. That's to say, with a header of:
>> Content-Transfer-Encoding: base64
>>
>> A couple of examples:
>> <b717951a-a78a-480c...@m16g2000yqc.googlegroups.com>
>> <1746ffd7-6cd8-4687...@m26g2000yqb.googlegroups.com>
>>
>> As most decent newsreaders decode base64 more or less transparently to
>> the user, it's a neat way to circumvent all the current regex based
>> filtering in Cleanfeed, (which has no base64 decode functionality). If
>> the post is too long, then it gets tagged as misplaced binary but the
>> limits on base64 are currently quite relaxed to allow for PGP key
>> exchange on Usenet.
>>
>> I'd be interested to hear opinions on how people think base64 content
>> should be handled.
>>
>> Should all base64 be considered binary?
>> Should Cleanfeed decode and examine the content?
>> Should base64 be limited to binary groups, (plus exceptions)?
>> Should it be ignored and left to the reader to choose how to handle it?
>
> Since plain text (or even HTML; yuck) needs NO encoding while binary does,
> it makes sense that all base64 encodings are binary.
But some plain text *does* require encoding. How else can words like
"co�rdination" and "clich�" be read as the author intended?
QP and B64 are unsatisfactory encoding methods, but *some* encoding
will be required until Unicode is universally adopted.
Frank Slootweg
[...]
> But some plain text *does* require encoding. How else can words like
> "co�rdination" and "clich�" be read as the author intended?
>
> QP and B64 are unsatisfactory encoding methods, but *some* encoding
> will be required until Unicode is universally adopted.
Didn't you just invalidate your own statement? Your posting did not
use any *encoding*, but was perfectly OK, because it had:
> Content-Type: text/plain; charset=iso-8859-1
I.e. it used a *charset*, no encoding.
Frank Slootweg
[...]
> So what's the correct behaviour?
>
> if payload contains base64
> and not Content-Transfer-Encoding: base64
> tag as binary
I think such a posting should be *dropped*, because a base64 encoded
article must have a "Content-Transfer-Encoding: base64" header and must
have a "Content-Type: ..." header.
But get a second opinion on this, because I don't do binaries.
> if payload contains base64
> and Content-Transfer-Encoding: base64
> and Content-Type: text/
> decode payload and process as text
Correct.
> if payload contains base64
> and Content-Transfer-Encoding: base64
> and not Content-Type: text/
> tag as binary
Somewhat correct, because (see above) it must have a "Content-Type:"
header which does *not* say "text/"
[...]
Frank Slootweg
[...]
> Since plain text (or even HTML; yuck) needs NO encoding while binary does,
> it makes sense that all base64 encodings are binary.
No offense, but I think this is plain wrong. You are correct in that
text articles do not *need* [1] encoding, but the standards
(specifically the MIME ones), *allow* encoding, so it's not up to
Cleanfeed to make such a 'value judgement'.
[...]
[1] This assumes that USEFOR says that the *article format* (not NNTP),
MUST be 8-bit clean. I haven't checked that.
D. Stussy
news:7l3me7F...@mid.individual.net...
So, if someone wants to be an asshole and make all their TEXT posts 34%
larger because they base-64 encode them on a whim, we should let them (or
at least not block them from doing so)? Why not bring back mass spamming
too?
This isn't a question of "can they?" It's a question of "should they?"
...And if they do, what are we going to do about it.
I view this as: If a particular encoding is not necessary, it should not
happen. So, what is "necessary?" I define necessary as: 1) The message
cannot be expressed without the encoding; i.e. it has no equivalent, or 2)
It's encoded equivalent produces a shorter message (e.g. compression).
However, base64, as compared to 7-bit ASCII, always expands the size of the
message, and therefore is NEVER necessary under #2, and never happens under
#1 as all ASCII characters can be expressed in unencoded form.
When using a non-7-bit-clean character set, the encoding only become
necessary if it results in a shorter message - as current methods already
escape for the non-7-bit-clean characters. However, as current encodings
change these 16-bit or other size character sets into strings of 7-bit
characters, base64 is then again expanding the size of the message. Some
OTHER encoding might not.
Xavier Roche
> I view this as: If a particular encoding is not necessary, it should not
> happen. So, what is "necessary?" I define necessary as: 1) The message
> cannot be expressed without the encoding; i.e. it has no equivalent, or 2)
> It's encoded equivalent produces a shorter message (e.g. compression).
> However, base64, as compared to 7-bit ASCII, always expands the size of the
> message, and therefore is NEVER necessary under #2, and never happens under
> #1 as all ASCII characters can be expressed in unencoded form.
Beware: do not mix (content-transfer-)encoding and charset. The term
"encoding" is actually totally ambiguous on the RFC side ; and sometimes
refers to charset (the transformation, partial or complete, from the
Unicode range to one or more characters), or content-transfer-encoding
(generally, the transformation of opaque binary data into 7-bit data),
or transfer-encoding (encoding a stream of bytes, such as regular
streams, chunked streams, .. used with live protocols such as HTTP)
Quoted-printable is probably the best *content-transfer-encoding* choice
if messages are to be 7-bit compatible, because in "most" cases (ie. all
languages except codepoints such as chinese) the characters are within
the ascii range (ie. a french text contains more 7-bit characters that
8-bit characters, whatever the charset is)
Base64 is the natural choice for.. binary data (because the 8-bit
distribution is uniform), and encoded languages with low density of
7-bit characters, such as chinese. (I don't mention ISO-2022 madenesses,
which are the sole exception for this, but how is crazy enough to use
these charsets anyway ?)
On Usenet, 8-bit messages have (more or less) always been considered
valid ("NNTP operates over any reliable bi-directional 8-bit-wide data
stream channel" for latest RFC, and all known implementations have been
8-bit clean for ages), hence any content-transfer-encoding is a waste of
time.
However, 7-bit text CAN be transformed with base64 - this is perfectly
legit according to the spec. This is utterly stupid, of course, but legit.
[ Note: I did not mention the UTF-7 "encoding", which is a mix between
utf-8 charset and content-transfer-encoding, as its use is discouraged
because of this bizarre status - http://www.imc.org/imcr-010.html ]
Julien ÉLIE
>> [1] In Windows Mail: Tools -> Options... -> Send tab -> News Sending
>> Format => Plain Text Settings... -> Message format -> MIME -> Encode
>> text using: -> Base 64 (other choices are "None" (default?) and "Quoted
>> Printable").
>
> Unless "None" means "8bit", that's a depressing set of three bad
> choices.
Yes, it means "8bit". It is the default.
(And it is also what I am currently using.)
There is also an option to allow 8bit characters in headers. It is
deactivated by default.
--
Julien �LIE
<< -- Tu dois avoir un messager z�l� autant qu'ail�
pour faire rapidement le trajet.
-- Oui ! et c'est une fine mouche ! >> (Ast�rix)
Frank Slootweg
[...]
> So, if someone wants to be an asshole and make all their TEXT posts 34%
> larger because they base-64 encode them on a whim, we should let them (or
> at least not block them from doing so)? Why not bring back mass spamming
> too?
*If* it was only a case of "assholes", then it would be simple. But
probably the majority of these postings is from clients which are not
configured as well as they theoretically could. Theoretically, because
most of the time the user is unaware of these things under the hood.
You and I may not *like* that, but as Xavier also points out, it's
*reality* *and* it is *standard conformant*.
Again, if you want to ban this stuff from *your* server, that's fine,
but Cleanfeed has no business filtering articles which are totally
legit.
D. Stussy
news:hcjj52$t7o$1...@news.httrack.net...
As such a transformation does expand the size of the message, that was my
point: It is stupid and thus should not be done. Under my premise, it
would no longer be legitimate. However, if some other encoding came along
which reduced the size of the message, that should be permitted. I was
trying to give Steve a framework with which to determine his answer which
need not depend solely on base64 encoding.
Just because it can be done does not mean it should be done.
As we have both classified it as "stupid," I think we're agreeing that it
should not be done. However, we diverge - in that you say that since it is
permissible, we must allow it, while I have said that we shouldn't allow
it. Both opinions are valid. The logical next question is: Does it
actually happen?
D. Stussy
news:hcjj52$t7o$1...@news.httrack.net...
> > I view this as: If a particular encoding is not necessary, it should
not
> > happen. So, what is "necessary?" I define necessary as: 1) The
message
> > cannot be expressed without the encoding; i.e. it has no equivalent, or
2)
> > It's encoded equivalent produces a shorter message (e.g. compression).
> > However, base64, as compared to 7-bit ASCII, always expands the size of
the
> > message, and therefore is NEVER necessary under #2, and never happens
under
> > #1 as all ASCII characters can be expressed in unencoded form.
>
> Beware: do not mix (content-transfer-)encoding and charset. The term
> "encoding" is actually totally ambiguous on the RFC side ; and sometimes
> refers to charset (the transformation, partial or complete, from the
> Unicode range to one or more characters), or content-transfer-encoding
> (generally, the transformation of opaque binary data into 7-bit data),
> or transfer-encoding (encoding a stream of bytes, such as regular
> streams, chunked streams, .. used with live protocols such as HTTP)
Although I feel that my prior comments are correct, I also noted a post in
Russian that had these characteristics:
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: base64
Now, granted that the post I saw today was spammy - having been posted to a
group dealing with Australia, I do note that there is an interdependence
between encoding and character set here.
Steve Crook
Message-Id: <7l3m2hF...@mid.individual.net>:
>> if payload contains base64
>> and not Content-Transfer-Encoding: base64
>> tag as binary
>
> I think such a posting should be *dropped*, because a base64 encoded
> article must have a "Content-Transfer-Encoding: base64" header and must
> have a "Content-Type: ..." header.
>
> But get a second opinion on this, because I don't do binaries.
Thanks, I'll check out some RFC's on that one. I'm logging posts that
match those conditions and as yet haven't seen any so it's probably not
a big issue.
>> if payload contains base64
>> and Content-Transfer-Encoding: base64
>> and Content-Type: text/
>> decode payload and process as text
>
> Correct.
This is now in place and undergoing testing. I'll probably include it
in the next Cleanfeed release. It's also prompted me to rewrite the
saveart functionality to include more options, such as logging decoded
payloads. :)
Xavier Roche
> Now, granted that the post I saw today was spammy - having been posted to a
> group dealing with Australia, I do note that there is an interdependence
> between encoding and character set here.
Well, yes and no. CTE and charset are independent, BUT OTOH codepoints
such as russian, chinese, arabic.. tend to use a lot more 8-bit
characters that english or french (or italian ..), whatever the charset
is, and are hence more elibible for base64 that in other cases.
[ QP is 3 bytes for a 8-bit code, and base64 is "only" 1.33 bytes --
when the 7-bit ratio is low, you should switch to base64 cte ]
Xavier Roche
> Just because it can be done does not mean it should be done.
"Be strict when sending and tolerant when receiving" [ Filtering on
content-transfer-encoding is IMHO not very reliable and probably a bit
dangerous ]
D. Stussy
Being overly tolerant in what one receives opens one to spam and other
malicious messages.
I don't accept articles where the "From" header indicates a mailbox in the
"example.com" domain, because RFC 2616 says such should NEVER appear on the
live Internet; only in documentation examples. I block roughly 1,000
articles per day (less than 1% of all text-group volume by article count)
based on stupidity such as this (and other syntax errors - like having two
"@"'s in a mailbox designation). PS: ".invalid" is permitted there, but
NOT in "Reply-To" which must be resolvable for article acceptance.
Obviously, there has been some abuse with "base64" encoding, else the issue
would not have arisen.
Kathy Morgan
> I don't accept articles where the "From" header indicates a mailbox in the
> "example.com" domain, because RFC 2616 says such should NEVER appear on the
> live Internet; only in documentation examples. I block roughly 1,000
> articles per day (less than 1% of all text-group volume by article count)
> based on stupidity such as this (and other syntax errors - like having two
> "@"'s in a mailbox designation). PS: ".invalid" is permitted there, but
> NOT in "Reply-To" which must be resolvable for article acceptance.
A "From" address with "example.com" should be accepted for the same
reason that an address with ".invalid" is accepted--I advise people who
insist on munging to use ".invalid" at the end of the munge, but there
are others giving advice to use the domain "example.com". In both cases
the intent is to use an address which is known not to be valid and that
will never be assigned to an actual mailbox.
Also, I think I've seen valid addresses with two "@"'s, but I wouldn't
swear to that.
--
Kathy
D. Stussy
news:1j8k64e.u1cj9d7rnx2kN%kmo...@spamcop.net...
I clearly disagree. RFC 2606 (Correction) says that "example" (as a TLD or
a 2LD under "com", "net", and "org" - and per ICANN contracts for the other
gTLDs as a reserved word not to be assigned) should NEVER APPEAR on the
live Internet, but exist only in documentation. Meanwhile, ".invalid" is
meant to appear on the live Internet (and so is "localhost").
ONLY the ".INVALID" TLD is permitted for munged addresses, and such is its
only purpose for existing.
For some reason, I'm always crossing 2606 and 2616. Argh!
Here's today's bad list:
- IP address literals need to be enclosed in brackets. Addresses not in
brackets aren't valid.
- The only "questionable" usage that I disallow is "@example.invalid" -
should it follow the ".invalid" TLD or the "example" 2LD rule?
- In addition to "@@", I have also seen ".." and "@." which yield null
domain elements.
- Although not appearing in the RFC, ".localdomain" is another dummy TLD
that is banned, as it appears in documentation and meant to be substituted
with the live domain of a site.
Before I removed the few specifically blocked troll users, the count of
entries was 1,178 for the past 19.5 hours:
<hcm3mh$e6$1...@ns.tolcom.ru> 439 Bad From ("Tanaka" <tanaka@1.1>)
<4aee92b6$0$2531$da0f...@news.zen.co.uk> 439 Bad From (Mark Murray
<w.h....@example.com>)
<b15te5ps3tk2rnb1c...@4ax.com> 439 Bad From (David Lowndes
<Dav...@example.invalid>)
<hcm506$pt1$1...@news.eternal-september.org> 439 Bad Reply-To
("Escape_the_Cult_Now" <kill...@invalid.invalid>)
<hcm599$rmd$1...@news.eternal-september.org> 439 Bad Reply-To
("Escape_the_Cult_Now" <kill...@invalid.invalid>)
<hcm5jl$tn9$1...@news.eternal-september.org> 439 Bad Reply-To
("Escape_the_Cult_Now" <kill...@invalid.invalid>)
<4aee9b2b$0$826$4faf...@reader5.news.tin.it> 439 Bad Reply-To ("Max max"
<1o1kve402t...@sneakemail.com.invalid>)
<hcm656$1p6$1...@news.eternal-september.org> 439 Bad Reply-To
("Escape_the_Cult_Now" <kill...@invalid.invalid>)
<4aee9c20$1...@news.home.net.pl> 439 Bad From ("Raist" <robike@@poczta.fm>)
<hcm682$2h9$1...@news.eternal-september.org> 439 Bad Reply-To
("Escape_the_Cult_Now" <kill...@invalid.invalid>)
<4aee9c23$1...@x-privat.org> 439 Bad Reply-To ("7pato" <@.riee.ere>)
<hcm6dj$3hj$1...@news.eternal-september.org> 439 Bad Reply-To
("Escape_the_Cult_Now" <kill...@invalid.invalid>)
<hcm6aj$2vf$1...@news.eternal-september.org> 439 Bad Reply-To
(ga...@askme.invalid)
<hcm6gr$4d5$1...@news.eternal-september.org> 439 Bad Reply-To
("Escape_the_Cult_Now" <kill...@invalid.invalid>)
<hcm6jc$4st$1...@news.eternal-september.org> 439 Bad Reply-To
("Escape_the_Cult_Now" <kill...@invalid.invalid>)
<4aee9dfb$1...@news4us.nl> 439 Bad Reply-To (james_t.kirk@invalid)
<4aee9e33$1...@news4us.nl> 439 Bad Reply-To (james_t.kirk@invalid)
<hcm6p5$5p3$1...@news.eternal-september.org> 439 Bad Reply-To
(ga...@askme.invalid)
<hcm6rd$6ab$1...@news.eternal-september.org> 439 Bad Reply-To
("Escape_the_Cult_Now" <kill...@invalid.invalid>)
<4aee9...@news4us.nl> 439 Bad Reply-To (james_t.kirk@invalid)
<4aee9ed3$1...@x-privat.org> 439 Bad Reply-To ("7pato" <a@.erie>)
<4aee9f63$1...@news4us.nl> 439 Bad Reply-To (james_t.kirk@invalid)
<hcm74d$8be$1...@news.eternal-september.org> 439 Bad Reply-To
("Escape_the_Cult_Now" <kill...@invalid.invalid>)
<Pine.LNX.4.64.09...@dawn.a.b.c> 439 Bad From (Matt Giwer
<matt@localhost>)
<Pine.LNX.4.64.09...@dawn.a.b.c> 439 Bad From (Matt Giwer
<matt@localhost>)
<Pine.LNX.4.64.09...@dawn.a.b.c> 439 Bad From (Matt Giwer
<matt@localhost>)
<hcm76s$8rg$1...@news.eternal-september.org> 439 Bad Reply-To
("Escape_the_Cult_Now" <kill...@invalid.invalid>)
<4aeea032$1...@news.home.net.pl> 439 Bad From ("dziobak"
<dziobak-usun@hot..pl>)
<slrnhet84s....@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<hcm7bv$a42$1...@aioe.org> 439 Bad From (Noob <ro...@127.0.0.1>)
<slrnhet894....@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<4aeea176$1...@extreme.x-privat.org> 439 Bad Reply-To
(gru...@willygroup.org.invalid)
<hcm7j3$be4$1...@news.eternal-september.org> 439 Bad Reply-To
(ga...@askme.invalid)
<hcm7qc$b0o$1...@aioe.org> 439 Bad From (Noob <ro...@127.0.0.1>)
<slrnhet8s3....@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<slrnhet91f....@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<dYSdnZNtoePGOXPX...@pipex.net> 439 Bad From ("Brian Cryer"
<not.here@localhost>)
<hcm894$fbp$1...@news.eternal-september.org> 439 Bad Reply-To
(eucl...@Mlive.invalid)
<hcm8cf$fbp$2...@news.eternal-september.org> 439 Bad Reply-To
(eucl...@Mlive.invalid)
<5g9te5dcrd5d6jq1o...@4ax.com> 439 Bad Reply-To (Conte
Oliver <alex65....@wmail.it.invalid>)
<4aeea66c$0$831$4faf...@reader5.news.tin.it> 439 Bad Reply-To ("Max max"
<1o1kve402t...@sneakemail.com.invalid>)
<hcm8rh$7en$1...@tdi.cu.mi.it> 439 Bad From (Uno Qualunque <ro...@127.0.0.1>)
<hcm8sv$hpp$1...@news.eternal-september.org> 439 Bad Reply-To
(eucl...@Mlive.invalid)
<hcm8vo$ka6$1...@news.eternal-september.org> 439 Bad Reply-To
(ga...@askme.invalid)
<gj8te51f27brobotu...@4ax.com> 439 Bad Reply-To (Nato Gobbo
<nato...@juventusmember.com.invalid>)
<_KxHm.17910$Ro6...@newsfe10.ams2> 439 Bad From (Philip Herlihy
<m...@here.localhost>)
<hcm9b8$7ta$1...@tdi.cu.mi.it> 439 Bad From (Uno Qualunque <ro...@127.0.0.1>)
<4aeea473$0$21033$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<slrnheta97....@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<slrnhetabj....@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<4aeea4f7$0$21033$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<hcm9ka$od2$1...@news.eternal-september.org> 439 Bad Reply-To
(ga...@askme.invalid)
<vJqdnWycXfWHN3PX...@giganews.com> 439 Bad From (P4nd1-P4nd4
<P4nd1-P4nd4@.net>)
<4aeeaa4f$0$269$1472...@news.sunsite.dk> 439 Bad From ("carl"
<carl@.com>)
<VsOdnYvqGoIqN3PX...@giganews.com> 439 Bad From (P4nd1-P4nd4
<P4nd1-P4nd4@.net>)
<4aeea67c$0$19998$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<4aeea67e$0$19998$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<4aeeab48$1...@x-privat.org> 439 Bad Reply-To ("7pato" <a@e..ei>)
<4aeea753$0$32645$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<4aeea7d6$0$32642$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<-vSdnSp7NpgnMXPX...@giganews.com> 439 Bad From (P4nd1-P4nd4
<P4nd1-P4nd4@.net>)
<4aeea8b3$0$31852$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<4aeead69$0$828$4faf...@reader5.news.tin.it> 439 Bad Reply-To ("Max max"
<1o1kve402t...@sneakemail.com.invalid>)
<4aeea926$0$20870$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<Zs6dncAfD71HM3PX...@brightview.co.uk> 439 Bad From
(op.6119177525734...@10.10.9.34)
<Zrudnej1gYJ_M3PX...@brightview.co.uk> 439 Bad From
(op.6249047309116...@10.10.81.68)
<baKdnQketI9-M3PX...@brightview.co.uk> 439 Bad From
(op.8920418566686...@10.10.60.254)
<jvudnfoiKIV5M3PX...@brightview.co.uk> 439 Bad From
(op.8930286467210...@10.10.25.117)
<6cydnXEIM-d1M3PX...@brightview.co.uk> 439 Bad From
(op.9618626961671...@10.10.46.215)
<udidnU3V39FyM3PX...@brightview.co.uk> 439 Bad From
(op.6198997308247...@10.10.63.106)
<uNadnbZ2JqtyM3PX...@brightview.co.uk> 439 Bad From
(op.2000302616981...@10.10.5.175)
<NbCdnSJisclyM3PX...@brightview.co.uk> 439 Bad From
(op.8014474590761...@10.10.11.254)
<IrqdnYHyPrhtM3PX...@brightview.co.uk> 439 Bad From
(op.5641642565714...@10.10.89.73)
<UOCdnX7fRbBrM3PX...@brightview.co.uk> 439 Bad From
(op.1689572717676...@10.10.82.145)
<aKedneee4NlqM3PX...@brightview.co.uk> 439 Bad From
(op.9297636145176...@10.10.53.5)
<ypKdnf6nS5JqM3PX...@brightview.co.uk> 439 Bad From
(op.1250475594544...@10.10.105.165)
<2MednXY9A_CfMnPX...@brightview.co.uk> 439 Bad From
(op.7485161807469...@10.10.0.216)
<W-udnQEeYb5mM3PX...@brightview.co.uk> 439 Bad From
(op.6674864766181...@10.10.83.9)
<qf2dncML18yZMnPX...@brightview.co.uk> 439 Bad From
(op.3477311828598...@10.10.67.33)
<g76dnULe6pKZMnPX...@brightview.co.uk> 439 Bad From
(op.5655759462149...@10.10.128.216)
<aJqdnU7IPZqZMnPX...@brightview.co.uk> 439 Bad From
(op.7837441380779...@10.10.33.253)
<nPidnThpK5aWMnPX...@brightview.co.uk> 439 Bad From
(op.5269207914679...@10.10.70.7)
<oM-dnbeUmruWMnPX...@brightview.co.uk> 439 Bad From
(op.8220950227811...@10.10.45.151)
<NoSdnbz4AKeWMnPX...@brightview.co.uk> 439 Bad From
(op.5987866820903...@10.10.113.92)
<VNadnUdE7o6RMnPX...@brightview.co.uk> 439 Bad From
(op.6280215915161...@10.10.111.243)
<fYidnQMI_7KIMnPX...@brightview.co.uk> 439 Bad From
(op.4251318482382...@10.10.71.214)
<aNCdnRBr8ZSIMnPX...@brightview.co.uk> 439 Bad From
(op.0389915308123...@10.10.7.82)
<HsidnQcX0YSIMnPX...@brightview.co.uk> 439 Bad From
(op.4769348807224...@10.10.52.23)
<DL6dnUBf4s2IMnPX...@brightview.co.uk> 439 Bad From
(op.2233960345011...@10.10.110.55)
<76KdnUHRAvCGMnPX...@brightview.co.uk> 439 Bad From
(op.5274563479275...@10.10.72.126)
<-4idnWaN1uiBMnPX...@brightview.co.uk> 439 Bad From
(op.8624125936853...@10.10.24.125)
<y5qdnZ5W0tSAMnPX...@brightview.co.uk> 439 Bad From
(op.9808332314479...@10.10.39.80)
<Gs-dnfA4Q_eDMnPX...@brightview.co.uk> 439 Bad From
(op.8441693331744...@10.10.48.53)
<J5qdnd3YQ9m4MnPX...@brightview.co.uk> 439 Bad From
(op.1189455560247...@10.10.45.88)
<roOdnZyqpZy4MnPX...@brightview.co.uk> 439 Bad From
(op.5065015223184...@10.10.8.163)
<Ooidncp4gay7MnPX...@brightview.co.uk> 439 Bad From
(op.1841757173110...@10.10.121.90)
<V_udnTkyMJW7MnPX...@brightview.co.uk> 439 Bad From
(op.5002707347364...@10.10.62.151)
<cqGdnZrkI_2xMnPX...@brightview.co.uk> 439 Bad From
(op.8747277121835...@10.10.105.36)
<GvOdnSi3xKawMnPX...@brightview.co.uk> 439 Bad From
(op.9888220374394...@10.10.110.118)
<zbudne3KZ_2wMnPX...@brightview.co.uk> 439 Bad From
(op.4103168443600...@10.10.48.59)
<oIudneF025GzMnPX...@brightview.co.uk> 439 Bad From
(op.9994500993553...@10.10.77.248)
<laOdnd20pPKrMnPX...@brightview.co.uk> 439 Bad From
(op.4250024317739...@10.10.68.95)
<_eCdneKEW-arMnPX...@brightview.co.uk> 439 Bad From
(op.0416289012544...@10.10.92.73)
<jM6dndAlFMKqMnPX...@brightview.co.uk> 439 Bad From
(op.4205454683036...@10.10.69.165)
<Sv-dnbOV9vuqMnPX...@brightview.co.uk> 439 Bad From
(op.9617254916086...@10.10.73.200)
<fuSdnTjW9f_VMnPX...@brightview.co.uk> 439 Bad From
(op.9297678683601...@10.10.119.208)
<rIudnS3OOvPUMnPX...@brightview.co.uk> 439 Bad From
(op.4410003424765...@10.10.62.225)
<F42dnfyQo93aMnPX...@brightview.co.uk> 439 Bad From
(op.9663194140738...@10.10.82.137)
<d4adnV-lDpDXMnPX...@brightview.co.uk> 439 Bad From
(op.9018143893534...@10.10.105.204)
<bYqdnYsidcrNMnPX...@brightview.co.uk> 439 Bad From
(op.9845195699584...@10.10.94.235)
<vOWdnVbMGbrMMnPX...@brightview.co.uk> 439 Bad From
(op.7157060172156...@10.10.29.239)
<J8ydnRwGm9jPMnPX...@brightview.co.uk> 439 Bad From
(op.4954863112265...@10.10.42.24)
<eqSdnXvU3JTOMnPX...@brightview.co.uk> 439 Bad From
(op.7047340386859...@10.10.41.101)
<25CdneFZgqXHMnPX...@brightview.co.uk> 439 Bad From
(op.1187714281412...@10.10.63.52)
<m8mdna0uVYzGMnPX...@brightview.co.uk> 439 Bad From
(op.5744676646194...@10.10.84.184)
<eYCdnRxAzuHGMnPX...@brightview.co.uk> 439 Bad From
(op.8928975923204...@10.10.107.112)
<ieOdndF7f_XGMnPX...@brightview.co.uk> 439 Bad From
(op.0839261528967...@10.10.61.178)
<M-OdncNUnpT-MnPX...@brightview.co.uk> 439 Bad From
(op.8668150511033...@10.10.121.7)
<q-OdnUZGXOj-MnPX...@brightview.co.uk> 439 Bad From
(op.4856450906811...@10.10.66.14)
<7eOdncg6R__5MnPX...@brightview.co.uk> 439 Bad From
(op.0448898295141...@10.10.100.152)
<KomdnW54mY75MnPX...@brightview.co.uk> 439 Bad From
(op.0755111137256...@10.10.17.150)
<OZmdnQwZD4z2MnPX...@brightview.co.uk> 439 Bad From
(op.8932735360462...@10.10.105.44)
<9ZednYq49qP2MnPX...@brightview.co.uk> 439 Bad From
(op.9329360044890...@10.10.108.120)
<lcKdnYm3dKTwMnPX...@brightview.co.uk> 439 Bad From
(op.8283206714748...@10.10.23.213)
<Z4ednWSTfuXzMnPX...@brightview.co.uk> 439 Bad From
(op.7137251238096...@10.10.45.141)
<gIudnbhMtKvpMnPX...@brightview.co.uk> 439 Bad From
(op.7342755763630...@10.10.25.247)
<waednVffGcPpMnPX...@brightview.co.uk> 439 Bad From
(op.8392745117727...@10.10.68.177)
<XrOdnTsJK9DoMnPX...@brightview.co.uk> 439 Bad From
(op.4178731127479...@10.10.51.77)
<PMmdnTeSRMbrMnPX...@brightview.co.uk> 439 Bad From
(op.1788354941231...@10.10.61.106)
<fcWdnWVM8uYaMnPX...@brightview.co.uk> 439 Bad From
(op.2978098392136...@10.10.91.254)
<5YSdnRkLK4QaMnPX...@brightview.co.uk> 439 Bad From
(op.2922181308351...@10.10.60.211)
<Pa2dnYtxm-wVMnPX...@brightview.co.uk> 439 Bad From
(op.7100774332833...@10.10.101.20)
<h7KdnXd23N0XMnPX...@brightview.co.uk> 439 Bad From
(op.8751483178861...@10.10.11.84)
<ro-dnVKPndgNMnPX...@brightview.co.uk> 439 Bad From
(op.1763241569428...@10.10.40.218)
<dqOdnQk4UP4NMnPX...@brightview.co.uk> 439 Bad From
(op.0899704390313...@10.10.15.97)
<X4-dnXcWv9kDMnPX...@brightview.co.uk> 439 Bad From
(op.5845086668018...@10.10.102.179)
<icSdnfiRq-0PMnPX...@brightview.co.uk> 439 Bad From
(op.6521630374410...@10.10.107.227)
<KI-dnXXZYJMJMnPX...@brightview.co.uk> 439 Bad From
(op.8845477952613...@10.10.14.149)
<bsSdnegySuYCMnPX...@brightview.co.uk> 439 Bad From
(op.0321413608405...@10.10.99.142)
<2aydnbToUO8CMnPX...@brightview.co.uk> 439 Bad From
(op.9369832149924...@10.10.104.193)
<4MKdnUKSKZ0DMnPX...@brightview.co.uk> 439 Bad From
(op.5916626788509...@10.10.45.78)
<UrqdnUPQs44vMnPX...@brightview.co.uk> 439 Bad From
(op.6800243295985...@10.10.1.124)
<AsKdnVvbN60tMnPX...@brightview.co.uk> 439 Bad From
(op.3852959671001...@10.10.120.79)
<8r2dnfiqUt0tMnPX...@brightview.co.uk> 439 Bad From
(op.0877304977987...@10.10.30.230)
<ypCdnT6ofq0rMnPX...@brightview.co.uk> 439 Bad From
(op.4907273942444...@10.10.31.114)
<WeednbKthJdZMnPX...@brightview.co.uk> 439 Bad From
(op.0005296587144...@10.10.34.170)
<YcmdnQ8Ml5JZMnPX...@brightview.co.uk> 439 Bad From
(op.8994407949450...@10.10.103.175)
<_t6dnX71yahbMnPX...@brightview.co.uk> 439 Bad From
(op.3179804444438...@10.10.82.106)
<S56dnWTMgpZZMnPX...@brightview.co.uk> 439 Bad From
(op.2986464521390...@10.10.35.23)
<_uadnQkR7-1TMnPX...@brightview.co.uk> 439 Bad From
(op.0274249487246...@10.10.16.80)
<nI2dnU6yc4NMMnPX...@brightview.co.uk> 439 Bad From
(op.7958077560382...@10.10.108.160)
<tq6dnbE2btxTMnPX...@brightview.co.uk> 439 Bad From
(op.0155845560721...@10.10.78.106)
<Fvqdnar0i-FSMnPX...@brightview.co.uk> 439 Bad From
(op.9355329369886...@10.10.103.242)
<BY6dnRP-0q9HMnPX...@brightview.co.uk> 439 Bad From
(op.2481404397118...@10.10.3.52)
<tK6dnZ-yK_lHMnPX...@brightview.co.uk> 439 Bad From
(op.3216317594442...@10.10.122.60)
<7smdnTEugZpHMnPX...@brightview.co.uk> 439 Bad From
(op.5376573873588...@10.10.86.74)
<Ca2dnUElrcJGMnPX...@brightview.co.uk> 439 Bad From
(op.7277716148483...@10.10.48.81)
<tOKdnXu6b7x7MnPX...@brightview.co.uk> 439 Bad From
(op.8810851579858...@10.10.83.68)
<-IadnZSmk4F6MnPX...@brightview.co.uk> 439 Bad From
(op.7230324763288...@10.10.14.52)
<XK-dnT5Hd4F1MnPX...@brightview.co.uk> 439 Bad From
(op.9305269163197...@10.10.1.93)
<UMmdnZ-iEf91MnPX...@brightview.co.uk> 439 Bad From
(op.6314380323269...@10.10.37.226)
<mPydnZn26f1tMnPX...@brightview.co.uk> 439 Bad From
(op.3926333493715...@10.10.115.160)
<4IGdnVSCNuRsMnPX...@brightview.co.uk> 439 Bad From
(op.4060486562060...@10.10.2.167)
<ZL2dnSHqX6RvMnPX...@brightview.co.uk> 439 Bad From
(op.5347978156821...@10.10.26.170)
<ePidnfRLl8NuMnPX...@brightview.co.uk> 439 Bad From
(op.9280491717906...@10.10.120.222)
<i4ydneL7N6FhMnPX...@brightview.co.uk> 439 Bad From
(op.2761546275251...@10.10.51.45)
<Ia6dnV9Bva5gMnPX...@brightview.co.uk> 439 Bad From
(op.1292989620676...@10.10.39.42)
<zP6dnYCph-mdLXPX...@brightview.co.uk> 439 Bad From
(op.0741863920811...@10.10.126.43)
<qNednXfyVZGcLXPX...@brightview.co.uk> 439 Bad From
(op.4131511396672...@10.10.49.61)
<EoOdnfX4l7CXLXPX...@brightview.co.uk> 439 Bad From
(op.9993158759519...@10.10.32.115)
<McSdnd5VdLWXLXPX...@brightview.co.uk> 439 Bad From
(op.4998326075133...@10.10.24.130)
<DKqdnalCUpKWLXPX...@brightview.co.uk> 439 Bad From
(op.0713518016333...@10.10.127.185)
<2-Kdnew96_iXLXPX...@brightview.co.uk> 439 Bad From
(op.0162484819178...@10.10.79.238)
<g7mdnUDgsOWOLXPX...@brightview.co.uk> 439 Bad From
(op.6390642320952...@10.10.54.67)
<vIidncG6G82JLXPX...@brightview.co.uk> 439 Bad From
(op.8946547884741...@10.10.22.236)
<hcmb76$f0$1...@deskrabbit.motzarella.org> 439 Bad From (Desk Rabbit
<m...@example.com>)
<pOGdnRHRC4bKLXPX...@brightview.co.uk> 439 Bad From
(op.4784823055438...@10.10.35.58)
<dcqdnUVn-rvELXPX...@brightview.co.uk> 439 Bad From
(op.7676009589783...@10.10.112.202)
<NZKdnSZhXcXFLXPX...@brightview.co.uk> 439 Bad From
(op.5913395652745...@10.10.108.157)
<n7SdnUUucPwHLXPX...@brightview.co.uk> 439 Bad From
(op.5522923113035...@10.10.32.161)
<lbSdnVJn-JYGLXPX...@brightview.co.uk> 439 Bad From
(op.6432143360112...@10.10.109.6)
<e6mdnRuEz8cBLXPX...@brightview.co.uk> 439 Bad From
(op.4908163978494...@10.10.9.43)
<7cCdnZ5ulNBCLXPX...@brightview.co.uk> 439 Bad From
(op.2945250420439...@10.10.27.216)
<R8ednbGvJeBCLXPX...@brightview.co.uk> 439 Bad From
(op.5435796277637...@10.10.127.221)
<SsGdnVaj9-l9LXPX...@brightview.co.uk> 439 Bad From
(op.4283181247910...@10.10.48.17)
<J8KdnYYA-6p8LXPX...@brightview.co.uk> 439 Bad From
(op.0552121610078...@10.10.93.216)
<PYWdnVgDAvZ6LXPX...@brightview.co.uk> 439 Bad From
(op.4751619651690...@10.10.63.190)
<4qOdneq0rdl6LXPX...@brightview.co.uk> 439 Bad From
(op.2694263323155...@10.10.103.243)
<_O2dnVd0epF1LXPX...@brightview.co.uk> 439 Bad From
(op.7886558182458...@10.10.30.75)
<ELKdnbxcL_h1LXPX...@brightview.co.uk> 439 Bad From
(op.2910780827549...@10.10.81.250)
<S7GdnZpYWZNtLXPX...@brightview.co.uk> 439 Bad From
(op.1848230018514...@10.10.109.59)
<_sudnUC-3INsLXPX...@brightview.co.uk> 439 Bad From
(op.1433838123929...@10.10.73.57)
<97qdnYdlX6ZpLXPX...@brightview.co.uk> 439 Bad From
(op.3249145936238...@10.10.107.104)
<3s-dnbDbssFmLXPX...@brightview.co.uk> 439 Bad From
(op.2710040301397...@10.10.21.68)
<RsWdnblo7fVsLXPX...@brightview.co.uk> 439 Bad From
(op.2580024303907...@10.10.124.68)
<dOCdnT77-u9mLXPX...@brightview.co.uk> 439 Bad From
(op.8459148077281...@10.10.90.88)
<IOOdnaPVjNRmLXPX...@brightview.co.uk> 439 Bad From
(op.8529003647833...@10.10.42.118)
<aK-dnT4p8d1iLXPX...@brightview.co.uk> 439 Bad From
(op.6778560907312...@10.10.81.205)
<U9KdnZsNr7qSLHPX...@brightview.co.uk> 439 Bad From
(op.9258913013256...@10.10.114.155)
<57qdnTUnGb6bLHPX...@brightview.co.uk> 439 Bad From
(op.0259468438896...@10.10.37.112)
<_-udnWZbB_WbLHPXn...@brightview.co.uk> 439 Bad From
(op.1929498210430...@10.10.83.231)
<8uKdnSKLtP-bLHPX...@brightview.co.uk> 439 Bad From
(op.8055882096615...@10.10.8.131)
<paqdnb5ns5-aLHPX...@brightview.co.uk> 439 Bad From
(op.5942708304392...@10.10.13.170)
<rNCdnVYND_OTLHPX...@brightview.co.uk> 439 Bad From
(op.7374853563162...@10.10.116.79)
<BImdnZ8bnIiTLHPX...@brightview.co.uk> 439 Bad From
(op.7976175297099...@10.10.40.103)
<cfGdnQ3yK8ONLHPX...@brightview.co.uk> 439 Bad From
(op.1409345814512...@10.10.39.104)
<TuGdnUVNhv2ELHPX...@brightview.co.uk> 439 Bad From
(op.4645948069936...@10.10.73.64)
<o4WdnQicK5qELHPX...@brightview.co.uk> 439 Bad From
(op.8883995373388...@10.10.78.17)
<b8Cdnb7AYuuKLHPX...@brightview.co.uk> 439 Bad From
(op.0506023106331...@10.10.34.85)
<7KmdnTxYIsHHLHPX...@brightview.co.uk> 439 Bad From
(op.9144552949391...@10.10.107.178)
<2cadnQYm3bfHLHPX...@brightview.co.uk> 439 Bad From
(op.1517192867901...@10.10.59.55)
<hcmbgs$f0$2...@deskrabbit.motzarella.org> 439 Bad From (Desk Rabbit
<m...@example.com>)
<n7OdnY8_aJTGLHPX...@brightview.co.uk> 439 Bad From
(op.7913681359139...@10.10.1.82)
<nqSdneiqr9bBLHPX...@brightview.co.uk> 439 Bad From
(op.3066120845604...@10.10.37.243)
<29Kdnd2SVZH4LHPX...@brightview.co.uk> 439 Bad From
(op.2414725489967...@10.10.108.74)
<Femdnd_WJNL5LHPX...@brightview.co.uk> 439 Bad From
(op.4239039105180...@10.10.34.2)
<74adnRDb3rP6LHPX...@brightview.co.uk> 439 Bad From
(op.1899292742951...@10.10.17.54)
<M6adnbuXyNb-LHPX...@brightview.co.uk> 439 Bad From
(op.3291720510374...@10.10.30.16)
<Joqdnfw0gdLzLHPX...@brightview.co.uk> 439 Bad From
(op.3236079785681...@10.10.25.19)
<I5-dnVq5T6ftLHPX...@brightview.co.uk> 439 Bad From
(op.5117056193140...@10.10.128.80)
<-qidnQ6j2_jwLHPX...@brightview.co.uk> 439 Bad From
(op.9854047387457...@10.10.95.229)
<vbmdnf6CAZrsLHPX...@brightview.co.uk> 439 Bad From
(op.7034746631026...@10.10.95.71)
<Y42dnSM048fqLHPX...@brightview.co.uk> 439 Bad From
(op.8314979626587...@10.10.30.247)
<slrnhetcbj....@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<hcmbla$6qd$1...@news.eternal-september.org> 439 Bad From (Axis of Evil
<6...@666.666>)
<hcmbm8$6qd$2...@news.eternal-september.org> 439 Bad From (Axis of Evil
<6...@666.666>)
<hcmbg2$ik0$1...@ss408.t-com.hr> 439 Bad From
(=?iso-8859-2?B?qXXmTXXmUGFQcm9saWo=?= <123...@654321.00>)
<8uqdnSBhfNrEL3PX...@brightview.co.uk> 439 Bad From
(op.1566011657008...@10.10.117.204)
<Pe-dnVh-srL0L3PX...@brightview.co.uk> 439 Bad From
(op.5682403059506...@10.10.112.131)
<dZidnZlv55v2L3PX...@brightview.co.uk> 439 Bad From
(op.1026784521291...@10.10.65.239)
<tLednUlxbbPsL3PX...@brightview.co.uk> 439 Bad From
(op.9945094864194...@10.10.27.38)
<M7KdnVsI7fXgL3PX...@brightview.co.uk> 439 Bad From
(op.0877880745058...@10.10.37.127)
<zL-dnXtaGLXhL3PX...@brightview.co.uk> 439 Bad From
(op.1791158312177...@10.10.99.137)
<ePudnV2d-9b9L3PX...@brightview.co.uk> 439 Bad From
(op.7017029803077...@10.10.127.107)
<9fGdnYQyBtv6L3PX...@brightview.co.uk> 439 Bad From
(op.6277439762422...@10.10.98.57)
<wOSdnZGfMJn6L3PX...@brightview.co.uk> 439 Bad From
(op.5659339295200...@10.10.117.203)
<0vudnc-6pZXjL3PX...@brightview.co.uk> 439 Bad From
(op.1110091989353...@10.10.108.30)
<-PGdnfBHts7CL3PX...@brightview.co.uk> 439 Bad From
(op.5251397894067...@10.10.57.159)
<FLqdndoGs4DCL3PX...@brightview.co.uk> 439 Bad From
(op.6774262410652...@10.10.68.170)
<qbednXYCs_viL3PX...@brightview.co.uk> 439 Bad From
(op.0486453658210...@10.10.67.176)
<9PCdna3Rp6L9L3PX...@brightview.co.uk> 439 Bad From
(op.4251261941345...@10.10.5.204)
<fNGdncDBmaQbL3PX...@brightview.co.uk> 439 Bad From
(op.3463962486559...@10.10.101.68)
<A_mdnZBJZKIbL3PX...@brightview.co.uk> 439 Bad From
(op.4696240063208...@10.10.41.246)
<cO2dnVuf7MUVL3PX...@brightview.co.uk> 439 Bad From
(op.2678672640445...@10.10.117.243)
<A_qdnWd0f-QUL3PX...@brightview.co.uk> 439 Bad From
(op.7208083432247...@10.10.39.4)
<ldWdnYUQZNjuL3PX...@brightview.co.uk> 439 Bad From
(op.4654308506089...@10.10.28.135)
<hsSdna-YJeLuL3PX...@brightview.co.uk> 439 Bad From
(op.9681126751984...@10.10.110.154)
<-vOdnSPs6aruL3PX...@brightview.co.uk> 439 Bad From
(op.3371904714179...@10.10.40.11)
<2aGdnbUDNtQNL3PX...@brightview.co.uk> 439 Bad From
(op.9956025704842...@10.10.110.139)
<bbydnRMvBbkNL3PX...@brightview.co.uk> 439 Bad From
(op.3141858467108...@10.10.73.110)
<9KSdnS6tlfsNL3PX...@brightview.co.uk> 439 Bad From
(op.1805357991899...@10.10.91.13)
<2v6dnfesQ5gJL3PX...@brightview.co.uk> 439 Bad From
(op.2327168715868...@10.10.7.108)
<65Gdnc6B5qkAL3PX...@brightview.co.uk> 439 Bad From
(op.7724124366327...@10.10.51.178)
<XoydnbcnBcQDL3PX...@brightview.co.uk> 439 Bad From
(op.2096024749502...@10.10.114.13)
<dvWdnYXpWLoCL3PX...@brightview.co.uk> 439 Bad From
(op.8811158161680...@10.10.81.165)
<7OSdnamx-MkCL3PX...@brightview.co.uk> 439 Bad From
(op.0298786857847...@10.10.55.200)
<Fs2dnVskj-w7L3PX...@brightview.co.uk> 439 Bad From
(op.2044093399017...@10.10.92.18)
<ReqdnVDm1q07L3PX...@brightview.co.uk> 439 Bad From
(op.8055692763296...@10.10.81.234)
<eK2dnT4Rq7o6L3PX...@brightview.co.uk> 439 Bad From
(op.7745135715993...@10.10.107.95)
<fYydnSnywIY1L3PX...@brightview.co.uk> 439 Bad From
(op.0410172919266...@10.10.1.42)
<oY6dnVIL-5MwL3PX...@brightview.co.uk> 439 Bad From
(op.6189826920742...@10.10.43.124)
<hcmbtr$8je$1...@deskrabbit.motzarella.org> 439 Bad From (Desk Rabbit
<m...@example.com>)
<mn.12ab7d9b4...@libero.it> 439 Bad From (veleno81
<velenokullin@at@libero.it>)
<hcmc10$86r$1...@news.eternal-september.org> 439 Bad Reply-To
(eucl...@Mlive.invalid)
<slrnhetcrm....@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<hcmc3n$86r$2...@news.eternal-september.org> 439 Bad Reply-To
(eucl...@Mlive.invalid)
<2OydnU9uUKNRLnPX...@brightview.co.uk> 439 Bad From
(op.1693202792975...@10.10.69.182)
<mn.12b07d9bc...@libero.it> 439 Bad From (veleno81
<velenokullin@at@libero.it>)
<XPmdnUya9I2MKXPX...@brightview.co.uk> 439 Bad From
(op.5803475739600...@10.10.71.225)
<gIKdnfR0QIFsKXPX...@brightview.co.uk> 439 Bad From
(op.4997445734733...@10.10.60.219)
<C6adnSTKfbJvKXPX...@brightview.co.uk> 439 Bad From
(op.1166861807588...@10.10.68.234)
<8KWdndrKTuhuKXPX...@brightview.co.uk> 439 Bad From
(op.7517727440270...@10.10.50.66)
<Xns9CB77...@193.202.122.175> 439 Bad From (Jesper <jesper@>)
<Xns9CB77...@193.202.122.175> 439 Bad From (Jesper <jesper@>)
<hcmch1$817$2...@optima5.xanadu-bbs.net> 439 Bad From ("John F. Morse"
<jo...@example.invalid>)
<hcmcjq$817$3...@optima5.xanadu-bbs.net> 439 Bad From ("John F. Morse"
<jo...@example.invalid>)
<slrnhete05....@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<586dnV2TZJu4K3PX...@brightview.co.uk> 439 Bad From
(op.2161602937043...@10.10.39.224)
<4aeeb84f$0$827$4faf...@reader5.news.tin.it> 439 Bad Reply-To
(inv...@invalid.invalid)
<Xns9CB77...@193.202.122.175> 439 Bad From (Jesper <jesper@>)
<Xns9CB77...@193.202.122.175> 439 Bad From (Jesper <jesper@>)
<4aeeb4f2$0$20377$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<4aeeb572$0$20978$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<dL2dndL4IYc4JHPX...@brightview.co.uk> 439 Bad From
(op.1009880294336...@10.10.111.146)
<hcmdnk$kgq$1...@news.eternal-september.org> 439 Bad Reply-To
(eucl...@Mlive.invalid)
<hcmdq0$nsl$1...@ss408.t-com.hr> 439 Bad From ("kopipejst" <...@.....com>)
<hcmdri$kgq$2...@news.eternal-september.org> 439 Bad Reply-To
(eucl...@Mlive.invalid)
<G9edndGHD-cSJ3PX...@brightview.co.uk> 439 Bad From
(op.9594488719106...@10.10.118.109)
<zaednZegOPoEJ3PX...@brightview.co.uk> 439 Bad From
(op.4059151097499...@10.10.19.216)
<ppOdnbfnPYsGJ3PX...@brightview.co.uk> 439 Bad From
(op.7852401474587...@10.10.120.254)
<slrnheteio...@penne.houghi> 439 Bad Reply-To
(reply.t...@your.provider.invalid)
<slrnhetefp...@penne.houghi> 439 Bad Reply-To
(reply.t...@your.provider.invalid)
<eMCdnfsmWdEhJnPX...@giganews.com> 439 Bad From ("Eugene A.
Calame" <......@..........>)
<Pine.LNX.4.64.09...@dawn.a.b.c> 439 Bad From (Matt Giwer
<matt@localhost>)
<hbqdnafSbq8bJnPX...@giganews.com> 439 Bad From (Keith H
<keherma.@.epix.net>)
<eMCdnfUmWdFqJnPX...@giganews.com> 439 Bad From ("Eugene A.
Calame" <......@..........>)
<eMCdnfomWdFKJnPX...@giganews.com> 439 Bad From ("Eugene A.
Calame" <......@..........>)
<eMCdnfQmWdGLIXPX...@giganews.com> 439 Bad From ("Eugene A.
Calame" <......@..........>)
<mn.12d27d9bc...@libero.it> 439 Bad From (veleno81
<velenokullin@at@libero.it>)
<4aeebd11$0$1098$4faf...@reader3.news.tin.it> 439 Bad Reply-To
(n.darold....@virgilio.it.invalid)
<4aeeb8d3$0$22641$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<49idnS9KzaawIHPX...@brightview.co.uk> 439 Bad From
(op.1221595568986...@10.10.10.133)
<hcmej8$8rm$1...@optima5.xanadu-bbs.net> 439 Bad From ("John F. Morse"
<jo...@example.invalid>)
<G8adnQdUbMTpIHPX...@brightview.co.uk> 439 Bad From
(op.1732482423954...@10.10.66.73)
<hcmem9$8rm$2...@optima5.xanadu-bbs.net> 439 Bad From ("John F. Morse"
<jo...@example.invalid>)
<xvGdna1YBZwVIHPX...@brightview.co.uk> 439 Bad From
(op.2085007452591...@10.10.76.228)
<faq-ip.txt.tmp-faq-1257160208$35...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<faq-ippds.txt.tmp-faq-1257160209$36...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<hcmejv$pmh$1...@ss408.t-com.hr> 439 Bad From ("kopipejst" <...@.....com>)
<faq-ivd2.txt.tmp-faq-1257160261$36...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<0ffte51dp4v5m5g35...@4ax.com> 439 Bad Reply-To (Conte
Oliver <alex65....@wmail.it.invalid>)
<nZqdnXrbULVDIHPX...@giganews.com> 439 Bad From ("Eugene A.
Calame" <......@..........>)
<nZqdnXXbULV6IHPX...@giganews.com> 439 Bad From ("Eugene A.
Calame" <......@..........>)
<iq-dndn-H7CEI3PX...@brightview.co.uk> 439 Bad From
(op.0198750939501...@10.10.126.145)
<E72dnUuYyaSEI3PX...@brightview.co.uk> 439 Bad From
(op.7433037399827...@10.10.38.153)
<1oudnR_abKaNI3PX...@brightview.co.uk> 439 Bad From
(op.7124299912020...@10.10.122.32)
<z-qdnWL4hY5TI3PX...@pipex.net> 439 Bad From ("Brian Cryer"
<not.here@localhost>)
<hcmf0u$qmr$1...@ss408.t-com.hr> 439 Bad From
(=?iso-8859-2?B?qXXmTXXmUGFQcm9saWo=?= <123...@654321.00>)
<hcmfcd$91l$1...@optima5.xanadu-bbs.net> 439 Bad From ("John F. Morse"
<jo...@example.invalid>)
<4aeebcfb$0$5270$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<4aeec234$0$972$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<slrnhetgji...@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<4aeec277$1...@extreme.x-privat.org> 439 Bad Reply-To
(gru...@willygroup.org.invalid)
<hcmfvd$188$1...@atlantis.news.neostrada.pl> 439 Bad From
(=?UTF-8?B?UGF3ZcWC?= <ro...@127.0.0.1>)
<4aeec3f0$0$1099$4faf...@reader2.news.tin.it> 439 Bad From (Rama
<ramalinux@slackware_12.2>)
<o9edneEbp7-BXnPX...@brightview.co.uk> 439 Bad From
(op.9895475288711...@10.10.117.129)
<hcmgki$kqg$1...@news.datemas.de> 439 Bad From ("Foxy at Work"
<privicy@.net.freeserve.co.uk>)
<SCzHm.51616$ze1....@news-server.bigpond.net.au> 439 Bad Reply-To ("."
<.@.com>)
<4aeec741$0$1104$4faf...@reader1.news.tin.it> 439 Bad From ("rawmode"
<@>)
<FA10800B-C4F4-40F3...@microsoft.com> 439 Bad From
(=?Utf-8?B?RHlwY2RpdmVy?= <dypc...@discussions.microsoft.com.>)
<hcmh77$2gd$1...@ss408.t-com.hr> 439 Bad From ("kopipejst" <...@.....com>)
<hcmhb9$9g4$2...@optima5.xanadu-bbs.net> 439 Bad From ("John F. Morse"
<jo...@example.invalid>)
<gJGdnS96uawSVXPX...@giganews.com> 439 Bad From (P4nd1-P4nd4
<P4nd1-P4nd4@.net>)
<4aeec924$0$1111$4faf...@reader2.news.tin.it> 439 Bad From (Rama
<ramalinux@slackware_12.2>)
<V9mdnRPza7UlVXPX...@giganews.com> 439 Bad From (P4nd1-P4nd4
<P4nd1-P4nd4@.net>)
<yvWdnTeOiINwVXPX...@giganews.com> 439 Bad From (P4nd1-P4nd4
<P4nd1-P4nd4@.net>)
<2-WdnRwCuZSrVHPX...@pipex.net> 439 Bad From ("Brian Cryer"
<not.here@localhost>)
<hcmidm$pol$1...@nemesis.news.neostrada.pl> 439 Bad From ("M@tix"
<Matix1992@.onet.poczta.pl>)
<ZeqdnbLzQK3LV3PX...@giganews.com> 439 Bad From (P4nd1-P4nd4
<P4nd1-P4nd4@.net>)
<hcmhrk$dsv$1...@news.hs-niederrhein.de> 439 Bad From (Olizy
<b...@example.com>)
<hcmhmm$3mq$1...@ss408.t-com.hr> 439 Bad From ("Danko"
<dankodrMAKNI@@gmail.com>)
<hcmhs8$dt5$1...@news.hs-niederrhein.de> 439 Bad From (NJ <N...@example.com>)
<hcmhse$dt4$2...@news.hs-niederrhein.de> 439 Bad From (Alan_Iverson
<Alan_I...@example.com>)
<4aeecb30$0$21127$426a...@news.free.fr> 439 Bad From (cartomi
<cartomi.chez.free.@>)
<hcmhtn$dui$1...@news.hs-niederrhein.de> 439 Bad From (Alan_Iverson
<Alan_I...@example.com>)
<hcmhvo$9qf$1...@optima5.xanadu-bbs.net> 439 Bad From ("John F. Morse"
<jo...@example.invalid>)
<slrnhetiqp...@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<hcmhvm$duc$1...@news.hs-niederrhein.de> 439 Bad From (kww
<du...@example.comj>)
<hcmhvs$dsv$2...@news.hs-niederrhein.de> 439 Bad From (Olizy
<b...@example.com>)
<hcmi3k$dt5$2...@news.hs-niederrhein.de> 439 Bad From (NJ <N...@example.com>)
<G_WdnY_VnoDzVnPX...@brightview.co.uk> 439 Bad Reply-To
(davidke...@gmail.invalid)
<nLmdnSuwGaTnVnPX...@brightview.co.uk> 439 Bad From
(op.8371208775197...@10.10.81.29)
<hcmi46$duc$2...@news.hs-niederrhein.de> 439 Bad From (kww
<du...@example.comj>)
<eNqdnainQJ5cVnPX...@brightview.co.uk> 439 Bad From
(op.8816499357280...@10.10.33.32)
<hcmi8j$dug$2...@news.hs-niederrhein.de> 439 Bad From (Alan_Iverson
<Alan_I...@example.com>)
<1rqdnRzdgouZUXPX...@brightview.co.uk> 439 Bad From
(op.0181373442970...@10.10.105.55)
<hcmibb$mti$1...@news.datemas.de> 439 Bad From ("Foxy at Work"
<privicy@.net.freeserve.co.uk>)
<hcmibr$mtk$1...@news.datemas.de> 439 Bad From ("Foxy at Work"
<privicy@.net.freeserve.co.uk>)
<4aeeccdb$0$2490$db0f...@news.zen.co.uk> 439 Bad From (Ar <A...@127.0.0.1>)
<w7ednZpnP7nXUXPX...@brightview.co.uk> 439 Bad From
(op.1063308931629...@10.10.74.21)
<hcmiej$mtu$1...@news.datemas.de> 439 Bad From ("Foxy at Work"
<privicy@.net.freeserve.co.uk>)
<slrnhetj4o...@aces.localdomain> 439 Bad From (Harold Stevens
<woo...@aces.localdomain>)
<hcmif4$dut$1...@news.hs-niederrhein.de> 439 Bad From (dzeno
<dz...@example.com>)
<op.u2roca04hswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<RMWdnSim69RIUXPX...@brightview.co.uk> 439 Bad From
(op.8099531187120...@10.10.27.20)
<hcmj5n$q9d$1...@nemesis.news.neostrada.pl> 439 Bad From ("M@tix"
<Matix1992@.onet.poczta.pl>)
<hcmiiv$dut$2...@news.hs-niederrhein.de> 439 Bad From (dzeno
<dz...@example.com>)
<IdmdnVirg6C0UHPX...@brightview.co.uk> 439 Bad From
(op.0926598552635...@10.10.112.110)
<hcmipd$7r3$1...@atlantis.news.neostrada.pl> 439 Bad From ("M@tix"
<Matix1992@.onet.poczta.pl>)
<y8edneADQtC6UHPX...@pipex.net> 439 Bad From ("Brian Cryer"
<not.here@localhost>)
<gP2dnaAuW7j0UHPX...@brightview.co.uk> 439 Bad From
(op.0597102002727...@10.10.26.250)
<Be2dnUZRX4TwUHPX...@brightview.co.uk> 439 Bad From
(op.3412529301061...@10.10.93.145)
<T6GdnSps1r33UHPX...@brightview.co.uk> 439 Bad From
(op.7559568660433...@10.10.29.27)
<hcmird$nfr$1...@news.datemas.de> 439 Bad From ("Foxy at Work"
<privicy@.net.freeserve.co.uk>)
<hcmisp$ng7$1...@news.datemas.de> 439 Bad From ("Foxy at Work"
<privicy@.net.freeserve.co.uk>)
<hcmisn$e26$1...@news.hs-niederrhein.de> 439 Bad From (dzeno
<dz...@example.com>)
<hcmiu6$ngg$1...@news.datemas.de> 439 Bad From ("Foxy at Work"
<privicy@.net.freeserve.co.uk>)
<HKednZG2GdamU3PX...@brightview.co.uk> 439 Bad From
(op.5767056409313...@10.10.12.78)
<hcmirq$6fa$1...@ss408.t-com.hr> 439 Bad From ("Danko"
<dankodrMAKNI@@gmail.com>)
<hcmjdf$9be$1...@atlantis.news.neostrada.pl> 439 Bad From ("M@tix"
<Matix1992@.onet.poczta.pl>)
<G96dneTmhP4sUnPX...@brightview.co.uk> 439 Bad From
(op.1735583754515...@10.10.10.135)
<zbidnZNAd886UnPX...@brightview.co.uk> 439 Bad From
(op.4953564538910...@10.10.111.210)
<KKSdnRxh-vUvUnPX...@brightview.co.uk> 439 Bad From
(op.3273890069217...@10.10.38.109)
<hcmk3c$r0v$1...@nemesis.news.neostrada.pl> 439 Bad From ("M@tix"
<Matix1992@.onet.poczta.pl>)
<hcmjo7$a3l$1...@atlantis.news.neostrada.pl> 439 Bad From ("M@tix"
<Matix1992@.onet.poczta.pl>)
<hcmkbr$r5n$1...@nemesis.news.neostrada.pl> 439 Bad From ("M@tix"
<Matix1992@.onet.poczta.pl>)
<Zoudnd3FeNuQT3PX...@brightview.co.uk> 439 Bad From
(op.6942142186644...@10.10.72.154)
<UYOdncML18xjTHPX...@brightview.co.uk> 439 Bad From
(op.9822686810348...@10.10.62.227)
<neudnftxIaCQT3PX...@brightview.co.uk> 439 Bad From
(op.6372904927521...@10.10.8.209)
<J4ydndXEUuKRT3PX...@brightview.co.uk> 439 Bad From
(op.4926803664158...@10.10.82.27)
<hcmke5$r70$1...@nemesis.news.neostrada.pl> 439 Bad From ("M@tix"
<Matix1992@.onet.poczta.pl>)
<slrnhetkae...@aces.localdomain> 439 Bad From (Harold Stevens
<woo...@aces.localdomain>)
<boAHm.51627$ze1....@news-server.bigpond.net.au> 439 Bad From (Avid Fan
<us...@example.net>)
<0J-dnSZo0omJTnPX...@pipex.net> 439 Bad From ("Brian Cryer"
<not.here@localhost>)
<PtKdndWk1OysTnPX...@brightview.co.uk> 439 Bad From
(op.6320595273830...@10.10.77.187)
<Xns9CB78...@91.208.207.159> 439 Bad From (Jesper <jesper@>)
<4aeed3bf$0$1096$4faf...@reader3.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<4aeed446$0$1096$4faf...@reader3.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<4aeed4a4$0$1104$4faf...@reader3.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<4aeed4e5$0$1095$4faf...@reader3.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<4aeed56b$0$1104$4faf...@reader3.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<hcmka1$9uj$1...@ss408.t-com.hr> 439 Bad From ("Danko"
<dankodrMAKNI@@gmail.com>)
<4aeed5d7$0$1094$4faf...@reader3.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<4aeed5fc$0$1096$4faf...@reader3.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<sP2dnTjjC4hWSHPX...@brightview.co.uk> 439 Bad From
(op.1275122069634...@10.10.53.135)
<G5idnZzJYJAtS3PX...@brightview.co.uk> 439 Bad From
(op.7335111532548...@10.10.31.153)
<S9OdnUoXB6gnS3PX...@brightview.co.uk> 439 Bad From
(op.0247178393410...@10.10.67.44)
<VLOdnb1RzOgnS3PX...@brightview.co.uk> 439 Bad From
(op.9376036787439...@10.10.39.31)
<4aeed79c$0$1102$4faf...@reader3.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<4aeed801$0$1104$4faf...@reader3.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<4aeed883$0$9716$426a...@news.free.fr> 439 Bad From (cartomi
<cartomi.chez.free.@>)
<4aeed8ab$0$1093$4faf...@reader3.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<lrlte5tqu50oqnb6m...@4ax.com> 439 Bad From (David Lowndes
<Dav...@example.invalid>)
<faq-ip.txt.tmp-faq-1257167403$54...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<faq-ippds.txt.tmp-faq-1257167404$55...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<hcmljj$d3a$1...@ss408.t-com.hr> 439 Bad From ("kopipejst" <...@.....com>)
<BP6dncX2DfGsR3PX...@brightview.co.uk> 439 Bad From
(op.3425255226905...@10.10.28.14)
<faq-ivd2.txt.tmp-faq-1257167461$55...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<egmte59j2ng1q440e...@4ax.com> 439 Bad From (Michael
<micha...@example.net>)
<LeSdnaEzqK46RnPX...@brightview.co.uk> 439 Bad From
(op.7171566592140...@10.10.23.215)
<hcmm4t$egj$1...@ss408.t-com.hr> 439 Bad From ("kopipejst" <...@.....com>)
<hcmmd2$ri7$1...@news.datemas.de> 439 Bad From ("Foxy at Work"
<privicy@.net.freeserve.co.uk>)
<vsmte5pefrr76s8l4...@4ax.com> 439 Bad Reply-To
(blac...@example.com)
<a331cb06-b590-43ed...@a31g2000yqn.googlegroups.com> 439
Bad From ("@@@" <ocire...@hotmail.it>)
<1dBHm.24083$Cq1....@newsfe12.ams2> 439 Bad From (Philip Herlihy
<m...@here.localhost>)
<XiBHm.24084$Cq1....@newsfe12.ams2> 439 Bad From (Philip Herlihy
<m...@here.localhost>)
<4aeee22b$0$1112$4faf...@reader1.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<hcmnnn$81p$1...@nntp.amis.hr> 439 Bad From ("Kreso" <1...@456.789>)
<4aeee23f$0$1112$4faf...@reader1.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<hcmnrk$t7j$1...@news.datemas.de> 439 Bad From ("Foxy at Work"
<privicy@.net.freeserve.co.uk>)
<rqCdnbRvsNWhf3PX...@brightview.co.uk> 439 Bad From
(op.3902401255816...@10.10.85.195)
<slrnheton7...@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<WqBHm.4507$Yy6....@newsfe02.iad> 439 Bad Reply-To ("Josepi"
<Complaints-to: ab...@giganews.uk.>)
<8sBHm.136418$uO.3...@en-nntp-09.dc1.easynews.com> 439 Bad From (CF
<C...@example.invalid>)
<JtBHm.4067$%U3....@newsfe21.iad> 439 Bad Reply-To ("Josepi"
<Complaints-to: ab...@giganews.uk.>)
<slrnhetov8...@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<slrnhetp36...@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<VuWdnWj1BMAheXPX...@brightview.co.uk> 439 Bad From
(op.8573020520570...@10.10.54.69)
<hcmohe$bqu$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<slrnhetpbl...@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<e69a2895-896a-45d1...@f16g2000yqm.googlegroups.com> 439
Bad From ("@@@" <ocire...@hotmail.it>)
<rkpte5ds17utfcgcj...@4ax.com> 439 Bad From (Jos�
<jo...@127.0.0.1>)
<7l87kvF...@mid.individual.net> 439 Bad From (Greg Samson
<uwizatcluestickdotorg-REM...@example.com>)
<aoKdnbsbKJ_hdXPX...@brightview.co.uk> 439 Bad From
(op.7376443043254...@10.10.91.165)
<-N6dnYRG75OpdXPX...@brightview.co.uk> 439 Bad From
(op.1241003796449...@10.10.109.133)
<4aeee9ab$0$16446$426a...@news.free.fr> 439 Bad From ("toto"
<toto@toto@toto>)
<hqednZKHR_rhdXPX...@brightview.co.uk> 439 Bad From
(op.6088662074352...@10.10.121.185)
<uN-dnalS6ajhdXPX...@brightview.co.uk> 439 Bad From
(op.1461171039390...@10.10.113.158)
<lcqte5ptgmn2m9d2s...@4ax.com> 439 Bad From (emjeppesen
<emj@>)
<4aeeea56$0$964$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<aMKdnXK1fK4SdHPX...@brightview.co.uk> 439 Bad From
(op.5454419543612...@10.10.0.249)
<hcmqfm$2jp$1...@nemesis.news.neostrada.pl> 439 Bad From ("Rumburak"
<r.g.80@.......pl>)
<4aeeeae6$0$931$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<7l8887F...@mid.individual.net> 439 Bad Reply-To ("mmyvusenet"
<mmyvu...@invalid.invalid>)
<7l8888F...@mid.individual.net> 439 Bad Reply-To ("mmyvusenet"
<mmyvu...@invalid.invalid>)
<7l8889F...@mid.individual.net> 439 Bad Reply-To ("mmyvusenet"
<mmyvu...@invalid.invalid>)
<op.u2rua50phswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<4aeeeba6$0$969$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<Xa6dnTNFg-5CdnPX...@brightview.co.uk> 439 Bad From
(op.7403199394741...@10.10.5.247)
<lcmdnVv7f4fwcXPX...@brightview.co.uk> 439 Bad From
(op.3209785637649...@10.10.95.46)
<b96dnWEPP8_wcXPX...@brightview.co.uk> 439 Bad From
(op.8133905788069...@10.10.37.92)
<zKmdnQEeYb7zcXPX...@brightview.co.uk> 439 Bad From
(op.4308115832580...@10.10.48.242)
<JBTO5QMJ...@parkhead.demon.co.uk> 439 Bad Reply-To
(look...@nospam.invalid)
<slrnhetr7e...@penne.houghi> 439 Bad Reply-To
(reply.t...@your.provider.invalid)
<hcmqn8$4nq$1...@news.eternal-september.org> 439 Bad From ("Gooner89"
<0.0.@0.0>)
<mn.13ac7d9bb...@Lombar.com> 439 Bad From
(=?ISO-8859-15?Q?=A5--_Lombar_--=A5?= <Jose@@@Lombar.com>)
<hcmr2o$8vk$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<kIydnUgZ9cibcnPX...@supernews.com> 439 Bad From (Martin
Johnson <us...@example.net>)
<4aeeefd5$0$1108$4faf...@reader2.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<4aeeefea$0$1113$4faf...@reader2.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<1vrte5dmcv1fqoghf...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<XOednUp4Y9J9cnPX...@brightview.co.uk> 439 Bad From
(op.3129527671737...@10.10.95.130)
<x6udnaBcLId9cnPX...@brightview.co.uk> 439 Bad From
(op.4354813005377...@10.10.79.155)
<mn.13b17d9b3...@Lombar.com> 439 Bad From
(=?ISO-8859-15?Q?=A5--_Lombar_--=A5?= <Jose@@@Lombar.com>)
<mn.13b27d9b7...@Lombar.com> 439 Bad From
(=?ISO-8859-15?Q?=A5--_Lombar_--=A5?= <Jose@@@Lombar.com>)
<kOGdnbpJh-W-bXPX...@brightview.co.uk> 439 Bad From
(op.8747423373130...@10.10.69.185)
<7l89n0F...@mid.individual.net> 439 Bad Reply-To ("mmyvusenet"
<mmyvu...@invalid.invalid>)
<7vedna5E9bAKbXPX...@bright.net> 439 Bad From (jim
<"sjedgingN0Sp"@m@mwt,net>)
<7l89msF...@mid.individual.net> 439 Bad Reply-To ("mmyvusenet"
<mmyvu...@invalid.invalid>)
<hcmrg3$hig$1...@mud.stack.nl> 439 Bad Sender (lsp...@96.49.149.2)
<4aeef19d$0$957$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<4aeef19d$1$957$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<fcste51jeu7v4t5m8...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<4aeef1c4$0$273$1472...@news.sunsite.dk> 439 Bad Reply-To
(mic...@michaelweber.invalid)
<slrnhetse7...@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<4aeef22d$0$283$1472...@news.sunsite.dk> 439 Bad Reply-To
(mic...@michaelweber.invalid)
<4aeef259$0$967$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<giste5p2o3ukv18pe...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<qiste515a06ktns0t...@4ax.com> 439 Bad From (emjeppesen
<emj@>)
<hcmrq6$puf$1...@mud.stack.nl> 439 Bad Sender (lsp...@96.49.149.2)
<O5adnT3U9ONTb3PX...@brightview.co.uk> 439 Bad From
(op.9823546316096...@10.10.6.232)
<nnste59l811far8hg...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<7l8aabF...@mid.individual.net> 439 Bad Reply-To
(via-amz...@invalid.invalid)
<7l8abjF...@mid.individual.net> 439 Bad Reply-To ("mmyvusenet"
<mmyvu...@invalid.invalid>)
<mn.13be7d9bb...@Lombar.com> 439 Bad From
(=?ISO-8859-15?Q?=A5--_Lombar_--=A5?= <Jose@@@Lombar.com>)
<4aeef408$0$903$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<4aeef46d$0$925$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<mn.13c37d9bf...@Lombar.com> 439 Bad From
(=?ISO-8859-15?Q?=A5--_Lombar_--=A5?= <Jose@@@Lombar.com>)
<TNadnfdDYf_3aHPX...@brightview.co.uk> 439 Bad From
(op.6315094388004...@10.10.4.11)
<l1zustpk2y0k$.2o25woo4...@40tude.net> 439 Bad From (Davey
<da...@example.invalid>)
<6a659c8f-8faa-4b60...@k19g2000yqc.googlegroups.com> 439
Bad From ("@@@" <ocire...@hotmail.it>)
<4aeef649$0$926$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<faq-ip.txt.tmp-faq-1257174604$74...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<faq-ippds.txt.tmp-faq-1257174605$74...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<faq-ivd2.txt.tmp-faq-1257174662$75...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<LJWdnQbqhMzIa3PX...@brightview.co.uk> 439 Bad From
(op.7613074070444...@10.10.14.43)
<F4-dnX4gcN_hanPX...@brightview.co.uk> 439 Bad From
(op.0744237804810...@10.10.51.220)
<782dnY1iV5MbanPX...@brightview.co.uk> 439 Bad From
(op.0912830642970...@10.10.52.67)
<hcmte2$290h$1...@ns.tolcom.ru> 439 Bad From ("chupacabra"
<chupacabra@@@tolcom.ru>)
<DtydnRnETKEkZXPX...@brightview.co.uk> 439 Bad From
(op.6691818774214...@10.10.124.170)
<YfydnUEfcZ0yZXPX...@brightview.co.uk> 439 Bad From
(op.8098102355626...@10.10.55.22)
<a-Sdna6NY6YnZXPX...@brightview.co.uk> 439 Bad From
(op.0971088686123...@10.10.91.55)
<272966a6d08ff928...@msgid.frell.theremailer.net> 439 Bad
>From (hummingbird <hummi...@127.0.0.1>)
<jKydnQa8uc2dZnPX...@brightview.co.uk> 439 Bad From
(op.9239113925146...@10.10.34.207)
<4aeefb62$0$2465$426a...@news.free.fr> 439 Bad From (cartomi
<cartomi.chez.free.@>)
<op.u2rxso0zhswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<-9CdnWUWn-__YHPX...@pipex.net> 439 Bad From ("aquazur-dra"
<davidarmes@nospam@hotmail.com>)
<hcmuhg$h9i$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<hcmukn$631$1...@news.datemas.de> 439 Bad From ("Foxy at Work"
<privicy@.net.freeserve.co.uk>)
<hcmup2$q8m$1...@aioe.org> 439 Bad From (Noob <ro...@127.0.0.1>)
<4aeeff6f$0$964$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<hcmv71$ooa$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<4aef0032$0$972$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<op.u2ryd8jxhswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<op.u2ryfrl4hswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<mn.13f57d9b2...@libero.it> 439 Bad From (veleno81
<velenokullin@at@libero.it>)
<op.u2ryldeihswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<4aef02bc$0$890$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<op.u2rytpmqhswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<mn.13fe7d9b8...@libero.it> 439 Bad From (veleno81
<velenokullin@at@libero.it>)
<op.u2ryt8p4hswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<mn.14037d9b7...@libero.it> 439 Bad From (veleno81
<velenokullin@at@libero.it>)
<4aef04a6$0$1116$4faf...@reader1.news.tin.it> 439 Bad Reply-To
(inv...@invalid.invalid)
<9yDHm.111256$Xw3....@en-nntp-04.dc1.easynews.com> 439 Bad From (CF
<C...@example.invalid>)
<slrnheu1ab...@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<GpadnUVcE5hKmHLX...@brightview.co.uk> 439 Bad From
(op.9476930619817...@10.10.72.51)
<XZWdnY9tvIRFmHLX...@brightview.co.uk> 439 Bad From
(op.8366613111232...@10.10.104.62)
<2bmdnbK3Y89EmHLX...@brightview.co.uk> 439 Bad From
(op.3568083066276...@10.10.97.91)
<L4SdnfQee9qBm3LX...@brightview.co.uk> 439 Bad From
(op.6678164513518...@10.10.65.238)
<ecudnWDvLbqAm3LX...@brightview.co.uk> 439 Bad From
(op.6006095100177...@10.10.9.120)
<aoednUBXW-WDm3LX...@brightview.co.uk> 439 Bad From
(op.2942282648255...@10.10.105.28)
<sIednQknL9S9m3LX...@brightview.co.uk> 439 Bad From
(op.3727958545137...@10.10.101.210)
<xrOdneWGAvy3m3LX...@brightview.co.uk> 439 Bad From
(op.8669224620999...@10.10.92.171)
<WvWdnSjTZfK3m3LX...@brightview.co.uk> 439 Bad From
(op.5264840576974...@10.10.87.148)
<TridnUMfqLuxm3LX...@brightview.co.uk> 439 Bad From
(op.4580906217902...@10.10.121.105)
<loGdnQnWppuxm3LX...@brightview.co.uk> 439 Bad From
(op.6904517851324...@10.10.108.116)
<6qadnSN9LMyom3LX...@brightview.co.uk> 439 Bad From
(op.4032271936231...@10.10.108.182)
<tvWdnXUhN6uum3LX...@brightview.co.uk> 439 Bad From
(op.4552555518262...@10.10.100.71)
<AbOdnTNip4upm3LX...@brightview.co.uk> 439 Bad From
(op.7916230485459...@10.10.1.240)
<Lt6dnWWPG_3hm3LX...@brightview.co.uk> 439 Bad From
(op.9853221139735...@10.10.125.212)
<rYadnWNSwuDhm3LX...@brightview.co.uk> 439 Bad From
(op.2185041280101...@10.10.27.210)
<bJidnVL22bvgm3LX...@brightview.co.uk> 439 Bad From
(op.5803416790207...@10.10.32.231)
<op.u2rzndn0hswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<cqGdnd_waM9Vm3LX...@brightview.co.uk> 439 Bad From
(op.3883496828062...@10.10.118.164)
<98OdncyYVK1Vm3LX...@brightview.co.uk> 439 Bad From
(op.6370789893477...@10.10.85.191)
<3vqdnWFPfK9Vm3LX...@brightview.co.uk> 439 Bad From
(op.0033341734438...@10.10.31.2)
<ml1ue59r4rg0mg1n8...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<mn.14117d9bb...@libero.it> 439 Bad From (veleno81
<velenokullin@at@libero.it>)
<gomdnZVAatKQmnLX...@brightview.co.uk> 439 Bad From
(op.3250397227277...@10.10.33.160)
<0Y2dnQM08tmQmnLX...@brightview.co.uk> 439 Bad From
(op.3093523430378...@10.10.81.218)
<LFDHm.39191$%%3.1...@newsfe23.ams2> 439 Bad From (Philip Herlihy
<m...@here.localhost>)
<op.u2rzr5kihswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<69WdncM-O5PJmnLX...@brightview.co.uk> 439 Bad From
(op.6453398454652...@10.10.87.253)
<yZOdnWsg-fzLmnLX...@brightview.co.uk> 439 Bad From
(op.1721659925766...@10.10.31.120)
<lO-dneLo9fDLmnLX...@brightview.co.uk> 439 Bad From
(op.3915993723461...@10.10.1.134)
<msSdnT1jm_zLmnLX...@brightview.co.uk> 439 Bad From
(op.4809510738170...@10.10.104.124)
<7ridnSgtWfD8mnLX...@brightview.co.uk> 439 Bad From
(op.2588471365558...@10.10.126.164)
<4aef0769$0$906$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<P8GdnX50_Pf4mnLX...@brightview.co.uk> 439 Bad From
(op.1776260697244...@10.10.39.38)
<tPudnftnXaD4mnLX...@brightview.co.uk> 439 Bad From
(op.1676585234530...@10.10.7.232)
<kIDHm.111257$Xw3....@en-nntp-04.dc1.easynews.com> 439 Bad From (CF
<C...@example.invalid>)
<urqdnWjxi6w1mnLX...@brightview.co.uk> 439 Bad From
(op.4455470448780...@10.10.102.32)
<vsidnQ2-nvg0mnLX...@brightview.co.uk> 439 Bad From
(op.0040259307337...@10.10.103.34)
<msqdnaeQt9I1mnLX...@brightview.co.uk> 439 Bad From
(op.4198514816329...@10.10.61.2)
<9a1ue5tj5v552h9ea...@4ax.com> 439 Bad Reply-To (Nato Gobbo
<nato...@juventusmember.com.invalid>)
<u01ue5prpqsui6egj...@4ax.com> 439 Bad Reply-To (Nato Gobbo
<nato...@juventusmember.com.invalid>)
<hcn1q8$7du$1...@nemesis.news.neostrada.pl> 439 Bad From ("Rumburak"
<r.g.80@.......pl>)
<9eGdnSEvLL2flXLX...@brightview.co.uk> 439 Bad From
(op.7575704475738...@10.10.119.137)
<6aWdnSflgrSelXLX...@brightview.co.uk> 439 Bad From
(op.6572618389014...@10.10.76.165)
<802ue5dieu0201gn6...@4ax.com> 439 Bad Reply-To (Conte
Oliver <alex65....@wmail.it.invalid>)
<kLDHm.111258$Xw3....@en-nntp-04.dc1.easynews.com> 439 Bad From (CF
<C...@example.invalid>)
<6n1ue516bnrvv9fc0...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<yu6dnTUuS6EZlXLX...@brightview.co.uk> 439 Bad From
(op.5269383510820...@10.10.109.61)
<o-qdnesXp4wYlXLX...@brightview.co.uk> 439 Bad From
(op.1920891022084...@10.10.66.152)
<hcn19a$rg2$1...@news.tornevall.net> 439 Bad Reply-To ("Don Bailey"
<jas...@aol.invalid>)
<g46dnbqa0e2YlHLX...@brightview.co.uk> 439 Bad From
(op.5777935864556...@10.10.107.192)
<4aef090a$0$1103$4faf...@reader1.news.tin.it> 439 Bad Reply-To
(inv...@invalid.invalid)
<Abmdnd6OGaPTlHLX...@brightview.co.uk> 439 Bad From
(op.2524960797743...@10.10.9.138)
<ha-dnbOE1LF_lHLX...@brightview.co.uk> 439 Bad From
(op.2915771799051...@10.10.12.188)
<AuadnUkAQpe7l3LX...@brightview.co.uk> 439 Bad From
(op.2023617645587...@10.10.4.146)
<OoKdnYe3N5a6l3LX...@brightview.co.uk> 439 Bad From
(op.9699640508587...@10.10.64.45)
<fvudnTf9p4C7l3LX...@brightview.co.uk> 439 Bad From
(op.9074994433750...@10.10.90.195)
<ccydnVFbVZ26l3LX...@brightview.co.uk> 439 Bad From
(op.3481092217989...@10.10.72.124)
<_LqdnVI64-qsl3LX...@brightview.co.uk> 439 Bad From
(op.2099555080819...@10.10.91.88)
<oJydnY6c282tl3LX...@brightview.co.uk> 439 Bad From
(op.4203354606343...@10.10.1.235)
<HPidnagVKOWsl3LX...@brightview.co.uk> 439 Bad From
(op.0116806500742...@10.10.89.117)
<n7OdnUcHDa6vl3LX...@brightview.co.uk> 439 Bad From
(op.1612929393732...@10.10.115.6)
<yo-dnf4dQrKhl3LX...@brightview.co.uk> 439 Bad From
(op.9098186173443...@10.10.48.224)
<puadnYoymayhl3LX...@brightview.co.uk> 439 Bad From
(op.9244662166884...@10.10.41.108)
<Q5ydndoiU5Sgl3LX...@brightview.co.uk> 439 Bad From
(op.3699962846362...@10.10.40.35)
<_fmdnbA9Ndzbl3LX...@brightview.co.uk> 439 Bad From
(op.0465292944317...@10.10.64.69)
<4d2dnWxTprmhl3LX...@brightview.co.uk> 439 Bad From
(op.9093220706065...@10.10.39.62)
<nIidnRg7O8DYl3LX...@brightview.co.uk> 439 Bad From
(op.9304601667265...@10.10.11.111)
<fb-dnaa4IO_Yl3LX...@brightview.co.uk> 439 Bad From
(op.7584132826369...@10.10.57.242)
<1UDHm.120025$Jp1....@en-nntp-02.dc1.easynews.com> 439 Bad From (CF
<C...@example.invalid>)
<mbudnTSwts9Xl3LX...@brightview.co.uk> 439 Bad From
(op.8936298017841...@10.10.26.1)
<102ue5tigma336a13...@4ax.com> 439 Bad From (jake
<ja...@127.0.0.1>)
<McadnQoupM-OlnLX...@brightview.co.uk> 439 Bad From
(op.3662815482501...@10.10.85.240)
<4aef0b92$0$925$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<7cc83$4aef0ba8$d9a2cd24$20...@news.hispeed.ch> 439 Bad From (John Smith
<john....@for.example>)
<tv2ue5p2sreod8djg...@4ax.com> 439 Bad From (jake
<ja...@127.0.0.1>)
<9u2ue59f0ekshk9bj...@4ax.com> 439 Bad From (your friend
<dev....@example.com>)
<hcn2b3$nsg$1...@deskrabbit.motzarella.org> 439 Bad From (Desk Rabbit
<m...@example.com>)
<hcn2l6$fbt$1...@atlantis.news.neostrada.pl> 439 Bad From ("Marcin"
<yahoo2n@delete@poczta.onet.pl>)
<3a3ue559emog8la6c...@4ax.com> 439 Bad From (Feico
<fe...@127.0.0.1>)
<4aef0d8f$0$1116$4faf...@reader1.news.tin.it> 439 Bad Reply-To
(inv...@invalid.invalid)
<hcn2lk$4ln$1...@sunce.iskon.hr> 439 Bad From ("@zr@"
<azra.im...@nospam.inet.hr>)
<op.u2r03cc8hswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<hcn2um$52n$1...@sunce.iskon.hr> 439 Bad From ("@zr@"
<azra.im...@nospam.inet.hr>)
<4aef0f31$0$1007$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<4aef1046$0$820$4faf...@reader5.news.tin.it> 439 Bad Reply-To
(inv...@invalid.invalid)
<4aef107a$0$820$4faf...@reader5.news.tin.it> 439 Bad Reply-To
(inv...@invalid.invalid)
<4aef107b$0$31274$607e...@cv.net> 439 Bad From ("Anne"
<jdo...@example.com>)
<d44ue5haq17jskse8...@4ax.com> 439 Bad Reply-To (Conte
Oliver <alex65....@wmail.it.invalid>)
<664ue5hhk603oqjkr...@4ax.com> 439 Bad Reply-To (Conte
Oliver <alex65....@wmail.it.invalid>)
<4aef11a3$0$943$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<2g4ue55oi9ub4fp5m...@4ax.com> 439 Bad Reply-To (Conte
Oliver <alex65....@wmail.it.invalid>)
<faq-ippds.txt.tmp-faq-1257181805$93...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<faq-ip.txt.tmp-faq-1257181804$93...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<faq-ivd2.txt.tmp-faq-1257181861$93...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<9pEHm.88718$1s6....@twister2.libero.it> 439 Bad Reply-To ("Gioca"
<gio_gio_80@@@@@libero@@@.it>)
<hcn3tn$261$1...@news.eternal-september.org> 439 Bad Reply-To
(Invi...@invalid.invalid)
<4aef1322$0$32720$426a...@news.free.fr> 439 Bad From (cartomi
<cartomi.chez.free.@>)
<jrEHm.120027$Jp1....@en-nntp-02.dc1.easynews.com> 439 Bad From (CF
<C...@example.invalid>)
<4aef139f$0$1101$4faf...@reader3.news.tin.it> 439 Bad From (Rama
<ramalinux@slackware_12.2>)
<4aef13ab$0$272$1472...@news.sunsite.dk> 439 Bad From ("carl"
<carl@.com>)
<1pudnZZFntI9jnLX...@brightview.co.uk> 439 Bad From
(op.0294499786690...@10.10.104.157)
<vqEHm.89434$9f6.1...@twister1.libero.it> 439 Bad Reply-To ("Gioca"
<gio_gio_80@@@@@libero@@@.it>)
<9b27320b-6e94-4924...@m16g2000yqc.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<LvEHm.6$sY...@newsfe17.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<4aef1485$0$1101$4faf...@reader3.news.tin.it> 439 Bad From (Rama
<ramalinux@slackware_12.2>)
<Xns9CB75F049F4...@188.40.43.213> 439 Bad From
("briant...@gmail.com" <briant...@localhost.localdomain>)
<hcn4cp$6iu$1...@sunce.iskon.hr> 439 Bad From ("@zr@"
<azra.im...@nospam.inet.hr>)
<9CEHm.9$sY...@newsfe17.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<7l8j16F...@mid.individual.net> 439 Bad From ("J.O. Aho"
<us...@example.net>)
<4aef1664$0$2539$da0f...@news.zen.co.uk> 439 Bad From (Mark Murray
<w.h....@example.com>)
<slrnheu5p3.2c...@satcidananda.hb.theunworthy.com> 439 Bad From
(fluffybunnie <fluffy...@127.0.0.1>)
<LBEHm.89441$9f6.1...@twister1.libero.it> 439 Bad Reply-To ("Gioca"
<"gio_gio_80@@@@@libero@@"@.it>)
<slrnhen8h...@pjr.gotdns.org> 439 Bad Reply-To (Peter J Ross
<peadar...@gmail.com>)
<Xns9CB761432BC...@188.40.43.213> 439 Bad From
("briant...@gmail.com" <briant...@localhost.localdomain>)
<hcn59l$ntu$1...@news.eternal-september.org> 439 Bad Reply-To
(a.non...@example.invalid)
<XMEHm.120037$Jp1....@en-nntp-02.dc1.easynews.com> 439 Bad From (CF
<C...@example.invalid>)
<4aef189c$0$4981$607e...@cv.net> 439 Bad From ("Anne"
<jdo...@example.com>)
<hcn5bk$obr$1...@news.eternal-september.org> 439 Bad From (RLM
<r...@127.0.0.1>)
<Xns9CB761DB389...@188.40.43.213> 439 Bad From
("briant...@gmail.com" <briant...@localhost.localdomain>)
<Xns9CB7623A8E3...@188.40.43.213> 439 Bad From
("briant...@gmail.com" <briant...@localhost.localdomain>)
<slrnheu6c8...@zeus.home.lan> 439 Bad Reply-To
(postmaster@localhost)
<yREHm.120043$Jp1....@en-nntp-02.dc1.easynews.com> 439 Bad From (CF
<C...@example.invalid>)
<hcn5nc$coj$1...@inews.gazeta.pl> 439 Bad From (Animka
<animka@to...nie.ja.wp.pl>)
<slrnheu6n...@satcidananda.hb.theunworthy.com> 439 Bad Reply-To
(in...@127.0.0.1)
<uWEHm.34838$La7....@uutiset.elisa.fi> 439 Bad From (MR2
<mriikone@ei..roskapostia..elisanet.fiu>)
<hcn5vq$mma$1...@ss408.t-com.hr> 439 Bad From
(=?iso-8859-2?B?qXXmTXXmUGFQcm9saWo=?= <123...@654321.00>)
<mn.14007d9bb...@Lombar.com> 439 Bad From
(=?ISO-8859-15?Q?=A5--_Lombar_--=A5?= <Jose@@@Lombar.com>)
<447ue5l7i4ra4r66a...@4ax.com> 439 Bad Reply-To (Conte
Oliver <alex65....@wmail.it.invalid>)
<ia7ue55ml17mb6p6u...@4ax.com> 439 Bad From (jake
<ja...@127.0.0.1>)
<slrnheu7de...@zeus.home.lan> 439 Bad Reply-To
(postmaster@localhost)
<hcn6ij$il0$03$1...@news.t-online.com> 439 Bad From (Thomas Stahl
<nob...@example.com>)
<4aeee22f$0$1098$4faf...@reader3.news.tin.it> 439 Bad Reply-To ("Max max"
<1o1kve402t...@sneakemail.com.invalid>)
<hcn6qn$lu1$1...@achot.icm.edu.pl> 439 Bad From (Paul <exa...@example.com>)
<op.u2r4essdhswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<slrnheu7l9...@zeus.home.lan> 439 Bad Reply-To
(postmaster@localhost)
<laFHm.5460$v47....@newsfe23.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<d9013ca3-d69c-4f86...@m26g2000yqb.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<d648c3e3-d5f9-4059...@o10g2000yqa.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<slrnheu7ua...@zeus.home.lan> 439 Bad Reply-To
(postmaster@localhost)
<f591112f-d49f-4464...@z41g2000yqz.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<2o7ue55dhhmtl6bpq...@4ax.com> 439 Bad From (dave
<da...@127.0.0.1>)
<a9-dnWF4j890gnLX...@bright.net> 439 Bad From (jim
<".sjedgingN0sp"@m...@mwt.net>)
<slrnheu80i.2e...@satcidananda.hb.theunworthy.com> 439 Bad From
(fluffybunnie <fluffy...@127.0.0.1>)
<4aeee689$0$65863$892e...@auth.newsreader.octanews.com> 439 Bad From
(llmyc <ll...@example.net>)
<slrnheu88e...@zeus.home.lan> 439 Bad Reply-To
(postmaster@localhost)
<KjFHm.39198$%%3.2...@newsfe23.ams2> 439 Bad From (Philip Herlihy
<m...@here.localhost>)
<af06f74f-5e05-4e13...@b15g2000yqd.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<kPSdnZQKg5JQvHLX...@posted.grandecom> 439 Bad From (JD
<J...@example.invalid>)
<l88ue59lg8arhogls...@4ax.com> 439 Bad Reply-To (NatoGobbo
<natogobbo...@juventusmember.com.invalid>)
<4aef21f0$0$23113$426a...@news.free.fr> 439 Bad From (cartomi
<cartomi.chez.free.@>)
<hcn77r$nth$1...@node1.news.atman.pl> 439 Bad From (Animka
<animka@to...nie.ja.wp.pl>)
<MoFHm.5462$v47....@newsfe23.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<Xns9CB7BA8356D...@69.16.176.253> 439 Bad From (Periander
<ulm@.4rubbish.britwar.co.uk>)
<spFHm.39201$%%3.3...@newsfe23.ams2> 439 Bad From (Philip Herlihy
<m...@here.localhost>)
<yt3zs1n5...@hyperion.com> 439 Bad Reply-To (raulatnewz@..gmail.com)
<lqFHm.5463$v47....@newsfe23.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<4aef237b$0$31264$607e...@cv.net> 439 Bad From ("BigArtie" <XXX@.com>)
<slrnheu8ss...@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<Xns9CB7BB36097B...@69.16.176.253> 439 Bad From (Chris Wilson
<ulm@.4rubbish.britwar.co.uk>)
<4aef2413$0$31278$607e...@cv.net> 439 Bad From ("BigArtie" <XXX@.com>)
<hcn8bs$ns8$1...@achot.icm.edu.pl> 439 Bad From (Paul <exa...@example.com>)
<hcn8d4$ns8$2...@achot.icm.edu.pl> 439 Bad From (Paul <exa...@example.com>)
<87acb9f5-ffae-4030...@o10g2000yqa.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<4aef24f0$0$31268$607e...@cv.net> 439 Bad From ("BigArtie" <XXX@.com>)
<4aef2504$0$1011$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<6a9ue513br0dkhinu...@4ax.com> 439 Bad From (dave
<da...@127.0.0.1>)
<4aef261b$0$27802$426a...@news.free.fr> 439 Bad Reply-To
(Ex-Ku...@detout.invalid)
<pan.2009.11.02...@example.net> 439 Bad From (Rich Grise
<rich...@example.net>)
<hcn8rp$ob7$1...@achot.icm.edu.pl> 439 Bad From (Paul <exa...@example.com>)
<7l8n9sF...@mid.individual.net> 439 Bad From (frank
<fr...@example.invalid>)
<hcn91c$sf$1...@news.eternal-september.org> 439 Bad Reply-To
(a.non...@example.invalid)
<qr9ue590h2d1usslv...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<slrnheni1...@pjr.gotdns.org> 439 Bad Reply-To (Peter J Ross
<peadar...@gmail.com>)
<hcn930$214$1...@news.eternal-september.org> 439 Bad Reply-To
(a.non...@example.invalid)
<XEFHm.89507$9f6.1...@twister1.libero.it> 439 Bad From ("ElPlaza."
<el_plaza@.libero.it>)
<7l8nj6F...@mid.individual.net> 439 Bad From (frank
<fr...@example.invalid>)
<7l8nmqF...@mid.individual.net> 439 Bad From (frank
<fr...@example.invalid>)
<k0aue59uamrfd1tl7...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<hcn9d8$1tb$1...@news.albasani.net> 439 Bad From ("U.P."
<u...@localhost.localdomain>)
<7923f4c0-012c-46cf...@v25g2000yqk.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<hcn9fs$pat$1...@achot.icm.edu.pl> 439 Bad From (Paul <exa...@example.com>)
<7l8o1uF...@mid.individual.net> 439 Bad From (frank
<fr...@example.invalid>)
<4aef2b3d$0$1007$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luZ@w...@adoo.fr.invalid>)
<7vaue5pf63ipdrtem...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<b0357eb8-8b0c-48d3...@37g2000yqm.googlegroups.com> 439 Bad
>From ("@Cookie@" <cookie...@gmail.com>)
<7l8oiaF...@mid.individual.net> 439 Bad From (frank
<fr...@example.invalid>)
<4aef2c5f$0$1419$4faf...@reader4.news.tin.it> 439 Bad From ("rawmode"
<@>)
<i0GHm.34866$La7....@uutiset.elisa.fi> 439 Bad From (MR2
<mriikone@ei..roskapostia..elisanet.fiu>)
<81GHm.88831$1s6....@twister2.libero.it> 439 Bad From ("Gene"
<........@.....>)
<91GHm.88832$1s6....@twister2.libero.it> 439 Bad From ("Gene"
<........@.....>)
<4aef2d3e$0$1113$4faf...@reader2.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<m%FHm.89519$9f6.1...@twister1.libero.it> 439 Bad From ("Gene"
<........@.....>)
<hcnabj$3pe$1...@ss408.t-com.hr> 439 Bad From ("Aleksandar"
<ac...@live.com.>)
<7l8ot7F...@mid.individual.net> 439 Bad From (frank
<fr...@example.invalid>)
<EMOdncPRH_BlsHLX...@giganews.com> 439 Bad From (P4nd1-P4nd4
<P4nd1-P4nd4@.net>)
<faq-ippds.txt.tmp-faq-1257189003$11...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<faq-ip.txt.tmp-faq-1257189002$11...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<faq-ivd2.txt.tmp-faq-1257189061$11...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<7l8p5uF...@mid.individual.net> 439 Bad From (frank
<fr...@example.invalid>)
<4aef2ec8$0$1097$4faf...@reader3.news.tin.it> 439 Bad From (Rama
<ramalinux@slackware_12.2>)
<4aef2f04$0$1113$4faf...@reader2.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<4aef2f30$0$1107$4faf...@reader2.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<4aef2f9a$0$1102$4faf...@reader2.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<4aef2f8e$0$1112$4faf...@reader2.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<4d290167-e9f1-4c81...@r5g2000yqb.googlegroups.com> 439 Bad
>From ("P@lp@tine02" <padaw...@hotmail.com>)
<7l8ptfF...@mid.individual.net> 439 Bad From (frank
<fr...@example.invalid>)
<811565b9-a569-431e...@l2g2000yqd.googlegroups.com> 439 Bad
>From ("P@lp@tine02" <padaw...@hotmail.com>)
<5fd55$4aef3257$541a8370$14...@cache6.tilbu1.nb.home.nl> 439 Bad From
("Kwibus" <kul@lie@home@.nl>)
<4aef32de$0$274$1472...@news.sunsite.dk> 439 Bad Reply-To ("jopa"
<ad...@jp-web.invalid>)
<upGHm.89541$9f6.1...@twister1.libero.it> 439 Bad Reply-To
(pelti...@Mgmail.com.invalid)
<hcnc9k$sgo$1...@achot.icm.edu.pl> 439 Bad From (Paul <exa...@example.com>)
<4aef34a9$0$1106$4faf...@reader2.news.tin.it> 439 Bad From ("Wiinoge"
<deepblue@>)
<op.u2r8sqqgilk2x8@frrdamid430p> 439 Bad Reply-To
(patrickr.dubois.don't.s...@free.fr.invalid)
<i4due5di5l45nf7bd...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<4aef3590$0$1009$ba4a...@news.orange.fr> 439 Bad From ("Mach2"
<ga.danio@@orange.fr>)
<slrnheudbt...@penne.houghi> 439 Bad Reply-To
(reply.t...@your.provider.invalid)
<hcncoa$t4s$1...@achot.icm.edu.pl> 439 Bad From (Paul <exa...@example.com>)
<Xns9CB7C8F977F8...@69.16.176.253> 439 Bad From (Periander
<ulm@.4rubbish.britwar.co.uk>)
<BHGHm.41958$y%.24578@newsfe29.ams2> 439 Bad From (Philip Herlihy
<m...@here.localhost>)
<DIGHm.41959$y%.21666@newsfe29.ams2> 439 Bad From (Philip Herlihy
<m...@here.localhost>)
<4aef...@news.x-privat.org> 439 Bad Reply-To (aar...@invalid.invalid)
<U7lITVB7...@217.169.1.80> 439 Bad Reply-To (Christopher Webber
<zarz...@zarzuela.net.invalid>)
<7meue5ph2rhopp5rq...@4ax.com> 439 Bad From (mick
<mick@work...>)
<BYGHm.51653$ze1....@news-server.bigpond.net.au> 439 Bad Reply-To ("."
<.@.com>)
<SZGHm.3273$6O1....@newsfe08.ams2> 439 Bad From (alan <Alan@.com>)
<6518284.p...@127.0.0.1> 439 Bad Reply-To (ro...@127.0.0.1)
<8_GHm.51654$ze1....@news-server.bigpond.net.au> 439 Bad Reply-To ("."
<.@.com>)
<4877172.Q...@127.0.0.1> 439 Bad Reply-To (ro...@127.0.0.1)
<4aef3d42$1...@extreme.x-privat.org> 439 Bad Reply-To
(gru...@willygroup.org.invalid)
<PPCdnWGprs5JoHLX...@brightview.co.uk> 439 Bad From
(op.2014419088391...@10.10.104.185)
<4MWdnYcGh7RCoHLX...@brightview.co.uk> 439 Bad From
(op.0066046583311...@10.10.80.189)
<HrqdnTFXVpZ9oHLX...@brightview.co.uk> 439 Bad From
(op.7185108713819...@10.10.73.90)
<S-adnesAu5lCoHLX...@brightview.co.uk> 439 Bad From
(op.5914690858555...@10.10.12.173)
<_J-dnWvM-_99oHLX...@brightview.co.uk> 439 Bad From
(op.9385697815946...@10.10.114.223)
<o6Cdnegm_elwoHLX...@brightview.co.uk> 439 Bad From
(op.3707367929606...@10.10.85.30)
<-bCdnQPjH51zoHLX...@brightview.co.uk> 439 Bad From
(op.8376185026610...@10.10.47.139)
<4LydndkIe-1zoHLX...@brightview.co.uk> 439 Bad From
(op.1828966900860...@10.10.37.128)
<UeKdnf4AJbJyoHLX...@brightview.co.uk> 439 Bad From
(op.4754784550129...@10.10.13.252)
<-aOdnQM9xINnoHLX...@brightview.co.uk> 439 Bad From
(op.8984972523647...@10.10.101.116)
<HLednXa7Xa5noHLX...@brightview.co.uk> 439 Bad From
(op.9730453664448...@10.10.63.93)
<TrWdnUhMU-9moHLX...@brightview.co.uk> 439 Bad From
(op.2152773033876...@10.10.9.29)
<W4ednbEZfc9moHLX...@brightview.co.uk> 439 Bad From
(op.4332098439690...@10.10.0.229)
<a_qdncsTsMaZo3LX...@brightview.co.uk> 439 Bad From
(op.2273021941048...@10.10.91.244)
<35GdnRVd5I6bo3LX...@brightview.co.uk> 439 Bad From
(op.6262658141696...@10.10.109.102)
<a5ydnap7Oq2Vo3LX...@brightview.co.uk> 439 Bad From
(op.5887828707386...@10.10.61.20)
<yKmdnZTSKeaVo3LX...@brightview.co.uk> 439 Bad From
(op.0510376922356...@10.10.49.22)
<p9GdnQMG2uSBo3LX...@brightview.co.uk> 439 Bad From
(op.3186152199080...@10.10.64.59)
<z7-dnf5SodWBo3LX...@brightview.co.uk> 439 Bad From
(op.2601405438736...@10.10.16.82)
<7NGdnWBZVLeAo3LX...@brightview.co.uk> 439 Bad From
(op.3579761891381...@10.10.108.56)
<buqdnfD5_rSCo3LX...@brightview.co.uk> 439 Bad From
(op.8127506952498...@10.10.16.85)
<uL2dnWxdG-G1o3LX...@brightview.co.uk> 439 Bad From
(op.1583238909669...@10.10.80.190)
<46udnQy_vqi3o3LX...@brightview.co.uk> 439 Bad From
(op.9390621243263...@10.10.86.246)
<0I2dnb4Gfsa1o3LX...@brightview.co.uk> 439 Bad From
(op.9350296200643...@10.10.37.92)
<i7udnTRKcuG3o3LX...@brightview.co.uk> 439 Bad From
(op.2004901155953...@10.10.99.248)
<ioGdnfAJbZyno3LX...@brightview.co.uk> 439 Bad From
(op.5487505653171...@10.10.69.46)
<aridnVuPNcKmo3LX...@brightview.co.uk> 439 Bad From
(op.7792331358572...@10.10.31.206)
<zradnWUOEPqoo3LX...@brightview.co.uk> 439 Bad From
(op.8716498708255...@10.10.56.143)
<SLmdnVCfQ_PXo3LX...@brightview.co.uk> 439 Bad From
(op.8783476924648...@10.10.9.190)
<BbSdnfvjt-HWo3LX...@brightview.co.uk> 439 Bad From
(op.0179156498231...@10.10.69.146)
<_uednZIkaM3Wo3LX...@brightview.co.uk> 439 Bad From
(op.5036186394903...@10.10.109.56)
<QJadncz89b_Wo3LX...@brightview.co.uk> 439 Bad From
(op.4280634068335...@10.10.59.196)
<TuednYDsHpH9o3LX...@brightview.co.uk> 439 Bad From
(op.5551682918292...@10.10.20.133)
<4IqdnR6Bndb9o3LX...@brightview.co.uk> 439 Bad From
(op.5855755180895...@10.10.100.224)
<_7HHm.82$sY...@newsfe17.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<3jfue551mock3n311...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<slrnheuf8k...@penne.houghi> 439 Bad Reply-To
(reply.t...@your.provider.invalid)
<sjfue5hn296smjd80...@4ax.com> 439 Bad From (A.Reader
<anony...@example.com>)
<klfue51a6lh0mg3ns...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<0pfue5da5kjmj2glr...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<4aef3fe3$0$21870$426a...@news.free.fr> 439 Bad Reply-To ("Dominique
Proscia" <d.pr...@free.fr.invalid>)
<ngfue5ppafbcq5vac...@4ax.com> 439 Bad Reply-To (H@..)
<hcnf6a$53a$1...@news.eternal-september.org> 439 Bad From ("Gooner89"
<0.0.@0.0>)
<pgHHm.83$sY5...@newsfe17.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<MiHHm.27$xt...@newsfe18.iad> 439 Bad From (Wanna-Be Sys Admin
<sysa...@example.com>)
<ViHHm.51657$ze1....@news-server.bigpond.net.au> 439 Bad Reply-To ("."
<.@.com>)
<%jHHm.86$sY5...@newsfe17.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<7l8ttlF...@mid.individual.net> 439 Bad From ("J.O. Aho"
<us...@example.net>)
<Ad-dnXbU7acp3HLX...@posted.grandecom> 439 Bad From (JD
<J...@example.invalid>)
<4aef41c7$0$25112$426a...@news.free.fr> 439 Bad Reply-To ("Dominique
Proscia" <d.pr...@free.fr.invalid>)
<tcgue5t8anr9rn1an...@4ax.com> 439 Bad From (Oren
<Or...@127.0.0.1>)
<JuHHm.88$sY...@newsfe17.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<5qgue5l3a71c3bqpo...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<fsfue5h9re89rkdp8...@4ax.com> 439 Bad Reply-To (H@..)
<-JCdnZfOA7tHonLX...@mozilla.org> 439 Bad From (Adhal
<us...@example.net>)
<2194566.U...@127.0.0.1> 439 Bad Reply-To (ro...@127.0.0.1)
<db699372a50d15bb...@aracari.127.0.0.1> 439 Bad From
(hummingbird <hummingb�r...@127.0.0.1>)
<14454853....@127.0.0.1> 439 Bad Reply-To (ro...@127.0.0.1)
<2662249.l...@127.0.0.1> 439 Bad Reply-To (ro...@127.0.0.1)
<hcngoc$spj$1...@news.mixmin.net> 439 Bad Reply-To (an...@domain.invalid)
<4aef4691$0$10263$426a...@news.free.fr> 439 Bad Reply-To ("Dominique
Proscia" <d.pr...@free.fr.invalid>)
<4aef46db$0$24695$426a...@news.free.fr> 439 Bad Reply-To ("Dominique
Proscia" <d.pr...@free.fr.invalid>)
<7GHHm.170$wq5...@newsfe19.iad> 439 Bad From ("John W. Krahn"
<som...@example.com>)
<QGHHm.23$M45...@newsfe06.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<wHHHm.51669$ze1....@news-server.bigpond.net.au> 439 Bad Reply-To ("."
<.@.com>)
<gKHHm.24$M4...@newsfe06.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<ZNHHm.51675$ze1....@news-server.bigpond.net.au> 439 Bad Reply-To ("."
<.@.com>)
<RQHHm.25$M4...@newsfe06.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<faq-ivd.txt.tmp-faq-1257196142$13...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<faq-ippds.txt.tmp-faq-1257196202$13...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<faq-ip.txt.tmp-faq-1257196202$13...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<Xns9CB7861E626...@188.40.43.213> 439 Bad From
("briant...@gmail.com" <briant...@localhost.localdomain>)
<faq-ivd2.txt.tmp-faq-1257196261$13...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<tchue5dk1k1qq36qh...@4ax.com> 439 Bad Reply-To (H@..)
<kZHHm.29$M45...@newsfe06.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<0qiue59ho4k23mso4...@4ax.com> 439 Bad Reply-To (H@..)
<N%HHm.31$M45...@newsfe06.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<7d2967c0fbbb37e2...@aracari.127.0.0.1> 439 Bad From
(hummingbird <hummingb�r...@127.0.0.1>)
<jviue5d1v3fuuor3p...@4ax.com> 439 Bad Reply-To (H@..)
<Xns9CB7E3B63A773g...@194.109.133.242> 439 Bad From (Jan
Mannoury <@>)
<hcnil2$tuk$1...@news.mixmin.net> 439 Bad Reply-To (an...@domain.invalid)
<j8jue51a2ri064r6v...@4ax.com> 439 Bad Reply-To
(jack.dom...@gmail.invalid)
<4aef4e03$0$2531$da0f...@news.zen.co.uk> 439 Bad From (Ar <A...@127.0.0.1>)
<fbjue5539t8bk8un3...@4ax.com> 439 Bad Reply-To (H@..)
<ldjue5pkvice9ldhs...@4ax.com> 439 Bad Reply-To (H@..)
<uCfx$iOH50...@adsl24.co.uk> 439 Bad From (Veggie Dave
<Veggie~Da...@127.0.0.1>)
<6jjue51k7rg0u83ei...@4ax.com> 439 Bad Reply-To (H@..)
<4aef4ed8$0$3604$7566...@news.cambrium.nl> 439 Bad From ("Hans"
<nobody@localhost.>)
<op.u2sd4ltdilk2x8@frrdamid430p> 439 Bad Reply-To
(patrickr.dubois.don't.s...@free.fr.invalid)
<4aef5047$0$4918$7566...@news.cambrium.nl> 439 Bad From ("Hans"
<nobody@localhost.>)
<4aef505d$1...@news.home.net.pl> 439 Bad From ("dziobak"
<dziobak-usun@hot..pl>)
<vNOdnZFzz6vlzXLX...@brightview.co.uk> 439 Bad From
(op.0275450198737...@10.10.108.202)
<ermdncMMuIrlzXLX...@brightview.co.uk> 439 Bad From
(op.9125250614361...@10.10.6.38)
<o7OdnWNQ5frnzXLX...@brightview.co.uk> 439 Bad From
(op.0046382642008...@10.10.121.172)
<sdGdncVpZMzhzXLX...@brightview.co.uk> 439 Bad From
(op.2437570428377...@10.10.71.192)
<296dnYf6C-sWzXLX...@brightview.co.uk> 439 Bad From
(op.7474675715797...@10.10.6.14)
<V7adnfvS_dgXzXLX...@brightview.co.uk> 439 Bad From
(op.4024897553037...@10.10.107.21)
<hcnjab$4th$1...@achot.icm.edu.pl> 439 Bad From (Paul <exa...@example.com>)
<sZ6dnZuafaMRzXLX...@brightview.co.uk> 439 Bad From
(op.8875887503094...@10.10.21.87)
<GqudnS3DBYcBzXLX...@brightview.co.uk> 439 Bad From
(op.1019546648389...@10.10.100.21)
<1IadncZiE40DzXLX...@brightview.co.uk> 439 Bad From
(op.6124938966403...@10.10.90.81)
<WPGdnfTz4pUAzXLX...@brightview.co.uk> 439 Bad From
(op.2366506330872...@10.10.34.153)
<w-udneMUdri8zHLX...@brightview.co.uk> 439 Bad From
(op.5399817570803...@10.10.60.149)
<v6OdnVU89qK8zHLX...@brightview.co.uk> 439 Bad From
(op.1477621328551...@10.10.30.89)
<SNCdnQaXA7m_zHLX...@brightview.co.uk> 439 Bad From
(op.1522189438764...@10.10.13.196)
<Qsqdne7lJbexzHLX...@brightview.co.uk> 439 Bad From
(op.4580092026512...@10.10.92.111)
<e8ednbzmOqewzHLX...@brightview.co.uk> 439 Bad From
(op.2593607101547...@10.10.55.247)
<9cGdnap4SafgzHLX...@brightview.co.uk> 439 Bad From
(op.7234688501494...@10.10.113.236)
<R7ydnWJ2jJAVzHLX...@brightview.co.uk> 439 Bad From
(op.4430853231445...@10.10.4.58)
<Nb6dnccJv4PkzHLX...@brightview.co.uk> 439 Bad From
(op.6312579692270...@10.10.0.254)
<4aef4f4a$0$25097$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<slrnheuki...@satcidananda.hb.theunworthy.com> 439 Bad Reply-To
(in...@127.0.0.1)
<1ikue5ps8ig6lcm6r...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<op.u2sdfkoghswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<op.u2scpzfphswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<pakue5ps55lm8v8or...@4ax.com> 439 Bad From (Oren
<Or...@127.0.0.1>)
<4aef5001$0$23656$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<4aef52d5$0$1093$4faf...@reader3.news.tin.it> 439 Bad From (sys-key
<""nunceprov\"\"@@capito?.it">)
<bf878c3a-823c-4cb0...@d5g2000yqm.googlegroups.com> 439 Bad
>From ("P@lp@tine02" <padaw...@hotmail.com>)
<4aef508f$0$25130$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<4aef542e$0$55442$dbd4...@news.wanadoo.nl> 439 Bad From (Marcel
<mar...@marcel.123>)
<-dydnZJnCeezyXLX...@insightbb.com> 439 Bad From (monkeys paw
<us...@example.net>)
<4aef5172$0$25130$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<jvkue5533s3v2et1a...@4ax.com> 439 Bad From (Oren
<Or...@127.0.0.1>)
<4aef521d$0$25133$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<4aef523d$0$25166$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<hcnkff$61n$1...@achot.icm.edu.pl> 439 Bad From (Paul <exa...@example.com>)
<2zIHm.134176$Gs.5...@en-nntp-01.dc1.easynews.com> 439 Bad From (CF
<C...@example.invalid>)
<4aef5302$0$25342$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<slrnheulf...@satcidananda.hb.theunworthy.com> 439 Bad From (idd
<i...@127.0.0.1>)
<7blue5lln3iqoekdj...@4ax.com> 439 Bad From (Simon C.
<Si...@simon.com.>)
<96f93d06-cb3d-4f69...@k17g2000yqb.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<d4CdnT5LeMWmy3LX...@brightview.co.uk> 439 Bad From
(op.8757227932794...@10.10.111.45)
<rrmdndF7tvumy3LX...@brightview.co.uk> 439 Bad From
(op.5518589287317...@10.10.91.58)
<4aef537c$0$25342$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<f8841b8b-b2db-48ee...@v25g2000yqk.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<5mlue5t50kl2c8hmh...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<hcnlf0$vtr$1...@news.mixmin.net> 439 Bad Reply-To (an...@domain.invalid)
<4aef5946$0$985$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luz@o...@ange.fr (Otez le 1er et le dernier @).invalid>)
<4aef5964$0$946$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luz@o...@ange.fr (Otez le 1er et le dernier @).invalid>)
<4aef59c5$0$966$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luz@o...@ange.fr (Otez le 1er et le dernier @).invalid>)
<4aef59ee$0$966$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luz@o...@ange.fr (Otez le 1er et le dernier @).invalid>)
<861f406c-3669-4509...@s31g2000yqs.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<4aef57a4$0$25133$bf49...@news.tele2.nl> 439 Bad From ("Manokwari62"
<manok62@@gmail@@com>)
<4aef5a6a$1...@news.home.net.pl> 439 Bad From ("dziobak"
<dziobak-usun@hot..pl>)
<4aef5b62$0$923$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luz@o...@ange.fr (Otez le 1er et le dernier @).invalid>)
<dljue5techsn97b6k...@4ax.com> 439 Bad Reply-To (H@..)
<limue5h48qjg14bs9...@4ax.com> 439 Bad From (Hugo Nebula
<abuse@localhost>)
<slrnheun1q...@aces.localdomain> 439 Bad From (Harold Stevens
<woo...@aces.localdomain>)
<75cb0a9bbb84ccd8...@aracari.127.0.0.1> 439 Bad From
(hummingbird <hummingb�r...@127.0.0.1>)
<09926032-9977-403c...@a31g2000yqn.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<4aef5cb3$0$958$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luz@o...@ange.fr (Otez le 1er et le dernier @).invalid>)
<komue55u5qs8lk0f9...@4ax.com> 439 Bad Reply-To (H@..)
<e4nue5173c506d1cr...@4ax.com> 439 Bad Reply-To (H@..)
<slrnheun7r...@aces.localdomain> 439 Bad From (Harold Stevens
<woo...@aces.localdomain>)
<L--dnZWzm5iIwHLX...@scnresearch.com> 439 Bad From ("pandora"
<pan...@peak.org>)
<Xns9CB7E3658644...@69.16.176.253> 439 Bad From (Periander
<ulm@.4rubbish.britwar.co.uk>)
<1rlue55147513cvae...@4ax.com> 439 Bad Reply-To
(jack.dom...@gmail.invalid)
<r6nue5pk7khtakjmo...@4ax.com> 439 Bad Reply-To (H@..)
<QPqdnVNH_ro6wHLX...@brightview.co.uk> 439 Bad From
(op.1172836659669...@10.10.6.24)
<W7qdnR_49-9MwHLX...@scnresearch.com> 439 Bad From ("pandora"
<pan...@peak.org>)
<e5GdnRmZwIvgw3LX...@giganews.com> 439 Bad From (P4nd1-P4nd4
<P4nd1-P4nd4@.net>)
<58JHm.120301$Jp1....@en-nntp-02.dc1.easynews.com> 439 Bad From (CF
<C...@example.invalid>)
<Xns9CB794565C3...@188.40.43.213> 439 Bad From
("briant...@gmail.com" <briant...@localhost.localdomain>)
<4aef5eea$0$83249$e4fe...@news.xs4all.nl> 439 Bad Reply-To
(nobody@localhost.)
<4aef5f06$0$5017$607e...@cv.net> 439 Bad From ("BigArtie" <XXX@.com>)
<slrnheunqi...@aces.localdomain> 439 Bad From (Harold Stevens
<woo...@aces.localdomain>)
<45e7e892-77ec-4468...@r24g2000yqd.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<op.u2sg7xqshswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<4aef6048$0$915$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luz@o...@ange.fr (Otez le 1er et le dernier @).invalid>)
<Xns9CB795BB9D3...@188.40.43.213> 439 Bad From
("briant...@gmail.com" <briant...@localhost.localdomain>)
<slrnheuo3n.11...@satcidananda.hb.theunworthy.com> 439 Bad From
(fluffybunnie <fluffy...@127.0.0.1>)
<n0oue5p6k86hma90i...@4ax.com> 439 Bad From (dave
<da...@127.0.0.1>)
<7rmdnds2bNIz_XLX...@brightview.co.uk> 439 Bad From
(op.7486149896641...@10.10.113.132)
<bNOdnbfta9My_XLX...@brightview.co.uk> 439 Bad From
(op.3962358013346...@10.10.99.53)
<9LCdnQTJDMpo_XLX...@brightview.co.uk> 439 Bad From
(op.6269987452355...@10.10.33.130)
<K92dnX_DqOFp_XLX...@brightview.co.uk> 439 Bad From
(op.1928242973185...@10.10.51.75)
<FIGdnRYUPo5v_XLX...@brightview.co.uk> 439 Bad From
(op.3955637605927...@10.10.25.238)
<7l95o7F...@mid.individual.net> 439 Bad From (Lars-Erik �sterud
<.@.>)
<43fef9f2-582c-4c4d...@g23g2000yqh.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<77mdnbhZ8MSj_HLX...@brightview.co.uk> 439 Bad From
(op.3633551533104...@10.10.66.100)
<Xns9CB79649D69...@188.40.43.213> 439 Bad From
("briant...@gmail.com" <briant...@localhost.localdomain>)
<t5lue5lhm5sqcnt9f...@4ax.com> 439 Bad Reply-To (me/2
<nu...@127.0.0.1>)
<7l95sfF...@mid.individual.net> 439 Bad From (Lars-Erik �sterud
<.@.>)
<4aef61a3$0$898$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luz@o...@ange.fr (Otez le 1er et le dernier @).invalid>)
<4aef...@extreme.x-privat.org> 439 Bad Reply-To
(gru...@willygroup.org.invalid)
<2c70e5db-d879-47ff...@k17g2000yqh.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<MmJHm.9$b_...@newsfe13.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<4aef622b$0$961$ba4a...@news.orange.fr> 439 Bad From ("CoatluZ"
<Coat@luz@o...@ange.fr (Otez le 1er et le dernier @).invalid>)
<unJHm.10$b_...@newsfe13.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<ZOudnZ_OB9oN_3LX...@scnresearch.com> 439 Bad From ("pandora"
<pan...@peak.org>)
<h9oue51u5q67n73rt...@4ax.com> 439 Bad From (jake
<ja...@127.0.0.1>)
<v6KdnYIIIOx6_3LX...@earthlink.com> 439 Bad Reply-To
("Newsgroup only please, address is no longer replyable."
<b...@example.invalid>)
<uioue5lu83do83d10...@4ax.com> 439 Bad Reply-To (me/2
<nu...@127.0.0.1>)
<4aef6355$0$1415$4faf...@reader4.news.tin.it> 439 Bad From ("rawmode"
<@>)
<op.u2sh5pz8hswpfo@dell3100> 439 Bad From ("Esra Sdrawkcab"
<ad...@127.0.0.1>)
<hcnobv$mct$1...@news.eternal-september.org> 439 Bad Reply-To
(eucl...@Mlive.invalid)
<hcnodn$mct$2...@news.eternal-september.org> 439 Bad Reply-To
(eucl...@Mlive.invalid)
<hcnofk$mct$3...@news.eternal-september.org> 439 Bad Reply-To
(eucl...@Mlive.invalid)
<lAJHm.135320$Gs.9...@en-nntp-01.dc1.easynews.com> 439 Bad From (CF
<C...@example.invalid>)
<4aef667f$0$1421$4faf...@reader4.news.tin.it> 439 Bad From ("rawmode"
<@>)
<faq-ip.txt.tmp-faq-1257203402$16...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<faq-ippds.txt.tmp-faq-1257203402$16...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<faq-ivd2.txt.tmp-faq-1257203461$16...@jazzmans.swingbox> 439 Bad From
(FAQposter <ro...@127.0.0.1>)
<9rpue5trtso9kajnu...@4ax.com> 439 Bad From (Andr�
<itgehton.de@>)
<OLJHm.118$sY5...@newsfe17.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<QMJHm.119$sY5...@newsfe17.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<e1f1c9d2-b2c1-4b3e...@g31g2000vbr.googlegroups.com> 439
Bad From ("@Cookie@" <cookie...@gmail.com>)
<hcnpbp$11e$1...@news.eternal-september.org> 439 Bad Reply-To
(SF...@Alumni.cmu.edu.invalid)
<7$$i2rX7g...@parkhead.demon.co.uk> 439 Bad Reply-To
(look...@nospam.invalid)
<hcnplp$2hm$1...@news.eternal-september.org> 439 Bad From
(James@Russell@Brownwood.Gmail@com (James))
<Xns9CB7EE00D4F6...@69.16.176.253> 439 Bad From (Chris Wilson
<ulm@.4rubbish.britwar.co.uk>)
<Xns9CB7EE6C0F50...@69.16.176.253> 439 Bad From (Periander
<ulm@.4rubbish.britwar.co.uk>)
<wWJHm.5478$v47...@newsfe23.iad> 439 Bad Reply-To ("Josepi"
<Complaints-to: ab...@giganews.uk.>)
<XXJHm.4852$Mg....@newsfe01.iad> 439 Bad Reply-To ("Josepi"
<Complaints-to: ab...@giganews.uk.>)
<4aef6b8d$1...@news.home.net.pl> 439 Bad Reply-To
(ad...@anty.spamowy.com.invalid)
<c7que5hqne4tieece...@4ax.com> 439 Bad From (your friend
<dev....@example.com>)
<G%JHm.392$wq5...@newsfe19.iad> 439 Bad Reply-To ("Josepi"
<Complaints-to: ab...@giganews.uk.>)
<x2KHm.6$XH...@newsfe22.iad> 439 Bad Reply-To ("Josepi" <Complaints-to:
ab...@giganews.uk.>)
<f6bf4d1f-5458-4c30...@l13g2000yqb.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<p5KHm.62$oo...@newsfe20.iad> 439 Bad From (Wanna-Be Sys Admin
<sysa...@example.com>)
<90281852-2c9c-4d74...@s31g2000yqs.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<o6KHm.444$a25...@newsfe03.iad> 439 Bad From (Poetic Justice
<PoeticJustice@talk-n-dog...com>)
<Xns9CB7E8C1337...@69.16.176.253> 439 Bad From (Periander
<ulm@.4rubbish.britwar.co.uk>)
<c8sue514s2tc3i48q...@4ax.com> 439 Bad Reply-To (H@..)
<crsue5p1otj0ie2jd...@4ax.com> 439 Bad From (jake
<ja...@127.0.0.1>)
<f1tue5do9arc9qrqn...@4ax.com> 439 Bad From (jake
<ja...@127.0.0.1>)
<b3tue5tbv6mt5hu5v...@4ax.com> 439 Bad From (Andy <1@2.3>)
<0c15177c-c8ae-40d1...@r24g2000yqd.googlegroups.com> 439
Bad From ("P@lp@tine02" <padaw...@hotmail.com>)
<mbtue5t1b9vl8cbpg...@4ax.com> 439 Bad From (jake
<ja...@127.0.0.1>)
<qasue5llu5tsttp29...@4ax.com> 439 Bad Reply-To (H@..)
<vdtue55o9li4rr7vh...@4ax.com> 439 Bad Reply-To (H@..)
<tftue5lmdiq0a3eqf...@4ax.com> 439 Bad Reply-To (H@..)
<hcnsr1$2e8$1...@news.eternal-september.org> 439 Bad From (" johnny@."
<joh...@invalid.invalid>)
<khtue51uebv8jfhc8...@4ax.com> 439 Bad From (jake
<ja...@127.0.0.1>)
<Xns9CB7C5202...@216.168.3.70> 439 Bad From (Red Green
<postm...@127.0.0.1>)
<eezuiegu8gjo.17sh0lrl5pn4j$.d...@40tude.net> 439 Bad From (fredg
<fgut...@example.invalid>)
<emBjiL3x...@zen50073.zen.co.uk> 439 Bad From (Paul Harris
<nos...@127.0.0.1>)
<r1uue5t9cb9idpi8m...@4ax.com> 439 Bad From (jake
<ja...@127.0.0.1>)
<4aef791d$1...@news.home.net.pl> 439 Bad Reply-To
(ad...@anty.spamowy.com.invalid)
<thtue5d6mbe1bg75u...@4ax.com> 439 Bad Reply-To (H@..)
<p8uue51gut7srsdac...@4ax.com> 439 Bad Reply-To (H@..)
<hcntjs$31e$1...@h1.uw.edu.pl> 439 Bad Sender (les...@90.153.90.202)
<hcnto4$9n3$1...@news.eternal-september.org> 439 Bad Reply-To ("Nunya
Bidnits" <inv...@invalid.invalid>)
<hcntoh$9pa$1...@news.eternal-september.org> 439 Bad From (" johnny@."
<joh...@invalid.invalid>)
<hcntsj$i4v$1...@inews.gazeta.pl> 439 Bad From (Animka
<animka@to...nie.ja.wp.pl>)
<hcntsj$i4v$2...@inews.gazeta.pl> 439 Bad From (Animka
<animka@to...nie.ja.wp.pl>)
<hcnu3i$ij5$1...@inews.gazeta.pl> 439 Bad From (Animka
<animka@to...nie.ja.wp.pl>)
<hcnu57$crb$1...@news.eternal-september.org> 439 Bad Reply-To ("Nunya
Bidnits" <inv...@invalid.invalid>)
<hcnua3$ds9$1...@news.eternal-september.org> 439 Bad From (" johnny@."
<joh...@invalid.invalid>)
<t9mdnXeWK4sS4XLX...@bright.net> 439 Bad From (jim
<".sjedgingN0sp"@m...@mwt.net>)
<hcnubv$j8h$1...@inews.gazeta.pl> 439 Bad From (Animka
<animka@to...nie.ja.wp.pl>)
<v1vue51pqb9v4knno...@4ax.com> 439 Bad From (jake
<ja...@127.0.0.1>)
<3f56e62f-9f14-434b...@m38g2000yqd.googlegroups.com> 439
Bad From ("@Cookie@" <cookie...@gmail.com>)
<98vue5542nq9haedg...@4ax.com> 439 Bad From (jake
<ja...@127.0.0.1>)
<hcnu83$35f$1...@h1.uw.edu.pl> 439 Bad Sender (les...@90.153.90.202)
<Xns9CB7AADE9B3...@188.40.43.213> 439 Bad From
("briant...@gmail.com" <briant...@localhost.localdomain>)
<kmvue55rp7o1kjubj...@4ax.com> 439 Bad From (jake
<ja...@127.0.0.1>)
<hcnuur$il1$1...@news.eternal-september.org> 439 Bad From ("QN"
<hiding...@example.com>)
<Xns9CB7CB3B7455Aw...@188.40.43.213> 439 Bad From (William
Baldwin <wbal...@example.com>)
<Xns9CB7CB5AB...@216.168.3.70> 439 Bad From (Red Green
<postm...@127.0.0.1>)
<hcnvc9$m8e$1...@news.eternal-september.org> 439 Bad From ("QN"
<hiding...@example.com>)
<Pine.LNX.4.64.09...@dawn.a.b.c> 439 Bad From (Matt Giwer
<matt@localhost>)
<Pine.LNX.4.64.09...@dawn.a.b.c> 439 Bad From (Matt Giwer
<matt@localhost>)
<Pine.LNX.4.64.09...@dawn.a.b.c> 439 Bad From (Matt Giwer
<matt@localhost>)
<Xns9CB7AEB69D8...@188.40.43.213> 439 Bad From
("briant...@gmail.com" <briant...@localhost.localdomain>)
<Xns9CB7B050733...@188.40.43.213> 439 Bad From
("briant...@gmail.com" <briant...@localhost.localdomain>)
<aa1ve51o071q699be...@4ax.com> 439 Bad From (jake
<ja...@127.0.0.1>)
<4aef8589$0$1103$4faf...@reader1.news.tin.it> 439 Bad From ("rawmode"
<@>)
<iBLHm.44$XH1...@newsfe22.iad> 439 Bad Reply-To ("Josepi"
<X-Complaints-to: ab...@www.giganews.uk.>)
<hco1be$35c$1...@sunce.iskon.hr> 439 Bad From ("Leo"
<leo...kulcar@inet...hr>)
<_8WdnYlEvpG3FHLX...@earthlink.com> 439 Bad From ("CW"
<cmagers@earthlink...net>)
<mWLHm.5111$rs....@newsfe05.iad> 439 Bad Reply-To ("Josepi"
<X-Complaints-to: ab...@www.giganews.uk.>)
<hco1fv$rrt$1...@node1.news.atman.pl> 439 Bad From (Animka
<animka@to...nie.ja.wp.pl>)
<hco1fv$rrv$1...@node1.news.atman.pl> 439 Bad From (Animka
<animka@to...nie.ja.wp.pl>)
<hco1no$7fd$1...@node2.news.atman.pl> 439 Bad From (Animka
<animka@to...nie.ja.wp.pl>)
<hco214$av0$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<hco24e$bkf$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<hco2a0$crc$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<hco28...@news5.newsguy.com> 439 Bad From (deimos <deimos@localhost>)
<H4MHm.7153$3P2....@newsfe09.iad> 439 Bad Reply-To ("Josepi"
<X-Complaints-to: ab...@www.giganews.uk.>)
<hco2sk$hea$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<hco30s$if7$1...@news.eternal-september.org> 439 Bad From (" johnny@."
<joh...@invalid.invalid>)
<hco36a$jp6$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<Xns9CB7D77...@74.209.131.10> 439 Bad From ("." <...@....>)
<slrnheqveq....@xs7.xs4all.nl> 439 Bad From (Rob
<nom...@example.com>)
<hco3n2$nh9$1...@news.eternal-september.org> 439 Bad From (" johnny@."
<joh...@invalid.invalid>)
<hco3nc$nqu$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<hco4k7$uen$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<hco4ng$usr$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<trGdnYJFrM-GBXLX...@scnresearch.com> 439 Bad From ("pandora"
<pan...@peak.org>)
<hco578$188$1...@news.eternal-september.org> 439 Bad From (" johnny@."
<joh...@invalid.invalid>)
<hco5fv$gs$1...@aioe.org> 439 Bad From (user1 <us...@example.net>)
<hco5jk$59i$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<hco5sm$76d$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<hco633$8dt$1...@news.eternal-september.org> 439 Bad From (" johnny@."
<joh...@invalid.invalid>)
<hco6cd$ap2$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<hco6j0$brh$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<vb7ve597io6iqm34m...@4ax.com> 439 Bad Reply-To (Roedy Green
<see_w...@mindprod.com.invalid>)
<8l7ve5h75dpnqogl9...@4ax.com> 439 Bad From (Andy <1@2.3>)
<bs7ve59gd4vnn4hnm...@4ax.com> 439 Bad Reply-To (Roedy Green
<see_w...@mindprod.com.invalid>)
<hco7gk$op0$1...@optima5.xanadu-bbs.net> 439 Bad From ("John F. Morse"
<jo...@example.invalid>)
<hco7qj$op0$2...@optima5.xanadu-bbs.net> 439 Bad From ("John F. Morse"
<jo...@example.invalid>)
<hco81f$op0$3...@optima5.xanadu-bbs.net> 439 Bad From ("John F. Morse"
<jo...@example.invalid>)
<hco844$op0$4...@optima5.xanadu-bbs.net> 439 Bad From ("John F. Morse"
<jo...@example.invalid>)
<hco856$mcm$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<hco872$op0$5...@optima5.xanadu-bbs.net> 439 Bad From ("John F. Morse"
<jo...@example.invalid>)
<hco8d2$nir$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<Hp6dnYpoqPpVOHLX...@giganews.com> 439 Bad From ("Eugene A.
Calame" <......@..........>)
<lf9ve5l7qc15c0dvm...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
<160fgcya59tar.z...@40tude.net> 439 Bad From (fredg
<fgut...@example.invalid>)
<hco8qq$qb7$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<hco925$rod$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<hco9ag$thu$1...@news.eternal-september.org> 439 Bad Reply-To ("@"
<inv...@invalid.invalid>)
<77ave552fa38ofqrf...@4ax.com> 439 Bad Reply-To
(ev...@theobvious.espphotography.com.invalid)
Frank Slootweg
[...]
> Obviously, there has been some abuse with "base64" encoding, else the issue
> would not have arisen.
AFAICT, that's an incorrect conclusion, because the examples with
Steve posted, were NOT "abuse with "base64" encoding". They were *spam*,
and they 'happened' to use base64 encoding for the reasons Xavier
explained (i.e. a charset which has mainly 8-bit characters). So the
abuse is spam. Since spam is not the topic of this thread, the examples
are not abuse in this context.
Steve said that he's now checking for real abuse (of base64 encoding),
so let's wait for those results.
Julien ÉLIE
> <ZOudnZ_OB9oN_3LX...@scnresearch.com>
> 439 Bad From ("pandora" <pan...@peak.org>)
Isn't it a valid From: header?
name-addr = [display-name] angle-addr
angle-addr = [CFWS] "<" addr-spec ">" [CFWS] /
obs-angle-addr
display-name = phrase
phrase = 1*word / obs-phrase
word = atom / quoted-string
quoted-string = [CFWS]
DQUOTE *([FWS] qcontent) [FWS] DQUOTE
[CFWS]
qcontent = qtext / quoted-pair
qtext = %d33 / ; Printable US-ASCII
%d35-91 / ; characters not including
%d93-126 / ; "\" or the quote character
obs-qtext
DQUOTE = %x22
Having glanced at your list of rejects, I see that you're dropping
tons of legitimate articles.
--
Julien �LIE
<< La diff�rence entre un chanteur et une paire de chaussures est que le chanteur
doit partir avant de lasser. La paire de chaussures, il vaut mieux les lacer
avant de partir. >> (Philippe Geluck)
Steve Crook
Message-Id: <7laq2oF...@mid.individual.net>:
> Steve said that he's now checking for real abuse (of base64 encoding),
> so let's wait for those results.
Hi Frank,
Having implemented base64 decoding in Cleanfeed and subsequently logged
messages for a few days I'll make a couple of cautious observations.
As expected there is a fair volume of spam that's base64 encoded. In
most instances the encoding is used simply because the content is 8bit.
There are a few instances where base64 appears to have been used to
obfuscate the content, probably to circumvent filtering but it's
currently low level.
In the brief period of logging, there are about 500 posts per day being
rejected as spam as a result of the decoding functionality. This
doesn't take into account the volume being rejected by EMP type filters
which previously ignored base64 encoded content, (or rather considered it
to be binary). As I only debugged the EMP code today, it's too soon to
provide decent figures but in the last 4 hours there have been 358 EMP
rejects with Content-Transfer-Encoding: base64 headers.
I'll provide more feedback over the next couple of days as I get
Cleanfeed better adjusted to handle the decoded content.
D. Stussy
news:7lb93cF...@mid.individual.net...
> Hi D. Stussy,
>
> > <ZOudnZ_OB9oN_3LX...@scnresearch.com>
> > 439 Bad From ("pandora" <pan...@peak.org>)
>
> Isn't it a valid From: header?
So, I missed one of the "few specifically blocked troll user" entries. I
tried to remove them from the list I posted.
I take it that you have found that the rest are in fact invalid.
> Having glanced at your list of rejects, I see that you're dropping
> tons of legitimate articles.
Sorry, I disagree. Syntactically invalid mailboxes in headers do not
constitute legitimate articles.
This affects only about 1% of all text-only traffic; about 1,100 articles
per day on the average. As I don't handle binaries, I cannot compute what
would be affected with them.
Here's what I checking them with:
^@
@\.
@[^(, ]*\.\.
@[[:alnum:]]*@
@(.+\.)?test>?$
@.+\.phx\.gbl>?$
@(.+\.)?[0-9]*>?$
@(.+\.)?localhost>?$
@(.+\.)?localdomain>?$
@(.+\.)?example(\.[a-z]{3,})?>?$
Plus 22 other patterns which kill trolls' articles. Any match to any
pattern causes a rejection. The third pattern does contain a space between
the brackets after the comma. Note that pattern #5 matches where "@" is
the last character (i.e. no domain part). Pattern #6 kills Microsoft's
abuse of an illegimate gTLD.
For the "Reply-To" header, this additional pattern is used:
@(.+\.)?invalid>?$
Julien ÉLIE
>> 439 Bad From ("pandora" <pan...@peak.org>)
>>
>> Isn't it a valid From: header?
>
> So, I missed one of the "few specifically blocked troll user" entries. I
> tried to remove them from the list I posted.
OK, I understand.
> I take it that you have found that the rest are in fact invalid.
Not at all!
I only had a glance at a few lines of your 1000+ rejects.
>> Having glanced at your list of rejects, I see that you're dropping
>> tons of legitimate articles.
>
> Sorry, I disagree. Syntactically invalid mailboxes in headers do not
> constitute legitimate articles.
I for one do not think that "malformed headers" implies "illegitimate".
But well, that's your policy choice.
--
Julien �LIE
<< Le village c'est moi ! >> (Ast�rix)
D. Stussy
> >> Having glanced at your list of rejects, I see that you're dropping
> >> tons of legitimate articles.
> >
> > Sorry, I disagree. Syntactically invalid mailboxes in headers do not
> > constitute legitimate articles.
>
> I for one do not think that "malformed headers" implies "illegitimate".
> But well, that's your policy choice.
To me, malformed is illegitimate.
A legitimate message is one that is properly formed (among other
characteristics).
Peter J Ross
Frank Slootweg <th...@ddress.is.invalid> wrote:
You know me better than to suppose that I'd use ISO-8859-1, Frank.
Funny things happen on the way to moderated newsgroups, which aren't
necessarily under the control of the poster or the moderator. My UTF-8
seems to have been "improved".
Anyway, I consider the use of MIME to be a kind of encoding, but
that's because I'm using the word "encoding" less strictly than you.
Peter J Ross
Stussy <spam+ne...@bde-arc.ampr.org> wrote:
> "Xavier Roche" <xro...@free.fr.NOSPAM.invalid> wrote in message
> news:hcnaq5$7u1$2...@news.httrack.net...
>> D. Stussy a �crit :
>> > Just because it can be done does not mean it should be done.
>>
>> "Be strict when sending and tolerant when receiving" [ Filtering on
>> content-transfer-encoding is IMHO not very reliable and probably a bit
>> dangerous ]
>
> Being overly tolerant in what one receives opens one to spam and other
> malicious messages.
Tolerating messages that are a bit bigger than you'd like them to be
doesn't open you up to anything other than willingness to consider
that you might be wrong.
> I don't accept articles where the "From" header indicates a mailbox in the
> "example.com" domain, because RFC 2616 says such should NEVER appear on the
> live Internet; only in documentation examples.
Your server, your rules. Other server admins may decide that accepting
such articles will do less harm than rejecting them.
> I block roughly 1,000
> articles per day (less than 1% of all text-group volume by article count)
> based on stupidity such as this (and other syntax errors - like having two
> "@"'s in a mailbox designation). PS: ".invalid" is permitted there, but
> NOT in "Reply-To" which must be resolvable for article acceptance.
Again, your server, your rules.
But can you find a single example of a spammer using .invalid in
Reply-To? In return I'll give you a hundred examples of non-spammers
who use .invalid in Reply-To because they don't understand the RFCs as
well as you do. Their software invites them to provide a Reply-To
line, and so they do.
> Obviously, there has been some abuse with "base64" encoding, else the issue
> would not have arisen.
There's certainly been some such abuse, but there's an issue about
false positives. Given the examples you've given of what "your rules"
on "your server" are like, false positives evidently worry you less
than they worry some of us.
--
PJR :-)
news.admin.announce (a low-volume, moderated Usenet group)
Read and post announcements of interest to news administrators.
See <http://www.robomod.net/news.admin.announce/info.html>.
Peter J Ross
Stussy <spam+ne...@bde-arc.ampr.org> wrote:
> "Julien �LIE" <iul...@nom-de-mon-site.com.invalid> wrote in message
> news:7lb93cF...@mid.individual.net...
>> Hi D. Stussy,
>>
>> > <ZOudnZ_OB9oN_3LX...@scnresearch.com>
>> > 439 Bad From ("pandora" <pan...@peak.org>)
>>
>> Isn't it a valid From: header?
>
> So, I missed one of the "few specifically blocked troll user" entries. I
> tried to remove them from the list I posted.
My friend pandora will be amused to learn that you think she's a
"troll user".
It's "your server, your rules", but obvious defects in your rules make
it unlikely that other servers will adopt them.
IMO, you're doing good work, but you need to stop letting your
personal prejudices get in the way.
Frank Slootweg
> a 2LD under "com", "net", and "org" - and per ICANN contracts for the other
> gTLDs as a reserved word not to be assigned) should NEVER APPEAR on the
> live Internet, but exist only in documentation.
RFC 2606 says no such thing! It doesn't say "that "example" ...
should NEVER APPEAR on the live Internet, but exist only in
documentation" (or wording to that effect).
It only says "recommended" and "can be used as", nothing more, nothing
less.
If you think otherwise, then give a specific quote.
> Meanwhile, ".invalid" is
> meant to appear on the live Internet (and so is "localhost").
>
> ONLY the ".INVALID" TLD is permitted for munged addresses, and such is its
> only purpose for existing.
Again, no such thing as "ONLY" in RFC 2606.
> Here's today's bad list:
> - IP address literals need to be enclosed in brackets. Addresses not in
> brackets aren't valid.
> - The only "questionable" usage that I disallow is "@example.invalid" -
> should it follow the ".invalid" TLD or the "example" 2LD rule?
It's not "questionable" at all! Before ".invalid" there can be
*anything*, i.e. for example :-) "@shit.invalid". If "shit" is allowed,
then why not "example"?
> - In addition to "@@", I have also seen ".." and "@." which yield null
> domain elements.
> - Although not appearing in the RFC, ".localdomain" is another dummy TLD
> that is banned, as it appears in documentation and meant to be substituted
> with the live domain of a site.
>
> Before I removed the few specifically blocked troll users, the count of
> entries was 1,178 for the past 19.5 hours:
[...]
You say:
> Meanwhile, ".invalid" is meant to appear on the live Internet (and so
> is "localhost").
Then what is wrong with this one:
> <Pine.LNX.4.64.09...@dawn.a.b.c> 439 Bad From (Matt Giwer
> <matt@localhost>)
[Many more examples of "localhost".]
And what's wrong with this one:
> <hcmch1$817$2...@optima5.xanadu-bbs.net> 439 Bad From ("John F. Morse"
> <jo...@example.invalid>)
[Stopped after some 700 lines.
Frank Slootweg
> In news.admin.net-abuse.policy on Sat, 31 Oct 2009 16:35:42 -0400,
> Frank Slootweg <th...@ddress.is.invalid> wrote:
>
> > Peter J Ross <p...@example.invalid> wrote:
> > [...]
> >
> >> But some plain text *does* require encoding. How else can words like
> >> "co�rdination" and "clich�" be read as the author intended?
> >>
> >> QP and B64 are unsatisfactory encoding methods, but *some* encoding
> >> will be required until Unicode is universally adopted.
> >
> > Didn't you just invalidate your own statement? Your posting did not
> > use any *encoding*, but was perfectly OK, because it had:
> >
> >> Content-Type: text/plain; charset=iso-8859-1
> >
> > I.e. it used a *charset*, no encoding.
>
> You know me better than to suppose that I'd use ISO-8859-1, Frank.
> Funny things happen on the way to moderated newsgroups, which aren't
> necessarily under the control of the poster or the moderator. My UTF-8
> seems to have been "improved".
Did your UTF-8 use Base64 or QP encoding? If so, why?
> Anyway, I consider the use of MIME to be a kind of encoding, but
> that's because I'm using the word "encoding" less strictly than you.
That's not the point. As Xavier also mentioned, the term "encoding" is
indeed ambiguous, because *all* character sets, even ASCII, use
"encoding" (into 8-bits). But *character set* encoding is not the topic
of this thread. The topic is encoding of plain text *messages*,
specifically Base64 encoding, but implicitly also the QP encoding which
you mention.
Your example
> >> But some plain text *does* require encoding. How else can words like
> >> "co�rdination" and "clich�" be read as the author intended?
> >>
> >> QP and B64 are unsatisfactory encoding methods, but *some* encoding
> >> will be required until Unicode is universally adopted.
is wrong, because neither Base64 nor QP encoding are *required*.