Re: Line wrapping in quotes

Posted by GregChapman on Aug 29, 2019; 10:27pm
URL: https://support.nabble.com/Line-wrapping-in-quotes-tp7604136p7604142.html

Hi Denis,

Denis Mekhanikov wrote

What makes me think that Nabble has something to do with it is that messages sent from other mailing clients look normal.
For example you can take a look at the following thread: http://apache-ignite-developers.2346864.n4.nabble.com/Asynchronous-registration-of-binary-metadata-td43021.html
Wrapping is not applied to the first message, but it is for the ones that follow it. I guess, that they were sent from Nabble, which made them 80-character-wide.

There are a number of ways to post to the Apache Ignite Developers list.
1. Post via an email client direct to the list.
2. Post direct the Nabble forum
3. Post via email to the Nabble forum

You also need to be know how Nabble operates when acting as an archive. Nabble simply subscribes to the mail list and as it receives posts from the mail list it posts them to what is, in effect, a standard Nabble forum. Once the forum is established people can then either post directly to the forum or via email to the forum (though this last option always strikes me as redundant, as it just puts an additional process in the chain. If you are going to post via email it makes far more sense to me to post direct to the mail list). Just as with the mail it receives from a subscription, any post received via email is processed to become a post on the forum.

When a new non-subscription post appears on a forum linked to a mail list, the new post is then immediately forwarded to the mail list, with the From: address spoofed to make it appear to come from the original poster and not the forum. What happens next depends on the mail list. In many cases mail lists only allow subscribers to post and a reject message is returned to Nabble. Nabble then flags the post as not accepted by the mail list, (and reminds the sender to subscribe to the original list). While people reading the forum can respond to the forum post, their posts will also only appear on the forum unless they are subscribers to the original list.

I am not clear, from your description below:

I exported a few emails in a raw format from my email client. The ones, that I sent using an external client have Content-Type: text/plain
The ones, that were sent from Nabble have Content-Type: multipart/alternative

You don't say whether the ones sent "using an external client" were sent to Nabble (Option 3) or sent to the mail list (Option 1) address.

Is there a way to make emails be wrapped before sending?

Having written all the above and expecting to finish by repeating that this is an issue with the mail list rather than the forum, I have just checked on one of my forums and found this administrator page which will have an impact...


It looks as if you are right and there is a setting that will affect things - but I don't think can be counted as the primary cause of your complaint.

For the creator of the  Apache Ignite Developers forum to have set "This list accepts only plain-text emails" surely means that the Dev list itself is set to strip out HTML attachments and so it is reasonable to ensure that emails sent to the list by Nabble are in the appropriate format for the list.

This would account for initial posts either emailed or posted directly to the forum appearing wrapped at the window edge while any posts received from the mail list will be in plain text format with 80 column wrapping and will be displayed that way on the forum

I note that the Users List archive was created by someone else and, as you say, the archive does not have the issue with wrapping, but I suspect that is because the list itself does not force plain text on its subscribers.

In short, unless the owner of the Dev list can be persuaded to allow HTML mail on the list and the creator of the archive can be persuaded to remove the "Plain text only" setting, then you will have to accept things as they are.

You can email the creator of the archive using the link at the foot of the main forum page.