X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=115-188-44-54.jetstream.xtra.co.nz;
X-Received: from [10.0.0.166] (115-188-44-54.jetstream.xtra.co.nz [115.188.44.54])
by netwin.co.nz (SurgeMail 7.3f) with ESMTP (TLS) id 5841073-1391920
for <surgemail-list@netwin.co.nz>; Thu, 25 Jan 2018 23:56:26 +0000
X-Return-Path: surgemail-support
Subject: Re: [SurgeMail List] Word attachment corruption
To: surgemail-list@netwin.co.nz
References: <366135e2-5e96-eca8-e984-a84831019a4b@eton.ca>
<869656bb-6fbb-7d20-3038-82f19e220d9e@netwinsite.com>
<0a71d129-aa63-7280-f035-b09295fb1ed8@eton.ca>
From: surgemail-support
Message-ID: <3369f7bc-556e-7fad-b021-ebb72f157583@netwinsite.com>
Date: Fri, 26 Jan 2018 12:56:23 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <0a71d129-aa63-7280-f035-b09295fb1ed8@eton.ca>
Content-Language: en-US
X-Authenticated-User: surgemail-support
X-Rcpt-To: <surgemail-list@netwin.co.nz>
X-SpamDetect: : 0.000000
X-Info: aspam skipped due to (g_smite_skip_relay)
X-Encryption: SSL encrypted
X-MyRbl: Color=Yellow Age=2 Spam=0 Notspam=0 Stars=0 Good=0 Friend=12 Surbl=0 Catch=0 r=0 ip=115.188.44.54
X-IP-stats: Incoming Last 0, First 2, in=54, out=0, spam=0 ip=115.188.44.54
List-Unsubscribe: <mailto:surgemail-list-leave@netwin.co.nz?subject=unsubscribe>
X-Mailing-List: surgemail-list@netwin.co.nz
List-ID: <surgemail-list@netwin.co.nz>
Precedence: bulk
Reply-To: surgemail-list@netwin.co.nz
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Well that's a strange one.
In step 3), find the email message that contains the docx corrupt
file, and send me the raw message file off the server.
e.g.
tellmail path user@xyz.com
cd (path)
cd mdir
cd new
find "docx" * (find the right message file)
zip it up, and email it to me.
surgemail-support@Netwinsite.com
ChrisP
On 26/01/2018 12:47 p.m., Neil Herber
(nospam) wrote:
Results of initial tests. (all IMAP services)
1) Use Windows Thunderbird client to send a .doc and .docx file
from one SM account to another - works fine.
2) Use Gmail webmail to send a .doc and .docx file to a SM
account - Read mail with TB client and the .docx has been
renamed "Part 1.3", but if I rename it to "Part 1.docx" it opens
fine in Word .
3) Use TB client to send both files via Gmail SMTP to a SM
account. Read files in TB client and the .docx file is corrupted
and will not open, the .doc file is fine. Use Surgeweb client to
download both files from the same email, and they are both fine.
My brain hurts, and I cannot figure out what is going on.
Possible interference from AV software? Not likely because
there are NO log entries for any actions on those emails. Just
FYI, I run Avira Pro and Malwarebytes Pro on the mail server.
Neil
On 2018-01-25 3:27 PM,
surgemail-support wrote:
As a rule of thumb, surgemail doesn't modify the contents of
messages at all.
So, most likely, this isn't happenning :-)
So... the trick will be to figure out what is happenning that
looks exactly like that but isn't :-). My guess is it's
really something at the sending or receiving end that is going
on, it could be the email client at either end...
First simplify and eliminate stuff.
1) Send the problem file to yourself. So it's sent and
received by the same email client. Does it get corrupt?
2) If it does get corrupt, run 'diff or fc' on the tewo
files, and send me the results.
3) Most likely it won't get corrupt, so then try with
different email clients and source/destination until you find
which is the key factor.
Let me know what you discover.
ChrisP.
On 26/01/2018 8:52 a.m., Neil
Herber (nospam) wrote:
My users are finding that Word .docx attachments get corrupted while the
same file saved as a .doc file (old Word) gets through fine.
Any suggestions???
SurgeMail Version 7.3e2-2, Built Sep 15 2017 10:35:20, Platform Windows
(Surgeweb Enabled)
Neil
--
I'd really appreciate it if you could take a moment to
like us on FaceBook, thanks
heaps! ChrisP.
--
Neil Herber
--
I'd really appreciate it if you could take a moment to
like us on FaceBook, thanks heaps! ChrisP.