Visit Our UNIX and Linux User Community

Contact Us Forum Support Area for Unregistered Users & Account Problems Unable to post or reply thread after login Post 302863621 by Unregistered on Monday 14th of October 2013 11:46:35 PM
Old 10-15-2013
Unable to post or reply thread after login

I am unable to post reply to a thread. Whenever I will reply to any post I get the message every time :
The message you have entered is too short. Please lengthen your message to at least 5 characters.

Even though length of the message is more than required.

for example I tried to post

Code:
 awk '{l=length;a=1;while(a<l){if(substr($0,a,100) ~ /^BUCA/){print substr($0,a+70,10)};a=a+100}}' s33

or anything I reply to post after login I get the above message.

my user id is raj_saini20
Unregistered
 

8 More Discussions You Might Find Interesting

1. Forum Support Area for Unregistered Users & Account Problems

unable to post thread

Hello, I'd like to post a aix thread but I'm unable to. Please let me know why this is happening. Thanks.... (1 Reply)
Discussion started by: sullivjp
1 Replies

2. Post Here to Contact Site Administrators and Moderators

Reply to thread I started 8 May 09 gone

And frankly, I'm a bit miffed by it. I had thanked the person who suggested a solution to the issue, pasted code to a shell script that may have helped other users, and was courteous, witty and all that the best forum admins look for in a member/contributor/poster. Now it's gone, with no... (1 Reply)
Discussion started by: SilversleevesX
1 Replies

3. Shell Programming and Scripting

if this post is easy to read so is to reply !!!

i have a html file with uploads a file and sends the username to a .cgi file using post method. the part of code in the cgi file is as below. i am able to get the filename but not able to get the username thats getting posted to the file how to know the value of username. i am trying to store... (2 Replies)
Discussion started by: sasidhdv
2 Replies

4. Forum Support Area for Unregistered Users & Account Problems

I cannot post new thread and reply after register

Hi, Admin, I have met a problem that I cannot post new thread and reply after register. It reminds some information as shown in the below: case 1: To create new threads in this forum your post count must be 10 or greater. You currently have 0 posts. case 2: To reply to threads in this forum... (1 Reply)
Discussion started by: Unregistered
1 Replies

5. Forum Support Area for Unregistered Users & Account Problems

I am still meet a problem when I want to reply or create a new thread

Hi, Scott, I am still meet a problem when I want to reply or create a new thread in "Shell Programming and Scripting" Forum, It reminds that: To create new threads in this forum your post count must be 10 or greater. You currently have 2 posts. To my surprise, I posted a thread in "Shell... (4 Replies)
Discussion started by: weichanghe2000
4 Replies

6. Forum Support Area for Unregistered Users & Account Problems

Not able to post thread/reply to thread

Dear Moderator I am not able to post any new thread or post reply to mine old thread. Kindly help as i am stuck on one problem and needed suggestion. Regards Jaydeep (1 Reply)
Discussion started by: jaydeep_sadaria
1 Replies

7. How to Post in the The UNIX and Linux Forums

Not able to reply to a post

I have a trouble here. I posted couple of questions and got some reply but when i go ahead and do a reply/quick reply to the question asked it doesn't goes. it simply keep on displaying the message "Posting quick reply please wait" and that wait never ends. I am not able to do a reply :(... (3 Replies)
Discussion started by: Sharma331
3 Replies

8. What is on Your Mind?

Updates to Forum Navbar and Thread Reply for Unregistered Users

Hey You may have noticed I changed the navbar at the top a bit. I've almost finished converting the navbar to divs from table tags. In addition, for unregistered users, instead of seeing a "New Reply" button, unregistered users see a "Login to Reply" and icon which looks the same as our... (2 Replies)
Discussion started by: Neo
2 Replies
MH-MAIL(5)							     [nmh-1.5]								MH-MAIL(5)

NAME
mh-mail - message format for nmh message system SYNOPSIS
any nmh command DESCRIPTION
nmh processes messages in a particular format. It should be noted that although neither Bell nor Berkeley mailers produce message files in the format that nmh prefers, nmh can read message files in that antiquated format. Each user possesses a mail drop box which initially receives all messages processed by post. Inc will read from that drop box and incorpo- rate the new messages found there into the user's own mail folders (typically "+inbox"). The mail drop box consists of one or more mes- sages. Messages are expected to consist of lines of text. Graphics and binary data are not handled. No data compression is accepted. All text is clear ASCII 7-bit data. The general "memo" framework of RFC-822 is used. A message consists of a block of information in a rigid format, followed by general text with no specified format. The rigidly formatted first part of a message is called the header, and the free-format portion is called the body. The header must always exist, but the body is optional. These parts are separated by an empty line, i.e., two consecutive newline characters. Within nmh , the header and body may be separated by a line consisting of dashes: From: Local Mailbox <user@example.com> To: cc: Fcc: +outbox Subject: The header is composed of one or more header items. Each header item can be viewed as a single logical line of ASCII characters. If the text of a header item extends across several real lines, the continuation lines are indicated by leading spaces or tabs. Each header item is called a component and is composed of a keyword or name, along with associated text. The keyword begins at the left margin, may NOT contain spaces or tabs, may not exceed 63 characters (as specified by RFC-822), and is terminated by a colon (`:'). Cer- tain components (as identified by their keywords) must follow rigidly defined formats in their text portions. The text for most formatted components (e.g., "Date:" and "Message-Id:") is produced automatically. The only ones entered by the user are address fields such as "To:", "cc:", etc. Internet addresses are assigned mailbox names and host computer specifications. The rough for- mat is "local@domain", such as "MH@UCI", or "MH@UCI-ICSA.ARPA". Multiple addresses are separated by commas. A missing host/domain is assumed to be the local host/domain. As mentioned above, a blank line (or a line of dashes) signals that all following text up to the end of the file is the body. No format- ting is expected or enforced within the body. Following is a list of header components that are considered meaningful to various nmh programs. Date: Added by post, contains date and time of the message's entry into the mail transport system. From: This header is filled in by default with the system's idea of the user's local mailbox. This can be changed with the Local-Mailbox profile entry. It contains the address of the author or authors (may be more than one if a "Sender:" field is present). For a stan- dard reply (using repl), the reply address is constructed by checking the following headers (in this order): "Mail-Reply-To:", "Reply-To:", "From:", "Sender:". A "From:" header MUST exist when the message is sent to post, otherwise the message will be rejected. Mail-Reply-To: For a standard reply (using repl), the reply address is constructed by checking the following headers (in this order): "Mail- Reply-To:", "Reply-To:", "From:", "Sender:". Mail-Followup-To: When making a "group" reply (using repl -group), any addresses in this field will take precedence, and no other reply address will be added to the draft. If this header is not available, then the return addresses will be constructed from the "Mail-Reply-To:", or "Reply-To:", or "From:", along with adding the addresses from the headers "To:", "cc:", as well as adding your personal address. Reply-To: For a standard reply (using repl), the reply address is constructed by checking the following headers (in this order): "Mail- Reply-To:", "Reply-To:", "From:", "Sender:". Sender: Required by post in the event that the message has multiple addresses on the "From:" line. It is otherwise optional. This line should contain the address of the actual sender. To: Contains addresses of primary recipients. cc: Contains addresses of secondary recipients. Bcc: Still more recipients. However, the "Bcc:" line is not copied onto the message as delivered, so these recipients are not listed. nmh uses an encapsulation method for blind copies, see send(1). Dcc: Still more recipients. However, the "Dcc:" line is not copied onto the messages as delivered. Recipients on the "Dcc:" line receive the same messsage as recipients on the "To:" and "cc:" lines. See send(1) for more details. Fcc: Causes post to copy the message into the specified folder for the sender, if the message was successfully given to the transport sys- tem. Message-ID: A unique message identifier added by post if the -msgid flag is set. Subject: Sender's commentary. It is displayed by scan. In-Reply-To: A commentary line added by repl when replying to a message. Resent-Date: Added when redistributing a message by post. Resent-From: Added when redistributing a message by post. Resent-To: New recipients for a message resent by dist. Resent-cc: Still more recipients. See "cc:" and "Resent-To:". Resent-Bcc: Even more recipients. See "Bcc:" and "Resent-To:". Resent-Fcc: Copy resent message into a folder. See "Fcc:" and "Resent-To:". Resent-Message-Id: A unique identifier glued on by post if the -msgid flag is set. See "Message-Id:" and "Resent-To:". Resent: Annotation for dist under the -annotate option. Forwarded: Annotation for forw under the -annotate option. Replied: Annotation for repl under the -annotate option. FILES
/var/mail/$USER Location of mail drop SEE ALSO
Standard for the Format of ARPA Internet Text Messages (RFC-822) CONTEXT
None MH.6.8 11 June 2012 MH-MAIL(5)

Featured Tech Videos

All times are GMT -4. The time now is 04:36 PM.
Unix & Linux Forums Content Copyright 1993-2021. All Rights Reserved.
Privacy Policy