<<< Date Index >>>     <<< Thread Index >>>

Re: Quest about SMIME and shell



On 2006-01-09 at 04:22 -0800, Zhan Zhaohua wrote:
>      We read the documents of mutt again.

Always good.  :-)

>      Could we think if we successful configure the
> "muttrc" file , mutt will auto add the smime when we
> send the mail. And we find this
> file:"http://dev.mutt.org/cgi-bin/viewcvs.cgi/mutt/contrib/smime.rc?rev=3.6";
> . Does it help for us to configure the smime in the
> muttrc? Could  we use this shell-command "cat smime.rc
> >> /ect/Muttrc" to add it? If we use the mutt which
> config file is default to use? "/ect/Muttrc" or
> "~/.muttrc"

Both /etc/Muttrc and ~/.muttrc are used.  The /etc/Muttrc is used by all
users on a system; ~/.muttrc is used only by the user calling mutt,
since ~ is a short form of $HOME, which is normally set to a different
value for each user.

Which one to use depends upon your local set-up and what you're doing.
Generally, if only one user-account needs the special smime set-up, then
it makes sense to put the config into the ~/.muttrc file.

You do not need to append the smime.rc into a muttrc, you can include it
by giving the filename to the "source" command; in English, the way the
word is used here, "source" means the same as "include".

 ~/.muttrc:
----------------------------8< cut here >8------------------------------
source /path/to/mutt/shared/configs/rc.smime

# This affects S/MIME signing, as opposed to TLS which already uses the system
# default paths if ssl_usesystemcerts true (is by default):
set smime_ca_location=/etc/ssl/certs

# Where we keep known certificates:
set smime_certificates="~/.smime/certificates"

# Path to where all private keys go. (must exist!)
set smime_keys="~/.smime/keys"

# Other SMIME settings ...
----------------------------8< cut here >8------------------------------

-- 
I am keeping international relations on a peaceable footing.
You are biding your time before acting.
He is coddling tyrants.
 -- Roger BW on topic of verb conjugation