Hello All,

https://github.com/axxisd/smapinntpd

2.2.1

* nntpserv.c
- Add user defined login option 'smartquote=on/off'

* smapinntpd.xlat
- Add more charset options for posting

* nntpserv.h
- Define 'opt_smartquote'
- Major version bump

* Update README
- Add user defined login option 'smartquote=on/off'

* Update CHANGELOG

https://github.com/axxisd/jamnntpd

2.3.0 Add 'smartquote' as a user toggle option during authentication

- Add more charset options for posting
- Update README with notes and examples about 'smartquote=on/off' option
- Update CHANGELOG

Side note: I should probably address my difference in CHANGELOG style/format, but I started out trying to match closely to what was already there from before. :(

Let me know if there's any issues!

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello All,

New versions of both Jamnntpd and Smapinntpd available:

https://github.com/axxisd/jamnntpd
https://github.com/axxisd/smapinntpd

2.3.2

* nntpserv.c
- Fix for extra space at the beginning of the origin line

* nntpserv.h
- Minor version bump

* Update CHANGELOG

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On Sat, 30 Mar 2024 16:31:52 +0100, Carlos Navarro -> Nicholas Boel wrote:

By looking at your change in the code, I'm afraid you have just disabled flowed text.

Wouldn't this change only affect a line starting with " * Origin: " ?

The problem is not only with Origin lines, it's with any line with
leading spaces.

Not 100% sure, but I think it may be that Thunderbird does not fully implement format=flowed according to the RFCs, WRT space stuffing.

While I can believe this, I also saw the same extra space at the beginning of the origin line with slrn, so I was led to believe this wasn't specific to Thunderbird.

Let's see what this line does.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello Carlos,

On Sat, 30 Mar 2024 09:01:50 -0500, I wrote to you:

On Sat, 30 Mar 2024 16:31:52 +0100, Carlos Navarro -> Nicholas Boel
wrote:

By looking at your change in the code, I'm afraid you have just
disabled flowed text.

Wouldn't this change only affect a line starting with " * Origin: " ?

When reading this message in Golded, my text seemed to have still been format=flowed?

The problem is not only with Origin lines, it's with any line
with leading spaces.

The "Let's see" line down below doesn't seem to have anything wrong with it.

Not 100% sure, but I think it may be that Thunderbird does not
fully implement format=flowed according to the RFCs, WRT space
stuffing.

While I can believe this, I also saw the same extra space at the
beginning of the origin line with slrn, so I was led to believe this wasn't specific to Thunderbird.

Let's see what this line does.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20240309
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

29 Mar 2024 19:59, you wrote to All:

2.3.2

* nntpserv.c
- Fix for extra space at the beginning of the origin line

By looking at your change in the code, I'm afraid you have just disabled flowed text.

The problem is not only with Origin lines, it's with any line with leading spaces.

Not 100% sure, but I think it may be that Thunderbird does not fully implement format=flowed according to the RFCs, WRT space stuffing.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

30 Mar 2024 09:04, you wrote to me:

By looking at your change in the code, I'm afraid you have just
disabled flowed text.

Wouldn't this change only affect a line starting with " * Origin:
" ?

When reading this message in Golded, my text seemed to have still been format=flowed?

This is not about GoldED. It affects how you read/receive it in the NNTP client.

Open your message with TB, resize the window and check if you see it like flowed or fixed

https://www.cyberiada.org/fido/tmpfiles/fixed-vs-flowed.png

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

30 Mar 2024 09:01, you wrote to me:

While I can believe this, I also saw the same extra space at the
beginning of the origin line with slrn, so I was led to believe this wasn't specific to Thunderbird.

Does slrn support format=flowed?

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

On Sun, 31 Mar 2024 15:06:16 +0200, Carlos Navarro -> Nicholas Boel wrote:

Wouldn't this change only affect a line starting with " * Origin:
" ?

When reading this message in Golded, my text seemed to have still been
format=flowed?

This is not about GoldED. It affects how you read/receive it in the NNTP client.

Open your message with TB, resize the window and check if you see it
like flowed or fixed

https://www.cyberiada.org/fido/tmpfiles/fixed-vs-flowed.png

Mine has never looked like the top of that screenshot. So I don't really know where you are seeing that, unless you have completely disabled format=flowed from Thunderbird or are using def_flowed=off.

Either way, if it has caused any issue for others, I have reverted the changes.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On Sun, 31 Mar 2024 15:06:54 +0200, Carlos Navarro -> Nicholas Boel wrote:

Does slrn support format=flowed?

Yes.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

31 Mar 2024 08:20, you wrote to me:

This is not about GoldED. It affects how you read/receive it in
the NNTP client.

Open your message with TB, resize the window and check if you see
it like flowed or fixed

https://www.cyberiada.org/fido/tmpfiles/fixed-vs-flowed.png

Mine has never looked like the top of that screenshot. So I don't
really know where you are seeing that, unless you have completely
disabled format=flowed from Thunderbird or are using def_flowed=off.

I wasn't seeing that, I had just looked at the code.

Just in case, I've tried applying your change to my test server. I can confirm that messages have "Content-Type: ... format=flowed" but paragraphs are fixed, not flowed. And, as I expected, resizing the message window does not rewrap the paragraphs as in flowed text (like in the bottom of the screenshot).

Could it be you were reading cached messages?

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

30 Mar 2024 11:31, I wrote to you:

Not 100% sure, but I think it may be that Thunderbird does not fully implement format=flowed according to the RFCs, WRT space stuffing.

To be more precise, TB seems to implement it properly for reading messages, but maybe not for quote-replying (with all those extra spaces)... But I'm not sure.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

31 Mar 2024 08:20, you wrote to me:

Does slrn support format=flowed?

Yes.

Ok, will have to check it...

Can you please quote-reply this message with slrn?

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

Hello Carlos,

On Mon, 1 Apr 2024 03:15:56 +0200, you wrote:

31 Mar 2024 08:20, you wrote to me:

Does slrn support format=flowed?

Yes.

Ok, will have to check it...

Can you please quote-reply this message with slrn?

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

Not sure how Smapinntpd will process it, but here quoting this I see the extra space before the origin line as well. Otherwise, here is the quote-reply you are looking for. Everything above was quoted as-is, with no manual intervention by me. So if there's anything unusual it is either slrn (which I've seen no issues with yet - they have all been TB related), or Smapinntpd itself.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- slrn/pre1.0.4-9 (Linux)
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On Mon, 1 Apr 2024 03:15:56 +0200, you wrote:

31 Mar 2024 08:20, you wrote to me:

Does slrn support format=flowed?

Yes.

Ok, will have to check it...

Can you please quote-reply this message with slrn?

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

slrn added one space to the origin line when quoting, and TB looks to have added two spaces. However, when saved I think it goes back to one space.

Either way, do remember that we did this:

mailnews.display.disable_format_flowed_support = true

So resizing your screen in TB is going to chop the lines up, rather than flow it (This was done to get rid of the non breaking spaces). However, we are still sending off our messages with flowed support, as far as I know.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

31 Mar 2024 16:20, you wrote to me:

Can you please quote-reply this message with slrn?

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

Not sure how Smapinntpd will process it, but here quoting this I see
the extra space before the origin line as well. Otherwise, here is the quote-reply you are looking for. Everything above was quoted as-is,
with no manual intervention by me. So if there's anything unusual it
is either slrn (which I've seen no issues with yet - they have all
been TB related), or Smapinntpd itself.

Thank you Nick. So it's not only TB... slrn also adds (or keeps) the extra space in quotes.

I don't know if the way they do is correct. If it is, then Smapi/JamNNTPd should remove those stuffed spaces from the quotes when posting to the messagebase. Either way, I'm working on a fix.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

On Sun, 7 Apr 2024 15:32:20 +0200, you wrote:

31 Mar 2024 16:20, you wrote to me:

Can you please quote-reply this message with slrn?

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

Not sure how Smapinntpd will process it, but here quoting this I see
the extra space before the origin line as well. Otherwise, here is
quote-reply you are looking for. Everything above was quoted as-is,
with no manual intervention by me. So if there's anything unusual it
is either slrn (which I've seen no issues with yet - they have all
been TB related), or Smapinntpd itself.

Thank you Nick. So it's not only TB... slrn also adds (or keeps) the
extra space in quotes.

Not sure what it's doing, exactly. I don't see the extra space in Golded or tin, but I do see it in slrn and TB. Must be specific to only some newsreaders.

I don't know if the way they do is correct. If it is, then
Smapi/JamNNTPd should remove those stuffed spaces from the quotes when posting to the messagebase. Either way, I'm working on a fix.

Testing it here as well. Thanks for the updates!

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)