pine_pine_set-up_pinegpg
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pine_pine_set-up_pinegpg [2022/07/22 22:02] – Updated formatting admin | pine_pine_set-up_pinegpg [2022/10/21 22:51] (current) – Disable gpg password cache admin | ||
---|---|---|---|
Line 12: | Line 12: | ||
| | ||
</ | </ | ||
+ | |||
+ | ==== Pine User Config ==== | ||
+ | < | ||
+ | vi / | ||
+ | user-domain=domainame.com | ||
+ | inbox-path={server.domain.com/ | ||
+ | customized-hdrs=From: | ||
+ | folder-collections={server.domain.com/ | ||
+ | </ | ||
+ | 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 27: | Line 37: | ||
When sending an email it will ask you for a " | When sending an email it will ask you for a " | ||
</ | </ | ||
+ | |||
+ | ==== GPG Password Cache ==== | ||
+ | |||
+ | In Debian bullseye when reading a gpg email, it will prompt for password and then spawn: / | ||
+ | Note this caches your GPG password. To prevent gpg password caching: | ||
+ | < | ||
+ | vi / | ||
+ | #add the following | ||
+ | default-cache-ttl 0 | ||
+ | </ | ||
+ | Test. You can also kill the gpg-agent process, but setting cache to 0 is easier. | ||
===== Automatic Login for Pine ===== | ===== Automatic Login for Pine ===== |
pine_pine_set-up_pinegpg.1658527330.txt.gz · Last modified: 2022/07/22 22:02 by admin