|Help for Pine - Incoming Folders|
|You are in Home > Collections > Incoming-Folders|
The idea of an Incoming-Folders collection is that every folder in this collection is used to receive mail. For example if you are subscribed to a mailing list you can use one of these folders to keep all mail sent and/or received from that list. If you have more than one account, you can also use this collection to read mail from your other accounts, without the need to close the program.
Of course INBOX is your primary incoming-folder, this is a special folder. You can not rename it, or delete it. All other incoming-folders can be deleted and/or renamed.
Besides the considerations that were exposed in the Introduction, here are some other reasons why you need to add this collection.
If you receive mail from mailing lists, having this collection, together with a filtering tool allows you to separate mail that is not personal, to the one that it is. In this way you can keep your INBOX only for personal mail (or vice versa, maybe you want to filter personal messages out).
In order to be able to use your Incoming-Folders collection, you must go to the configuration screen (Press M S C) and
The next step is quite interesting, you must quit Pine and restart it again. This is just a convenience for the programmer that users must suffer.
When you restart Pine, you will see a new collection in your folders screen, in fact, you will see that INBOX is separated from the other folders, which are found in the Mail collection.
In order to add a new folder to this collection, be sure that you are in the folder list screen and put the cursor over any of the folders in this collection (so the first time you do this, you will have to put the cursor over INBOX). Here are the steps you need to follow:
If you are going to add your folder in a different server,
or if you are going to a maildrop,
you need to
enter the location of the server. This part is a little bit complicated to
describe in general terms. There are security considerations that are
supported by newer versions of Pine, that may make you change the
configuration of the server, these considerations are described at the end
of these instructions. At this time we will describe the basics.
In this step you need to specify the folder that you want to add as an
or the folder from where you want to pull messages to a maildrop
. This step is highly dependent on what your situation is.
Here are your options
You can also add the full path to the folder, if you don't remember that the path is relative to your $HOME directory.
If you are not using a maildrop, proceed to step 6, otherwise the next paragraph applies to you.
If you are using a maildrop on a news server, you need to enter the name of the newsgroup preceded by the string #news.. For example to add a maildrop for the newsgroup comp.mail.pine one would add the folder #news.comp.mail.pine. Now proceed to step 4
If you are using a maildrop, the next step allows you to define where you will move your message from the original mailbox specified in the previous steps. Normally one would use a maildrop to save messages to a local folder, but you can actually use any location for the target of your maildrop.
Once you get to this point, you have the following options
Now you are ready to proceed to Step 5
In this step you need to enter the location of the oflder where you want your messages saved. Examples could be "/var/spool/mail/username", or "mail/testfolder", or "INBOX" in the case that you are using a remote inbox as a maildrop. Here you must apply the same rules that you used in Step 3.
Now you are ready to proceed to Step 6.
This is the easiest step of all. You need to give a nickname to your incoming folder. This is the name that you will see for the folder. You can give it any name that you like. You can always change this easily with the R Rename command later. Of course, you should give it a name that resembles its use and/or location.
You are done!.
Here there are a few security considerations. When you connect to a server, in the form described above, your login name and password to that server, could be read by someone "sniffing" (meaning spying) your connection to the server. Although, some people do not care about this kind of insecurity, it may be required for you to set up a secure connection, if this is your case, and your server supports secure ssl connections you must add the string /ssl to the definition of the server.
Adding the string /ssl establishes a secure connection between you and the server, so even if someone is sniffing that line, they won't be able to know what is being communicated through that line.
Notice that some servers have "self-signed certificates", that means that they are the only person that guarantee that they are the people that you want to connect to. In other words, they claim that they are who you think they are, but no third party authority has checked that. When Pine finds a server with a self-signed certificate, an error is produced, which can be solved by adding the string /NoValidate-Cert to the definition of the server.
When you add the /NoValidate-Cert to the definition of the server, you are betting against the odds. What you are saying is that you will set up a secure connection to any server that identifies itself as the one that you want to connect to, even if it is not the one you want. In other words, by writing this string, you may be connecting (securely) to the wrong server, and therefore you may have your login/password stolen.
You can't, it's a security measure. Pine is not only thought to be used for personal use but also by use for universities, companies, etc. If anyone had access to your computer/account, that person could take control of your e-mail, and send messages in your name (meaning spam, for example).
Don't lose hope, however. If you are using PC-Pine all you need to do is to to create an empty file called pine.pwd in the same directory where your PINERC file is located.
If you are not using the PC version of Pine, you must compile this support in. Instructions to compile this password support can be found here.
After you have compiled the support for the password file and/or created an empty file in the corresponding place, Pine will take care of the rest of the process for you.
Let's assume that you need to copy a message from one folder to one of your incoming folders (e.g. INBOX). The way to do this, is very similar to what you would do if you were going to save a message. Just press S as if you were going to save the message and keep pressing ^N until the word "Incoming-Folders" appears in the prompt. Now you can enter the name of the folder (its nickname as entered in Step 4 above) in the Incoming-Folders collection that you want to save to (e.g. INBOX), and that will save the message in that folder.
|You are in Home > Collections > Incoming-Folders|