Spundun Bhatt wrote:
Another thing mentioned last time in a similar thread was top-posting. While I have harrassed the online community a lot with my top posted mails, I am trying to change that, is there any guidelines available for this? Sometimes I feel that if my message is starting on the second page of the mail, no-one is going to read it.

Here are guidelines that I follow and would encourage others to do so too. This is for general purpose reference and discussion and is not directed towards anyone in particular.


General email guidelines:

-- Use plain text instead of HTML.
-- Wrap email at 72 characters as a lower limit.
-- Do not ask for read receipts or delivery receipts unless necessary.
-- Forward emails as attachment and not as inline text.
-- Enable threading in your email client.
-- Use sigdashes (--) before your signature.
-- Keep signatures concise so that it does not detract from message content.
-- Separate code listings out with a distinct start and end delimiter (e.g. ====)
-- When composing a new message with new subject create a new email rather than replying to an older message.
-- When replying, create a reply from the email message that you wish to reply to and not just any message on the thread.
-- When replying to existing messages include only the relevant portions of original email.
-- Compose reply below quoted text rather than above. For each section of original message add reply below it.
-- Any lengthy information (e.g. compilation failure log) should be attached to email rather than stated in the body of the email.
-- When referring to a web resource provide web link rather than the resource itself.
-- When providing lengthy web links put on a new line to prevent mixing with remainder of text.


That would encapsulate good practice in general although preferences will vary.

With regards
Dhruba Bandopadhyay


-- [EMAIL PROTECTED] mailing list



Reply via email to