Re: [exim] no message ID - newsgroup posting problem

Pàgina inicial
Delete this message
Reply to this message
Autor: Matthew Byng-Maddick
Data:  
A: Exim Users List
Assumpte: Re: [exim] no message ID - newsgroup posting problem
On Fri, Sep 16, 2005 at 01:25:39PM -0700, John W. Baxter wrote:
> On 9/16/05 2:54 AM, "John Burnham" <john.burnham@???> wrote:
> > On 15/09/05, Jamie Nudds <jamie.nudds@???> wrote:
>>> I have exim 4.50 server that posts emails to a newsgroup server (innd) via
>>> mailpost. However when Outlook users email to the newsgroup it is rejected
>>> with the reason "no Message-ID: found". I can't see any option in the
>>> innd conf files to stop this.
>> Well, you could always get Exim to add message-ids to those messages
>> without them - stick something like

[...]
> Which in turn is part of what
>    control = submission
> does (it also supplies missing From: and Date: headers which are the two
> required headers).

[...]
> Message-Id: (per RFC2822) is optional but SHOULD be present. I guess that
> is "less optional" than the just plain "optional" headers are. Fortunately,
> almost every message we see in our corner of the world does have a
> Message-Id: header. (Unfortunately, some we generate ourselves don't
> (yet).)


Message-ID is used by NNTP to de-dupe in propagation, it is therefore a
required part of NNTP. It would have been useful in mail-to-news and for
other reasons if they'd made it a required part of the standard for mail
transfer too, but they didn't, so we have to live with it. It is also
used by netnews in the References: header to generate the thread tree.

In the case of this mail-to-news gateway, I'd say it should be adding
message-id headers for the things it's going to mail-to-news where they
don't already exist. This does cause you problems with threading and
references, but...

Hope this clears some things up - you shouldn't be looking to turn off
messageid processing in inn.

Cheers

MBM

-- 
Matthew Byng-Maddick          <mbm@???>           http://colondot.net/
                      (Please use this address to reply)