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 <[email protected]> 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? ---------------------------------------------------------------------------- -- 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 ______________________________________________ Giacom email security by www.messagestream.com ------------------------------------------------------------------------------ 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
