Michael, Many thanks for your help.
I've double-checked the config, and yes I have a 'MyName' record with a FQDN using our own DNS. I've set the myHelo setting to 'use myName' and ensured I have hMailserver on a different hostname like you have, just to be sure all's basically the same as what you appear to be using. The only difference is that I have hMailserver on port 2525, but using the same IP. Unfortunately, I'm still getting the same result. Michael, can you kindly confirm you're definitely not getting the same as me if you send an email from your PC directly into ASSP v2?... Here are some example headers from another test done this morning - I've removed the line breaks to simplify the headers. As you can see, in ASSP v2 one set of 'Received' headers is missing. The above settings are the same for both ASSP v1 and v2. ASSP v1 ------- Return-Path: <t...@mipost.co.uk> Received: from inbound104.mstream.com ([77.36.34.151]) by inbound102.mstream.com with hMailServer ; Wed, 22 May 2013 10:09:00 +0100 Received: from MYPC ([77.36.34.43] helo= MYPC) by inbound104.mstream.com with ESMTP (ASSP 1.99); 22 May 2013 10:09:00 +0100 From: "test account" < <mailto:t...@mipost.co.uk> t...@mipost.co.uk> ASSP v2 ------- Return-Path: <t...@mipost.co.uk> Received: from inbound104.mstream.com ([77.36.34.151]) by inbound102.mstream.com with hMailServer ; Wed, 22 May 2013 10:15:12 +0100 From: "test account" < <mailto:t...@mipost.co.uk> t...@mipost.co.uk> Michael, if you're not seeing this, perhaps there's something else triggering this difference in the config, but I can't seem to find it. Would it be possible to get a sanitized copy of your config off-list to test? Thanks Nick -----Original Message----- From: Michael Thomas [mailto:m...@mathbox.net] Sent: 21 May 2013 20:52 To: For Users of ASSP Subject: Re: [Assp-user] Missing 'Received' headers in ASSP v2 Nick, In "Server Setup" section, do you have the "My Name (myName)" field set to your ASSP FQDN? And in "My Helo (myHelo)" field did you select "use myName"? > Our routing inbound is Internet >> ASSP >> hMailserver, then onto some I have same set up. No issue here. ASSP on port 25. ASSP My Name: mx01-scanner.domain.tld hMailserver on port 125. hMailserver FQDN: mx01.domain.tld Both ASSP and hmailserver write a received header. Michael Thomas Mathbox 978-687-3300 Toll Free: 1-877-MATHBOX (1-877-628-4269) On 5/21/2013 12:21 PM, Nick Marshall wrote: > Hello > > > > I published this query a couple of months ago and it's still plaguing > me - I wonder if anyone could help please. > > > > We moved from ASSP v1 to ASSP v2 a few months back, and have noticed a > difference in the way the 'Received' headers are written when using > 'Transparent' Helo mode. > > > > Both v1 and v2 are the very latest versions as of today. > > > > Our routing inbound is Internet >> ASSP >> hMailserver, then onto some > internally written indexing and archiving system to store the > messages, then into Exchange. In the past we've used the headers to > identify the Internet-based sending server - this information is > available in the second received header in the ASSP v1 example below. > This data is stored in our index for email trail purposes. > > > > When moving to ASSP v2, we noticed the second set of Received headers > was missing, and therefore we can't then get a fix on the sending server. > > > > Below are the headers from the .eml files out the back of hMailserver > from the same controlled test using both ASSP1 and ASSP2. As you'll > see there are one set of 'Received' headers missing in v2, and this > importantly is the 'Received' header containing the IP address of the > sending server (or PC in this test): > > > > ------- ASSP v1 ------- > > > > Return-Path: < <mailto:t...@mipost.co.uk> t...@mipost.co.uk> > > Received: from MYPC ([77.36.34.151]) > > by inbound104.mstream.com > > with hMailServer ; Thu, 21 Apr 2013 14:31:02 +0100 > > Received: from MYPC ([77.36.34.43] helo=MYPC) by > -------- MISSING IN ASSP V2 --------- > > Filter-Layer with ESMTP (ASSP 1.98); 18 Apr 2013 > > 14:31:02 +0100 > > From: "test account" < <mailto:t...@mipost.co.uk> t...@mipost.co.uk> > > To: < <mailto:t...@mipost.co.uk> t...@mipost.co.uk> > > Subject: test - ASSP v1 > > Date: Thu, 18 Apr 2013 14:31:02 +0100 > > Message-ID: < <mailto:002901ce3c38$f8b4d9c0$ea1e8d40$@mipost.co.uk> > 002901ce3c38$f8b4d9c0$ea1e8d40$@mipost.co.uk> > > MIME-Version: 1.0 > > Content-Type: multipart/alternative; > > > > ______________________________________________ > Giacom email security by www.messagestream.com > > > boundary="----=_NextPart_000_002A_01CE3C41.5A798FE0" > > X-Mailer: Microsoft Outlook 15.0 > > Thread-Index: Ac48OPLpmi5vZXPaS2OS4laGaN+UMw== > > Content-Language: en-gb > > > > > > ------- ASSP v2 ------- > > > > Return-Path: < <mailto:t...@mipost.co.uk> t...@mipost.co.uk> > > Received: from MYPC ([77.36.34.151]) > > by inbound104.mstream.com > > with hMailServer ; Thu, 18 Apr 2013 14:24:30 +0100 > > From: "test account" < <mailto:t...@mipost.co.uk> t...@mipost.co.uk> > > To: < <mailto:t...@mipost.co.uk> t...@mipost.co.uk> > > Subject: test - ASSPv2 > > Date: Thu, 18 Apr 2013 14:24:30 +0100 > > Message-ID: < <mailto:002001ce3c38$0f0a4710$2d1ed530$@mipost.co.uk> > 002001ce3c38$0f0a4710$2d1ed530$@mipost.co.uk> > > MIME-Version: 1.0 > > Content-Type: multipart/alternative; > > boundary="----=_NextPart_000_0021_01CE3C40.70CEFD30" > > X-Mailer: Microsoft Outlook 15.0 > > Thread-Index: Ac48OA5a+QSdOINXR9KJ6J/h/JaZ+A== > > Content-Language: en-gb > > > > ------ > > > > I know Perl reasonably well, and have been trying to understand where > the differences might be, but I'm at the end of my ability. I wondered > if anyone would kindly help identify if there's anything I can do to fix it. > > > > Many thanks > > Nick > > > > > > ---------------------------------------------------------------------- > -------- Try New Relic Now & We'll Send You this Cool Shirt New Relic > is the only SaaS-based application performance monitoring service that > delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! > http://p.sf.net/sfu/newrelic_d2d_may > _______________________________________________ > Assp-user mailing list > Assp-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-user > ---------------------------------------------------------------------------- -- Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
