🚀 go-pugleaf

In article <D6DDu6.4C3@demon.co.uk> Dave Williams (dave@demon.net) wrote:

> My understanding is that x-nntp-posting-host is added with IHAVE - 
> NNTP-Posting-Host would be added for machines using POST anyway. Again,
> unless my grin on sanity is less than I'd suspected it might be.

Actually, I get X-Nntp-Posting-Host and I post with POST. You also got it
on your posting :-) I used to get NNTP-Posting-Host when Demon were
running the previous version of C-News, but it changed when they upgraded,
so I presume somebody decided to make C-News RFC compliant by making it an
X header.

Also, somebody demonstrated the other day how they could inject an article
onto Demon's server with no trace of where it really came from. I presume
they used IHAVE to do this.

> Not unless the maillist software is _very_ broken ; Sender headers are
> allowed for (specified?) in the appropriate RFC as a mechanism for actually
> validating the UID used when mail is transmitted.

But for mail, the 'Sender:' header should only be added by the originating
host (which is the customer, not Demon). For news, Demon is the originating
host (except for IHAVE), so they are allowed to (and indeed should) add it.

It's all irrelevant anyway, as Demon don't add 'Sender:' headers for
mail, only for news.

> It's optional, you're quite correct - however if you omit it then
> the NNTP server which you use will quite happily tack on a default; 
> is there any NNTP server software which doesn't add it?

The problem is that Demon's default is something like 'Demon Internet' which
can mislead those receiving it about the sender's status.

Tom

-- 
Tom Hughes (tom@compton.demon.co.uk)
5 Lampits, Hoddesdon, Herts EN11 8EH
... The truth is a virus.....