RE: The IETF's email mess [was: RE: Large messages to 6man list]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Eduard,
At 12:28 AM 21-08-2023, Vasilenko Eduard wrote:
If you would continue to ban HTML then please do it in a more specific way:
1. Reject the message (with sender notification).
Or
2. Convert it to text (with some information lost).
The current way (the chair should release/reject the message manually) is for sure the worst method to ban technology, automation is very needed. RFC on "IETF HTML banning rules" would be good to have because it is a way to have a "consensus".

IMHO about top posting: It is a very right way to copy sentences that should be commented on the top.
The rest of the message is better to keep below for context.

PS: By the way, why IETF mail server deletes all empty line? Not possible to separate different messages. Even more, if the previous line is finished without a dot or comma then lines would be merged.
What is wrong with empty lines?!? Even minimal mark-up is not possible.

I was a bit surprised to see an IPv6 working group discussing email. I don't remember seeing a mailing list moderator openly blocking an email which was relevant to the Working Group's work. It may happen that an email goes to the moderation queue, e.g. when the sender was not subscribed to the mailing list. A moderator has the ability to release that email and allow future emails from that sender to go to the mailing list automatically.

Participants could agree on having some context to understand a discussion. It may take some time for participants to agree, if that is even possible, on how to do that.

It would be useful to have an example of what was sent and what was received to find out why the empty lines were deleted.

Regards,
S. Moonesamy



[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux