V2 adds its own received header every time. And there is IMHO no way to 
skip this.


(3) Received: from myhost1 ([x.x.x.x])
          by myhost2 (Lotus Domino Release 8.5.3FP3 HF145)
          with SMTP id 2013040318393206-106 ;
          Wed, 3 Apr 2013 18:39:32 +0200 
(2) Received: from lists.sourceforge.net ([x.x.x.x])
                 by myhost1
                 ; Wed, 3 Apr 2013 18:39:30 +0200
(1) Received: from lists.sourceforge.net ([216.34.181.88] 
helo=lists.sourceforge.net)
                 by myhost1 with SMTPS(AES256-SHA) (2.2.2); 3 Apr 2013 
18:39:25 +0200


1 - ASSP
2 - hmailserver
3 - domino

Thomas





Von:    "Nick Marshall" <n...@mypost.co.uk>
An:     "'For Users of ASSP'" <assp-user@lists.sourceforge.net>, 
Datum:  03.04.2013 18:39
Betreff:        Re: [Assp-user] Antwort: Wrong IP address in myHelo 
transparent mode



Thanks for the reply.

OK, when we switch to using 'MyName' in 'myHelo' instead of using
transparent mode, the results are then different in ASSP v2 than in v1. 
See
below:

MULTITHREAD (V2):

Received: from inbound104.messagestream.com ([77.36.34.151])
                 by inbound104.ourserver.com
                 with hMailServer ; Wed, 3 Apr 2013 17:17:59 +0100


SINGLE THREAD (V1):

Received: from inbound104.messagestream.com ([77.36.34.151])
                 by inbound104.ourserver.com
                 with hMailServer ; Wed, 3 Apr 2013 17:24:21 +0100
Received: from mail27.wdc03.rsgsv.net ([205.201.131.27]
helo=mail27.wdc03.rsgsv.net)
                 by inbound104.ourserver.com with ESMTP (ASSP 1.98); 3 Apr 
2013
                 17:24:11 +0100


As you can see, in v1 we get an extra set of Received headers, which
represent the step between ASSP and the outside world - in v2, this step 
is
missing. This is consistent with all emails received.


N


-----Original Message-----
From: Thomas Eckardt [mailto:thomas.ecka...@thockar.com] 
Sent: 03 April 2013 16:19
To: For Users of ASSP
Subject: [Assp-user] Antwort: Wrong IP address in myHelo transparent mode

ASSP is a PROXY. So the MTA behind ASSP will every time see ASSP's 
outbound
IP as connected IP.

myHelo transparent mode: the helo will be transparent and will never match
the connected IP at the MTA

Thomas





Von:    "" <n...@mypost.co.uk>
An:     <assp-user@lists.sourceforge.net>, 
Datum:  03.04.2013 17:10
Betreff:        [Assp-user] Wrong IP address in myHelo transparent mode



Hi All,

 

We're just upgrading from v1 to v2 ASSP and we have a different behaviour
with the transparent mode of myHelo in the email headers of inbound mail. 

 

As you'll see from the typical headers below, the server connects from the
sending server to hMailserver behind ASSP correctly, however the IP 
address
listed here - 77.36.34.151 - is the IP address of the local machine, and 
not
the IP of the hostname 'incisivemedia.outbound.ed10.com'. This causes all
sorts of problems for us with some indexing systems we have further down 
the
line, so does anyone have any idea what's causing this, or a way of 
getting
round the problem - we need to use transparent mode and be able to see the
sending server, but the IP address must match the hostname.

 

---

 

Received: from incisivemedia.outbound.ed10.com ([77.36.34.151])

                by inbound104.ourserver.com

                with hMailServer ; Wed, 3 Apr 2013 15:05:01 +0100

 

---

 

Thanks for your help

 

N




______________________________________________
Giacom email security by www.messagestream.com

----------------------------------------------------------------------------
--
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire the most
talented Cisco Certified professionals. Visit the Employer Resources 
Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the 


individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known
virus in this email!
*******************************************************





------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************


------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to