TOPIC:

We are getting strange header information below the email message from This email address is being protected from spambots. You need JavaScript enabled to view it. when sending to This email address is being protected from spambots. You need JavaScript enabled to view it. and This email address is being protected from spambots. You need JavaScript enabled to view it.. See attached file.

2014
Received: from edgsmgps01.fairfaxcounty.gov (edgsmgps01.fairfaxcounty.gov
[166.94.15.27]) by toastmastersclubs.org (8.14.4/8.14.4) with ESMTP id
s1RFd9b5006209 for <This email address is being protected from spambots. You need JavaScript enabled to view it.>; Thu, 27 Feb 2014
15:39:09 GMT
DKIM-Signature:
X-AuditID: a65e0f19-f79716d000005f27-c4-530f5c1d69b6
Received: from ffxexcgc02.FFX.CO.FAIRFAX.VA.US (Unknown_Domain
[10.171.32.24]) by edgsmgps01.fairfaxcounty.gov (Symantec Messaging Gateway) with SMTP id E6.6F.24359.D1C5F035; Thu, 27 Feb 2014 10:39:09 -0500 (EST)
Received: from FFXEXMPS03.FFX.CO.FAIRFAX.VA.US ([169.254.3.175]) by ffxexcgc02.FFX.CO.FAIRFAX.VA.US ([10.171.32.24]) with mapi id 14.03.0158.001; Thu, 27 Feb 2014 10:39:08 -0500

This issue started on Feb. 21st and again Feb. 27th.
Any reasons what caused this?

That is all issued by your local mail server, you need to talk to your IT people.

Brian,

Thank you for your response.

We are still having issue sending messages to This email address is being protected from spambots. You need JavaScript enabled to view it. and This email address is being protected from spambots. You need JavaScript enabled to view it.. We noticed the email messages leave our SMTP gateway with a subject when it then sent out by the toastmasters server, they arrive without a subject.

The message coming from members looks like it is triggering your spam assassin anti-spam software to modify the message header by possibly inserting a blank line in front of it and therefore causing the problem that we are seeing.

Would you please check your SpamAssassin 3.3.1 on Toastmastersclubs.org and modify the header?.

Thank you,
Tai

Tai,

My apologies for your problem and any inconvenience. I may have made a change to the email system on that date that did not work well.

There have been a number of changes to the email system since the date you mention.

Have you tried sending an email to the members or officers list lately?

We have been troubleshooting on the mail server side since Friday. I and other officers have been sending emails to members and officers list again this morning and the same issue occur.

We noticed this issue started on Feb 18th.
Has this issue been resolved on the Toastmasters email system?

I made a few changes tonight that may impact your situation.

Because of the wide variety of email provider and email messages I will not know for sure whether you are still having an issue until you try to send an email. Sorry, but that is just one of the challenges of working with the email system.

If you are still having a problem, please post back here with specifics--email from, to, subject, date/time, etc. Just saying "I still have a problem" is not very helpful and will not give me the information I need to investigate further.

Thank You SteveTheTechie!
We will test it out and provide a response. We appreciated your help.

A test was sent out to This email address is being protected from spambots. You need JavaScript enabled to view it. on Wed. 3/5/2014 at 8:40 AM, the members received the email. The email they received was not formatted correctly with raw html text (see below). The changes you made last night 3/6/2014 11:56 PM did not work for us.

---

Original Message

---

From: This email address is being protected from spambots. You need JavaScript enabled to view it. [This email address is being protected from spambots. You need JavaScript enabled to view it.]
Sent: Wednesday, March 05, 2014 8:40 AM
Subject:

2014
Received: from edgsmggc01.fairfaxcounty.gov (edgsmggc01.fairfaxcounty.gov
[166.94.6.104]) by toastmastersclubs.org (8.14.4/8.14.4) with ESMTP id
s25De9kk026870 for <This email address is being protected from spambots. You need JavaScript enabled to view it.>; Wed, 5 Mar 2014
13:40:09 GMT
DKIM-Signature:
X-AuditID: a65e0667-f79a56d000001c44-76-53172939d01b
Received: from ffxexcps04.FFX.CO.FAIRFAX.VA.US (Unknown_Domain [10.129.0.53]) by edgsmggc01.fairfaxcounty.gov (Symantec Messaging Gateway) with SMTP id B8.90.07236.93927135; Wed, 5 Mar 2014 08:40:09 -0500 (EST)
Received: from FFXEXMGC01.FFX.CO.FAIRFAX.VA.US ([169.254.1.225]) by ffxexcps04.FFX.CO.FAIRFAX.VA.US ([10.129.0.53]) with mapi id 14.03.0158.001; Wed, 5 Mar 2014 08:40:08 -0500
From: "Toastmasters Club 9807 on behalf of Todd Overstreet"
<This email address is being protected from spambots. You need JavaScript enabled to view it.>
To: "This email address is being protected from spambots. You need JavaScript enabled to view it." <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Subject: Test
Thread-Topic: Test
Thread-Index: Ac84eGykEr/2u2VwTsKV9ykYuJHdGA==
Date: Wed, 5 Mar 2014 13:40:08 +0000
Message-ID:
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.175.4.5]
Content-Type: multipart/alternative; boundary="_000_C7A6706AFB0BBC44A4ECC4860830A2C732B70E1Fffxexmgc01FFXCO_"
MIME-Version: 1.0
X-Brightmail-Tracker:
H4sIAAAAAAAAA11Ta2xLYRj29bTdp+1nZ13XfqtpOK5jagQhGRb8IIbRuISsc7qetY2uXc7p
WTYiYf8sEpcwNGGTLWUsEdsPYwR1H4shE7eQuMWduEcQ39fTzpl/z3ne932e5837HciYa6Ed
BkIRQQzxQU5v0Bo2DZgyfnquzZV/rM0x7eLBd5pCMO/ejz36YrDKWODhI1WugC80YeYao//b
7ru6yi5zdW/rcWYjuM3WgYEQs5Nxd8+WNAVbcc+jo/o6YIBmthfg2NYOrfLRDvDN9jYt7dKz
BbjlWJSpAxBa2CX417WRlM5kEa5vfpwQsrBmvP/iFUbBTnz6Z6eeYi07Ah++0ZLAiF2Otzzc
q6MYEOPvXa0aihnWhu8/a9AogVjcfOoGo+As/OrpH52CHbi+dp9e6Q/jD3fr0xTNDHx17zPt
NmCOqqSiqraoqk3h83Bj5ye9gsfh2IE3TApfP/tUo+YbQdphkCN4fVKFz1eWP9FZzgfEcr66
LCyHIjVOX7iqDZCLxNx6Xwc4f7YgDlgIOBN6Ca0us46vkmoq4mAx1HBZaMIYm8s8yBP21vh5
yV8qykFB4ixon5HQqI/2yMG1nANp7pB5Wx8ryVJloCwQlqVSWQzGAYYMGd1qo6NevmadIIYV
wTgYDLWcDVU7yDzr4yPCWkGoFMRUdSWEHEY6GiVDFHxCdXkgGEmVydyT0aTCqiuJQMPQLBrI
ri78n0kDB9JgBrtFEkJeQeTlCFmHPMZSibzGOCiCJpLZQK2RVMlXEDZpm4naqK0pxSYsh6Bz
1NKaIvvbdQGX3YbcibS0wy+H+tawW1HRbzKaripQSftQVPKc8Nkqvr/qazCfXC8TZdCQJvLL
/ctoRu3UzJgkExFz0CUaMSvJ/a9VRM5uQasHJRaO8BH1wifooCnFJhfuUBZOkv3l7BvBpmjR
kV0G9xRn8P0GboW3ac4v59vjO7afzNzPTnXPMF5Y2LLIv1SXJedKB7o9DuvmxctKms7MeH37
UUPj3LwLsHX39mEBNm/X+O5Yw9vR6Yfe2xbkD780aWdnS8XXd5fXM57ZRxCf/bl41As8p/FW
1ZcHvZorqwoP6UzFH8+190SPNnNayc9PHMuIEv8XiPASWpUEAAA=
X-Spam-Status: No, score=0.0 required=5.0 tests=HTML_MESSAGE,RP_MATCHES_RCVD
autolearn=unavailable version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on toastmastersclubs.org
X-Loop:
Reply-To: This email address is being protected from spambots. You need JavaScript enabled to view it.
CC:

--_000_C7A6706AFB0BBC44A4ECC4860830A2C732B70E1Fffxexmgc01FFXCO_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Wednesday at 840 AM

Todd W. Overstreet
Information Technology
703-324-3652


--_000_C7A6706AFB0BBC44A4ECC4860830A2C732B70E1Fffxexmgc01FFXCO_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> >
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> <p class=3D"MsoNormal">Wednesday at 840 AM<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Todd W. Overstreet<o:p></o:p></p> <p class=3D"MsoNormal">Information Technology<o:p></o:p></p> <p class=3D"MsoNormal">703-324-3652<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>

--_000_C7A6706AFB0BBC44A4ECC4860830A2C732B70E1Fffxexmgc01FFXCO_--

What happens if you send out the email as text or as Rich text and not html?

Tested with sending out as text and as Rich text. Same issue.
Not all members are having this issue.

Is there a common email client?

Are all the people having problems using the same email client and version?

If the email was sent as plain text how did you get html in the delivered email?

Sorry for my delay with this response.

Yes, we all are on the same email client, Outlook 2010. The email was sent as plain text, delivered as unformatted with html code.

We saw there is an extra space in the header of the message above "2014". please see attached files. We found many anti-spam programs sometimes caused this problem. It causes the header to malformed in the email message. Members are still having the same issue with sending email to This email address is being protected from spambots. You need JavaScript enabled to view it. on as behalf of...

X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on

.toastmastersclubs.org



2014

Received: from edgsmgps01.fairfaxcounty.gov (edgsmgps01.fairfaxcounty.gov

[166.94.15.27]) by toastmastersclubs.org (8.14.4/8.14.4) with ESMTP id

s27IDbuL023281 for <This email address is being protected from spambots. You need JavaScript enabled to view it.>; Fri, 7 Mar 2014

18:13:37 GMT

I have worked with our exchange admin and this is what we found in the message from toastmasters to our domain.



The header from the capture shows a blank line / space in the middle of the data portion. In message headers this space indicates that the body of the message should start. In this case it looks like the spam assassin line is followed by the space, then the body starts with 2014 and then more received headers. The formatting is not correct and that is happening before it reaches the message Gateway. This can cause the remaining headers to be treated as body data. Members are still having email issue, received email from This email address is being protected from spambots. You need JavaScript enabled to view it. is not formatted correctly. Please help!

I am capturing emails for club 9807 to a file to allow for closer examination.

Can you please resend the email in question so I can take a look at the incoming email?
(let me know when you have resent it)

email in question just sent. Please take a look at the email sent on 3/14 2:38 PM

Ok, I have that email. Let me do some testing on it.

Ok, I made a small change.

Can you please try sending your email again and let us know your results?

I never had any issues with sending out email to members so I won't be a good candidate to test it out. I asked the people that were having this issue to test by sending the email, but haven't gotten a response. I hope to get the result to you soon.

Thank you, the email issue has been resolved with the small change that you made on your side. What change did you make to resolve this issue?

We use an email code library that is starting to show its age. (11 yrs old) It cannot handle parsing the "From" lines in the header that have a space immediately after the "From" instead of a colon. I did not realize that was the case when I started working with the email system, and I inadvertently removed a workaround that was in place for that. Now that I understand the limitations of the email library we are using, I put the workaround back in place.