The 02.10.15 at 00:05, Theo v. Werkhoven wrote: [pine]
It also places the signature two lines below the "leader" line, above the quoted text. At least, by default.
Then you need to adjust the relevant option in Pine. In Mutt this option has a big warning saying that lot's of folks won't appreciate it, and the default is to put the sig where it belongs, on the bottom.
Unfortunately, pine (nor balsa, kmail, netscape or mozilla) allows me to fully tune behaviour based on mailbox, for example. In this list, I usually preffer not to top-post, meaning I have to cut and paste a few things (not only the signature), but in the rest of my mail I can't, because the rest of my correspondants complain they can not follow me. As I said, I'm tolerant and I adjust.
That is *not* so you can start typing at that point, it is done, so that you can start trimming off irrelevant text from that point down. Is it really that hard to do? Delete text to a piece of quoted text where you want to reply to, type your response, delete text down to the next piece of text you want to reply to etc.
That's what I usually do :-)
But it takes longer, and seems to be against what is customary in most businesses: they claim that a sort answer is easier to see at the top of the message, specially when there are dozens or hundred of emails to process. Also they dislike somebody else trimiming what they said, because the exact meaning can be altered.
When you're in a I2I conversation you try to be nice, and give polite answers and remarks don't you? You're not trying to mouth off someone just because it would save you a few minutes. Why then would you think your time is so precious in an email conversation that it makes it ok to screw up a logically arranged top-to-bottom discussion by putting ones comment on top of all that's been said before?
It is not my idea to do it that way. I was "forced" to act that way, when I was already used to quote and trim as necesary. The custom of top-posting comes not necesarily from microsoft, but from corporate and bussines mail.
Ignoring the relevant RFC1855 in mailing lists and usenet posts is just plain rude and totally disrespectful of the people the you might want to get help from.
Sorry: I didn't know it was required RFC training to write here. No mention of that in the subscription form :-p
It's basic politeness and etiquette to learn some "how to get along" rules before you engage in a mixed company. Same thing you do when you start a new job, get to know new friends etc.
Exactly. From the FAQ: | Please read the following frequently asked, frequently asked questions | before posting to the list. As with any mailing list or newsgroup, | it's usually a good idea to read the list for a few days before | posting If you watch the list for some days, you see many flavours. But no mention of the RFC1855 are on the "instructions" :-p
Anyway, the RFC docs are no longer included with the suse distro.
And one google click away is too much I'm sure.
If you know that such a thing as the RFC exist: only technically minded people and professionals will know. Any way: why has suse stoped including them, amongst many other things? Of course they can be obtained from some site or another, the same as I can download the full gnu-linux from each source and compile myself. But I may not have the time, bandwith, inclination or training to do it: so I buy a distro.
For me it is very simple: topposter and bulkquoters will be ignored, period.
If it suits yourself... Me, I'm more tolerant.
Good for you, but my life is way too short, and the number of lists and newsgroups I read way to big to try to keep up with every topposters comment and the context it's suppost to fit in, or to find a 'me too' somewhere on the bottom of a 10k message.
Heh! In such cases, I much prefer to see a top post. If the person doesn't trim and clip, but leave the quote intact, I preffer the "me too" above. Much faster reading X-)
From ~doc/rfc/rfc1855.txt.gz
| - A good rule of thumb: Be conservative in what you send and | liberal in what you receive. You should not send heated messages | (we call these "flames") even if you are provoked. On the other | hand, you shouldn't be surprised if you get flamed and it's | prudent not to respond to flames.
Your sig seperator is broken, it should be: <newline><dash><dash><space><newline>
Pine puts the dashes, not me: my ".signature" file contains no dashes. Can't help it, sorry. -- Cheers, Carlos Robinson