Re[2]: Sig cutoff

2019-09-04 Thread Paul Van Noord
9/4/2019  9:24 PM

Hi Thomas,

On 9/4/2019 Thomas Fernandez wrote:


>> What causes GMX to perceive that they authority to edit ANY message???

TF> First I need someone else using GMX as well to confirm, and then we
TF> can ask them exactly this question.

Could be interesting... Staying tuned in...

TF> --


TF> Cheers,
TF> Thomas.

TF> Message reply created with The Bat! Version 8.8.9 (64-bit)
TF> under Windows 10.0 Build 18362


TF> 
TF> Current version is 8.0.18 | 'Using TBUDL' information:
TF> http://www.silverstones.com/thebat/TBUDLInfo.html


- --
Paul

The Bat! v.8.8.2.8 (BETA) on Windows 7 Pro 64 bit 6.1.7600
No IMAP  No OTFE



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re[2]: Sig cutoff

2019-09-04 Thread Paul Van Noord
9/4/2019  9:13 AM

Hi Tbudl,

On 9/3/2019 tbudl@thebat.dutaint.com wrote:

jlttcu> Hello Thomas Fernandez,

jlttcu> On Tuesday, September 3, 2019, 2:21:55 PM, Thomas Fernandez wrote:

>> ...and now it's gone. Weird.

>> Can someboy lese using GMX please test this, so that we can see
>> whether they cut trailing blanks in order to "improve" customer
>> experience?

jlttcu> I don't use GMX, but looking through other messages on the list,
jlttcu> messages from Chris Wilson and Feli Wilke also appear to come via GMX
jlttcu> (using a different domain name in Chris' case) and are also missing
jlttcu> the space, so it does look like it could be a GMX issue.

jlttcu> Thomas, if you DM me a reply, I can check to see whether the space is
jlttcu> missing from that, which will rule out the list software doing
jlttcu> something to messages via GMX.

What causes GMX to perceive that they authority to edit ANY message???

- --
Paul

The Bat! v.8.8.2.8 (BETA) on Windows 7 Pro 64 bit 6.1.7600
No IMAP  No OTFE



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re[2]: Sig cutoff

2019-09-03 Thread Chris Wilson

Hello Thomas,

On Tuesday, September 3, 2019,  you wrote:

TF> Hello Thomas,

TF> On Tue, 3 Sep 2019 20:09:05 +0700 GMT (03-Sep-19, 20:09 +0700 GMT),
TF> Thomas Fernandez wrote:

>> Hello jb,

>> On Tue, 3 Sep 2019 09:26:45 +0100 GMT (03-Sep-19, 15:26 +0700 GMT),
>> jb_lists...@trink.co.uk wrote:

>>> Hello Thomas Fernandez,

>>> On Monday, September 2, 2019, 2:28:46 AM, Thomas Fernandez wrote:

 Funny thing, this: The cut-off works when I reply to your message, but
 not when I reply to my own. I double-checked, and yes, there is one
 black after the two dashes in my template...

 Please try to reply to your own message and see whether it works fine.

 --

>>> It appears from my message thread in TB (v8.8) that Thomas' cut mark
>>> is missing the space (I've copied it into a text editor to
>>> double-check) and Jack's is correct.

>>> Jack's messages are therefore quoting correctly, and Thomas' aren't.

>> The blank is definitely in the template, please see attached. I also
>> checked when creating this reply.

>> --

TF> ...and now it's gone. Weird.

TF> Can someboy lese using GMX please test this, so that we can see
TF> whether they cut trailing blanks in order to "improve" customer
TF> experience?

TF> --


TF> Cheers,
TF> Thomas.

TF> Message reply created with The Bat! Version 8.8.9 (64-bit)
TF> under Windows 10.0 Build 18362


TF> 
TF> Current version is 8.0.18 | 'Using TBUDL' information:
TF> http://www.silverstones.com/thebat/TBUDLInfo.html



I  checked before posting this, delimiter is present, two dashes and a
space.



-- 

Chris Wilson

"Using The Bat! v5.8.10 on Windows 7 6.1 Build 7601 Service Pack 1"








-- 



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html