The only thing that displayed wrong for me was the From:
Subject was fine.
Using Outlook 2007
-Original Message-
From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On
Behalf Of =?iso-2022-jp?Q?=1B$B2f$
Sent: Thursday, April 22, 2010 12:30 PM
To: twsocket@elists.org
S
Jeff Hamblin wrote:
> On 4/22/2010 9:29 AM, Arno wrote:
>> Hi,
>>
>> This is a test e-mail sent with v7 MailSnd demo and a modified/fixed
>> TSmtpCli. ...
>
>
> I'm running Thunderbird 3.04 on Win7x64. No extra stuff installed.
>
> The message and the attached file came through and displayed we
On 4/22/2010 9:29 AM, Arno wrote:
> Hi,
>
> This is a test e-mail sent with v7 MailSnd demo and a modified/fixed TSmtpCli.
> ...
I'm running Thunderbird 3.04 on Win7x64. No extra stuff installed.
The message and the attached file came through and displayed well.
The only thing that looked bad
Arno Garrels wrote:
> Hi,
>
> Well, the subject line has been refolded for some reason, don't know
> why?
Of course due to a blind MTA prefixing the subject with "Re:[twsocket]"
which destroys the proper MIME encoding.
--
Arno Garrels
--
To unsubscribe or change your settings for TWSocket m
Hi,
Well, the subject line has been refolded for some reason, don't know why?
Here's what was actually sent:
Subject: =?iso-2022-jp?Q?TSmtpCli test =1B$B$$$m$O$K$[$X$I!!$A$j$L$k$r2f?=
=?iso-2022-jp?Q?=1B$B2f$,@$C/$>=1B(B =1B$B>o$J$i$`2f$,@$C/$>=1B(B ?=
=?iso-2022-jp?Q? =1B$B>o$J$i$`2f$,@$C/$>
Hi,
This is a test e-mail sent with v7 MailSnd demo and a modified/fixed TSmtpCli.
The charset is MBCS "iso-2022-jp", those MBCS were not properly supported by
TSmtpCli including UTF-7. Especially the MIME inline encoding with folded
header
lines are a nightmare to code with those charsets. In
>The safest way is to PostMessage a custom message from SessionClosed event
>and reconnect from the corresponding event handler.
Well, that's exactly what I'm doing:
if (not FInternalClose) and (FState in [csConnected, csRequesting,
csReceivingData]) then
PostState(csReconnect);
So you re
So what's the right and proper way to reconnect a socket? Should I start
reconnecting only from SocketSessionClosed?
The safest way is to PostMessage a custom message from SessionClosed event
and reconnect from the corresponding event handler.
--
francois.pie...@overbyte.be
The author of the
Good morning to all,
I have done some investigations and noticed one interesting thing: the error
appears only when the socket handle is equal to previous. Here's the log:
(SetState is my procedure to change client's state, and I also added to
TWSocket code two log writes: "TCustomWSocket.Connec
