Moderators: TrackerSupp-Daniel, Tracker Support, Vasyl-Tracker Dev Team, Sean - Tracker, Chris - Tracker Supp, Tracker Supp-Stefan, Ivan - Tracker Software, Andrew - Tracker Support, Tracker - Clarion Support, John - Tracker Supp, Support Staff, moderators
Because the problem is intermittent, it is hard to isolate, and once it happens, the evidence is further corrupted by the anti-spam headers inserted by the various mail processing agents. So I guess I'm wondering whether this problem has ever been reported before and whether you have any advice on how to resolve it.
Here's an excerpt of what the problem looks like when the email is received (with the actual customer domains xxxxx'd out):
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on
X-Spam-Status: No, score=-0.5 required=5.0 tests=BAYES_00,FORGED_RCVD_HELO,
Received: from unknown (HELO server1.xxxxxx.loc) (220.127.116.11)
by mxavas13.fe.aruba.it with SMTP; 4 Jun 2007 14:01:41 -0000
Received: from friend ([192.168.0.2]) by server1.xxxxxx.loc with Microsoft
Mon, 4 Jun 2007 16:04:18 +0200
Subject: FT 1179 31/05/07
X-Mailer: netlib30 v. 3.50.0100
X-OriginalArrivalTime: 04 Jun 2007 14:04:18.0078 (UTC) FILETIME=[3DDEC3E0:01C7A6B1]
Date: 4 Jun 2007 16:04:18 +0200
- Site Admin
- Posts: 8204
- Joined: Tue Jun 29, 2004 10:34 am
- Location: Vancouver Island - Canada
This is going to be very difficult for us trace and help with remotely - it seems that the issue is most likely due to some local settings with the users MS SMTP server setup - but exactly what the issue is .....
If we thought it would help - we could install MS SMTP server locally - but duplicating the issue is not going to be easy - if we can do so at all without being able to exactly replicate their installation which of course is impossible to do locally.
Could you arrange for such a user to send to us directly several emails to see if one or more arrive displaying this issue please ?
If so - please email to firstname.lastname@example.org with a link within the email body back to this forum message for reference.
Also another possible work around which may or may not be acceptable - use the 'email.zip' method provided to wrap the files in a zip archive - this could possibly help to ensure they are embedded without corruption.