Hi,
Maybe I am too lazy to google this stuff but what are PGP messages.. I
mean I see emails with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
..
..
-BEGIN PGP SIGNATURE-
etc so what does it mean ? Why does mutt support PGP ?
Do we need anything to have it setup in our mutt..
Or do we
On Tue, Jul 29, 2008 at 08:43:58PM -0500, Kyle Wheeler wrote:
> On Tuesday, July 29 at 06:59 PM, quoth Tom:
> > I would like to set up a group and an alias for that group. I read
> > the manual and the wiki and the recent post and still to dumb to
> > figure it out. I want the group name to be f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, July 29 at 06:59 PM, quoth Tom:
> I would like to set up a group and an alias for that group. I read
> the manual and the wiki and the recent post and still to dumb to
> figure it out. I want the group name to be fargo. I would like the
I would like to set up a group and an alias for that group. I read the manual
and the wiki and the recent post and still to dumb to figure it out.
I want the group name to be fargo. I would like the alias to be fargo if the
group name and alias can be the same.
The email addreses are [EMAIL PRO
On 29 Jul 2008 18:14 -0400, by [EMAIL PROTECTED] (Derek Martin):
> The risk here is tiny, but non-zero. Someone would have to be able to
> gain root priviledges to read the raw swap device to get your
That's where (on Linux, at least) encrypted swap partitions come in
handy. You can set it up to
On Mon, Jul 28, 2008 at 10:54:40PM -0500, Kyle Wheeler wrote:
> On Monday, July 28 at 07:56 PM, quoth Derek Martin:
> >On Mon, Jul 28, 2008 at 12:58:00PM -0500, Kyle Wheeler wrote:
> >> Nothing will be stored in plaintext on disk, your encryption is
> >> guaranteed to be world-class, and best of al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, July 29 at 02:14 PM, quoth David Champion:
> ":set my_var" yields "my_var: unknown variable" too. Try, for
> example,
>
> :source "echo set ?index_format |"
Wow, duh, my_* variables have to be set *to* something.
> I'm kind of su
On 29 Jul 2008 14:14 -0500, by [EMAIL PROTECTED] (David Champion):
> I was going to suggest this approach as well, although I'd have proposed
> "openssl enc" instead of gpg, I guess. Not much call for an asymmetric
> cipher here, especially as the point is to store secret data on a
Off topic, but
> :source "echo set my_var |"
>
> All I get is the error message:
>
> source: errors in echo set my_var |
":set my_var" yields "my_var: unknown variable" too. Try, for example,
:source "echo set ?index_format |"
I was going to suggest this approach as well, although I'd have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, July 29 at 08:40 AM, quoth Nicolas Rachinsky:
>For source, the ending pipe means:
> If the filename ends with a vertical bar (|), then filename is
> considered to be an executable program from which to read input (eg.
> source ~/bin/m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, July 29 at 05:10 PM, quoth Chris Green:
>When running this script at the command line everything works as
>expected - I get the mail in my inbox with the report as the body of
>the mail, about 8KB in size. However, when I execute the same
Er, I fell in this trap too.
It seems like my yesterday messages were blocked (graylisted) in some
way by that robot, and today, after following a link (now inactive) [1]
from a trashmail, my messages were let in.
This is not fair at all.
Due to the transitory nature of this annoyance, I posted
Unfortunately, the msmtp configuration part didn't go so well as I
wished it to go.
msmtp from version 1.4.15 has stdin password reading disabled, or at
least 'deprecated'; from the ChangeLog:
"- Do not let getpass() read from stdin, because we read the mail from
there."
In fact, the password r
Hello everyone,
I've been trying to use Mutt to help me with some simple status monitoring on a
server I'm running. The idea is fairly simple: use a shell script to parse the
output from a disk status report, and if there's a problem then send me an
email with the report attached.
When runnin
14 matches
Mail list logo
