🚀 go-pugleaf

In article <19950401.224933.42@compton.demon.co.uk>,
Tom Hughes (tom@compton.demon.co.uk) wrote:
: 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.

It would make sense. Shock and horrors - C-News, RFC compliant? 

: 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.

That'll be how they did it, yes. 

: But for mail, the 'Sender:' header should only be added by the originating
: host (which is the customer, not Demon).

Indeed. 

: For news, Demon is the originating host (except for IHAVE), 
: so they are allowed to (and indeed should) add it.

Quite.

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

This is what was confusing me. I could've sworn that's what was being
complained about. My brain must be a bit wonky - it's hot, and I'm 
trying to persuade my mobile phone to work. All in all I'm confused :) 

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

It's always the same, really. We could do (perhaps) with borrowing
a page out of Nyx's book and adding an X-Disclaimer header to every
outgoing Demon-dialup posting, to make things clear.

--
-- Dave Williams
-- E-Mail: dave@demon.net -- Phone:  0181 371 1000
-- Disclaimer: These opinions are MINE, not those of Demon Internet Limited