Re: Stopping Sporge tutorial using NewsProxy (where do we get nfilter.dat)?

de Me.Here 01/30/2008 04:50

[OK] Frank Slootweg wrote:
> [Intentional top-post.]
>
> Oops! I just saw that I mixed up two posters!
>
> I thought I was responding to "M.L." and that he had changed his bad
> habits (no attribution and abuse of the privacy.net domain), but I was
> responding to you, Me.Here <me.here@home_on_the.net>. I guess that both
> proves our point about the need for proper attribution and my sillyness
> (expecting someone to actually change his bad habits).
>
> So I take back my thanks to "M.L." and hope that my advice about
> ".invalid" is of use to you (Me.Here <me.here@home_on_the.net>) or/and
> someone else.
>
> A little earlier, I wrote:
>> Me.Here <me.here@home_on_the.net> wrote:
>>> [OK] Frank Slootweg wrote:
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>> Thanks! :-)
>>
>>>> I assume that you mean that that's a limitation of NewsProxy? I.e.
>>>> NewsProxy can't filter on headers for which the server doesn't offer
>>>> XHDR/XPAT/<other> support? (I use Hamster which can filter on any header
>>>> (or/and the body).)
>> [...]
>>> Frank, that doesn't make sense - no software can filter on headers they
>>> don't see or get offered from their newsserver. In short, it isn't a
>>> limitation with NewsProxy, it's a limitation imposed by the newsserver.
>> 'Q' has already responded to that part (use HEAD), so I don't have to.
>>
>> Leaves me to thank you for your change of 'address' in your From:
>> line!
>>
>> However another minor but important nit:
>>
>> While I haven't checked whether underscores in a domain name are at
>> all valid, the proper and standard (RFC 2606 "Reserved Top Level DNS
>> Names") way to indicate that a domain is fake is to add ".invalid" to
>> the end (see my From: line). I.e. ".invalid" is a *defined* Top Level
>> Domain Name, which is *guaranteed* to never exist. Using ".invalid" has
>> the added advantage that compliant mailers do not even *try* to send
>> mail to such non-addresses, because they *know* it's not a valid/working
>> e-mail address.
>>
>> So in short, it would be best if you would use something like
>> me.here@home_on_the.net.invalid, but *anything* ending in ".invalid" is
>> fine, so perhaps just the shorter me.here@home.invalid
>>
>> I hope this helps and thanks again.
>>
>> [...]

Yeah, I was scratching my head for a short while lol

Hmmm, interesting point. Might have to change my reply to addy to
something witty using .invalid as you suggested :-)

--
I filter all Google posts - sorry, too much spam