Hi again,... On Fri, Jun 17, 2011 at 2:50 PM, e-letter <inp...@gmail.com> wrote: > On 15/06/2011, Christian Lohmaier <lohmaier+ooofut...@googlemail.com> wrote: >> On Wed, Jun 15, 2011 at 11:45 PM, Friedrich Strohmaier >> <damokles4-lis...@bits-fritz.de> wrote: >>> e-letter schrieb: >>>> On 12/06/2011, Friedrich Strohmaier <damokles4-lis...@bits-fritz.de> >>> wrote: >>> >>>> This does not occur with gmail; all messages are _not_ received as >>>> attachments but as a single message >>> >>> So *GMAIL IS BUGGY*. >> >> No, the description is wrong of course the messages are /received/ as >> attachments, they are received as everybody else does. There are no >> special messages crafted for gmail users, the original source is the >> same for all. >> But gmail /*displays*/ them as a single message. Whether you consider >> this as a bug or feature is up to you :-) > > So gmail is breaking the (rfc?) convention? That makes this inline > display behaviour a bug, in my opinion but probably a feature by > others.
No. Read again. How it displays them is up to gmail. And whether or not you consider this a bug of a feature is a matter of taste. What definitely /IS/ a bug/lacking functionality though is the possibility to treat the seperate messages as seperate, as would be needed to properly reply in order to not break the thread. > Interestingly, this message shows the original message content after > activating the reply hyperlink; looking at the header and comparing > with the digest mode message header, maybe the from address being > test... is the cause. No - you cited another one from test previously that according to your description showed the problem. >>> [request single message before replying] >> And this is the only way of not breaking the thread with gmail. That's >> the other reason why it is pointless to try to "fix" something here >> that is not broken on our end. > > In other mailing lists the thread is maintained if the subject text is > copied, but may be broken if there is a small change in space > characters. No, it is not. It is for *you*, but only you, but not for those who actually track threads by the proper headers. When changing subject in gmail, it will always throw away all References and In-Reply-to headers. >> Using gmail for mailinglists were you reply to is anti-social as >> written before, as you don't have a chance of keeping the thread. You >> will always break the thread on reply, messing the lists up for >> everyone, those who read it later in one of the archives, anyone who >> uses a threaded reader (and that also includes gmail, where "threaded" >> is more like "collected by summary). > > Isn't relying on threads also weak when threads become long and may > continue beyond the normal 1 month categories of mail archives? That's the point of keeping the thread, to be able to continue reading it. And mail-archives are out of the question here, how they handle threading and display is up to them. 1month categories does men absolutely /nothing/ to gmane or mail-archive.com The month-categorization by classic archives just is a help for the reader to be able to quickly locate a message when the user knows when the mail was written. But with search becoming more powerful (and "affordable" in terms of disk-space requirements and computing power on the server that hosts the archives), this is no longer a real issue. But even if it was: Those who take part in the discussion are affected, not only the archives. ciao Christian -- Unsubscribe instructions: E-mail to test+h...@documentfoundation.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/test/ All messages sent to this list will be publicly archived and cannot be deleted
