Hi!
F.B.> Looks like the message did not go through ASSP.
N.M.> The message definitely did go through ASSP
N.M.> - it's in a very controlled test environment I'm using...
1.1)
Install archive Plugin ASSP_ARC.pm ,
turn on archiving:
DoASSP_ARC:=1
1.2)
Look in folder
ASSP_ARCinPATH
-- .eml[s] exists?
Headers is Ok ?
N.M.> Every email passing through ASSP v2 is like this,
N.M.> missing the headers connecting to the server before ASSP.
Send examples to me
"headers connecting to the server" -- what are mean?
N.M.> Can anyone else kindly help?
Look on:
==
X-Assp-Version: 2.XXX.XXXX(XXXXXXXXXX) on ASSP.nospam
==
==
Received: from mailserver.turnkeycolo.com ([ 192.999.999.999]) by ZZZZZZZZZZZZ
with ZZZZZZZZZZZZZZZZZZZZZZ;
Mon, 30 Jul 2012 21:11:59 +0300
Received: from mailserver.turnkeycolo.com ([64.128.191.115]
helo=mailserver.turnkeycolo.com)
by ASSP.nospam with ESMTP (2.1.2); 30 Jul 2012 21:11:58 +0300
==
-- all as need
{
==
Received: from ZZZZZZZZZZZZZZZZZZZZZZ by ZZZZZZZZ ZZZZZZZZZZZZZ ZZZZZZZZZZZZZZZ;
Mon, 30 Jul 2012 21:12:01 +0300
Received: from mailserver.turnkeycolo.com ([ 192.999.999.999]) by ZZZZZZZZZZZZ
with ZZZZZZZZZZZZZZZZZZZZZZ;
Mon, 30 Jul 2012 21:11:59 +0300
Received: from mailserver.turnkeycolo.com ([64.128.191.115]
helo=mailserver.turnkeycolo.com)
by ASSP.nospam with ESMTP (2.1.2); 30 Jul 2012 21:11:58 +0300
Received: (qmail 15558 invoked from network); 30 Jul 2012 18:05:16 -0000
Received: from unknown (HELO miqxslqf.com) ([email protected]@89.96.63.62)
by with SMTP; Mon, 30 Jul 2012 14:05:16 -0400
Message-ID: <[email protected]>
From: "Aleksey Grachev" <[email protected]>
To: <[email protected]>
Subject: [SPAM] [X_Assp_Spam: YES] [MessageLimit][lowlimit] ZZZZZZZZZZZ
Date: Mon, 30 Jul 2012 20:00:23 +0200
X-Assp-Version: 2.XXX.XXXX(XXXXXXXXXX) on ASSP.nospam
X-Assp-Delay: delayed for 6m 39s; 30 Jul 2012 21:11:59 +0300
X-Assp-Received-SPF: none ip=64.128.191.115 [email protected]
helo=mailserver.turnkeycolo.com
X-Assp-Message-Score: 45 (Bayesian Probability: 1.00000)
X-Assp-IP-Score: 45 (Bayesian Probability: 1.00000)
X-Assp-Spam-Prob: 1.00000
X-Assp-Tag: MessageLimit
==
}
Best regards, Victor Miasnikov
Blog: http://vvm.blog.tut.by/
----- Original Message -----
From: "Nick Marshall"
To: "'For Users of ASSP'"
Sent: Wednesday, May 22, 2013 6:40 PM
Subject: Re: [Assp-user] Missing 'Received' headers in ASSP v2
> No problem.
>
> This is inbound SMTP traffic, not outbound - I'm just pointing my PC to ASSP
> to test.
>
> Can anyone else kindly help?
>
> Nick
>
----- Original Message -----
From: "Nick Marshall"
To: "'For Users of ASSP'"
Sent: Wednesday, May 22, 2013 5:17 PM
Subject: Re: [Assp-user] Missing 'Received' headers in ASSP v2
> Fritz
>
> Thanks for feedback.
>
> The message definitely did go through ASSP - it's in a very controlled test
> environment I'm using...
>
> Every email passing through ASSP v2 is like this, missing the headers
> connecting to the server before ASSP.
>
> Nick
>
> -----Original Message-----
> From: Fritz Borgstedt [mailto:[email protected]]
> Sent: 22 May 2013 11:01
> To: For Users of ASSP
> Subject: Re: [Assp-user] Missing 'Received' headers in ASSP v2
>
> For Users of ASSP schreibt:
>>ASSP v2
>>-------
>>Return-Path: <[email protected]>
>>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:[email protected]> [email protected]>
>
> Looks like the message did not go through ASSP.
> Are there other ASSP-headers?
>
> ----------------------------------------------------------------------------
> --
>> 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):
>>>
>>>
. . .
>>>
>>> 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user
