On Fri, 2/20/2026 6:54 AM, J. P. Gilliver wrote:
On 2026/2/19 15:2:47, Paul wrote:
[]
Did you test with a Nightly, as a check for forward-progress ?
I'm not familiar at all with running these, but this is the
quickest way to tell whether the MID mod got any traction.
No, I'm on the ESR line - quite the opposite of nightlies!
<snip>
The Nightly does not appear to honour <news:a@b.c>
[Picture]
https://i.postimg.cc/xCS716xC/No-Native-MID-In-TB-Nightly-149.gif
I tried from the command line too, and it seems uninterested.
Looks like Thunderbird will need an AddOn or similar.
On Fri, 20 Feb 2026 08:54:55 -0500, Paul <nospam@needed.invalid> wrote:
On Fri, 2/20/2026 6:54 AM, J. P. Gilliver wrote:
On 2026/2/19 15:2:47, Paul wrote:
[]
Did you test with a Nightly, as a check for forward-progress ?
I'm not familiar at all with running these, but this is the
quickest way to tell whether the MID mod got any traction.
No, I'm on the ESR line - quite the opposite of nightlies!
<snip>
The Nightly does not appear to honour <news:a@b.c>
[Picture]
https://i.postimg.cc/xCS716xC/No-Native-MID-In-TB-Nightly-149.gif
I tried from the command line too, and it seems uninterested.
Looks like Thunderbird will need an AddOn or similar.
That was established the other day, when I posted links to the add-ons.
On Fri, 20 Feb 2026 17:00:46 -0500, Paul <nospam@needed.invalid> wrote:[]
[]OutlookOutlook Express. Outlook has no Usenet capability.
On 2026/2/20 23:0:4, Char Jackson wrote:
On Fri, 20 Feb 2026 17:00:46 -0500, Paul <nospam@needed.invalid> wrote:[]
[]OutlookOutlook Express. Outlook has no Usenet capability.
Mostly correct. However, on one setup I used (at work), it did: I think
it called the msimn.exe that was present. But - IIRR, it was well over a >decade ago, maybe two - it presented the news component as if it was
inside the Outlook hierarchy.
Thanks! Outlook Express rocks, but you already knew that! :-)
[snip]I also tried to put your posts message-ID
No, for a message-ID, the format is <news:MID> without the two
slashes, i.e. for my post:
<news:10na0k5.jo0.1@ID-201911.user.individual.net>
With the slashes, it indeed expects a server.
As mentioned in an earlier post:
Bottom line;
<news:10na0k5.jo0.1@ID-201911.user.individual.net>
should work and I expect it to work in good old Outlook Express.
On 2026/2/20 23:0:4, Char Jackson wrote:
On Fri, 20 Feb 2026 17:00:46 -0500, Paul <nospam@needed.invalid> wrote:[]
[]OutlookOutlook Express. Outlook has no Usenet capability.
Mostly correct. However, on one setup I used (at work), it did: I think
it called the msimn.exe that was present. But - IIRR, it was well over a decade ago, maybe two - it presented the news component as if it was
inside the Outlook hierarchy.
R.Wieser <address@is.invalid> wrote:
Frank,
I don't know if it still works in Outlook Express (Rudy?).
Yes, it does. Both when clicking the news:// link inside a post, or when
putting it into my webbrowser (FF 52) (which than handed it off to OE).
Thanks! Outlook Express rocks, but you already knew that! :-)
I also tried to put your posts message-ID
(10na0k5.jo0.1@ID-201911.user.individual.net) after the news:// protocol
header, but although OE tried, it told me that it could not find the server >> (ID-201911.user.individual.net).
No, for a message-ID, the format is <news:MID> without the two
slashes, i.e. for my post:
<news:10na0k5.jo0.1@ID-201911.user.individual.net>
On 2/20/2026 6:57 PM, J. P. Gilliver wrote:
On 2026/2/20 23:0:4, Char Jackson wrote:It was not msimn.exe.
On Fri, 20 Feb 2026 17:00:46 -0500, Paul <nospam@needed.invalid> wrote:[]
[]OutlookOutlook Express. Outlook has no Usenet capability.
Mostly correct. However, on one setup I used (at work), it did: I think
it called the msimn.exe that was present. But - IIRR, it was well over a
decade ago, maybe two - it presented the news component as if it was
inside the Outlook hierarchy.
Msimn was prior to Outlook Express and IE4, though Outlook Express(included with MSN Explorer 2.6 and with IE4 circa 1997) initial release for the most part was just a renaming msinm client as Outlook Express. Msimn(Internet Mail and News) was included in Win95 but not
later and originally could be used(as an email and news client) in
addition to Win95 Windows Messaging(mail only client, which was also a a rename or Windows Exchange[not to be confused with Exchange Server - and
the reason for the rename to Windows Messaging).
Outlook required Exchange Server(not available in commercial Win95-XP
o/s) for newsgroups.
The *news* connection you may be recalling in Outlook with Outlook
Express was quite simple.
Afaik, at one time an Outlook Express add-in was available but it only
was a call to open Outlook Express for 'news'.
The most common and dependable version was a 3rd party add-in called
MAPILab NNTP which provided a read/post news method within the main
Outlook application(effectively using Outlook Express code as the
vehicle to read/post).
On 2026/2/21 10:30:38, ...w-i|#-o-#-n|# wrote:
On 2/20/2026 6:57 PM, J. P. Gilliver wrote:
On 2026/2/20 23:0:4, Char Jackson wrote:It was not msimn.exe.
On Fri, 20 Feb 2026 17:00:46 -0500, Paul <nospam@needed.invalid> wrote: >>> [][]
OutlookOutlook Express. Outlook has no Usenet capability.
Mostly correct. However, on one setup I used (at work), it did: I think
it called the msimn.exe that was present. But - IIRR, it was well over a >>> decade ago, maybe two - it presented the news component as if it was
inside the Outlook hierarchy.
Msimn was prior to Outlook Express and IE4, though Outlook
Express(included with MSN Explorer 2.6 and with IE4 circa 1997) initial
release for the most part was just a renaming msinm client as Outlook
Express. Msimn(Internet Mail and News) was included in Win95 but not
later and originally could be used(as an email and news client) in
addition to Win95 Windows Messaging(mail only client, which was also a a
rename or Windows Exchange[not to be confused with Exchange Server - and
the reason for the rename to Windows Messaging).
Outlook required Exchange Server(not available in commercial Win95-XP
o/s) for newsgroups.
The *news* connection you may be recalling in Outlook with Outlook
Express was quite simple.
Afaik, at one time an Outlook Express add-in was available but it only
was a call to open Outlook Express for 'news'.
We had the full Outlook - calendar, all the rest, quite useful in a work environment. Until some point, we also had news access - it included
some internal newsgroups, and at least some external.
The most common and dependable version was a 3rd party add-in calledThat was the impression I got. I'd be surprised if the company I worked
MAPILab NNTP which provided a read/post news method within the main
Outlook application(effectively using Outlook Express code as the
vehicle to read/post).
for (anagram of messybeast) did things like that add-on, but maybe it
did; it obviously must have been running a newsserver, given the
in-house 'groups, so it may have.
On Sat, 21 Feb 2026 01:57:54 +0000, "J. P. Gilliver" <G6JPG@255soft.uk> >wrote:
On 2026/2/20 23:0:4, Char Jackson wrote:
On Fri, 20 Feb 2026 17:00:46 -0500, Paul <nospam@needed.invalid> wrote: >>[][]
OutlookOutlook Express. Outlook has no Usenet capability.
Mostly correct. However, on one setup I used (at work), it did: I think
it called the msimn.exe that was present. But - IIRR, it was well over a >>decade ago, maybe two - it presented the news component as if it was
inside the Outlook hierarchy.
I don't think that's right, but do you have a reference? I've never
heard of Outlook having a Usenet presence.
Outlook Express had news access. It wasn't that good, although I
couldn't tell you why at this distance. I used it for a few weeks before
I discovered Agent.
Outlook Express had news access. It wasn't that good, although I
couldn't tell you why at this distance. I used it for a few weeks before
I discovered Agent.
On Sun, 22 Feb 2026 19:01:34 +0000, Peter Johnson wrote:
[snip]
Outlook Express had news access. It wasn't that good, although I
couldn't tell you why at this distance. I used it for a few weeks before
I discovered Agent.
Some people had a problem when you're replying and it would start with the cursor at the top, leading to top-posting. That one never bothered me,
since I knew to click before typing anything.
There was also a problem with multi-part binaries, although I don't
remember what.
I stopped using OE (and IE) around the time that Firefox was first called Firefox (version .8).
On Sun, 22 Feb 2026 19:01:34 +0000, Peter Johnson wrote:
[snip]
Outlook Express had news access. It wasn't that good, although I
couldn't tell you why at this distance. I used it for a few weeks before
I discovered Agent.
Some people had a problem when you're replying and it would start with the cursor at the top, leading to top-posting. That one never bothered me,
since I knew to click before typing anything.
There was also a problem with multi-part binaries, although I don't
remember what.
I stopped using OE (and IE) around the time that Firefox was first called Firefox (version .8).
On 2026/2/22 19:12:35, Mark Lloyd wrote:
On Sun, 22 Feb 2026 19:01:34 +0000, Peter Johnson wrote:
[snip]
Outlook Express had news access. It wasn't that good, although I
couldn't tell you why at this distance. I used it for a few weeks before >>> I discovered Agent.
Some people had a problem when you're replying and it would start with the >> cursor at the top, leading to top-posting. That one never bothered me,
since I knew to click before typing anything.
Some even suggested that was to encourage snipping/interposting, rather
than not doing any snipping and adding all of your response at the
bottom, which is (almost) as bad as top-posting.
This was rather countered, though, by it also putting the .sig, if you
had one, at the top.
OE-Quotefix mostly fixed it, though.
There was also a problem with multi-part binaries, although I don't
remember what.
Ditto (the not remembering part).
What was it called before that - Netscape plus or something? (I used to
I stopped using OE (and IE) around the time that Firefox was first called
Firefox (version .8).
use the Netscape Communicator suite - i. e. as well as a browser, it did email or news [or both, I don't remember]. Quite good, IIRR.)
On 2026/2/22 19:12:35, Mark Lloyd wrote:
On Sun, 22 Feb 2026 19:01:34 +0000, Peter Johnson wrote:
[snip]
Outlook Express had news access. It wasn't that good, although I
couldn't tell you why at this distance. I used it for a few weeks before >> I discovered Agent.
Some people had a problem when you're replying and it would start with the cursor at the top, leading to top-posting. That one never bothered me, since I knew to click before typing anything.
Some even suggested that was to encourage snipping/interposting, rather
than not doing any snipping and adding all of your response at the
bottom, which is (almost) as bad as top-posting.
As to top- versus bottom-posting, the latter is worse, because you
have to page through all the quotes, to see if perhaps there's a bit of interposting.
[...]--
On 2026/2/22 19:12:35, Mark Lloyd wrote:[]
On Sun, 22 Feb 2026 19:01:34 +0000, Peter Johnson wrote:
[snip]
Outlook Express had news access. It wasn't that good, although I
couldn't tell you why at this distance. I used it for a few weeks before >> I discovered Agent.
Some people had a problem when you're replying and it would start with the cursor at the top, leading to top-posting. That one never bothered me, since I knew to click before typing anything.
Some even suggested that was to encourage snipping/interposting, rather
than not doing any snipping and adding all of your response at the
bottom, which is (almost) as bad as top-posting.
This was rather countered, though, by it also putting the .sig, if you
had one, at the top.
OE-Quotefix mostly fixed it, though.
There was also a problem with multi-part binaries, although I don't remember what.
Ditto (the not remembering part).
On 23 Feb 2026 10:49:40 GMT, Frank Slootweg wrote:
[snip]
As to top- versus bottom-posting, the latter is worse, because you
have to page through all the quotes, to see if perhaps there's a bit of interposting.
What I find worse, is neither of those. It's inadequate snipping.
[...]
On 23 Feb 2026 10:49:40 GMT, Frank Slootweg wrote:
[snip]
As to top- versus bottom-posting, the latter is worse, because you
have to page through all the quotes, to see if perhaps there's a bit of interposting.
What I find worse, is neither of those. It's inadequate snipping.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 74 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 121:14:34 |
| Calls: | 1,194 |
| Files: | 1,352 |
| Messages: | 290,208 |
