The problem has been identified and mostly fixed. It is
believed to only be
affecting a small number of systems.
The bug is related to individual SMTP message headers being
sent one TCP
packet at a time or even being spread across several TCP
packets. It would
seem that this problem has been around for a very long time,
so we are not
sure why it has only just become apparent in the latest
builds. The
suspicion is that something was masking this in the TCP
buffering so that
only larger packets were being sent previously.
A 3.8k3 patched production release build has been done. This
fixes the
problem where the headers are being sent one tcp packet at a
time which
should cover most if not all problem cases that are actually
being seen on
systems. This can be downloaded from:
ftp://ftp.netwinsite.com/pub/surgemail/
Tomorrow we will repatch with a final version of this fix
that will
completely fix this, and update the remaining builds that
have not been
updated tonight. This at least should be able to get
everyone struggling
with this issue be able to fix their system.
This is the only change in the 3.8k3 build over 3.8k2 and
you only need the
surgemail binary. If you are not experiencing problems with
message header
corruption I would recommend you wait until tomorrows builds
before
upgrading.
Marijn
----- Original Message -----
From: "Support Surgemail CP"
<surgemail-support netwinsite.com>
Newsgroups: netwin.surgemail
Sent: Tuesday, August 28, 2007 10:04 AM
Subject: Re: [SurgeMail List] Help with Webmail issue
> Thanks for reporting this:
>
> Could you send me your surgemail.ini and tellmail
status output and let
> me know what platform you are on.
> Also is the 'recipient' addresses a direct address or
is it forwarded
> via another account with a redirect ?
>
> Thanks.
>
> ChrisP.
>
>
>
> Jake Steidl wrote:
>>> This message is in MIME format. Since your mail
reader does not
>>> understand
>>>
>> this format, some or all of this message may not be
legible.
>>
>> --B_3270888435_15219144
>> Content-type: text/plain;
>> charset="US-ASCII"
>> Content-transfer-encoding: 7bit
>>
>> Hello all,
>>
>> Since the last upgrade the other day, 3.8k2-2
Windows, all people
>> emailing
>> from webmail are having this issue. All emails on
the recipient end are
>> seeing weird stuff.
>>
>> Example:
>>
>> <--Start Email
>> om
>> st
>> 1s
>> 00
>> t>
>> 0
>> 1"
>> Date: Fri, 24 Aug 2007 19:06:14 -0400
>> Subject: (No subject header)
>> Message-ID: <1187996774_5739pop.mountainair.net>
>> X-Authenticated-User: usermountainair.net
>> X-SpamDetect: : 0.000000
>> X-Info: aspam skipped due to
(g_smite_skip_trusted)
>>
>> Test
>>
>> End Email-->
>>
>>
>>
>> The above is what is coming through as the body of
the message. This is
>> not
>> view source.
>> The subject is not coming through and it is adding
all sorts of weird
>> characters. Almost like all the header info, etc.
is coming through. The
>> test above was an email to myself to verify the
issue.
>>
>> Any ideas on how to fix this?
>>
>> Thanks,
>>
>> Jake
>>
>>
>> --B_3270888435_15219144
>> Content-type: text/html;
>> charset="US-ASCII"
>> Content-transfer-encoding: quoted-printable
>>
>> <HTML>
>> <HEAD>
>> <TITLE>Help with Webmail issue</TITLE>
>> </HEAD>
>> <BODY>
>> <FONT FACE=3D"Verdana, Helvetica,
Arial"><SPAN
>> STYLE=3D'font-size:12.0px'>Hello=
>> all,<BR>
>> <BR>
>> Since the last upgrade the other day, 3.8k2-2
Windows, all people
>> emailing =
>> from webmail are having this issue. All emails on
the recipient end are
>> seei=
>> ng weird stuff.<BR>
>> <BR>
>> Example:<BR>
>> <BR>
>> <--Start Email<BR>
>> om<BR>
>> st<BR>
>> 1s<BR>
>> 00<BR>
>> t><BR>
>> 0<BR>
>> 1"<BR>
>> Date: Fri, 24 Aug 2007 19:06:14 -0400<BR>
>> Subject: (No subject header)<BR>
>> Message-ID: <<FONT
>>
COLOR=3D"#0000FF"><U>1187996774_5739pop.mountainair.ne=
>> t</U></FONT>><BR>
>> X-Authenticated-User: <FONT
>> COLOR=3D"#0000FF"><U>usermountainair.net</U></FO=
>> NT> <BR>
>> X-SpamDetect: : 0.000000 <BR>
>> X-Info: aspam skipped due to
(g_smite_skip_trusted)<BR>
>> <BR>
>> Test<BR>
>> <BR>
>> End Email--><BR>
>> <BR>
>> <BR>
>> <BR>
>> The above is what is coming through as the body of
the message. This is
>> not=
>> view source.<BR>
>> The subject is not coming through and it is adding
all sorts of weird
>> chara=
>> cters. Almost like all the header info, etc. is
coming through. The test
>> abo=
>> ve was an email to myself to verify the
issue.<BR>
>> <BR>
>> Any ideas on how to fix this?<BR>
>> <BR>
>> Thanks,<BR>
>> <BR>
>> Jake<BR>
>> </SPAN></FONT>
>> </BODY>
>> </HTML>
>>
>>
>> --B_3270888435_15219144--
>>
>>
>>
>>
>
>
|
