Gnus development mailing list
 help / color / mirror / Atom feed
From: Norbert Koch <n.koch@delta-ii.de>
Subject: Re: pop password
Date: 07 Nov 1998 13:47:30 +0100	[thread overview]
Message-ID: <vo3e7vy8il.fsf@apollonius.delta-ii.de> (raw)
In-Reply-To: Stainless Steel Rat's message of "07 Nov 1998 08:26:36 -500"

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> "viteno" == Norbert Koch <n.koch@delta-ii.de> writes:
> 
> viteno> Anyway, I'm wondering why I do have to set 'pop3-password'. IIRC,
> viteno> 'nnmail-pop-password' should have the same effect, shouldn't it?
> 
> Not really.  You see, you should not manually set either of them.  If you
> do, your POP password is stored in memory, which is very bad.
> 
> Although, properly speaking, pop3-movemail when called by Gnus should
> inherit Gnus' (nnmail's) password.  The appended patch should fix that.

[...]

Thanks for the patch, it works :-)

Anyway, basically I agree with you that it's not the best thing to
store the pop password (not my login passwd BTW) on disk. OTOH if this
means to type the password every odd minute, it's going to become
annoying over the time. If I reduce access to my mail folder wherein I
keep my gnus initialisation file, only I and all sorts of BOFH are
able to gain this information. But, IMO in a UNIX world I run this
risk all day long.

Cheers, norbert.

-- 
Cursed, cursed creator! Why did I live? Why, in that instant, did I
not extinguish the spark of existance that you had so wantonly
bestowed?


      parent reply	other threads:[~1998-11-07 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-07 11:47 Norbert Koch
     [not found] ` <x790hnab1v.fsf@peorth.gweep.net>
1998-11-07 12:47   ` Norbert Koch [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vo3e7vy8il.fsf@apollonius.delta-ii.de \
    --to=n.koch@delta-ii.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).