Bernd Froehlich <befr@eaglesoft.de> wrote:
On 19. Jun 2024 at 22:51:11 CEST, "J. J. Lodder" <J. J. Lodder> wrote:
There were several attempts to recreate it, without great succes.
(also one in ukcsm, iirc)
Only MacCafe survives, afaik.
You forgot Usenapp.
??? Whatever it is, Usenapp is not an attempt to recreate MacSoup.
Works great over here (I´m a former SOUP fan too).
So that is why you produce garbage headers?
On 19. Jun 2024 at 22:51:11 CEST, "J. J. Lodder" <J. J. Lodder> wrote:
There were several attempts to recreate it, without great succes.
(also one in ukcsm, iirc)
Only MacCafe survives, afaik.
You forgot Usenapp.
Works great over here (I´m a former SOUP fan too).
Bernd Froehlich <befr@eaglesoft.de> wrote:
On 19. Jun 2024 at 22:51:11 CEST, "J. J. Lodder" <J. J. Lodder> wrote:
There were several attempts to recreate it, without great succes.
(also one in ukcsm, iirc)
Only MacCafe survives, afaik.
You forgot Usenapp.
??? Whatever it is, Usenapp is not an attempt to recreate MacSoup.
Works great over here (I´m a former SOUP fan too).
So that is why you produce garbage headers?
On 20 Jun 2024 at 10:51:24 BST, "J. J. Lodder" <J. J. Lodder> wrote:
Bernd Froehlich <befr@eaglesoft.de> wrote:
On 19. Jun 2024 at 22:51:11 CEST, "J. J. Lodder" <J. J. Lodder> wrote:
There were several attempts to recreate it, without great succes.
(also one in ukcsm, iirc)
Only MacCafe survives, afaik.
You forgot Usenapp.
??? Whatever it is, Usenapp is not an attempt to recreate MacSoup.
Works great over here (I´m a former SOUP fan too).
So that is why you produce garbage headers?
That subject string might have said:
Re: [MacCafé] Freeware newsreader for macOS, now available in English
except that it is missing the leading =? which if present makes it a valid encoded-word string.
On 20 Jun 2024 at 10:51:24 BST, "J. J. Lodder" <J. J. Lodder> wrote:
Bernd Froehlich <befr@eaglesoft.de> wrote:
On 19. Jun 2024 at 22:51:11 CEST, "J. J. Lodder" <J. J. Lodder> wrote:
There were several attempts to recreate it, without great succes.
(also one in ukcsm, iirc)
Only MacCafe survives, afaik.
You forgot Usenapp.
??? Whatever it is, Usenapp is not an attempt to recreate MacSoup.
Works great over here (I´m a former SOUP fan too).
So that is why you produce garbage headers?
That subject string might have said:
Re: [MacCafé] Freeware newsreader for macOS, now available in English
except that it is missing the leading =? which if present makes it a valid encoded-word string.
TimS <tim@streater.me.uk> wrote:
On 20 Jun 2024 at 10:51:24 BST, "J. J. Lodder" <J. J. Lodder> wrote:
Bernd Froehlich <befr@eaglesoft.de> wrote:
On 19. Jun 2024 at 22:51:11 CEST, "J. J. Lodder" <J. J. Lodder> wrote: >>>>
There were several attempts to recreate it, without great succes.
(also one in ukcsm, iirc)
Only MacCafe survives, afaik.
You forgot Usenapp.
??? Whatever it is, Usenapp is not an attempt to recreate MacSoup.
Works great over here (I´m a former SOUP fan too).
So that is why you produce garbage headers?
That subject string might have said:
Re: [MacCafé] Freeware newsreader for macOS, now available in English
except that it is missing the leading =? which if present makes it a valid >> encoded-word string.
Everything that is not plain ASCII is invalid, in Subject: strings,
On 20 Jun 2024 at 14:45:02 BST, "J. J. Lodder" <J. J. Lodder> wrote:
TimS <tim@streater.me.uk> wrote:
On 20 Jun 2024 at 10:51:24 BST, "J. J. Lodder" <J. J. Lodder> wrote:
Bernd Froehlich <befr@eaglesoft.de> wrote:
On 19. Jun 2024 at 22:51:11 CEST, "J. J. Lodder" <J. J. Lodder> wrote: >>>>
There were several attempts to recreate it, without great succes.
(also one in ukcsm, iirc)
Only MacCafe survives, afaik.
You forgot Usenapp.
??? Whatever it is, Usenapp is not an attempt to recreate MacSoup.
Works great over here (I´m a former SOUP fan too).
So that is why you produce garbage headers?
That subject string might have said:
Re: [MacCafé] Freeware newsreader for macOS, now available in English
except that it is missing the leading =? which if present makes it a valid >> encoded-word string.
Everything that is not plain ASCII is invalid, in Subject: strings,
Which is why that subject line (corrrectly translated, note), required and requires transmission in encoded-word format.
TimS <tim@streater.me.uk> wrote:
On 20 Jun 2024 at 14:45:02 BST, "J. J. Lodder" <J. J. Lodder> wrote:
TimS <tim@streater.me.uk> wrote:
On 20 Jun 2024 at 10:51:24 BST, "J. J. Lodder" <J. J. Lodder> wrote:
Bernd Froehlich <befr@eaglesoft.de> wrote:
On 19. Jun 2024 at 22:51:11 CEST, "J. J. Lodder" <J. J. Lodder> wrote: >>>>>>
There were several attempts to recreate it, without great succes. >>>>>>> (also one in ukcsm, iirc) Only MacCafe survives, afaik.
You forgot Usenapp.
??? Whatever it is, Usenapp is not an attempt to recreate MacSoup.
Works great over here (I´m a former SOUP fan too).
So that is why you produce garbage headers?
That subject string might have said:
Re: [MacCafé] Freeware newsreader for macOS, now available in English >>>>
except that it is missing the leading =? which if present makes it a valid >>>> encoded-word string.
Everything that is not plain ASCII is invalid, in Subject: strings,
Which is why that subject line (corrrectly translated, note), required and >> requires transmission in encoded-word format.
Right, not plain, so an error,
On 20 Jun 2024 at 19:10:18 BST, "J. J. Lodder" <J. J. Lodder> wrote:
TimS <tim@streater.me.uk> wrote:
On 20 Jun 2024 at 14:45:02 BST, "J. J. Lodder" <J. J. Lodder> wrote:
TimS <tim@streater.me.uk> wrote:
On 20 Jun 2024 at 10:51:24 BST, "J. J. Lodder" <J. J. Lodder> wrote: >>>>
Bernd Froehlich <befr@eaglesoft.de> wrote:
On 19. Jun 2024 at 22:51:11 CEST, "J. J. Lodder" <J. J. Lodder> wrote: >>>>>>
There were several attempts to recreate it, without great succes. >>>>>>> (also one in ukcsm, iirc) Only MacCafe survives, afaik.
You forgot Usenapp.
??? Whatever it is, Usenapp is not an attempt to recreate MacSoup. >>>>>
Works great over here (I´m a former SOUP fan too).
So that is why you produce garbage headers?
That subject string might have said:
Re: [MacCafé] Freeware newsreader for macOS, now available in English >>>>
except that it is missing the leading =? which if present makes it a >>>> evalid ncoded-word string.
Everything that is not plain ASCII is invalid, in Subject: strings,
Which is why that subject line (corrrectly translated, note), required and >> requires transmission in encoded-word format.
Right, not plain, so an error,
Not if you encode it. The output of encoding a string as an encode-word is always ASCII only, whether or not the input contains non-ASCII Unicode. When you decode it, you get your original string back, complete with accented characters, if any.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 05:01:19 |
| Calls: | 10,386 |
| Calls today: | 1 |
| Files: | 14,058 |
| Messages: | 6,416,627 |