Occasionally a message displays in Tbird's message pane with a much
larger font size than others.
I've narrowed it down to 7bit encoding, and the major culprit is Forte
Agent.

There appears to be no setting to handle this.

Ed

Ed,

> Occasionally a message displays in Tbird's message pane with a much larger
> font size than others.
> I've narrowed it down to 7bit encoding,

> There appears to be no setting to handle this.

Maybe this helps :

https://askubuntu.com/questions/156645/thunderbird-font-size-varies-with-encoding-in-content-type-header

(DDG search : TBird 7bit encoding font size)

Regards,
Rudy Wieser

R.Wieser wrote:
> Ed,
>
>> Occasionally a message displays in Tbird's message pane with a much larger
>> font size than others.
>> I've narrowed it down to 7bit encoding,
>
>> There appears to be no setting to handle this.
>
> Maybe this helps :
>
> https://askubuntu.com/questions/156645/thunderbird-font-size-varies-with-encoding-in-content-type-header
>
> (DDG search : TBird 7bit encoding font size)
>
> Regards,
> Rudy Wieser
>
>

That might have been useful 12 years ago, Rudy, with Tbird 13.

Ed

Ed Cryer <ed@somewhere.in.the.uk> wrote:

From your headers:
> Content-Transfer-Encoding: 7bit
> User-Agent: Mozilla Thunderbird

> Occasionally a message displays in Tbird's message pane with a much
> larger font size than others.
> I've narrowed it down to 7bit encoding, and the major culprit is Forte
> Agent.
>
> There appears to be no setting to handle this.

But your own client, Thunderbird, per your configuration of it, is
adding the same header. It wouldn't be just Agent adding this header.
It also be for all similarly configured Tbird users.

Go to the alt.comp.software.thunderbird newsgroup (where you should have
posted) to see lots of posts with the "Content-Transfer-Encoding: 7bit"
header. Do all those posts also look wrong sized, too?

Ed Cryer <ed@somewhere.in.the.uk> wrote:

> R.Wieser wrote:
>
>>> Occasionally a message displays in Tbird's message pane with a much
>>> larger font size than others. I've narrowed it down to 7bit
>>> encoding,
>>
>>> There appears to be no setting to handle this.
>>
>> Maybe this helps :
>>
>> https://askubuntu.com/questions/156645/thunderbird-font-size-varies-with-encoding-in-content-type-header
>
> That might have been useful 12 years ago, Rudy, with Tbird 13.

Your response is unclear, plus you didn't identify your Tbird version.
Does your response mean you tried, but the effects were nil, or that
those settings are not available (where described or elsewhere) in
whatever version of Tbird you are using?

The User-Agent header in your articles is non-standard. You must be
inserting your own UA header that merely has "Mozilla Thunderbird".

The UA headers for typical Tbird users has a much longer string, and one
which may indicate the version of Tbird. Better to explicitly declare
your version.

https://www.useragentstring.com/pages/Thunderbird/
Alas, doesn't show UAs for later Tbird versions.

https://explore.whatismybrowser.com/useragents/explore/software_name/thunderbird/
Only a partial list. Have to download their database list to see all,
but you have to buy their full list ($50 AUD). No thanks.

I don't see your issue is with Windows 10, but with Tbird. Since the
artifact of which you ask is in Thunderbird, probably a better newsgroup
to ask would be alt.comp.software.thunderbird. When looking at the UA
headers there, you'll see not just Tbird users post there.

Since the referenced forum article was for using Tbird on Ubuntu, it may
not apply to you on Windows. There are some differences in Tbird on
Windows versus Linux.

On 10/13/2023 2:43 PM, Ed Cryer wrote:
> Occasionally a message displays in Tbird's message pane with a much larger font size than others.
> I've narrowed it down to 7bit encoding, and the major culprit is Forte Agent.
>
> There appears to be no setting to handle this.
>
> Ed

I wrote a rant and erased it.

For TBird 115, its frantic user-edits of userchrome.css and prefs.js
are worthy of a rant.

Why are they releasing software, and having the user community
chase it around with broom and dustpan, and userchrome.css edits ?

Paul

VanguardLH wrote:

> The User-Agent header in your articles is non-standard. You must be
> inserting your own UA header that merely has "Mozilla Thunderbird".

That is the standard User-Agent header for TB from v115 (and presumably
onwards).

VanguardLH wrote:

> Go to the alt.comp.software.thunderbird newsgroup (where you should have
> posted) to see lots of posts with the "Content-Transfer-Encoding: 7bit"
> header. Do all those posts also look wrong sized, too?

I agree take it there, post a screenshot of a "normal" and a "big font"
message along with headers from each ... 7bit encoding by itself is
nothing exotic.

On 10/13/2023 3:45 PM, VanguardLH wrote:

>
> The User-Agent header in your articles is non-standard.

The designer-twits removed the version number.

To make it harder for us to help people.

Paul

Ed,

> That might have been useful 12 years ago, Rudy, with Tbird 13.

Damn, I missed that date. :-(

Though, maybe some searching will return a more recent result ? Might
also work better when you include your TBirds version number.

I just did another quick search and found a few other posts in the last few
years related to TBirds fontsize differences. I'm sure you will be able to
find them too.

Regards,
Rudy Wieser

Andy Burns <usenet@andyburns.uk> wrote:

> VanguardLH wrote:
>
>> The User-Agent header in your articles is non-standard. You must be
>> inserting your own UA header that merely has "Mozilla Thunderbird".
>
> That is the standard User-Agent header for TB from v115 (and presumably
> onwards).

Then a poor choice by Mozilla. It does not properly identify the user
agent. They might've as well as have used "An email & newsreader
client". The 2nd referenced article notes the v155 of Tbird is using:

Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:115.0) Gecko/20100101 Thunderbird/115.x.y;

They list similar UA strings going back to Tbird 102. Can't get farther
back without buying their UA database which isn't going to happen.

Thanks for the update, though. One source says Tbird's UA is the long
string, another says the vague short string. I doubt many Tbird users
bother with, or even know about, the UA header, and don't delve into the
config editor to change general.useragent.override. Some more might use
add-ons to change the UA string, but those would be a small percent.

Many posters neglect to give specifics, like the version of whatever OS
or program/app they are asking about. Not always correct to assume they
are using the latest version. The UA header helps when that info is
absent from their posts. Besides the Tbird version, the UA also helps
identify under what OS they are using Tbird since Tbird is multi
platform. In fact, some users refuse to give that info when requested
because they think it is irrelevant, but don't really know. The micky
poster is like that. So getting it when omitted or refused can help
focus the responses.

Changing to the short uninformative UA string isn't going to help with
fingerprinting for a long time. It identifies someone using 115, or
later, of Tbird versus earlier versions. If fingerprinting was the
issue, Mozilla should have defaulted to not adding the UA header at all
to hide Tbird users along with all other users of clients that also
don't report or were configured not to report a UA header.

Apparently there are 2 UA settings (besides the override already
mentioned):

old one: mailnews.headers.sendUserAgent
new one: mailnews.headers.useMinimalUserAgent

For the new one, the default is True, which means, yep, we get the short
and rather useless UA string for Tbird 115+. The first one was there
before, and decided whether or not to even included the UA header, or
not; however, if the override setting was left blank, the effect was the
same, so unclear why 2 settings are needed to omit the UA header. Since
the override setting has been there for, well, perhaps forever then why
wouldn't users concerned with hiding their OS and Tbird version have set
the override setting to empty, or to some vague string? We get another
option that overlaps another option. And both require the user to delve
into the config editor to define. Stupid.

Instead of add the useMinimalUserAgent setting, Mozilla could've just
change the default value of the UA header by setting the override
setting to "Mozilla Thunderbird". Just reuse a setting already there.
Adding more settings that effect the same result just confuses users,
and makes a mess of configuring the UA string. It also means add-on
authors have to account for more than just the override setting. More
work for no real gain.

"Implement configuration to send a minimal User-Agent header, or no
header at all, in sent emails"
https://bugzilla.mozilla.org/show_bug.cgi?id=1114475

VanguardLH wrote:
> Ed Cryer <ed@somewhere.in.the.uk> wrote:
>
> From your headers:
>> Content-Transfer-Encoding: 7bit
>> User-Agent: Mozilla Thunderbird
>
>
>> Occasionally a message displays in Tbird's message pane with a much
>> larger font size than others.
>> I've narrowed it down to 7bit encoding, and the major culprit is Forte
>> Agent.
>>
>> There appears to be no setting to handle this.
>
> But your own client, Thunderbird, per your configuration of it, is
> adding the same header. It wouldn't be just Agent adding this header.
> It also be for all similarly configured Tbird users.
>
> Go to the alt.comp.software.thunderbird newsgroup (where you should have
> posted) to see lots of posts with the "Content-Transfer-Encoding: 7bit"
> header. Do all those posts also look wrong sized, too?

That NG isn't on E-September or aioe.
I did find alt.comp.software.easter-eggs, though.

Don't waste my time with misdirections.

Ed

On 2023-10-14 01:00, Paul wrote:
> On 10/13/2023 3:45 PM, VanguardLH wrote:
>
>>
>> The User-Agent header in your articles is non-standard.
>
> The designer-twits removed the version number.
>
> To make it harder for us to help people.

No, even Alpine defaults now to not saying the version. It is intended
as a security feature, not giving attackers information about what
software you are running.

In Alpine there is a setting for changing this and go back to the
informative string, so perhaps Thunderbird has it as well.

--
Cheers,
Carlos E.R.

Ed Cryer wrote:

> That NG isn't on E-September

It has been since day one, you might need to refresh your groups list.

> or aioe.

Yeah well, *nothing* is on aioe these days ...

On 2023-10-14 15:41, Ed Cryer wrote:
> VanguardLH wrote:
>> Ed Cryer <ed@somewhere.in.the.uk> wrote:
>>
>>  From your headers:
>>> Content-Transfer-Encoding: 7bit
>>> User-Agent: Mozilla Thunderbird
>>
>>
>>> Occasionally a message displays in Tbird's message pane with a much
>>> larger font size than others.
>>> I've narrowed it down to 7bit encoding, and the major culprit is Forte
>>> Agent.
>>>
>>> There appears to be no setting to handle this.
>>
>> But your own client, Thunderbird, per your configuration of it, is
>> adding the same header.  It wouldn't be just Agent adding this header.
>> It also be for all similarly configured Tbird users.
>>
>> Go to the alt.comp.software.thunderbird newsgroup (where you should have
>> posted) to see lots of posts with the "Content-Transfer-Encoding: 7bit"
>> header.  Do all those posts also look wrong sized, too?
>
> That NG isn't on E-September or aioe.
> I did find alt.comp.software.easter-eggs, though.
>
> Don't waste my time with misdirections.

I can see that group in my news server just fine. There is no misdirection.

--
Cheers,
Carlos E.R.

On 2023-10-13 21:18, Ed Cryer wrote:
> R.Wieser wrote:
>> Ed,
>>
>>> Occasionally a message displays in Tbird's message pane with a much
>>> larger
>>> font size than others.
>>> I've narrowed it down to 7bit encoding,
>>
>>> There appears to be no setting to handle this.
>>
>> Maybe this helps :
>>
>> https://askubuntu.com/questions/156645/thunderbird-font-size-varies-with-encoding-in-content-type-header
>>
>> (DDG search : TBird 7bit encoding font size)
>>
>> Regards,
>> Rudy Wieser
>>
>>
>
> That might have been useful 12 years ago, Rudy, with Tbird 13.

It has not changed that much.

In my TH 115, I go to settings, then type "font" in the search box.

Fonts & Colours
Default font: Size: Advanced

Click on advanced, and you will see different font settings for a
variety of "languages". You probably need "Latin", but check. It might
be "Other".

--
Cheers,
Carlos E.R.

Ed Cryer <ed@somewhere.in.the.uk> wrote:
> VanguardLH wrote:
> > Ed Cryer <ed@somewhere.in.the.uk> wrote:
> >
> > From your headers:
> >> Content-Transfer-Encoding: 7bit
> >> User-Agent: Mozilla Thunderbird
> >
> >
> >> Occasionally a message displays in Tbird's message pane with a much
> >> larger font size than others.
> >> I've narrowed it down to 7bit encoding, and the major culprit is Forte
> >> Agent.
> >>
> >> There appears to be no setting to handle this.

Can you post a message-id of a posting with this problem (and of one
without it)?

> > But your own client, Thunderbird, per your configuration of it, is
> > adding the same header. It wouldn't be just Agent adding this header.
> > It also be for all similarly configured Tbird users.
> >
> > Go to the alt.comp.software.thunderbird newsgroup (where you should have
> > posted) to see lots of posts with the "Content-Transfer-Encoding: 7bit"
> > header. Do all those posts also look wrong sized, too?
>
> That NG isn't on E-September or aioe.
> I did find alt.comp.software.easter-eggs, though.
>
> Don't waste my time with misdirections.

Easy does it!

I don't use eternal-september.org and neither does VanguardLH, but
alt.comp.software.thunderbird has existed for quite some time now and
I'm sure others would have complained if eternal-september.org doesn't
carry it.

Are you sure you have refreshed your newsgroups list from the server?

Frank Slootweg wrote:

>>>> Occasionally a message displays in Tbird's message pane with a much
>>>> larger font size than others.
>>>> I've narrowed it down to 7bit encoding, and the major culprit is Forte
>>>> Agent.
>>>>
>>>> There appears to be no setting to handle this.
>
> Can you post a message-id of a posting with this problem (and of one
> without it)?
>

Now, that seems a more rational approach, Frank. I'll gladly follow that.

I've looked at all the messages in this thread right down to your
latest, to which I'm replying. They're all ok except the three from
VanguardLH.

See you,

Ed

Ed Cryer <ed@somewhere.in.the.uk> wrote:
> Frank Slootweg wrote:
>
> >>>> Occasionally a message displays in Tbird's message pane with a much
> >>>> larger font size than others.
> >>>> I've narrowed it down to 7bit encoding, and the major culprit is Forte
> >>>> Agent.
> >>>>
> >>>> There appears to be no setting to handle this.
> >
> > Can you post a message-id of a posting with this problem (and of one
> > without it)?
>
> Now, that seems a more rational approach, Frank. I'll gladly follow that.
>
> I've looked at all the messages in this thread right down to your
> latest, to which I'm replying. They're all ok except the three from
> VanguardLH.
>
> See you,

All look fine to me. But I've set fixed width ('Monospace:') font
(because using proportional spacing is silly on a plain text medium).

N.B. I'm using a (frozen) stone age version of Thunderbird (60.9.0),
so that might/will matter as well.

I don't see anything special in the (Message Source of) VanguardLH's
postings. He has indeed a 'Content-Transfer-Encoding: 7bit' header, but
so have some others, for example Andy Burns and Paul (but they have
different 'Content-Type:' headers (than VanguardLH)).

Perhaps your Thunderbird gets confused by VanguardLH's unneeded [1]
(see my post) but (AFAICT) correct Content-* headers?

[1] "us-ascii" and "7bit" are defaults.

Ed Cryer <ed@somewhere.in.the.uk> wrote:

> VanguardLH wrote:
>> Ed Cryer <ed@somewhere.in.the.uk> wrote:
>>
>> From your headers:
>>> Content-Transfer-Encoding: 7bit
>>> User-Agent: Mozilla Thunderbird
>>
>>> Occasionally a message displays in Tbird's message pane with a much
>>> larger font size than others.
>>> I've narrowed it down to 7bit encoding, and the major culprit is Forte
>>> Agent.
>>>
>>> There appears to be no setting to handle this.
>>
>> But your own client, Thunderbird, per your configuration of it, is
>> adding the same header. It wouldn't be just Agent adding this header.
>> It also be for all similarly configured Tbird users.
>>
>> Go to the alt.comp.software.thunderbird newsgroup (where you should have
>> posted) to see lots of posts with the "Content-Transfer-Encoding: 7bit"
>> header. Do all those posts also look wrong sized, too?
>
> That NG isn't on E-September or aioe.
> I did find alt.comp.software.easter-eggs, though.
>
> Don't waste my time with misdirections.

If a newsgroup doesn't show up that others mention, refresh the
newsgroups list in your NNTP client. Have you tried that yet?

And, yes, alt.comp.software.thunderbird does exist on ES. I also have
an account at ES although it is my backup Usenet provider. My primary
is individual.net. That newsgroup shows on both servers.

AIOE has been dead for a long time, so don't recite that Usenet provider
as to what and what not it has. AIOE has nothing anymore. It's dead.
That you mention AIOE not having a newsgroup when AIOE has been dead for
many months shows you haven't kept up with the news here. The death of
AIOE has been discussed in Usenet. As I recall, inquiries started
showing up around Jan 2023 about AIOE being dead.

Before lambasting someone, especially someone trying to help, check your
facts first. For ES, refresh the groups list in Tbird. Do so for any
other NNTP servers to which your Tbird connect. However, delete the
AIOE server in Tbird since AIOE went dead many months ago.

Frank Slootweg wrote:
> Ed Cryer <ed@somewhere.in.the.uk> wrote:
>> Frank Slootweg wrote:
>>
>>>>>> Occasionally a message displays in Tbird's message pane with a much
>>>>>> larger font size than others.
>>>>>> I've narrowed it down to 7bit encoding, and the major culprit is Forte
>>>>>> Agent.
>>>>>>
>>>>>> There appears to be no setting to handle this.
>>>
>>> Can you post a message-id of a posting with this problem (and of one
>>> without it)?
>>
>> Now, that seems a more rational approach, Frank. I'll gladly follow that.
>>
>> I've looked at all the messages in this thread right down to your
>> latest, to which I'm replying. They're all ok except the three from
>> VanguardLH.
>>
>> See you,
>
> All look fine to me. But I've set fixed width ('Monospace:') font
> (because using proportional spacing is silly on a plain text medium).
>
> N.B. I'm using a (frozen) stone age version of Thunderbird (60.9.0),
> so that might/will matter as well.
>
> I don't see anything special in the (Message Source of) VanguardLH's
> postings. He has indeed a 'Content-Transfer-Encoding: 7bit' header, but
> so have some others, for example Andy Burns and Paul (but they have
> different 'Content-Type:' headers (than VanguardLH)).
>
> Perhaps your Thunderbird gets confused by VanguardLH's unneeded [1]
> (see my post) but (AFAICT) correct Content-* headers?
>
> [1] "us-ascii" and "7bit" are defaults.

All was ok with TB102. This problem arrived with 115.

My current suspect is "us-ascii".
I've tried all the 115 display settings, to no avail.

Ed

VanguardLH wrote:
> Ed Cryer <ed@somewhere.in.the.uk> wrote:
>
>> VanguardLH wrote:
>>> Ed Cryer <ed@somewhere.in.the.uk> wrote:
>>>
>>> From your headers:
>>>> Content-Transfer-Encoding: 7bit
>>>> User-Agent: Mozilla Thunderbird
>>>
>>>> Occasionally a message displays in Tbird's message pane with a much
>>>> larger font size than others.
>>>> I've narrowed it down to 7bit encoding, and the major culprit is Forte
>>>> Agent.
>>>>
>>>> There appears to be no setting to handle this.
>>>
>>> But your own client, Thunderbird, per your configuration of it, is
>>> adding the same header. It wouldn't be just Agent adding this header.
>>> It also be for all similarly configured Tbird users.
>>>
>>> Go to the alt.comp.software.thunderbird newsgroup (where you should have
>>> posted) to see lots of posts with the "Content-Transfer-Encoding: 7bit"
>>> header. Do all those posts also look wrong sized, too?
>>
>> That NG isn't on E-September or aioe.
>> I did find alt.comp.software.easter-eggs, though.
>>
>> Don't waste my time with misdirections.
>
> If a newsgroup doesn't show up that others mention, refresh the
> newsgroups list in your NNTP client. Have you tried that yet?
>
> And, yes, alt.comp.software.thunderbird does exist on ES. I also have
> an account at ES although it is my backup Usenet provider. My primary
> is individual.net. That newsgroup shows on both servers.
>
> AIOE has been dead for a long time, so don't recite that Usenet provider
> as to what and what not it has. AIOE has nothing anymore. It's dead.
> That you mention AIOE not having a newsgroup when AIOE has been dead for
> many months shows you haven't kept up with the news here. The death of
> AIOE has been discussed in Usenet. As I recall, inquiries started
> showing up around Jan 2023 about AIOE being dead.
>
> Before lambasting someone, especially someone trying to help, check your
> facts first. For ES, refresh the groups list in Tbird. Do so for any
> other NNTP servers to which your Tbird connect. However, delete the
> AIOE server in Tbird since AIOE went dead many months ago.

I'm well aware of aieo's demise, I have been for weeks. But the
news-server is still installed on one of my backup PCs, and I can survey
the last group list there.

Now, did you think of that before you jumped to your hasty conclusions
based on flimsy evidence? And before you rushed in with your arrogant,
overweening piece of dialogue?

Ed

Ed Cryer <ed@somewhere.in.the.uk> wrote:

> Frank Slootweg wrote:
>
>>>>> Occasionally a message displays in Tbird's message pane with a much
>>>>> larger font size than others.
>>>>> I've narrowed it down to 7bit encoding, and the major culprit is Forte
>>>>> Agent.
>>>>>
>>>>> There appears to be no setting to handle this.
>>
>> Can you post a message-id of a posting with this problem (and of one
>> without it)?
>>
>
> Now, that seems a more rational approach, Frank. I'll gladly follow that.
>
> I've looked at all the messages in this thread right down to your
> latest, to which I'm replying. They're all ok except the three from
> VanguardLH.

From the headers of their posts in this thread:

VanguardLH (40tude Dialog)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Frank (tin)
Content-Type header is absent.
Content-Transfer-Encoding header is absent.

Ed Cryer (Thunderbird)
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Andy (Thunderbird)
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Paul (Ratcatcher, perhaps bogus UA string)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Carlos (Thunderbird)
Content-Transfer-Encoding: 7bit

Am I, VanguardLH, the only one that incites the font size problem in
your setup of Thunderbird? I cannot see how some posters using the same
"Content-Transfer-Encoding: 7bit" header cause a font sizing problem for
you, but other posters also using that same header that do not cause a
font sizing problem, could be caused by posters using the same header.
It's there: a font size problem. It's not there: no font size problem.

What is different, if it is just my posts that cause the font sizing
problem for you, is the Content-Type header. My client declares it uses
plain text (ASCII), and nothing fancier (that was added later), like
UTF-8. The other posters' clients declare using UTF-8. I don't need to
use UTF-8, because I never use characters outside the ASCII-7 character
set.

I my client, the list of fallback character sets (for writing) is:

us-ascii
iso-8859-* (16 entries where * is 0 to 16)
utf-8
utf-7
gb2312

They default in the order listed, top down. Default charsets for
reading are different, but my fallback reading charset list could be
different than what Thunderbird uses. Every NNTP client should support
the ASCII charset, especially since the others are extensions of ASCII.

When I write an article as the originator, it will use ASCII. If I
reply to someone that used non-ASCII characters, and those are in the
quoted section of my reply, then my client has to fallback to a charset
that supports those non-ASCII characters. That a client uses, say,
UTF-8 does not mandate there are non-ASCII characters in the article.
So, if I reply to someone using UTF-8, and quote part of their article,
but that part does not employ non-ASCII characters, then my client will
use ASCII.

Odd Thunderbird cannot handle posts that are solely ASCII. Or doesn't
have the same font sizing problem with posts from users that don't
declare those headers, like Frank. UTF-8 extends ASCII. Before adding
support for any other charsets, ASCII should be the first one supported.

Am I the only poster the only one that causes the font sizing problem
for you? When you started your thread, you didn't mention specific
posters, but just claimed the Content-Transfer-Encoding header was the
culprit despite you add it, and so several other posters you say their
articles don't cause the problem. My guess it is the charset specified
in the Content-Type header, but a single instance (just me) is not
sufficient proof. Who ELSE causes font sizing problems in your Tbird?

VanguardLH wrote:

> I my client, the list of fallback character sets (for writing) is:
> us-ascii iso-8859-* (16 entries where * is 0 to 16) utf-8 utf-7 gb2312

Over the years, there are two character encodings that I've noticed
trigger thunderbird to use a noticeably different font, big5 (chinese)
and koi8 (russian) i haven't seen any of those in this thread.

Ed Cryer <ed@somewhere.in.the.uk> wrote:

> VanguardLH wrote:
>> Ed Cryer <ed@somewhere.in.the.uk> wrote:
>>
>>> VanguardLH wrote:
>>>> Ed Cryer <ed@somewhere.in.the.uk> wrote:
>>>>
>>>> From your headers:
>>>>> Content-Transfer-Encoding: 7bit
>>>>> User-Agent: Mozilla Thunderbird
>>>>
>>>>> Occasionally a message displays in Tbird's message pane with a much
>>>>> larger font size than others.
>>>>> I've narrowed it down to 7bit encoding, and the major culprit is Forte
>>>>> Agent.
>>>>>
>>>>> There appears to be no setting to handle this.
>>>>
>>>> But your own client, Thunderbird, per your configuration of it, is
>>>> adding the same header. It wouldn't be just Agent adding this header.
>>>> It also be for all similarly configured Tbird users.
>>>>
>>>> Go to the alt.comp.software.thunderbird newsgroup (where you should have
>>>> posted) to see lots of posts with the "Content-Transfer-Encoding: 7bit"
>>>> header. Do all those posts also look wrong sized, too?
>>>
>>> That NG isn't on E-September or aioe.
>>> I did find alt.comp.software.easter-eggs, though.
>>>
>>> Don't waste my time with misdirections.
>>
>> If a newsgroup doesn't show up that others mention, refresh the
>> newsgroups list in your NNTP client. Have you tried that yet?
>>
>> And, yes, alt.comp.software.thunderbird does exist on ES. I also have
>> an account at ES although it is my backup Usenet provider. My primary
>> is individual.net. That newsgroup shows on both servers.
>>
>> AIOE has been dead for a long time, so don't recite that Usenet provider
>> as to what and what not it has. AIOE has nothing anymore. It's dead.
>> That you mention AIOE not having a newsgroup when AIOE has been dead for
>> many months shows you haven't kept up with the news here. The death of
>> AIOE has been discussed in Usenet. As I recall, inquiries started
>> showing up around Jan 2023 about AIOE being dead.
>>
>> Before lambasting someone, especially someone trying to help, check your
>> facts first. For ES, refresh the groups list in Tbird. Do so for any
>> other NNTP servers to which your Tbird connect. However, delete the
>> AIOE server in Tbird since AIOE went dead many months ago.
>
> I'm well aware of aieo's demise, I have been for weeks. But the
> news-server is still installed on one of my backup PCs, and I can survey
> the last group list there.
>
> Now, did you think of that before you jumped to your hasty conclusions
> based on flimsy evidence? And before you rushed in with your arrogant,
> overweening piece of dialogue?
>
> Ed

Your bitching about a response to your bitch (the "misdirection" slur)?
Tit for tat.

You knew AIOE was dead, and yet you mention a newsgroup is not listed
there, but there is no "there". No one but you would know how you
maintain the groups list in whatever NNTP clients, or instances thereof.
Perhaps you only retrieved the newsgroups to which you subscribe which
means other newsgroups would not get retrieved into the groups list.

However, you also declared the newsgroup is not at ES, which was wrong.
Don't care how you managed your groups list in some other client on some
other host for a non-existent NNTP server. But ES is active, and you
claimed the newsgroup wasn't there, either.

I didn't misdirect. You didn't refresh. Not my fault. Yours.