SRS Header Rewrite Not Working Properly on Message Forwarding . . .
Problem reported by Bruce Barnes - April 8, 2015 at 9:32 AM
Submitted
According to the SRS header rewrite specification, when a message is forwarded from someone's account, and the MX server, in this case, SmarterMail 13.3.5561.17888, forwards the message, the message header should be REWRITTEN to show the NEW SENDING e-mail address.
 
This has become particularly important now that OUTLOOK.COM, YAHOO!, COMCAST, and even our own SmarterMail installation at ChicagoNetTech.com is enforcing DMARC and vetting every aspect of a message header in an effort to prevent unauthorized messages from being received by our respective MX servers.
 
Unfortunately, SRS header rewrite appears to be broken in the latest version of SmarterMail.  It's also broken in several previous minor and major versions as well.
 
I noticed this when working with several different clients with whom I was trying to setup spam housekeeping.  Admittedly, several of them were not checking incoming e-mail in any way, and, in at least one instance, the SmarterMail server had been so poorly configured by the hosting company that it was amazing that any mail was getting through whatsoever, but I digress.
 
We have properly enabled in SmarterMail
 
Enabling SRS in SmarterMail to Prevent SPF Fail on Forwarded E-Mail Messages
Enabling SRS in SmarterMail to Prevent SPF Fail on Forwarded E-Mail Messages
 
 
Per the SRS rewrite protocol, the return-path is to be preserved in the outgoing message.  
 
Here's a graphic to help illustrate the issue:
 
Forward WITHOUT SRS Forwarding Header Rewrite - will fail
Forward WITHOUT SRS Forwarding Header Rewrite - will fail
 
and here's a graphic with the SRS rewrite added - allowing the message to pass SPF when received at the new mailbox
 
Forward WITH SRS Forwarding Header Rewrite - will PASS
Forward WITH SRS Forwarding Header Rewrite - will PASS
 
To test this, I setup an account, TEST@CHICAGONETTECH.COM, which forwards to another account, so I can see the message header rewrite in action.  
 
According to the header shown below, there was NO SRS REWRITE:
 
Return-Path: bbarnes@chicagonettech.com 

Received: from reszmta-ch2-08v.sys.comcast.net (LHLO reszmta-ch2-08v.sys.comcast.net) (69.252.207.72) by resmail-ch2-329v.sys.comcast.net with LMTP; Wed, 8 Apr 2015 16:03:19 +0000 (UTC) 

Received: from resimta-ch2-13v.sys.comcast.net ([69.252.207.13]) by reszmta-ch2-08v.sys.comcast.net with comcast id DTou1q00A0Hsqf101U3K8E; Wed, 08 Apr 2015 16:03:19 +0000 

Received: from securemail.chicagonettech.com ([173.165.112.155]) by resimta-ch2-13v.sys.comcast.net with comcast id DU191q00A3MDP2501U19dq; Wed, 08 Apr 2015 16:01:09 +0000 

X-CAA-SPAM: 00000 

X-Authority-Analysis: v=2.1 cv=Q5Bc4uGa c=1 sm=1 tr=0 
    a=mPdxyGmiULMihcXJBqGhDw==:117 a=mPdxyGmiULMihcXJBqGhDw==:17 
    a=BvmIL-y6AAAA:8 a=C_IRinGWAAAA:8 a=GGcpBh7Jt_oA:10 a=oEzvXX9GNFgA:10 
    a=tS228Fp5AAAA:8 a=e9J7MTPGsLIA:10 a=DAwyPP_o2Byb1YXLmDAA:9 
    a=Zr7miEi8wWIA:10 a=cKsnjEOsciEA:10 a=2oeSqxxVzlsA:10 a=3j4BkbkPAAAA:8 
    a=jU4qhlNgAAAA:8 a=dLlGIdxEAAAA:8 a=1XWaLZrsAAAA:8
    a=STZmhPMTLkd5KhuouBMA:9 a=dOnhtoqqiL3_Y-V6:21 a=JdB8LfO07to-XmEx:21
    a=QEXdDO2ut3YA:10 a=r8Rnbmbiu_sA:10 a=sU3Ul_KeppsA:10 a=yGW8d-8WM1kA:10
    a=gA6IeH5FQcgA:10 a=NWVoK91CQyQA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8
    a=MRhXl2DJMnZU5BNz2RMA:9 a=Roc9qq-cKchXe6Iz:21 a=RCMycJvN6f3Gv-yx:21
    a=7nlW5L_vBE57OG1z:21 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10
    a=_KN1Omkaj_e7Zxuq31MA:9 a=ZVk8-NSrHBgA:10 

Authentication-Results: resimta-ch2-13v.sys.comcast.net; 
        dkim=pass header.d=chicagonettech.com header.b=W+lnkXmR 

X-SmarterMail-Authenticated-As: bbarnes@chicagonettech.com 

DomainKey-Signature: a=rsa-sha1; c=simple; q=dns; d=chicagonettech.com; s=secure; h=received:reply-  to:from:to:subject:date:organization:message-id :x-mailer:thread-index:content-language:mime-version:content-type; b=XRVgw00k2mFBiODU1nlkbBif5q22KP8Ok0vivn3lxgv36Jz1l82miuxvcTmIBzKhE y0a5yZWVmAVxtWL/X2ZfXDx4e+Km4K7EwHUKZr3/OHsGShM6hV8oIHtNE/TnjKef1 Fo9OS/ZBmy+7GL6O2h1QEyOQwNh4+v3+0uV4iluaJb1kkrzBno+dkk/BBpt3KikJc vtZxCSjLwIXkooiHnYKIEvicTZutoeVXRqnwjZhB4Z6nPRmIUd5r4+VGQhQJiz+Oz vknQ+rJL177iEjOILQYI+Vy7Rdh7aY5hANhhJArfK//8z5jEvM5d3ZwKkriEZU6+j rOhVw0NdOdE+zmAXA== 

DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=chicagonettech.com; s=secure; h=content-type:mime-version:content-language:thread-index:x-mailer :message-id:organization:date:subject:to:from:reply-to; bh=xNMz80ZIFA7KNg/KFHTihSdo8O1ZktbxX4r+/TcmR6M=; b=W+lnkXmRjdCRlF4YgGe02svz9rczhRNozp1Bo0AfcVOCadVHGUX8SWWUwB2MjvEDC DYB4I3OU6cL2GUvC3GMNztx8kkS8+31Z5FQJhxuCEG9DDg/qaCyc2DpjSapFJrpYu qmT6hyFyO6Z9inrkvwYJfq9ersJfKIuvLSITbqbZ6VbczgeDfq7ZfacHBOEaI2TcG S10ASTbIrbX2LsVem+fhy1aSQsWLchLEbZi7Knlc0wUHUGBlW6Nz2kz3oF2b3O9Py S8Q1MYqSoE4j37cC9OCKS80XgaxSJSR/B0NJOvtnEtv8SAeYDWsRLk1g0RZul0RNb 1z0ZxZD644kG1RE0w== 

Received: from MrsPeele (173-165-112-149-Illinois.hfc.comcastbusiness.net [173.165.112.149]) by securemail.chicagonettech.com with SMTP 
    (version=TLS\Tls 
    cipher=Aes256 bits=256); Wed, 8 Apr 2015 11:01:02 -0500 

Reply-To: <bbarnes@chicagonettech.com> 

From: "Bruce Barnes" <bbarnes@chicagonettech.com> 

To: "Test Account" <test@chicagonettech.com> 

Subject: SRS Forward Test 

Date: Wed, 8 Apr 2015 11:00:59 -0500 

Organization: ChicagoNetTech Inc 

Message-ID: <01e101d07215$34c96d40$9e5c47c0$@chicagonettech.com> 

X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdByFRrf+dSkghTeSiuqbrpVVrH78g== 

Content-Language: en-us 

MIME-Version: 1.0 

Content-Type: multipart/signed; 
    protocol="application/x-pkcs7-signature"; 
    micalg=2.16.840.1.101.3.4.2.1; 
    boundary="----=_NextPart_000_01DA_01D071EB.4B8DECB0"
 
Therein lies a major issue with our efforts to ensure proper delivery of messages which are forwarded by our hosted users.  
 
Because of new security protocols, now in effect, with outlook.com, YAHOO!, Comcast, and many other providers, including ourselves, forwarded messages are being REJECTED because they look like they have not been properly SMTP AUTHENTICATED, with the error similar to the one shown below:
 
Recipient address: junior@REDACTED.com
Reason: Server rejected MAIL FROM address.
Diagnostic code: smtp;550 Authentication is required for relay
Remote system: dns;mail.constructionloffredo.com (TCP|10.23.118.207|51704|162.144.76.230|25) (srv2.REDACTED.ca Wed, 08 Apr 2015 14:37:31 +0000 UTC)
 
Please resolve this issue ASAP - in the NEXT MINOR RELEASE, as, without working SRS, SmarterMail is almost useless.
 
Bruce Barnes
ChicagoNetTech Inc
brucecnt@comcast.net

Phonr: (773) 491-9019
Phone: (224) 444-0169

E-Mail and DNS Security Specialist
Network Security Specialist

Customer Service Portal: https://portal.chicagonettech.com
Website: https://www.ChicagoNetTech.com
Security Blog: http://networkbastion.blogspot.com/

Web and E-Mail Hosting, E-Mail Security and Consulting

17 Replies

Reply to Thread
1
Robert Emmett Replied
Employee Post
Thank you, Bruce, for bringing this to our attention.  I have added it to our bugs list for further evaluation.
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
1
Scarab Replied
I wonder if that is why SRS Rewrites done by Smartermail are not routed by Smartermail Gateways causing them to eventually bounce as undeliverable with the NDR bounce-back having no where to go, as this has been an issue since version 11 of Smartermail. This may have been broken for some time.
0
Bruce Barnes Replied
Sorry to have to ask about a timetable, but I have several banks asking for when a resolution will be available. Thanks.
Bruce Barnes
ChicagoNetTech Inc
brucecnt@comcast.net

Phonr: (773) 491-9019
Phone: (224) 444-0169

E-Mail and DNS Security Specialist
Network Security Specialist

Customer Service Portal: https://portal.chicagonettech.com
Website: https://www.ChicagoNetTech.com
Security Blog: http://networkbastion.blogspot.com/

Web and E-Mail Hosting, E-Mail Security and Consulting
0
Robert Emmett Replied
Employee Post
Bruce, we will expedite our evaluation. We will advise on an fix later today.
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Robert Emmett Replied
Employee Post
Bruce, we performed an internal test and it wrapped properly. If you are forwarding from a local account to a local account, it does not wrap it. It will only wrap on outgoing mail. Please check your delivery logs after forwarding the mail out. It should have the proper SRS header rewrite. Please advise on your findings.
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Robert Emmett Replied
Employee Post
Bruce, here is a snippet of our delivery logs after testing the SRS rewrite:
 
08:33:07 [54000] RSP: 220 mail.externalserver.com
08:33:07 [54000] CMD: EHLO MyPc.st.local
08:33:07 [54000] RSP: 250-mail.externalserver.com Hello [70.167.205.116]
08:33:07 [54000] RSP: 250-SIZE 31457280
08:33:07 [54000] RSP: 250-AUTH LOGIN CRAM-MD5
08:33:07 [54000] RSP: 250-STARTTLS
08:33:07 [54000] RSP: 250-8BITMIME
08:33:07 [54000] RSP: 250 OK
08:33:07 [54000] CMD: MAIL FROM:<SRS0=AXT4=EK=gmail.com=bgrosz@testdomain.com> SIZE=385
08:33:14 [54000] RSP: 250 OK <srs0=axt4=ek=gmail.com=bgrosz@testdomain.com> Sender ok
08:33:14 [54000] CMD: RCPT TO:<bgrosz@externaldomain.com>
08:33:14 [54000] RSP: 250 OK <bgrosz@externaldomain.com> Recipient ok
08:33:14 [54000] CMD: DATA
08:33:14 [54000] RSP: 354 Start mail input; end with <CRLF>.<CRLF>
08:33:14 [54000] RSP: 250 OK
08:33:14 [54000] CMD: QUIT
08:33:14 [54000] RSP: 221 Service closing transmission channel
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Bruce Barnes Replied

Thanks for the quick response, Robert.

I understand that the SmarterMail logs may not show the SRS Header rewrite data, they are not required to have that data, but that is not the point of the issue I brought before SmarterTools.

The issue is the fact that the SRS Header rewrite protocol, available via PDF, at: www.libsrs2.org/srs/srs.pdfclearly states that the re-written header must be inserted, by the SENDING MX server, into the HEADER of all messages which are FORWARDED from the e-mail address which receives the message.

Here is the official protocol specification from: www.libsrs2.org/srs/srs.pdf, an excerpt from which, describing the basis of SRS Header Rewriting, is included immediately below:

1. Introduction

This version of the document is contemporary with version 0.30 of Mail::SRS, and version 1.0.11 of libsrs2.

1.1 Overview

Sender Permitted From (SPF, http://spf.pobox.com/) is a mechanism for preventing sender
forgery in SMTP transactions, thus allowing domain owners control over who may send mail from their domain. 

The Sender Rewriting Scheme (SRS, http://www.anarres.org/projects/srs/,
http://spf.pobox.com/srs.html), is a mechanism for rewriting sender addresses when a mail is forwarded in such a way that mail forwarding continues to work in an SPF compliant world.

This document outlines the design of the SRS convention and explains some of the gaming behind it.

It also provides notes to implementers, and links to some useful resources.

1.2 Who does this affect?

SRS must be implemented by all mail servers which forward mail from a domain which does not designate the sender of that mail in its SPF record. 

- This includes:

 * Many servers which support forward files
 * Third party mail forwarders

- This does not include:

 * All mail user agents.
 * Most mailing list providers.
 * All simple send/receive-only mail servers which do no forwarding.
 * Company internal smarthosts which forward only outgoing mail from the company and
   are listed in the company's SPF record.

1.3 How is it implemented

A modification to the forwarding mechanism within the mail server will perform address rewriting whenever a mail is forwarded.  Patches are being made available with the Mail::SRS distribution for all major mail servers.

2 The SRS Mechanism

2.1 The Problem

SPF requires the client address to match the return path in a mail. This prevents clients from submitting mails with forged return paths. However, consider what happens when a mail goes over a forwarder.

Hop | Client id  | Recipient | Return path | SPF
 1  | source.com | alias@forward.com | user@source.com | Accept
 2  | forward.com | target@destination.com | user@source.com | Reject


2.2 The Reversable Scheme - THIS IS THE PROPER SOLUTION

destination.com will only accept mails with a return path matching the client-id. The client-id of the forwarded mail is forward.com, therefore the return path must also be via forward.com. Therefore, forward.com must rewrite the return path in such a way that it is an address at forward.com, yet mails to that address will still reach user@source.com. The simplest possible scheme is as follows:

Hop | Client id | Recipient | Return path
 1 | source.com | alias@forward.com | user@source.com 
 2 | forward.com | target@destination.com | user=source.com@forward.com 

The SPF response may be omitted from the table since it will always accept. 

Now when a bounce or reply mail is received by user=source.com@forward.com, forward.com will rewrite the destination address to user@source.com and forward it.
SOURCE OF ABOVE DOCUMENTATION: www.libsrs2.org/srs/srs.pdf
 
Back to the issue at hand:
 
As I understand the SRS Header rewrite specifications, per the PDF document referenced above, the header must be rewritten in all forwards, whether the original message:
  • is internal to internal, with the receiving account being an external account, or;
  • external to internal, with the receiving account being an external account, or;
  • internal to internal, with the receiving account being an internal account.

The requirement of the SRS Header rewrite being mandated on ALL forwarded MX transactions is to prevent non-deliveries caused by SPF mismatches.

In the case of the originally submitted problem, the transaction was INTERNAL to INTERNAL, with the forward being to an  EXTERNAL e-mail address, IE:

the test documentation I provided was from a ChicagoNetTech to ChicagoNetTech, IE:

 
In the test results which are shown below, I am sending:
 
 
and here are the results - again, from an EXTERNAL account to a SmarterMail account, forwarded to an EXTERNAL ACCOUNT.
 
Once again, the FORWARDING ADDRESS was NOT inserted as the SENDING ADDRESS during the SRS HEADER REWRITE process:
----------------- START HEADER ------------------
Return-Path: srs0=d28f=ek=gmail.com=chicagonettech@chicagonettech.com

Received: from reszmta-ch2-05v.sys.comcast.net (LHLO
 reszmta-ch2-05v.sys.comcast.net) (69.252.207.69) by
 resmail-ch2-329v.sys.comcast.net with LMTP; Thu, 9 Apr 2015 16:08:18 +0000
 (UTC)

Received: from resimta-ch2-12v.sys.comcast.net ([69.252.207.12])
	by reszmta-ch2-05v.sys.comcast.net with comcast
	id Drux1q00t0GbAJl01s8JBH; Thu, 09 Apr 2015 16:08:18 +0000

Received: from securemail.chicagonettech.com ([173.165.112.155])
	by resimta-ch2-12v.sys.comcast.net with comcast
	id Ds5D1q00V3MDP2501s5DKF; Thu, 09 Apr 2015 16:05:14 +0000

X-CAA-SPAM: 00000

X-Authority-Analysis: v=2.1 cv=eoFRz+ZX c=1 sm=1 tr=0
 a=mPdxyGmiULMihcXJBqGhDw==:117 a=mPdxyGmiULMihcXJBqGhDw==:17 a=BvmIL-y6AAAA:8
 a=C_IRinGWAAAA:8 a=GGcpBh7Jt_oA:10 a=pGLkceISAAAA:8 a=1XWaLZrsAAAA:8
 a=e9J7MTPGsLIA:10 a=3j4BkbkPAAAA:8 a=jU4qhlNgAAAA:8 a=dLlGIdxEAAAA:8
 a=CB4OEuVYmEujtS6SXy4A:9 a=QEXdDO2ut3YA:10 a=r8Rnbmbiu_sA:10
 a=yGW8d-8WM1kA:10 a=gA6IeH5FQcgA:10 a=NWVoK91CQyQA:10
 a=z7xXriHXSji1e45u9F4A:9 a=Qo3Lp01S8S0owuux:21

Authentication-Results: resimta-ch2-12v.sys.comcast.net;
	dkim=pass header.d=gmail.com header.b=jcEz/iMJ

Received: from mail-la0-f50.google.com (mail-la0-f50.google.com [209.85.215.50]) by securemail.chicagonettech.com with SMTP
	(version=TLS\Tls
	cipher=Aes256 bits=256);
   Thu, 9 Apr 2015 11:04:59 -0500

Received: by labbd9 with SMTP id bd9so81702675lab.2;
        Thu, 09 Apr 2015 09:04:55 -0700 (PDT)

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=YYj6ZDwA2g2auNtpvqY78biQEjeiJl5Jf/1ZwI2SCx0=;
        b=jcEz/iMJyw6xNXT3OL8TemkjDPgCc+1MinGWxvBux4AUVH6amVKyi5D6iuCGMv2Qih
         nUSOt9bhvPvdBcnSroYs+rOtzGymqVSOS2bI6kcSB+clg3rbf/KIBqJqP7OoJBZr2aBN
         E/VuZ6i+dZbV2vAXzaE8zMZllW4PdsjQqcEPYvC2yCesJn02L5flnDZRi0tqu8QHis/M
         68W2WsJHO8rIMXnOOEsuMRYrH15RaRT463U+LQNJx05TmTWl/JeLKZTLvKOuMLZ/xbmd
         TuZIWmSayf26AKu5SQ3WN4N/QESDCVC6AX3JYnpWsa1g4V+rgLKtLpHt6kiIa+OwnCLh
         RMBw==
MIME-Version: 1.0
X-Received: by 10.112.168.102 with SMTP id zv6mr5855186lbb.45.1428595493878;
 Thu, 09 Apr 2015 09:04:53 -0700 (PDT)
Received: by 10.25.33.1 with HTTP; Thu, 9 Apr 2015 09:04:53 -0700 (PDT)
Date: Thu, 9 Apr 2015 11:04:53 -0500
Message-ID: <CAE-jRogypNuL4qKxZSL34jLfYo_-TLApno2PGkZ9neNBDtNR4g@mail.gmail.com>

Subject: SRS Header Rewrite Test #2

From: Bruce Barnes <chicagonettech@gmail.com>

To: test@chicagonettech.com, Bruce Barnes <bbarnes@chicagonettech.com>
Content-Type: multipart/alternative; boundary=001a11c33d32f0c2e605134cceb7

--001a11c33d32f0c2e605134cceb7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
------------------- END HEADER -------------------
So, while I understand what you are saying about SMTP LOGS, there is nothing in the SRS REWRITE PROTOCOL which mandates putting anything into SMTP or DELIVERY LOGS.
 
The mandate is the REPLACEMENT of the SENDING E-MAIL ADDRESS in the MESSAGE HEADER to reflect the E-MAIL ADDRESS which  is FORWARDING the message after it has been received from the original sender and is being forwarded by a user's account.
 
Right now, this is broken and causes 550, SMTP AUTHENTICATION ERRORS.  If it was working properly, there would be no errors.
Bruce Barnes
ChicagoNetTech Inc
brucecnt@comcast.net

Phonr: (773) 491-9019
Phone: (224) 444-0169

E-Mail and DNS Security Specialist
Network Security Specialist

Customer Service Portal: https://portal.chicagonettech.com
Website: https://www.ChicagoNetTech.com
Security Blog: http://networkbastion.blogspot.com/

Web and E-Mail Hosting, E-Mail Security and Consulting
0
Employee Replied
Employee Post
Hi Bruce,
 
I don't see in the documentation you posted that the SRS address needs to be inserted into the header of the message by the forwarding server.  I also looked over the full documentation and didn't see that.
 
It does say the return-path needs to be rewritten, but the forwarding server doesn't insert the return-path header - the receiving server inserts that and it uses the value of the address given in the Mail From command during the SMTP session from the forwarding server to the receiving server.
 
So in my test I sent from my gmail address to my smartertools address which forwards to my outlook.com address with SRS enabled on our SmarterTools server.
 
Gmail sends the message to the smartertools server to my address.  SmarterTools receives the message and first delivers the message locally to my bgrosz account and inserts the return-path on that locally delivered message which will be set to my gmail address that the message was sent from.  The SmarterTools mail server sees that it should forward this message to my outlook.com address and also sees the SRS is enabled.  So the SmarterTools server connects to the outlook.com server over SMTP and for the Mail From address gives the SRS encoded address so the SPF check will be done against smartertools.com and not gmail.com.  Outlook.com then adds the return-path to the message which will be set to the SRS encoded value that the SmarterTools.com server gave it in the SMTP Mail From command.

Testing in this scenario, I have a Return-Path in the header of the message in my Outlook.com account set to the SRS encoded address.  It also says that SPF passed.
0
Bruce Barnes Replied
From: Meng Wong's illustrations for Sender Rewriting Scheme:
 
I don't see SmarterMail doing the rewrite shown in the diagram below: IE: 
 
A message is sent from ann@orig.com, where:

MAILFROM:<ann@orig.com>

is sent to bob@pobox.com

and the header changes the MAIL FROM as follows to

MAILFROM:<SRSO+yf09=CW=orig.com=ann@pobox.com>

and then forwards to cob@third.com

 

 

SmarterMail already does this, properly, with ListSrv sends and a mailing list is sent out, so it should be very easily accomplished with a standard SRS Forward, but only when enabled.

 

Comparing verbatim email forwarding with Sender Rewriting Scheme

 

In traditional or verbatim forwarding, the return-path is preserved in the outgoing message. In an SPF world, forwarders need to rewrite the return-path to stay in good standing. The SRS library implementations help perform the needed transformation. Full-time forwarding services may prefer to integrate this logic directly into their MTAs. Smaller sites don't have to: they can just call the srs utility which does all the work.

The rewritten return-path contains the original sender so whitelisting can still work, albeit with some tweaking. To prevent bad guys from using forwarders as an open relay, SRS adds a hash (yf09). It also adds a timestamp (Cw) which causes addresses to expire. If cob@third.com is undeliverable, pobox.com gets the bounce; it unwraps ann@orig.com and forwards the bounce back to her. Note that no escaping is needed.

What if there are multiple forwarders? No problem: the SRS0 marker tells other forwarders that SRS has already happened. The second forwarder changes SRS0 to SRS1, slaps on the first forwarder's domain, and leaves everything else untouched. Subsequent forwarders just change the domain at the end. Thus is address growth kept in check. Mail::SRS and pysrs also provide a database-backed version that guarantees short addresses.


Edit text of this page | View other revisions
Last edited 2008-01-08 13:58 (UTC) by Julian Mehnle (diff)
 
 

SmarterMail does this CORRECTLY when the message is sent from an OUTSIDE SOURCE to an account on the SmarterMail server:

Using my example from the second test, outlined in my previous post:

A message was sent from chicagonettech@comcast.net, where:

MAILFROM:<chicagonettech@comcast.net>

is sent to test@chicagonettech.com

and the header changes the MAIL FROM as follows to

MAILFROM:<Return-Path: srs0=d28f=ek=gmail.com=chicagonettech@chicagonettech.com>

and then forwards to srstest@comcast.net

 

SmarterMail FAILS when the message is sent from an INSIDE SOURCE to an account on the SmarterMail server, which is forwarded to an OUTSIDE ACCOUNT. IE

Using my example from the first test, as outlined in my original post:

A message was sent from bbarnes@chicacgonettech.com where: [hosted on SmarterMail]

MAILFROM:<bbarnes@chicagonettech.com>

is sent to test@chicagonettech.com [hosted on SmarterMail]

and the header changes the MAIL FROM as follows to

MAILFROM:<Return-Path: bbarnes@chicagonettech.com>

and then forwards to srstest@comcast.net

=====================

 

Summary:

FAIL:

Message sent from an INTERNAL SMARTERMAIL e-mail address, which are sent to another INTERNAL SMARTERMAIL e-mail address, which is hosted on the same SmarterMail server as the originating address, which, when received, is then FORWARDED, by the receiving SmarterMail hosted account, to an e-mail address hosted on an EXTERNAL MX server BOUNCE with "550 SMTP AUTHENTICATION REQUIRED" ERROR, when sent to  AOL.COM, HOTMAIL.COM, OUTLOOK.COM, and GMAIL.COM accounts, because NO SRS HEADER REWRITE is made:

A message was sent from bbarnes@chicacgonettech.com where: [hosted on SmarterMail]
is sent to test@chicagonettech.com [hosted on SmarterMail]
and the header changes the MAIL FROM as follows to
MAILFROM:<Return-Path: bbarnes@chicagonettech.com>
and then forwards to srstest@comcast.net

=====================

PASS:

Message sent from an EXTERNALLY HOSTED e-mail address, whether the originating external server is a SmarterMail server, or another manufacturer's MX server package, which are sent to a SMARTERMAIL e-mail address, which, when received, is then FORWARDED, by the receiving SmarterMail hosted account, to an e-mail address hosted on an EXTERNAL MX server are SUCCESSFULLY DELIVERED, because the SRS HEADER is properly rewritten:

EG: A message was sent from chicagonettech@comcast.net, where:
MAILFROM:<chicagonettech@comcast.net>
is sent to test@chicagonettech.com
and
the header changes the MAIL FROM as follows to
MAILFROM:<Return-Path: srs0=d28f=ek=gmail.com=chicagonettech@chicagonettech.com>
and then forwards to srstest@comcast.net

=====================

NOTE:  the use of a COMCAST.NET account was chosen for this test because Comcast.net is not yet bouncing on SRS header rewrite fails.

Bruce Barnes
ChicagoNetTech Inc
brucecnt@comcast.net

Phonr: (773) 491-9019
Phone: (224) 444-0169

E-Mail and DNS Security Specialist
Network Security Specialist

Customer Service Portal: https://portal.chicagonettech.com
Website: https://www.ChicagoNetTech.com
Security Blog: http://networkbastion.blogspot.com/

Web and E-Mail Hosting, E-Mail Security and Consulting
1
Employee Replied
Employee Post
Ah, I see the issue now.  I originally tested from one external address to a SmarterMail account that forwards to another external address which worked properly.  I didn't test from an internal to internal address that forwards to external.  That didn't work and is definitely a bug.
 
We will fix that and I will let you know as soon as that is available.
 
Thanks.
0
Bruce Barnes Replied
Thanks!  That will make a lot of people very happy.
Bruce Barnes
ChicagoNetTech Inc
brucecnt@comcast.net

Phonr: (773) 491-9019
Phone: (224) 444-0169

E-Mail and DNS Security Specialist
Network Security Specialist

Customer Service Portal: https://portal.chicagonettech.com
Website: https://www.ChicagoNetTech.com
Security Blog: http://networkbastion.blogspot.com/

Web and E-Mail Hosting, E-Mail Security and Consulting
0
Employee Replied
Employee Post
Hey Bruce,
 
It looks like I must have done something wrong in my initial test as I can't reproduce that issue any more.  When I went to fix the issue I saw that it does SRS encode as long as the sending domain is different from the forwarding domain.  When I tested this on my local instance of SmarterMail it correctly SRS encoded when sending from the local domainA to local domainB which forwards to an external address.  I then retested this on our live server and also correctly encoded when going from one internal domain to another that forwards out to an external.
 
One thing that could cause what you are seeing is if you are overriding the SRS setting in the domain settings.  Did you make sure that the domains on your server experiencing this issue  do not have the SRS setting under the "Technical" tab set to disabled?
 
If the domain setting is not set to disabled, then we will need more information on how to reproduce the issue.  Just to be clear, this is how I am testing:
 
I have bgrosz@domainA.com and bgrosz@domainB.com both hosted on the same SmarterMail server.  I enable the global SRS setting and both domainA.com and domainB.com have their SRS setting set to "Use Server Default".  I set bgrosz@domainB.com to forward to user@externaldomain.com.  I then send a message from bgrosz@domainA.com to bgrosz@domainB.com.  The message delivers to bgrosz@domainB.com and also forwards to user@externaldomain.com.  The delivery log shows the "Mail From" command using an SRS encoded sender address.
 
Is that the correct scenario I should be testing or did I miss something?
0
Bruce Barnes Replied
Apologies for the very lengthy response, but I wanted to document that this WORKS when sent from EXTERNAL to SMARTERMAIL which is forwarded to EXTERNAL.
 
It FAILS, per the last two examples in the response, when sent from an account on the SAME DOMAIN to another account on that domain, which is forwarded to an external e-mail address
 
With regard to your question about whether or not the SRS settings are overwritten at the DOMAIN Level, they are not.  The SRS settings are not overridden in the technical tab.
 
chicagonettech.com technical tab settings
 
The SRS forward test which is failing can be seen in the first log I included.
 
The test message was going from bbarnes@chicagonettech.com to test@chicagonettech.com.
 
test@chicagonettech.com forwards the message to an outside mailbox of : srstest@comcast.net .
 
The header below is the original header from the message forwarded from test@chicagonettech.com to srstest@comcast.net
 
The message is NOT DELETED from the test@chicagonettech.com account when it is forwarded.
Return-Path: bbarnes@chicagonettech.com 

Received: from reszmta-ch2-08v.sys.comcast.net (LHLO reszmta-ch2-08v.sys.comcast.net) (69.252.207.72) by resmail-ch2-329v.sys.comcast.net with LMTP; Wed, 8 Apr 2015 16:03:19 +0000 (UTC) 

Received: from resimta-ch2-13v.sys.comcast.net ([69.252.207.13]) by reszmta-ch2-08v.sys.comcast.net with comcast id DTou1q00A0Hsqf101U3K8E; Wed, 08 Apr 2015 16:03:19 +0000 

Received: from securemail.chicagonettech.com ([173.165.112.155]) by resimta-ch2-13v.sys.comcast.net with comcast id DU191q00A3MDP2501U19dq; Wed, 08 Apr 2015 16:01:09 +0000 

X-CAA-SPAM: 00000 

X-Authority-Analysis: v=2.1 cv=Q5Bc4uGa c=1 sm=1 tr=0 
    a=mPdxyGmiULMihcXJBqGhDw==:117 a=mPdxyGmiULMihcXJBqGhDw==:17 
    a=BvmIL-y6AAAA:8 a=C_IRinGWAAAA:8 a=GGcpBh7Jt_oA:10 a=oEzvXX9GNFgA:10 
    a=tS228Fp5AAAA:8 a=e9J7MTPGsLIA:10 a=DAwyPP_o2Byb1YXLmDAA:9 
    a=Zr7miEi8wWIA:10 a=cKsnjEOsciEA:10 a=2oeSqxxVzlsA:10 a=3j4BkbkPAAAA:8 
    a=jU4qhlNgAAAA:8 a=dLlGIdxEAAAA:8 a=1XWaLZrsAAAA:8
    a=STZmhPMTLkd5KhuouBMA:9 a=dOnhtoqqiL3_Y-V6:21 a=JdB8LfO07to-XmEx:21
    a=QEXdDO2ut3YA:10 a=r8Rnbmbiu_sA:10 a=sU3Ul_KeppsA:10 a=yGW8d-8WM1kA:10
    a=gA6IeH5FQcgA:10 a=NWVoK91CQyQA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8
    a=MRhXl2DJMnZU5BNz2RMA:9 a=Roc9qq-cKchXe6Iz:21 a=RCMycJvN6f3Gv-yx:21
    a=7nlW5L_vBE57OG1z:21 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10
    a=_KN1Omkaj_e7Zxuq31MA:9 a=ZVk8-NSrHBgA:10 

Authentication-Results: resimta-ch2-13v.sys.comcast.net; 
        dkim=pass header.d=chicagonettech.com header.b=W+lnkXmR 

X-SmarterMail-Authenticated-As: bbarnes@chicagonettech.com 

DomainKey-Signature: a=rsa-sha1; c=simple; q=dns; d=chicagonettech.com; s=secure; h=received:reply-  to:from:to:subject:date:organization:message-id :x-mailer:thread-index:content-language:mime-version:content-type; b=XRVgw00k2mFBiODU1nlkbBif5q22KP8Ok0vivn3lxgv36Jz1l82miuxvcTmIBzKhE y0a5yZWVmAVxtWL/X2ZfXDx4e+Km4K7EwHUKZr3/OHsGShM6hV8oIHtNE/TnjKef1 Fo9OS/ZBmy+7GL6O2h1QEyOQwNh4+v3+0uV4iluaJb1kkrzBno+dkk/BBpt3KikJc vtZxCSjLwIXkooiHnYKIEvicTZutoeVXRqnwjZhB4Z6nPRmIUd5r4+VGQhQJiz+Oz vknQ+rJL177iEjOILQYI+Vy7Rdh7aY5hANhhJArfK//8z5jEvM5d3ZwKkriEZU6+j rOhVw0NdOdE+zmAXA== 

DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=chicagonettech.com; s=secure; h=content-type:mime-version:content-language:thread-index:x-mailer :message-id:organization:date:subject:to:from:reply-to; bh=xNMz80ZIFA7KNg/KFHTihSdo8O1ZktbxX4r+/TcmR6M=; b=W+lnkXmRjdCRlF4YgGe02svz9rczhRNozp1Bo0AfcVOCadVHGUX8SWWUwB2MjvEDC DYB4I3OU6cL2GUvC3GMNztx8kkS8+31Z5FQJhxuCEG9DDg/qaCyc2DpjSapFJrpYu qmT6hyFyO6Z9inrkvwYJfq9ersJfKIuvLSITbqbZ6VbczgeDfq7ZfacHBOEaI2TcG S10ASTbIrbX2LsVem+fhy1aSQsWLchLEbZi7Knlc0wUHUGBlW6Nz2kz3oF2b3O9Py S8Q1MYqSoE4j37cC9OCKS80XgaxSJSR/B0NJOvtnEtv8SAeYDWsRLk1g0RZul0RNb 1z0ZxZD644kG1RE0w== 

Received: from MrsPeele (173-165-112-149-Illinois.hfc.comcastbusiness.net [173.165.112.149]) by securemail.chicagonettech.com with SMTP 
    (version=TLS\Tls 
    cipher=Aes256 bits=256); Wed, 8 Apr 2015 11:01:02 -0500 

Reply-To: <bbarnes@chicagonettech.com> 

From: "Bruce Barnes" <bbarnes@chicagonettech.com> 

To: "Test Account" <test@chicagonettech.com> 

Subject: SRS Forward Test 

Date: Wed, 8 Apr 2015 11:00:59 -0500 

Organization: ChicagoNetTech Inc 

Message-ID: <01e101d07215$34c96d40$9e5c47c0$@chicagonettech.com> 

X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdByFRrf+dSkghTeSiuqbrpVVrH78g== 

Content-Language: en-us 

MIME-Version: 1.0 

Content-Type: multipart/signed; 
    protocol="application/x-pkcs7-signature"; 
    micalg=2.16.840.1.101.3.4.2.1; 
    boundary="----=_NextPart_000_01DA_01D071EB.4B8DECB0"
If you want to try the same test, I can give you a local account, on the SmarterMail server, under the chicagonettech.com domain and you can send to the test@chicagonettech.com e-mail address from the same-SmarterMail-server account.
 
We can try the forward to test@chicagonettech.com
 
We can also try the forward to another account of your choice so you can see the header in both accounts.
 
When we send from a same-domain account,
 
Here is a test
 
with the message received at TEST@CHICAGONETTECH.COM being forwarded
 
the forwarded message is left on the SmarterMail server
 
Both the originating, and receiving account are on the same SmarterMail server, which is running
 
 - SmarterMail Enterprise Version 13.3.5561.17888
 
Here is the COPY of the message, which was sent from TEST@ECHICAGO.COM to TEST@CHICAGONETTECH.COM,
 
This copy is from the SENT ITEMS box, in TEST@ECHICAGO.COM
 
Both ECHICAGO.COM and CHICAGONETTECH.COM are on the same SmarterMail server: FIFI.CHICAGONETTECH.COM, which has the SMTP MX server name of SECUREMAIL.CHICAGONETTECH.COM on the IP address of 173.165.112.155.
 
The physical server, FIFI.CHICAGONETTECH.COM, which is the server to which SmarterMail is licensed, has an IP address of 173.165.112.146
 
The originating IP address is my laptop, via my wireless router, on 173.165.112.149
 
The message was originated via the SmarterMail web interface, from my laptop, "MrsPeele", connected via 173.165.112.149
 
Here is the original message, from the SENT ITEMS box of TEST@ECHICAGO.COM:
Received: by fifi.chicagonettech.com via HTTP;
Mon, 13 Apr 2015 13:26:28 -0500
From: "Test Account" <test@echicago.com>
To: <test@chicagonettech.com>
Subject: SRS Forwarding Test #4 - 20150413132545 hours, CDT | GMT-0500 hours.
Date: Mon, 13 Apr 2015 13:26:28 -0500
Reply-To: test@echicago.com
Message-ID: <063d121ca7a046c2aa83a1da892624ea@echicago.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=01598a4cca92401293fa3ed22af147ee
X-Originating-IP: [173.165.112.149]

SRS Forwarding Test #4 - 20150413132545 hours, CDT | GMT-0500 hours.

The is an SRS HEADER REWRITE forwarding test.

This is being sent form TEST@ECHICAGO.COM to TEST@CHICAGONETTECH.COM, both of which are housed on the same SmarterMail e-mail server.

The account, TEST@CHICAGONETTECH.COM is set to FORWARD to SRSTEST@COMCAST.NET 

When the test is received at SRSTEST@COMCAST.NET, we will pull the headers to check the SRS Header Rewrite and see if it works properly.

Bruce Barnes
 
Here is the message, as it was received, by TEST@CHICAGONETTECH.COM.  The original message is included after the headers. 
 
The raw content shown below was captured via the SmarterMail web interface using the VIEW, RAW CONTENT option in the message window:
 
Received: by fifi.chicagonettech.com via HTTP;
	Mon, 13 Apr 2015 13:26:28 -0500
From: "Test Account" <test@echicago.com>
To: <test@chicagonettech.com>
Subject: SRS Forwarding Test #4 - 20150413132545 hours, CDT | GMT-0500 hours.
Date: Mon, 13 Apr 2015 13:26:28 -0500
Reply-To: test@echicago.com
Message-ID: <063d121ca7a046c2aa83a1da892624ea@echicago.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=01598a4cca92401293fa3ed22af147ee
X-Originating-IP: [173.165.112.149]
X-SmarterMail-TotalSpamWeight: 0 (Authenticated)

This is a multipart message in MIME format.

--01598a4cca92401293fa3ed22af147ee
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

SRS Forwarding Test #4 - 20150413132545 hours, CDT | GMT-0500 hours.
  
 The is an SRS HEADER REWRITE forwarding test.
  
 This is being sent form TEST@ECHICAGO.COM to TEST@CHICAGONETTECH.COM, both 
of which are housed on the same SmarterMail e-mail server.
  
 The account, TEST@CHICAGONETTECH.COM is set to FORWARD to 
SRSTEST@COMCAST.NET 
  
 When the test is received at SRSTEST@COMCAST.NET, we will pull the headers 
to check the SRS Header Rewrite and see if it works properly.
  
 Bruce Barnes
 

--01598a4cca92401293fa3ed22af147ee
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<span style=3D"font-family: Arial, Helvetica, Sans-Serif; font-size: 12px">=
<div><span style=3D"font-size: 18px;"><span style=3D"font-family: tahoma,ge=
neva,sans-serif;">SRS Forwarding Test #4 - 20150413132545 hours, CDT | GMT-=
0500 hours.</span></span></div>

<div>&nbsp;</div>

<div><span style=3D"font-family: tahoma,geneva,sans-serif;">The is an SRS H=
EADER REWRITE forwarding test.</span></div>

<div>&nbsp;</div>

<div><span style=3D"font-family: tahoma,geneva,sans-serif;">This is being s=
ent form <a href=3D"mailto:TEST@ECHICAGO.COM">TEST@ECHICAGO.COM</a> to <a h=
ref=3D"mailto:TEST@CHICAGONETTECH.COM">TEST@CHICAGONETTECH.COM</a>, both of=
 which are housed on the same SmarterMail e-mail server.</span></div>

<div>&nbsp;</div>

<div><span style=3D"font-family: tahoma,geneva,sans-serif;">The account, <a=
 href=3D"mailto:TEST@CHICAGONETTECH.COM">TEST@CHICAGONETTECH.COM</a> is set=
 to FORWARD to <a href=3D"mailto:SRSTEST@COMCAST.NET">SRSTEST@COMCAST.NET</=
a> </span></div>

<div>&nbsp;</div>

<div><span style=3D"font-family: tahoma,geneva,sans-serif;">When the test i=
s received at <a href=3D"mailto:SRSTEST@COMCAST.NET">SRSTEST@COMCAST.NET</a=
>, we will pull the headers to check the SRS Header Rewrite and see if it w=
orks properly.</span></div>

<div>&nbsp;</div>

<div><span style=3D"font-family: tahoma,geneva,sans-serif;">Bruce Barnes</s=
pan></div>

<div>&nbsp;</div>

<div>&nbsp;</div>

<div>&nbsp;</div>

<div>&nbsp;</div></span>

--01598a4cca92401293fa3ed22af147ee--
 
and here is the header, and message, as received, via the FORWARD from TEST@CHICAGONETTECH.COM to SRSTEST@COMCAST.NET.
 
As we can see, by the very first line in the header content, the SRS HEADER REWRITE is done properly, when sent from two different domains hosted on the same SmarterMail server:
 
Return-Path: srs0=gipl=ep=echicago.com=test@chicagonettech.com

Received: from reszmta-ch2-06v.sys.comcast.net (LHLO
 reszmta-ch2-06v.sys.comcast.net) (69.252.207.70) by
 resmail-ch2-329v.sys.comcast.net with LMTP; Mon, 13 Apr 2015 18:26:33 +0000
 (UTC)
Received: from resimta-ch2-09v.sys.comcast.net ([69.252.207.9])
	by reszmta-ch2-06v.sys.comcast.net with comcast
	id FWBk1q0230Ci9Hx01WSZNK; Mon, 13 Apr 2015 18:26:33 +0000
Received: from securemail.chicagonettech.com ([173.165.112.155])
	by resimta-ch2-09v.sys.comcast.net with comcast
	id FWSY1q01g3MDP2501WSYJY; Mon, 13 Apr 2015 18:26:33 +0000
X-CAA-SPAM: 00000
X-Authority-Analysis: v=2.1 cv=GbGZnGnL c=1 sm=1 tr=0
 a=mPdxyGmiULMihcXJBqGhDw==:117 a=mPdxyGmiULMihcXJBqGhDw==:17 a=BvmIL-y6AAAA:8
 a=C_IRinGWAAAA:8 a=GGcpBh7Jt_oA:10 a=Bt3p9Rs6QdQA:10 a=Xm9Mzi6sAAAA:8
 a=e9J7MTPGsLIA:10 a=DAwyPP_o2Byb1YXLmDAA:9 a=Zr7miEi8wWIA:10
 a=cKsnjEOsciEA:10 a=2oeSqxxVzlsA:10 a=r1H4BbjvijncVQZpuskA:9
 a=CjuIK1q_8ugA:10 a=sU3Ul_KeppsA:10 a=8vG2tF8b-f_JTBIIM4EA:9
 a=gmRP-p3XMpfHO0LB:21 a=wPNLvfGTeEIA:10
Authentication-Results: resimta-ch2-09v.sys.comcast.net;
	dkim=pass header.d=echicago.com header.b=TdipogfD
X-SmarterMail-Authenticated-As: test@echicago.com
DomainKey-Signature: a=rsa-sha1; c=simple; q=dns;
        d=echicago.com; s=secure;
        h=received:from:to:subject:date:reply-to:message-id:mime-version
          :content-type:x-originating-ip;
        b=HUcFC1dXgD45QqZgf10Mh6mfUd/KGW6We3AQrGYvDH0CfH9eUFIxQpPLhAkUdCk5Y
          /LswCxyC73jwpJGgZbg7DLNnFSgzM6QL9Jm8lkbvvfLEO0c4IWF2oSg4+KU4GzBzl
          AVWNDqjKew9l+NnjH3EQ4Q7Ua+w30Ngv0UEG4eCFzqFClIbZE5qcESxuLph9zMHFd
          54Ba0D6ZpNqx8Pox5aV/uhm5DMXgPf7JJpGAZg19b1yNzOWpH/ZRSjNHKUcRLoLXl
          HAZW7qvAOBwZeeRQtzbXuVS8tmafcoD7+bkwi7tvGB6cmKLspd+L31+o9kfcUZijg
          6Ymyk02D0VcmBjGcQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
        d=echicago.com; s=secure;
        h=x-originating-ip:content-type:mime-version:message-id:reply-to
          :date:subject:to:from:received;
        bh=1IiqSsYwj8Xp7li4UfXfaHme+aeVAXY4h+uiWWa8qSU=;
        b=TdipogfDSyvYEotGQbXW/VukoUjLOwxvgVOXdlAahs6k+S/0Iq3D9SQfkoLKGQ0Wy
          UsZaDHLbYN4/V9w+hCcINy+SjtgjQXtNz3jVi+j/epT4N9QwuYrnJ1QsGRyw4UOTO
          gPx48JUm3SCX1ZYK36WKAmzmvzQjPVSRnm2Wi385k2TEGtMb/aI+rTH52KQpppmZK
          5bBbUEV8jR9xjq5aWaVbs0zCGp8GNdXuFuC6Ee0IisYMqeaZ5JwWZs9Tu4hLZ7vot
          BQ+Fa8DNetGNx1LE5xFmK3qGnuTWQjFBY11mthPUj5saXtDEot4juo1hLVk4q8mUj
          pFHBL8HTrH9BOY7oQ==
Received: by fifi.chicagonettech.com via HTTP;
	Mon, 13 Apr 2015 13:26:28 -0500
From: "Test Account" <test@echicago.com>
To: <test@chicagonettech.com>
Subject: SRS Forwarding Test #4 - 20150413132545 hours, CDT | GMT-0500 hours.
Date: Mon, 13 Apr 2015 13:26:28 -0500
Reply-To: test@echicago.com
Message-ID: <063d121ca7a046c2aa83a1da892624ea@echicago.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=01598a4cca92401293fa3ed22af147ee
X-Originating-IP: [173.165.112.149]

This is a multipart message in MIME format.

--01598a4cca92401293fa3ed22af147ee
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

SRS Forwarding Test #4 - 20150413132545 hours, CDT | GMT-0500 hours.
  
 The is an SRS HEADER REWRITE forwarding test.
  
 This is being sent form TEST@ECHICAGO.COM to TEST@CHICAGONETTECH.COM, both 
of which are housed on the same SmarterMail e-mail server.
  
 The account, TEST@CHICAGONETTECH.COM is set to FORWARD to 
SRSTEST@COMCAST.NET 
  
 When the test is received at SRSTEST@COMCAST.NET, we will pull the headers 
to check the SRS Header Rewrite and see if it works properly.
  
 Bruce Barnes
  
  
  
  


--01598a4cca92401293fa3ed22af147ee
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<span style=3D"font-family: Arial, Helvetica, Sans-Serif; font-size: 12px">=
<div><span style=3D"font-size: 18px;"><span style=3D"font-family: tahoma,ge=
neva,sans-serif;">SRS Forwarding Test #4 - 20150413132545 hours, CDT | GMT-=
0500 hours.</span></span></div>

<div>&nbsp;</div>

<div><span style=3D"font-family: tahoma,geneva,sans-serif;">The is an SRS H=
EADER REWRITE forwarding test.</span></div>

<div>&nbsp;</div>

<div><span style=3D"font-family: tahoma,geneva,sans-serif;">This is being s=
ent form <a href=3D"mailto:TEST@ECHICAGO.COM">TEST@ECHICAGO.COM</a> to <a h=
ref=3D"mailto:TEST@CHICAGONETTECH.COM">TEST@CHICAGONETTECH.COM</a>, both of=
 which are housed on the same SmarterMail e-mail server.</span></div>

<div>&nbsp;</div>

<div><span style=3D"font-family: tahoma,geneva,sans-serif;">The account, <a=
 href=3D"mailto:TEST@CHICAGONETTECH.COM">TEST@CHICAGONETTECH.COM</a> is set=
 to FORWARD to <a href=3D"mailto:SRSTEST@COMCAST.NET">SRSTEST@COMCAST.NET</=
a> </span></div>

<div>&nbsp;</div>

<div><span style=3D"font-family: tahoma,geneva,sans-serif;">When the test i=
s received at <a href=3D"mailto:SRSTEST@COMCAST.NET">SRSTEST@COMCAST.NET</a=
>, we will pull the headers to check the SRS Header Rewrite and see if it w=
orks properly.</span></div>

<div>&nbsp;</div>

<div><span style=3D"font-family: tahoma,geneva,sans-serif;">Bruce Barnes</s=
pan></div>

<div>&nbsp;</div>

<div>&nbsp;</div>

<div>&nbsp;</div>

<div>&nbsp;</div></span>

--01598a4cca92401293fa3ed22af147ee--
So, to summarize what we just did, we sent
 
TO TEST@CHICAGONETTECH.COM - both of which are on the same SmarterMail Enterprise server, running Version 13.3.5561.17888 of the SmarterMail software.
 
This shows that the SRS HEADER REWRITE is handled properly when a message is sent from two different domains, both of which are hosted on the same SmarterMail server.
 
From my post above, dated 9 April, 2015, at 10:08 PM [2208 hours], we can also see that messages sent from an EXTERNAL domain to a domain hosted on the SmarterMail server, which, upon receipt, forwards to an account hosted externally, also pass:
 

SmarterMail does this CORRECTLY when the message is sent from an OUTSIDE SOURCE to an account on the SmarterMail server:

Using my example from the second test, outlined in my previous post:

A message was sent from chicagonettech@comcast.net, where:

MAILFROM:<chicagonettech@comcast.net>

is sent to test@chicagonettech.com

and the header changes the MAIL FROM as follows to

MAILFROM:<Return-Path: srs0=d28f=ek=gmail.com=chicagonettech@chicagonettech.com>

and then forwards to srstest@comcast.net

 

SmarterMail FAILS when the message is sent from an INSIDE SOURCE to an account on the SmarterMail server, which is forwarded to an OUTSIDE ACCOUNT. IE

Using my example from the first test, as outlined in my original post:

A message was sent from bbarnes@chicacgonettech.com where: [hosted on SmarterMail]

MAILFROM:<bbarnes@chicagonettech.com>

is sent to test@chicagonettech.com [hosted on SmarterMail]

and the header changes the MAIL FROM as follows to

MAILFROM:<Return-Path: bbarnes@chicagonettech.com>

and then forwards to srstest@comcast.net

 
FAILS ONLY WHEN INTERNAL SMARTERMAIL - SAME DOMAIN TO SAME DOMAIN, FORWARDED EXTERNALLY:
 
The SRS HEADER REWRITE issue appears to only be a problem when sending from an e-mail account which is on the same domain as the receiving e-mail account, when the receiving e-mail account forwards to an account on a domain hosted externally, IE: (using a new test, done as this e-mail was being written)
 
This time, we're going
 
from CHICAGONETTECH@GMAIL.COM  (gmail.com)
to TEST@CHICAGONETTECH.COM (SmarterMail Enterprise Version 13.3.5561.17888)
which will forward to TRSTEST@COMCAST.NET  (comcast.net):
 
Here's the original message, as sent from CHICAGONETTECH@GMAIL.COM
 
MIME-Version: 1.0
Received: by 10.25.33.1 with HTTP; Mon, 13 Apr 2015 12:18:46 -0700 (PDT)
Date: Mon, 13 Apr 2015 14:18:46 -0500
Delivered-To: chicagonettech@gmail.com
Message-ID: <CAE-jRoh9zfrChhRFmdQz2wAyKf-D7Yw943u-RFhsCdrGAk7DdA@mail.gmail.com>
Subject: SRS Forwarding Test #5 - 2015041414158 hours, CDT | GMT-0500 hours
From: Bruce Barnes <chicagonettech@gmail.com>
To: test@chicagonettech.com
Content-Type: multipart/alternative; boundary=001a11401c00acf3ba05139ffb39

--001a11401c00acf3ba05139ffb39
Content-Type: text/plain; charset=UTF-8

SRS Forwarding Test #5 - 2015041414158 hours, CDT | GMT-0500 hours

The is an SRS HEADER REWRITE forwarding test.

This is being sent form CHICAGONETTECH@GMAIL.COM  to TEST@CHICAGONETTECH.COM,


he account, TEST@CHICAGONETTECH.COM is set to FORWARD to SRSTEST@COMCAST.NET,
keeping a copy of the message on the CHICAGONETTECH.COM SmarterMail server.

When the test is received at SRSTEST@COMCAST.NET, we will pull the headers
to check the SRS Header Rewrite and see if it works properly.

Bruce Barnes

--001a11401c00acf3ba05139ffb39
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>SRS Forwarding Test #5 - 2015041414158 hours, CDT | G=
MT-0500 hours</div><div><br></div><div>The is an SRS HEADER REWRITE forward=
ing test.
</div><div><br></div><div>
This is being sent form=C2=A0<a href=3D"mailto:CHICAGONETTECH@GMAIL.COM">CH=
ICAGONETTECH@GMAIL.COM</a> =C2=A0to <a href=3D"mailto:TEST@CHICAGONETTECH.C=
OM">TEST@CHICAGONETTECH.COM</a>, </div><div><br></div><div>

The account, <a href=3D"mailto:TEST@CHICAGONETTECH.COM">TEST@CHICAGONETTECH.=
COM</a> is set to FORWARD to <a href=3D"mailto:SRSTEST@COMCAST.NET">SRSTEST=
@COMCAST.NET</a>, keeping a copy of the message on the <a href=3D"http://CH=
ICAGONETTECH.COM">CHICAGONETTECH.COM</a> SmarterMail server.</div><div><br>=
</div><div>

When the test is received at <a href=3D"mailto:SRSTEST@COMCAST.NET">SRSTEST=
@COMCAST.NET</a>, we will pull the headers to check the SRS Header Rewrite =
and see if it works properly.
</div><div><br></div><div>
Bruce Barnes</div></div>

--001a11401c00acf3ba05139ffb39--
 
Here is the message, and headers, as received by the account, TEST@CHICAGONETTECH.COM
 
Return-Path: <chicagonettech@gmail.com>
Received: from mail-la0-f47.google.com (mail-la0-f47.google.com [209.85.215.47]) by securemail.chicagonettech.com with SMTP
	(version=TLS\Tls
	cipher=Aes256 bits=256);
   Mon, 13 Apr 2015 14:18:53 -0500
Received: by lagv1 with SMTP id v1so65508608lag.3
        for <test@chicagonettech.com>; Mon, 13 Apr 2015 12:18:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=Z11IknXu11z50LoZD0KWyN1/FadUcqNI1OsK5yW2qNI=;
        b=usV6Xk7HjaYbbZI652JAxNwXtgLmvPpYEiyNMUXoRs/RGkVNdTQikFJFytBtjFhHhC
         G9hhEGwH0O86wU9Gi4ZIipOzCqOVfM7tFuMatuK42i/8AzgvXAfFlCVNUhPiDae97qkG
         iBt63GN7i4z0TBhPxFCmUFuHLkrrBqEjIb3sq5wm14DX6Y23sQsP9ad9npMq2XpN7XWQ
         uTlOgA+27jjYtmxTqFr1JV3YuWdv4ClMqUJQJCD/kuer9+i4yiqAKKCnlhY9bDjzWYU5
         fPaPD+5JVjNtywVdywJHIJfvYxojlOfTR9MMwx90jrTAEuF1C+ugCdYFEdBh46FJVyHu
         kbjg==
MIME-Version: 1.0
X-Received: by 10.112.168.102 with SMTP id zv6mr14707464lbb.45.1428952726726;
 Mon, 13 Apr 2015 12:18:46 -0700 (PDT)
Received: by 10.25.33.1 with HTTP; Mon, 13 Apr 2015 12:18:46 -0700 (PDT)
Date: Mon, 13 Apr 2015 14:18:46 -0500
Message-ID: <CAE-jRoh9zfrChhRFmdQz2wAyKf-D7Yw943u-RFhsCdrGAk7DdA@mail.gmail.com>
Subject: SRS Forwarding Test #5 - 2015041414158 hours, CDT | GMT-0500 hours
From: Bruce Barnes <chicagonettech@gmail.com>
To: test@chicagonettech.com
Content-Type: multipart/alternative; boundary=001a11c33d32ad6ebf05139ffb6e
X-SmarterMail-Spam: SPF_Pass, DK_None, DKIM_Pass
X-SmarterMail-TotalSpamWeight: 0

--001a11c33d32ad6ebf05139ffb6e
Content-Type: text/plain; charset=UTF-8

SRS Forwarding Test #5 - 2015041414158 hours, CDT | GMT-0500 hours

The is an SRS HEADER REWRITE forwarding test.

This is being sent form CHICAGONETTECH@GMAIL.COM  to TEST@CHICAGONETTECH.COM,


The account, TEST@CHICAGONETTECH.COM is set to FORWARD to SRSTEST@COMCAST.NET,
keeping a copy of the message on the CHICAGONETTECH.COM SmarterMail server.

When the test is received at SRSTEST@COMCAST.NET, we will pull the headers
to check the SRS Header Rewrite and see if it works properly.

Bruce Barnes

--001a11c33d32ad6ebf05139ffb6e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>SRS Forwarding Test #5 - 2015041414158 hours, CDT | G=
MT-0500 hours</div><div><br></div><div>The is an SRS HEADER REWRITE forward=
ing test.
</div><div><br></div><div>
This is being sent form=C2=A0<a href=3D"mailto:CHICAGONETTECH@GMAIL.COM">CH=
ICAGONETTECH@GMAIL.COM</a> =C2=A0to <a href=3D"mailto:TEST@CHICAGONETTECH.C=
OM">TEST@CHICAGONETTECH.COM</a>, </div><div><br></div><div>

he account, <a href=3D"mailto:TEST@CHICAGONETTECH.COM">TEST@CHICAGONETTECH.=
COM</a> is set to FORWARD to <a href=3D"mailto:SRSTEST@COMCAST.NET">SRSTEST=
@COMCAST.NET</a>, keeping a copy of the message on the <a href=3D"http://CH=
ICAGONETTECH.COM">CHICAGONETTECH.COM</a> SmarterMail server.</div><div><br>=
</div><div>

When the test is received at <a href=3D"mailto:SRSTEST@COMCAST.NET">SRSTEST=
@COMCAST.NET</a>, we will pull the headers to check the SRS Header Rewrite =
and see if it works properly.
</div><div><br></div><div>
Bruce Barnes</div></div>

--001a11c33d32ad6ebf05139ffb6e--
 
and here is the message with headers, as receive at TRSTEST@COMCAST.NET
 
Return-Path: srs0=pyve=ep=gmail.com=chicagonettech@chicagonettech.com
Received: from reszmta-po-01v.sys.comcast.net (LHLO
 reszmta-po-01v.sys.comcast.net) (96.114.154.193) by
 resmail-ch2-329v.sys.comcast.net with LMTP; Mon, 13 Apr 2015 19:19:02 +0000
 (UTC)
Received: from resimta-po-20v.sys.comcast.net ([96.114.154.148])
	by reszmta-po-01v.sys.comcast.net with comcast
	id FWz91q02H3CNMcY01XK22U; Mon, 13 Apr 2015 19:19:02 +0000
Received: from securemail.chicagonettech.com ([173.165.112.155])
	by resimta-po-20v.sys.comcast.net with comcast
	id FXK01q02d3MDP2501XK1Do; Mon, 13 Apr 2015 19:19:02 +0000
X-CAA-SPAM: 00000
X-Authority-Analysis: v=2.1 cv=ccxcrxzM c=1 sm=1 tr=0
 a=mPdxyGmiULMihcXJBqGhDw==:117 a=mPdxyGmiULMihcXJBqGhDw==:17 a=BvmIL-y6AAAA:8
 a=C_IRinGWAAAA:8 a=GGcpBh7Jt_oA:10 a=pGLkceISAAAA:8 a=1XWaLZrsAAAA:8
 a=e9J7MTPGsLIA:10 a=bIulGtrH072MWFeye7sA:9 a=QEXdDO2ut3YA:10
 a=tw8zJAZk69UA:10 a=8nTdw60Y5alnFNf4V1kA:9 a=6BkAL57NTmUz95JU:21
Authentication-Results: resimta-po-20v.sys.comcast.net;
	dkim=pass header.d=gmail.com header.b=usV6Xk7H
Received: from mail-la0-f47.google.com (mail-la0-f47.google.com [209.85.215.47]) by securemail.chicagonettech.com with SMTP
	(version=TLS\Tls
	cipher=Aes256 bits=256);
   Mon, 13 Apr 2015 14:18:53 -0500
Received: by lagv1 with SMTP id v1so65508608lag.3
        for <test@chicagonettech.com>; Mon, 13 Apr 2015 12:18:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=Z11IknXu11z50LoZD0KWyN1/FadUcqNI1OsK5yW2qNI=;
        b=usV6Xk7HjaYbbZI652JAxNwXtgLmvPpYEiyNMUXoRs/RGkVNdTQikFJFytBtjFhHhC
         G9hhEGwH0O86wU9Gi4ZIipOzCqOVfM7tFuMatuK42i/8AzgvXAfFlCVNUhPiDae97qkG
         iBt63GN7i4z0TBhPxFCmUFuHLkrrBqEjIb3sq5wm14DX6Y23sQsP9ad9npMq2XpN7XWQ
         uTlOgA+27jjYtmxTqFr1JV3YuWdv4ClMqUJQJCD/kuer9+i4yiqAKKCnlhY9bDjzWYU5
         fPaPD+5JVjNtywVdywJHIJfvYxojlOfTR9MMwx90jrTAEuF1C+ugCdYFEdBh46FJVyHu
         kbjg==
MIME-Version: 1.0
X-Received: by 10.112.168.102 with SMTP id zv6mr14707464lbb.45.1428952726726;
 Mon, 13 Apr 2015 12:18:46 -0700 (PDT)
Received: by 10.25.33.1 with HTTP; Mon, 13 Apr 2015 12:18:46 -0700 (PDT)
Date: Mon, 13 Apr 2015 14:18:46 -0500
Message-ID: <CAE-jRoh9zfrChhRFmdQz2wAyKf-D7Yw943u-RFhsCdrGAk7DdA@mail.gmail.com>
Subject: SRS Forwarding Test #5 - 2015041414158 hours, CDT | GMT-0500 hours
From: Bruce Barnes <chicagonettech@gmail.com>
To: test@chicagonettech.com
Content-Type: multipart/alternative; boundary=001a11c33d32ad6ebf05139ffb6e

--001a11c33d32ad6ebf05139ffb6e
Content-Type: text/plain; charset=UTF-8

SRS Forwarding Test #5 - 2015041414158 hours, CDT | GMT-0500 hours

The is an SRS HEADER REWRITE forwarding test.

This is being sent form CHICAGONETTECH@GMAIL.COM  to TEST@CHICAGONETTECH.COM,


he account, TEST@CHICAGONETTECH.COM is set to FORWARD to SRSTEST@COMCAST.NET,
keeping a copy of the message on the CHICAGONETTECH.COM SmarterMail server.

When the test is received at SRSTEST@COMCAST.NET, we will pull the headers
to check the SRS Header Rewrite and see if it works properly.

Bruce Barnes

--001a11c33d32ad6ebf05139ffb6e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>SRS Forwarding Test #5 - 2015041414158 hours, CDT | G=
MT-0500 hours</div><div><br></div><div>The is an SRS HEADER REWRITE forward=
ing test.
</div><div><br></div><div>
This is being sent form=C2=A0<a href=3D"mailto:CHICAGONETTECH@GMAIL.COM">CH=
ICAGONETTECH@GMAIL.COM</a> =C2=A0to <a href=3D"mailto:TEST@CHICAGONETTECH.C=
OM">TEST@CHICAGONETTECH.COM</a>, </div><div><br></div><div>

he account, <a href=3D"mailto:TEST@CHICAGONETTECH.COM">TEST@CHICAGONETTECH.=
COM</a> is set to FORWARD to <a href=3D"mailto:SRSTEST@COMCAST.NET">SRSTEST=
@COMCAST.NET</a>, keeping a copy of the message on the <a href=3D"http://CH=
ICAGONETTECH.COM">CHICAGONETTECH.COM</a> SmarterMail server.</div><div><br>=
</div><div>

When the test is received at <a href=3D"mailto:SRSTEST@COMCAST.NET">SRSTEST=
@COMCAST.NET</a>, we will pull the headers to check the SRS Header Rewrite =
and see if it works properly.
</div><div><br></div><div>
Bruce Barnes</div></div>

--001a11c33d32ad6ebf05139ffb6e--
Test #5 WORKED, IE: Return-Path: srs0=pyve=ep=gmail.com=chicagonettech@chicagonettech.com
 
So, we've finally figured out what this is causing problems.
 
When a message is sent FROM the e-mail account, back TO the same e-mail account, and, up on receipt, is being forwarded to an external account
 
This is not an uncommon practice in a small business or office where a secretary has access to an executive's e-mial account and the secretary will send an e-mail to the account holder because the message she has access to his or her account and the account holder's account is set to forward all of the received messages to the account holder's person account,
 
In the example below, we sent
 
FORWARDED TO SRSTEST@COMCAST.NET
 
and the SRS HEADER REWRITE FAILS!
 
Return-Path: test@chicagonettech.com
Received: from reszmta-ch2-06v.sys.comcast.net (LHLO
 reszmta-ch2-06v.sys.comcast.net) (69.252.207.70) by
 resmail-ch2-329v.sys.comcast.net with LMTP; Mon, 13 Apr 2015 19:39:00 +0000
 (UTC)
Received: from resimta-ch2-05v.sys.comcast.net ([69.252.207.5])
	by reszmta-ch2-06v.sys.comcast.net with comcast
	id FX9u1q01b07XTwt01Xf0Wb; Mon, 13 Apr 2015 19:39:00 +0000
Received: from securemail.chicagonettech.com ([173.165.112.155])
	by resimta-ch2-05v.sys.comcast.net with comcast
	id FXez1q00m3MDP2501Xez2U; Mon, 13 Apr 2015 19:39:00 +0000
X-CAA-SPAM: 00000
X-Authority-Analysis: v=2.1 cv=AsNg3YNP c=1 sm=1 tr=0
 a=mPdxyGmiULMihcXJBqGhDw==:117 a=mPdxyGmiULMihcXJBqGhDw==:17 a=BvmIL-y6AAAA:8
 a=C_IRinGWAAAA:8 a=GGcpBh7Jt_oA:10 a=Bt3p9Rs6QdQA:10 a=e9J7MTPGsLIA:10
 a=DAwyPP_o2Byb1YXLmDAA:9 a=Zr7miEi8wWIA:10 a=cKsnjEOsciEA:10
 a=2oeSqxxVzlsA:10 a=W89gahLHbSbTjdo4YBsA:9 a=CjuIK1q_8ugA:10
 a=7OrUaCZVdsMA:10 a=WKfFM33X2ZoA:10 a=-2_-vqIR2MIA:10 a=Rc1EUYcw0_8A:10
 a=0HyWx39L-eKa0J2GsRYA:9 a=wPNLvfGTeEIA:10 a=h4o7JVsIGEQA:10
 a=sdFr-HtQZskA:10 a=rOwxisJxjCgA:10
Authentication-Results: resimta-ch2-05v.sys.comcast.net;
	dkim=pass header.d=chicagonettech.com header.b=eCIGL5q/
X-SmarterMail-Authenticated-As: test@chicagonettech.com
DomainKey-Signature: a=rsa-sha1; c=simple; q=dns;
        d=chicagonettech.com; s=secure;
        h=received:from:to:subject:date:reply-to:message-id:mime-version
          :content-type:x-originating-ip;
        b=RsMwSsWMI0OA/KH30ZJtRq5Lwz7egYs69BHT58zry1YAoEqFiZkt8EAvzklHnBbs1
          2zHnl8Np0AH4EKV5Y6eS6iBWZm/Zp+Mcua9EAPBZZszvW/DrS7DZ9Wk/f+YCJId4f
          Ib21ka0CcF0/eLSalR3kiJDBlMH7zaL0iytIlAZkvcsmBsgAjGKE2lfjpolLmknIW
          0kauHwrF//rO2TzMwgM+aD+W+U1uJXshk2Q7LXtSYRzWdCgUwjD64G1Z0u9bMK/je
          IFpwqkSNkzzIiZtSB5KvBMyevCZ18chrRCv+TUcZhKs/CjW9MH4sH4E3vF8jpE4y0
          gDjW2DSp81z6CNaAw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
        d=chicagonettech.com; s=secure;
        h=x-originating-ip:content-type:mime-version:message-id:reply-to
          :date:subject:to:from;
        bh=ZKpRRhHttmmwaVp0vJ+ge6qbTp+OM2eYcK89ip1I7t8=;
        b=eCIGL5q/EOXjBGYS26W3FEns6iG/FIvquCV6iAMZNbV9JoihP9Qb34cvfiFNs7PXM
          oBDbshPJHK8JvxJfprS0fEGmPFnyh4/1VBz1jGSwc2s6yq+/7H24lKeQHKzsQAt6s
          1kUwqr7oj5gwuEuJVs2SoUee32Gb3L8X+GJBf6jqEgeCVIRWBSzDLgZ3MVYa3G1XN
          zWtev+q1VEc2k/eOstk60QWIKitzxpg3qaq8HcQIEtJRmYaWIpcSwgyYkCbkBh8LV
          FS/sDzcMlRC4GIvsIh54o0yzZqYqcfanI6S5OdaSpvGCde5DpH7GxUkRSF5NXf+Ur
          nAFLypeJPB1hHNarQ==
Received: by fifi.chicagonettech.com via HTTP;
	Mon, 13 Apr 2015 14:38:54 -0500
From: "Test Account" <test@chicagonettech.com>
To: "Test Account" <test@chicagonettech.com>
Subject: SRS Header Rewrite Test #6 - 20140413143848 CDT GMT-0500
Date: Mon, 13 Apr 2015 14:38:54 -0500
Reply-To: test@chicagonettech.com
Message-ID: <5ece08b0aefa4796909dbd330a4786e3@chicagonettech.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=60e15a54824a41d183e0ce599fa873f0
X-Originating-IP: [173.165.112.149]

This is a multipart message in MIME format.

--60e15a54824a41d183e0ce599fa873f0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

SRS Header Rewrite Test #6 - 20140413143848 CDT GMT-0500

--60e15a54824a41d183e0ce599fa873f0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<span style=3D"font-family: Arial, Helvetica, Sans-Serif; font-size: 12px">=
<div>SRS Header Rewrite Test #6 - 20140413143848 CDT GMT-0500</div>

<div>&nbsp;</div>

<div>&nbsp;</div></span>

--60e15a54824a41d183e0ce599fa873f0--
 
The SRS HEADER Rewrite test also fails when sending from DIFFERENT accounts in the same domain, IE:  No SRS Header Rewrite has occurred in the example below:
 
which FORWARDS to SRSTEST@COMCAST.NET
 
and the SRS HEADER REWRITE test FAILS
 
Return-Path: bbarnes@chicagonettech.com
Received: from reszmta-po-08v.sys.comcast.net (LHLO
 reszmta-po-08v.sys.comcast.net) (96.114.154.200) by
 resmail-ch2-329v.sys.comcast.net with LMTP; Mon, 13 Apr 2015 19:46:57 +0000
 (UTC)
Received: from resimta-po-12v.sys.comcast.net ([96.114.154.140])
	by reszmta-po-08v.sys.comcast.net with comcast
	id FXVJ1q005320yuQ01XmxAf; Mon, 13 Apr 2015 19:46:57 +0000
Received: from securemail.chicagonettech.com ([173.165.112.155])
	by resimta-po-12v.sys.comcast.net with comcast
	id FXmw1q01F3MDP2501Xmwui; Mon, 13 Apr 2015 19:46:57 +0000
X-CAA-SPAM: 00000
X-Authority-Analysis: v=2.1 cv=XbkHzeJ5 c=1 sm=1 tr=0
 a=mPdxyGmiULMihcXJBqGhDw==:117 a=mPdxyGmiULMihcXJBqGhDw==:17 a=BvmIL-y6AAAA:8
 a=C_IRinGWAAAA:8 a=GGcpBh7Jt_oA:10 a=Bt3p9Rs6QdQA:10 a=e9J7MTPGsLIA:10
 a=DAwyPP_o2Byb1YXLmDAA:9 a=Zr7miEi8wWIA:10 a=cKsnjEOsciEA:10
 a=2oeSqxxVzlsA:10 a=vifKMDAIpc2fmqIicQ0A:9 a=CjuIK1q_8ugA:10
 a=Pd4CVNc0RaIA:10 a=yGW8d-8WM1kA:10 a=QXwcZi-eDDEA:10 a=MNB8fz3yKCkA:10
 a=hH0qkwBOpLoA:10 a=F6nnEmoIq-42JzzfMaUA:9 a=lQ3VYgOeIU_gyI23:21
 a=wPNLvfGTeEIA:10
Authentication-Results: resimta-po-12v.sys.comcast.net;
	dkim=pass header.d=chicagonettech.com header.b=WG8tuEJv
X-SmarterMail-Authenticated-As: bbarnes@chicagonettech.com
DomainKey-Signature: a=rsa-sha1; c=simple; q=dns;
        d=chicagonettech.com; s=secure;
        h=received:from:to:subject:date:reply-to:message-id:mime-version
          :content-type:x-originating-ip;
        b=xRJYqxPUkXAnUvM3jq20TpTfRaUygbSNzJzdlafR9QrtnlYSU0rg3PrB5MD9V7HFK
          XFoaMpDl9khpgwCWX/sXF785Y3C1FmcLDX2vLkKbH44ofceoWQn9Icl11ip2iAsG9
          ZWBUsX/btn6Vzea6mn9b0eEQqIIs3DbVlXx7P4NsAbphUifRu90vjbsgdXnzXRs81
          U0MUcnbXV+7ZxzNNLXk7Hu+acb51TEVzei9wIeXHJWVl1fh+d2dxi7P+pX1ApHL/n
          Udsdim4w+KymtrlCZnBk+plAVrWMeL45BaimTwGHUhaI6n0gkXILVibaKizgo4itx
          DDMIeDPnjNtUwHVPw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
        d=chicagonettech.com; s=secure;
        h=x-originating-ip:content-type:mime-version:message-id:reply-to
          :date:subject:to:from;
        bh=Qau+ZeOevw3C33hQGqOVy7k2N8J8NHEc8PuJwhGw8p4=;
        b=WG8tuEJvc7+cxKC6pL1YyYihASYt+Wq9r9WWWNHcJAcJTzh6mMoD1aKDDhHGCqTJh
          QN8YvKL4msUqQ63EHBcNXr7avpTUH+wqCYCNYgNKqyxsHpqSwX6RNwLDQ8U7BQdpP
          9ZyFSBz3cg3R2ogu/TADqwvYZbGNQsdrQ7EUCrIvakIk8Yd+dgqOuBvqr3CnuYUGL
          LsLY1l5/z+CTwRZMWCcsdBU2R734bGdlOZ5jqXZ5OU6ktz4hNO1UghEuPcLJqFIde
          piItbaHe3giOTMRtKXk1X0RG5IpyTPvoiu5wOOY9kIVItY6OoC0rnWOdd6u6PVtBn
          i0CO9Z1puilKTFCJw==
Received: by fifi.chicagonettech.com via HTTP;
	Mon, 13 Apr 2015 14:46:50 -0500
From: "Bruce Barnes" <bbarnes@chicagonettech.com>
To: "Test Account" <test@chicagonettech.com>
Subject: SRS Header Rewrite Test #7 - 20140413144637
Date: Mon, 13 Apr 2015 14:46:50 -0500
Reply-To: bbarnes@chicagonettech.com
Message-ID: <d01facce9d3940019e3dafb91f7aa632@chicagonettech.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=a47620ebc7724ce8848b9415a8e7d47e
X-Originating-IP: [173.165.112.149]

This is a multipart message in MIME format.

--a47620ebc7724ce8848b9415a8e7d47e
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

SRS Header Rewrite Test #7 - 20140413144637
  
  Bruce Barnes   
ChicagoNetTech   

e-mail: bbarnes@chicagonettech.com   
website: https://www.chicagonettech.com   
portal: https://portal.chicagonettech.com   
facebook: chicagonettech  

--a47620ebc7724ce8848b9415a8e7d47e
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<span style=3D"font-family: Arial, Helvetica, Sans-Serif; font-size: 12px">=
<div><span style=3D"font-size: 12px;"><span style=3D"font-family: verdana,g=
eneva,sans-serif;"><span style=3D"font-size: 14px;">SRS Header Rewrite Test=
 #7 - 20140413144637</span></span></span></div>

<div>&nbsp;</div>

<div>
<div><span style=3D"font-family: verdana,geneva,sans-serif;"><font style=3D=
"color: rgb(34, 34, 34); font-family: sans-serif; font-size: 12pt;">Bruce B=
arnes</font></span>

<p style=3D"color: rgb(34, 34, 34); line-height: 13px; font-family: Helveti=
ca, Arial, sans-serif; font-size: 9px; margin-top: 0px; margin-bottom: 0px;=
"><span style=3D"font-family: verdana,geneva,sans-serif;"><font style=3D"fo=
nt-family: sans-serif; font-size: 12pt;">ChicagoNetTech</font></span></p>

<p style=3D"color: rgb(34, 34, 34); line-height: 13px; font-family: Helveti=
ca, Arial, sans-serif; font-size: 9px; margin-top: 0px; margin-bottom: 0px;=
"><span style=3D"font-family: verdana,geneva,sans-serif;"><font style=3D"fo=
nt-family: sans-serif; font-size: 12pt;">&nbsp;</font></span></p>

<p style=3D"color: rgb(34, 34, 34); line-height: 13px; font-family: Helveti=
ca, Arial, sans-serif; font-size: 9px; margin-top: 0px; margin-bottom: 0px;=
"><span style=3D"font-family: verdana,geneva,sans-serif;"><font style=3D"fo=
nt-family: sans-serif; font-size: 12pt;">e-mail:&nbsp;<span class=3D"clicka=
ble ClickableEmail inactive" email=3D"bbarnes@chicagonettech.com" style=3D"=
border-width: 0px 0px 1px; border-style: dotted; border-color: rgb(51, 51, =
51); cursor: pointer;">bbarnes@chicagonettech.com</span></font></span></p>

<p style=3D"color: rgb(34, 34, 34); line-height: 13px; font-family: Helveti=
ca, Arial, sans-serif; font-size: 9px; margin-top: 0px; margin-bottom: 0px;=
"><span style=3D"font-family: verdana,geneva,sans-serif;"><font style=3D"fo=
nt-family: sans-serif; font-size: 12pt;">website:&nbsp;<a href=3D"https://w=
ww.chicagonettech.com/" target=3D"_blank">https://www.chicagonettech.com</a=
></font></span></p>

<p style=3D"color: rgb(34, 34, 34); line-height: 13px; font-family: Helveti=
ca, Arial, sans-serif; font-size: 9px; margin-top: 0px; margin-bottom: 0px;=
"><span style=3D"font-family: verdana,geneva,sans-serif;"><font style=3D"fo=
nt-family: sans-serif; font-size: 12pt;">portal: <a href=3D"https://portal.=
chicagonettech.com">https://portal.chicagonettech.com</a></font></span></p>

<p style=3D"color: rgb(34, 34, 34); line-height: 13px; font-family: Helveti=
ca, Arial, sans-serif; font-size: 9px; margin-top: 0px; margin-bottom: 0px;=
"><span style=3D"font-family: verdana,geneva,sans-serif;"><font style=3D"fo=
nt-family: sans-serif; font-size: 12pt;">facebook: chicagonettech</font></s=
pan></p>
</div>
</div></span>

--a47620ebc7724ce8848b9415a8e7d47e--
 
 
Bruce Barnes
ChicagoNetTech Inc
brucecnt@comcast.net

Phonr: (773) 491-9019
Phone: (224) 444-0169

E-Mail and DNS Security Specialist
Network Security Specialist

Customer Service Portal: https://portal.chicagonettech.com
Website: https://www.ChicagoNetTech.com
Security Blog: http://networkbastion.blogspot.com/

Web and E-Mail Hosting, E-Mail Security and Consulting
1
Employee Replied
Employee Post
Hi Bruce,
 
I'm confused why SRS encoding would be required if the domain is the same for the originator of the message and the forwarder.  The point of SRS is to encode the MAIL FROM address so it will use the forwarding domain for the SPF check.  If the originators domain and forwarders domain are the same that wouldn't accomplish anything.  We purposely don't do SRS encoding if the originator domain and forwarding domain are the same.
 
So if I send from user@gmail.com to user@smartermaildomain.com which forwards to user@outlook.com you need to SRS encode the user@gmail.com address to look like it is from the smartermaildomain.com domain so it will pass SPF checks.
 
If you send from userA@smartermaildomain.com to userB@smartermaildomain.com which forwards to user@outlook.com, the SRS encoding doesn't make any sense since the originator of the message is already coming from the smartermaildomain.com domain.  SPF and DMARC alignment checks should pass as the domain will match for the MAIL FROM, the FROM header field and the d= tag of the DKIM signature.
 
So I don't think the lack of SRS encoding in this scenario is causing the DMARC rejection.  You may want to open a ticket for this issue so we can get more specific information that you probably wouldn't want to post here.  You can just let support know to forward the message to me and refund the ticket (if you don't have any free ones available to use).
0
Bruce Barnes Replied
I understand your confusion.  It took me a while to figure out exactly when the failures occur.
 
The lack of SRS Rewrite only causes an error when the message originates on an e-mail address which is on the same domain as the receiving e-mail address, and the receiving e-mail address forwards the e-mail outside of the SmarterMail system.  The last two examples shown in my previous post.
 
Here are the two examples of when the SRS Forward fails:
 
The SRS HEADER Rewrite test fails when sending from THE SAME ACCOUNT to the SAME ACCOUNT in the SAME DOMAIN, where the sending/receiving account forwards outside the domain,  IE:  No SRS Header Rewrite has occurred in the example below:
 
FORWARDED TO SRSTEST@COMCAST.NET
 
and the SRS HEADER REWRITE FAILS!
 
Return-Path: test@chicagonettech.com
Received: from reszmta-ch2-06v.sys.comcast.net (LHLO
 reszmta-ch2-06v.sys.comcast.net) (69.252.207.70) by
 resmail-ch2-329v.sys.comcast.net with LMTP; Mon, 13 Apr 2015 19:39:00 +0000
 (UTC)
Received: from resimta-ch2-05v.sys.comcast.net ([69.252.207.5])
	by reszmta-ch2-06v.sys.comcast.net with comcast
	id FX9u1q01b07XTwt01Xf0Wb; Mon, 13 Apr 2015 19:39:00 +0000
Received: from securemail.chicagonettech.com ([173.165.112.155])
	by resimta-ch2-05v.sys.comcast.net with comcast
	id FXez1q00m3MDP2501Xez2U; Mon, 13 Apr 2015 19:39:00 +0000
X-CAA-SPAM: 00000
X-Authority-Analysis: v=2.1 cv=AsNg3YNP c=1 sm=1 tr=0
 a=mPdxyGmiULMihcXJBqGhDw==:117 a=mPdxyGmiULMihcXJBqGhDw==:17 a=BvmIL-y6AAAA:8
 a=C_IRinGWAAAA:8 a=GGcpBh7Jt_oA:10 a=Bt3p9Rs6QdQA:10 a=e9J7MTPGsLIA:10
 a=DAwyPP_o2Byb1YXLmDAA:9 a=Zr7miEi8wWIA:10 a=cKsnjEOsciEA:10
 a=2oeSqxxVzlsA:10 a=W89gahLHbSbTjdo4YBsA:9 a=CjuIK1q_8ugA:10
 a=7OrUaCZVdsMA:10 a=WKfFM33X2ZoA:10 a=-2_-vqIR2MIA:10 a=Rc1EUYcw0_8A:10
 a=0HyWx39L-eKa0J2GsRYA:9 a=wPNLvfGTeEIA:10 a=h4o7JVsIGEQA:10
 a=sdFr-HtQZskA:10 a=rOwxisJxjCgA:10
Authentication-Results: resimta-ch2-05v.sys.comcast.net;
	dkim=pass header.d=chicagonettech.com header.b=eCIGL5q/
X-SmarterMail-Authenticated-As: test@chicagonettech.com
DomainKey-Signature: a=rsa-sha1; c=simple; q=dns;
        d=chicagonettech.com; s=secure;
        h=received:from:to:subject:date:reply-to:message-id:mime-version
          :content-type:x-originating-ip;
        b=RsMwSsWMI0OA/KH30ZJtRq5Lwz7egYs69BHT58zry1YAoEqFiZkt8EAvzklHnBbs1
          2zHnl8Np0AH4EKV5Y6eS6iBWZm/Zp+Mcua9EAPBZZszvW/DrS7DZ9Wk/f+YCJId4f
          Ib21ka0CcF0/eLSalR3kiJDBlMH7zaL0iytIlAZkvcsmBsgAjGKE2lfjpolLmknIW
          0kauHwrF//rO2TzMwgM+aD+W+U1uJXshk2Q7LXtSYRzWdCgUwjD64G1Z0u9bMK/je
          IFpwqkSNkzzIiZtSB5KvBMyevCZ18chrRCv+TUcZhKs/CjW9MH4sH4E3vF8jpE4y0
          gDjW2DSp81z6CNaAw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
        d=chicagonettech.com; s=secure;
        h=x-originating-ip:content-type:mime-version:message-id:reply-to
          :date:subject:to:from;
        bh=ZKpRRhHttmmwaVp0vJ+ge6qbTp+OM2eYcK89ip1I7t8=;
        b=eCIGL5q/EOXjBGYS26W3FEns6iG/FIvquCV6iAMZNbV9JoihP9Qb34cvfiFNs7PXM
          oBDbshPJHK8JvxJfprS0fEGmPFnyh4/1VBz1jGSwc2s6yq+/7H24lKeQHKzsQAt6s
          1kUwqr7oj5gwuEuJVs2SoUee32Gb3L8X+GJBf6jqEgeCVIRWBSzDLgZ3MVYa3G1XN
          zWtev+q1VEc2k/eOstk60QWIKitzxpg3qaq8HcQIEtJRmYaWIpcSwgyYkCbkBh8LV
          FS/sDzcMlRC4GIvsIh54o0yzZqYqcfanI6S5OdaSpvGCde5DpH7GxUkRSF5NXf+Ur
          nAFLypeJPB1hHNarQ==
Received: by fifi.chicagonettech.com via HTTP;
	Mon, 13 Apr 2015 14:38:54 -0500
From: "Test Account" <test@chicagonettech.com>
To: "Test Account" <test@chicagonettech.com>
Subject: SRS Header Rewrite Test #6 - 20140413143848 CDT GMT-0500
Date: Mon, 13 Apr 2015 14:38:54 -0500
Reply-To: test@chicagonettech.com
Message-ID: <5ece08b0aefa4796909dbd330a4786e3@chicagonettech.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=60e15a54824a41d183e0ce599fa873f0
X-Originating-IP: [173.165.112.149]

This is a multipart message in MIME format.

--60e15a54824a41d183e0ce599fa873f0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

SRS Header Rewrite Test #6 - 20140413143848 CDT GMT-0500

--60e15a54824a41d183e0ce599fa873f0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<span style=3D"font-family: Arial, Helvetica, Sans-Serif; font-size: 12px">=
<div>SRS Header Rewrite Test #6 - 20140413143848 CDT GMT-0500</div>

<div>&nbsp;</div>

<div>&nbsp;</div></span>

--60e15a54824a41d183e0ce599fa873f0--
and
 
The SRS HEADER Rewrite test also fails when sending from DIFFERENT accounts in the same domain, IE:  No SRS Header Rewrite has occurred in the example below:
 
which FORWARDS to SRSTEST@COMCAST.NET
 
and the SRS HEADER REWRITE test FAILS
 
Return-Path: bbarnes@chicagonettech.com
Received: from reszmta-po-08v.sys.comcast.net (LHLO
 reszmta-po-08v.sys.comcast.net) (96.114.154.200) by
 resmail-ch2-329v.sys.comcast.net with LMTP; Mon, 13 Apr 2015 19:46:57 +0000
 (UTC)
Received: from resimta-po-12v.sys.comcast.net ([96.114.154.140])
	by reszmta-po-08v.sys.comcast.net with comcast
	id FXVJ1q005320yuQ01XmxAf; Mon, 13 Apr 2015 19:46:57 +0000
Received: from securemail.chicagonettech.com ([173.165.112.155])
	by resimta-po-12v.sys.comcast.net with comcast
	id FXmw1q01F3MDP2501Xmwui; Mon, 13 Apr 2015 19:46:57 +0000
X-CAA-SPAM: 00000
X-Authority-Analysis: v=2.1 cv=XbkHzeJ5 c=1 sm=1 tr=0
 a=mPdxyGmiULMihcXJBqGhDw==:117 a=mPdxyGmiULMihcXJBqGhDw==:17 a=BvmIL-y6AAAA:8
 a=C_IRinGWAAAA:8 a=GGcpBh7Jt_oA:10 a=Bt3p9Rs6QdQA:10 a=e9J7MTPGsLIA:10
 a=DAwyPP_o2Byb1YXLmDAA:9 a=Zr7miEi8wWIA:10 a=cKsnjEOsciEA:10
 a=2oeSqxxVzlsA:10 a=vifKMDAIpc2fmqIicQ0A:9 a=CjuIK1q_8ugA:10
 a=Pd4CVNc0RaIA:10 a=yGW8d-8WM1kA:10 a=QXwcZi-eDDEA:10 a=MNB8fz3yKCkA:10
 a=hH0qkwBOpLoA:10 a=F6nnEmoIq-42JzzfMaUA:9 a=lQ3VYgOeIU_gyI23:21
 a=wPNLvfGTeEIA:10
Authentication-Results: resimta-po-12v.sys.comcast.net;
	dkim=pass header.d=chicagonettech.com header.b=WG8tuEJv
X-SmarterMail-Authenticated-As: bbarnes@chicagonettech.com
DomainKey-Signature: a=rsa-sha1; c=simple; q=dns;
        d=chicagonettech.com; s=secure;
        h=received:from:to:subject:date:reply-to:message-id:mime-version
          :content-type:x-originating-ip;
        b=xRJYqxPUkXAnUvM3jq20TpTfRaUygbSNzJzdlafR9QrtnlYSU0rg3PrB5MD9V7HFK
          XFoaMpDl9khpgwCWX/sXF785Y3C1FmcLDX2vLkKbH44ofceoWQn9Icl11ip2iAsG9
          ZWBUsX/btn6Vzea6mn9b0eEQqIIs3DbVlXx7P4NsAbphUifRu90vjbsgdXnzXRs81
          U0MUcnbXV+7ZxzNNLXk7Hu+acb51TEVzei9wIeXHJWVl1fh+d2dxi7P+pX1ApHL/n
          Udsdim4w+KymtrlCZnBk+plAVrWMeL45BaimTwGHUhaI6n0gkXILVibaKizgo4itx
          DDMIeDPnjNtUwHVPw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
        d=chicagonettech.com; s=secure;
        h=x-originating-ip:content-type:mime-version:message-id:reply-to
          :date:subject:to:from;
        bh=Qau+ZeOevw3C33hQGqOVy7k2N8J8NHEc8PuJwhGw8p4=;
        b=WG8tuEJvc7+cxKC6pL1YyYihASYt+Wq9r9WWWNHcJAcJTzh6mMoD1aKDDhHGCqTJh
          QN8YvKL4msUqQ63EHBcNXr7avpTUH+wqCYCNYgNKqyxsHpqSwX6RNwLDQ8U7BQdpP
          9ZyFSBz3cg3R2ogu/TADqwvYZbGNQsdrQ7EUCrIvakIk8Yd+dgqOuBvqr3CnuYUGL
          LsLY1l5/z+CTwRZMWCcsdBU2R734bGdlOZ5jqXZ5OU6ktz4hNO1UghEuPcLJqFIde
          piItbaHe3giOTMRtKXk1X0RG5IpyTPvoiu5wOOY9kIVItY6OoC0rnWOdd6u6PVtBn
          i0CO9Z1puilKTFCJw==
Received: by fifi.chicagonettech.com via HTTP;
	Mon, 13 Apr 2015 14:46:50 -0500
From: "Bruce Barnes" <bbarnes@chicagonettech.com>
To: "Test Account" <test@chicagonettech.com>
Subject: SRS Header Rewrite Test #7 - 20140413144637
Date: Mon, 13 Apr 2015 14:46:50 -0500
Reply-To: bbarnes@chicagonettech.com
Message-ID: <d01facce9d3940019e3dafb91f7aa632@chicagonettech.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=a47620ebc7724ce8848b9415a8e7d47e
X-Originating-IP: [173.165.112.149]

This is a multipart message in MIME format.

--a47620ebc7724ce8848b9415a8e7d47e
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

SRS Header Rewrite Test #7 - 20140413144637
  
  Bruce Barnes   
ChicagoNetTech   

e-mail: bbarnes@chicagonettech.com   
website: https://www.chicagonettech.com   
portal: https://portal.chicagonettech.com   
facebook: chicagonettech  

--a47620ebc7724ce8848b9415a8e7d47e
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<span style=3D"font-family: Arial, Helvetica, Sans-Serif; font-size: 12px">=
<div><span style=3D"font-size: 12px;"><span style=3D"font-family: verdana,g=
eneva,sans-serif;"><span style=3D"font-size: 14px;">SRS Header Rewrite Test=
 #7 - 20140413144637</span></span></span></div>

<div>&nbsp;</div>

<div>
<div><span style=3D"font-family: verdana,geneva,sans-serif;"><font style=3D=
"color: rgb(34, 34, 34); font-family: sans-serif; font-size: 12pt;">Bruce B=
arnes</font></span>

<p style=3D"color: rgb(34, 34, 34); line-height: 13px; font-family: Helveti=
ca, Arial, sans-serif; font-size: 9px; margin-top: 0px; margin-bottom: 0px;=
"><span style=3D"font-family: verdana,geneva,sans-serif;"><font style=3D"fo=
nt-family: sans-serif; font-size: 12pt;">ChicagoNetTech</font></span></p>

<p style=3D"color: rgb(34, 34, 34); line-height: 13px; font-family: Helveti=
ca, Arial, sans-serif; font-size: 9px; margin-top: 0px; margin-bottom: 0px;=
"><span style=3D"font-family: verdana,geneva,sans-serif;"><font style=3D"fo=
nt-family: sans-serif; font-size: 12pt;">&nbsp;</font></span></p>

<p style=3D"color: rgb(34, 34, 34); line-height: 13px; font-family: Helveti=
ca, Arial, sans-serif; font-size: 9px; margin-top: 0px; margin-bottom: 0px;=
"><span style=3D"font-family: verdana,geneva,sans-serif;"><font style=3D"fo=
nt-family: sans-serif; font-size: 12pt;">e-mail:&nbsp;<span class=3D"clicka=
ble ClickableEmail inactive" email=3D"bbarnes@chicagonettech.com" style=3D"=
border-width: 0px 0px 1px; border-style: dotted; border-color: rgb(51, 51, =
51); cursor: pointer;">bbarnes@chicagonettech.com</span></font></span></p>

<p style=3D"color: rgb(34, 34, 34); line-height: 13px; font-family: Helveti=
ca, Arial, sans-serif; font-size: 9px; margin-top: 0px; margin-bottom: 0px;=
"><span style=3D"font-family: verdana,geneva,sans-serif;"><font style=3D"fo=
nt-family: sans-serif; font-size: 12pt;">website:&nbsp;<a href=3D"https://w=
ww.chicagonettech.com/" target=3D"_blank">https://www.chicagonettech.com</a=
></font></span></p>

<p style=3D"color: rgb(34, 34, 34); line-height: 13px; font-family: Helveti=
ca, Arial, sans-serif; font-size: 9px; margin-top: 0px; margin-bottom: 0px;=
"><span style=3D"font-family: verdana,geneva,sans-serif;"><font style=3D"fo=
nt-family: sans-serif; font-size: 12pt;">portal: <a href=3D"https://portal.=
chicagonettech.com">https://portal.chicagonettech.com</a></font></span></p>;

<p style=3D"color: rgb(34, 34, 34); line-height: 13px; font-family: Helveti=
ca, Arial, sans-serif; font-size: 9px; margin-top: 0px; margin-bottom: 0px;=
"><span style=3D"font-family: verdana,geneva,sans-serif;"><font style=3D"fo=
nt-family: sans-serif; font-size: 12pt;">facebook: chicagonettech</font></s=
pan></p>
</div>
</div></span>

--a47620ebc7724ce8848b9415a8e7d47e--
I have a couple of support tickets available and will open one later tonight, referring to this post, and ask them to forward the ticket to you.
 
I have no problem giving access to the server and test accounts so you, or they, can replicate the situation.
 
Thanks,
Bruce Barnes
ChicagoNetTech Inc
brucecnt@comcast.net

Phonr: (773) 491-9019
Phone: (224) 444-0169

E-Mail and DNS Security Specialist
Network Security Specialist

Customer Service Portal: https://portal.chicagonettech.com
Website: https://www.ChicagoNetTech.com
Security Blog: http://networkbastion.blogspot.com/

Web and E-Mail Hosting, E-Mail Security and Consulting
0
Lakshan Salgado Replied
So did this get fixed or resolved?
0
Brian Ellwood Replied
Right... After reading all that I need to know!

Reply to Thread