<p>Thanks to everyone for the replies.</p><p>Joseph </p>

<p>Hi,</p><p>I'm sending emails using Outlook via Mercury.</p><p>The message-id is coming out as something looking like.... <003a01cac9e9$3406e330$9c14a990$@co.uk> i.e the domain part of the id is not complete. </p><p>Please could someone point me in the right direction as to what I need to set up to get the correct message-id.</p><p>I'm using mercury mail 4.72 and using the MercuryE SMTP client. </p><p>I believe  that this incorrect header could be why some of my outgoing email is ending up as spam.  </p><p>Many thanks.</p><p>Joseph. </p>

<p>It is the client (Outlook) that sets the Message-ID.</p><p>It is only there to provide a 'unique' ID for the message.</p><p>This will not be why some of your mail is marked as spam. </p><p>Most likely that some servers will not like direct SMTP delivery from your IP address. </p>

<blockquote><p>I'm using mercury mail 4.72 and using the MercuryE SMTP client. </p></blockquote><blockquote>I believe  that this incorrect header could be why some of my outgoing email is ending up as spam.  </blockquote><p>I doubt if this is enough to make your mail spam, but give us a copy of what you are sending from Outlook to MercuryS by providing a MercuryS session log.  Munge any passwords (even encrypted) in the file.</p><p> </p><p> </p>

<p>Thanks,</p><p>This is an extract of what I'm sending through... from the mercuryS session log... </p><p>It does look like the mangled ID is coming from Outlook  - slightly off topic I know, but why should it be doing that? </p><p class="MsoNormal">21:55:26.718: Connection from 87.194.109.106, Mon Mar 22 21:55:25 2010<lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.765: << 220 xxxx.co.uk ESMTP server ready.<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.796: >> EHLO MOTTYPC<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.843: << 250-xxxx.co.uk Hello MOTTYPC; ESMTPs are:<cr><lf>250-TIME<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.843: << 250-SIZE 0<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.843: << 250 HELP<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.843: >> MAIL FROM: <gassubs@xxxx.co.uk><cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.843: << 250 Sender OK - send RCPTs.<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.843: >> RCPT TO: <joseph@yyyyyyyyy.com><cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.875: << 250 Recipient OK - send RCPT or DATA.<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.875: >> DATA<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.875: << 354 OK, send data, end with CRLF.CRLF<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.953: >> From: "Gas Subs" <gassubs@xxxx.co.uk><cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.953: >> To: <joseph@yyyyy.com><cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.953: >> Subject: FW: TEST Gas and Electricity Prices<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.953: >> Date: Mon, 22 Mar 2010 21:55:25 -0000<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.953: >> Message-ID: <000001caca0a$61261590$237240b0$@co.uk><cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.953: >> MIME-Version: 1.0<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.984: >> Content-Type: multipart/alternative;<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.984: >>               boundary="----=_NextPart_000_0001_01CACA0A.61261590"<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.984: >> X-Mailer: Microsoft Office Outlook 12.0<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.984: >> Thread-Index: AcrJ4EcVOEUj2ue4Siy05rd4vBwHmQAAFHFwAAAIwNAACmdNkA==<cr><lf><o:p></o:p></p> <p class="MsoNormal">21:55:26.984: >> Content-Language: en-gb<cr><lf><o:p></o:p></p> 21:55:26.984: >> <cr><lf><p> </p><p> </p><p> </p>

<p>> It does look like the mangled ID is coming from Outlook  - slightly off topic I know, but why should it be doing that? I have no idea since I only use Lookout in testing.  That said there is nothing that really says what the message ID should look like except that each message ID must be unique to that message. Here's the message ID I get with Outlook 2002 Message-id:    <C81CD428A30D45D89B8F34624BA78A46@DellD8MBDT91></p><p>The domain used here is just the machine name.  This is certainly a unique message ID since the Dell machine name is unique. </p><p> </p>

<p>Probably because it is coded for americans so is expecting yourdomain.com not yourdomain.co.uk, hence you only get the co.uk suffix.</p><p>As previously stated the message-id should be irrelevant for delivery purposes. </p>

<blockquote><p>Probably because it is coded for americans so is expecting yourdomain.com not yourdomain.co.uk, hence you only get the co.uk suffix.</p></blockquote><p>In my case it appears to be picking up what I have entered for "Full computer name" </p><blockquote>As previously stated the message-id should be irrelevant for delivery purposes. </blockquote>Agreed, not material to a spam/not spam decision.   There are simply too many ways the valid unique Message-Id: can be generated to make this at all useful for spam detection.