User Tools

Site Tools


pine_pine_set-up_pinegpg

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
pine_pine_set-up_pinegpg [2022/07/19 21:13] – external edit 127.0.0.1pine_pine_set-up_pinegpg [2022/07/22 23:23] admin
Line 8: Line 8:
 <br>http://www.washington.edu/pine/getpine/linux.html#deb-howto <br>http://www.washington.edu/pine/getpine/linux.html#deb-howto
 </del> </del>
 +
 +<code>
  apt-get install alpine  apt-get install alpine
 +</code>
 +
 +==== Pine User Config ====
 +<code>
 +vi /home/user/.pinerc
 +user-domain=domainame.com
 +inbox-path={server.domain.com/user=username/ssl/novalidate-cert}INBOX
 +customized-hdrs=From: Firstname Surname <user@domain.com>
 +folder-collections={server.domain.com/user=username/ssl/novalidate-cert}INBOX.[]
 +</code>
 +With the above, you should be able to login to imaps and send emails.
  
 =====Add-In for Pine for Gnupg -- Pinepgp===== =====Add-In for Pine for Gnupg -- Pinepgp=====
Line 15: Line 28:
  
 ===== Manual gpg and Pine ===== ===== Manual gpg and Pine =====
 +<code>
  vi /$HOME/.pinerc  vi /$HOME/.pinerc
  ##include/replace with the lines below.  ##include/replace with the lines below.
Line 22: Line 36:
  
 When sending an email it will ask you for a "filter". Hit CTRL + N to select gpg sign. Additonal sending-filters can be added for encrypt etc. as on: http://computing.ee.ethz.ch/.doc/pgp/index.html#howtosetuppineforuseiwthgpg When sending an email it will ask you for a "filter". Hit CTRL + N to select gpg sign. Additonal sending-filters can be added for encrypt etc. as on: http://computing.ee.ethz.ch/.doc/pgp/index.html#howtosetuppineforuseiwthgpg
 +</code>
  
 ===== Automatic Login for Pine ===== ===== Automatic Login for Pine =====
Line 27: Line 42:
  
 Because Pine uses ssh keys - it does not work over ssl (2 different security methods) - and therefore pine must access port 143 on the mailserver (as opposed to 993 for imaps). Because Pine uses ssh keys - it does not work over ssl (2 different security methods) - and therefore pine must access port 143 on the mailserver (as opposed to 993 for imaps).
 +<code>
   - Setup ssh keys - so you can login to the mailserver (*nix) directly. See the tutorial on this website for [[Sshkeys]]   - Setup ssh keys - so you can login to the mailserver (*nix) directly. See the tutorial on this website for [[Sshkeys]]
   - Test the above with "ssh mail.server.com /usr/bin/imapd" and it should login for you with PREAUTH.   - Test the above with "ssh mail.server.com /usr/bin/imapd" and it should login for you with PREAUTH.
Line 38: Line 53:
 What is happenning - is that pine is ssh'ing into the mailserver and running this command [[ssh-command="%s|%s -l %s exec /etc/r%sd"]] to run imapd for the user. What is happenning - is that pine is ssh'ing into the mailserver and running this command [[ssh-command="%s|%s -l %s exec /etc/r%sd"]] to run imapd for the user.
  
 +</code>
 This works fine for mbox. If Maildir is on the mailserver - a special script must be put in place before running imapd by the user. This works fine for mbox. If Maildir is on the mailserver - a special script must be put in place before running imapd by the user.
  
 Instead of: Instead of:
 +<code>
  ln -s /usr/bin/imapd /etc/rimapd  ln -s /usr/bin/imapd /etc/rimapd
 Do the following: Do the following:
- vi /etc/rimapd  <nowiki>//</nowiki>make sure its not in place already!+ vi /etc/rimapd  #make sure its not in place already!
      
  #!/bin/sh  #!/bin/sh
  exec /usr/bin/imapd $HOME/Maildir 2>/dev/null  exec /usr/bin/imapd $HOME/Maildir 2>/dev/null
    
- chmod 755 /etc/rimapd  <nowiki>//</nowiki>to make it executable!+ chmod 755 /etc/rimapd  #to make it executable! 
 +</code>
 That should work fine. The reason for /dev/null is so that *any* stdout or stderr is not sent to the commandline, but rather sent to /dev/null. That should work fine. The reason for /dev/null is so that *any* stdout or stderr is not sent to the commandline, but rather sent to /dev/null.
  
 Also note that Pine is now accessing our server over 143 (via ssh) and as such the port needs to be open! More Info on Maildir + pine + autologin at: <br /> Also note that Pine is now accessing our server over 143 (via ssh) and as such the port needs to be open! More Info on Maildir + pine + autologin at: <br />
-http://www.tkrat.org/pipermail/tkrat/2002q4.txt <br /> +  * http://www.tkrat.org/pipermail/tkrat/2002q4.txt 
-http://people.cs.uct.ac.za/~bmerry/software.html <br /> +  http://people.cs.uct.ac.za/~bmerry/software.html 
-http://www.mail-archive.com/courier-users@lists.sourceforge.net/msg06351.html+  http://www.mail-archive.com/courier-users@lists.sourceforge.net/msg06351.html
  
 ===== Spell Checker for Pine ===== ===== Spell Checker for Pine =====
 CTRL+T calls the spell checker when composing an email in pine. The necessary bash spell packages must be installed firstly however. CTRL+T calls the spell checker when composing an email in pine. The necessary bash spell packages must be installed firstly however.
 +<code>
  apt-get install spell aspell aspell-en aspell-bin  apt-get install spell aspell aspell-en aspell-bin
 +</code>
 That should provide all the necessary packages for pine to do spell checking. I dont think it spell checks the "Subject :" entry however. That should provide all the necessary packages for pine to do spell checking. I dont think it spell checks the "Subject :" entry however.
  
 ===== Pine with SSL ===== ===== Pine with SSL =====
 The following is a mailaccount which has ssl support. To test this: The following is a mailaccount which has ssl support. To test this:
 +<code>
  telnet mailserver.com 993  telnet mailserver.com 993
 +</code>
  
 Because this second mailaccount has a lot of folders and its own inbox I wanted to keep it seperate from my main .pinerc. So I made a .pinerc_email2: Because this second mailaccount has a lot of folders and its own inbox I wanted to keep it seperate from my main .pinerc. So I made a .pinerc_email2:
 +<code>
  vi /home/$user/.pinerc_email2  vi /home/$user/.pinerc_email2
  inbox-path={mailserver.com/user=sburke/ssl/novalidate-cert}  inbox-path={mailserver.com/user=sburke/ssl/novalidate-cert}
Line 73: Line 96:
  pine -p .pinerc_email2  pine -p .pinerc_email2
  #open pine with a custom .pinerc  #open pine with a custom .pinerc
 +</code>
  
 I then use screen to switch around between mail accounts. Its quicker than going in and out of mailfolders as if I had put all the mailservers in one .pinerc. I then use screen to switch around between mail accounts. Its quicker than going in and out of mailfolders as if I had put all the mailservers in one .pinerc.
  
 http://www.madboa.com/geek/pine-ssl/ http://www.madboa.com/geek/pine-ssl/
pine_pine_set-up_pinegpg.txt · Last modified: 2022/10/21 23:51 by admin