Re: mutt caching DNS queries
On Sat, Mar 24, 2012 at 11:32:49AM +0100 I heard the voice of Lubos Kolouch, and lo! it spake thus: 3) empty/change resolv.conf This is where your issue is. It's not mutt (or anything else) caching DNS responses; it's the resolver library caching resolv.conf. -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
Re: Exploit.IFrame.FileDownload virus??
On Mon, Jul 15, 2002 at 04:56:04PM +0200 I heard the voice of Thomas Baker, and lo! it spake thus: saying Your password is 12zxjkjl123kjl12jz. But the size of each of the messages, according to Mutt, was 65k. that use it, such as Outlook. No surprise there! The only surprise to me is that 250k infected file which appeared P'raps it's the size difference that's kicking you. Are you sure that the message was 65k bytes, not 65k lines? -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: run external command when there is new mail
On Mon, Jun 24, 2002 at 09:41:46PM +0200 I heard the voice of Rocco Rutte, and lo! it spake thus: Have the pros and cons of an external mail notification program already been discussed on the lists? Hmm, what about biff and comsat allthough it doesn't catch all your folders at once... FWIW, I've found xbuffy to be a nigh-on perfect solution; especially with Maildir/'s, as its message-counting then doesn't interfere with mutt's new message detection. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: auto{conf,make,*} probs under freebsd
On Thu, Jun 20, 2002 at 10:33:01PM -0500 I heard the voice of David T-G, and lo! it spake thus: Hi again, all -- I am able to make my cocktail but not, for some reason, install it. Once I run a make I cannot run another one; I get bash-2.05a$ make install Makefile, line 447: Need an operator Makefile, line 448: Need an operator ... I would guess it's because those statements are GNUmake type statements, not Bmake type. Use 'gmake', not 'make'. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: Mutt ignoring 'From ' lines in mailbox
On Tue, Apr 02, 2002 at 12:46:36PM -0600 I heard the voice of David DeSimone, and lo! it spake thus: Mutt chooses to be picker about the From syntax because some mailers don't properly escape a From that is inside the body of the message. Well. Mutt doesn't escape ^From in the body either when it writes, since it always writes with Content-Length: headers. There's no way to win with mbox. You escape From_'s, you mangle the message, which can do things like screw up crypto signatures, and the various other similar problems. You don't escape them and rely totally on Content-Length:, you get yourself into trouble if the file is edited manually or otherwise changed without updating Content-Length to match. Say I change stuff in the middle of a message, and the last line is From something date. If I don't adjust the Content-Length:, depending on how smart the parser is, it'll either: - Puke when (end-of-header+content-length) isn't the start of a new message - Search forward from(end-of-header+content-length) to try and figure out where the next message is, in which case it'll either get an extra empty message (my From) if I added stuff, or skip over a whole message and include it in the current, if I deleted stuff. - Search forward AND backward, in which case, who knows? -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: OT: OS / distro / kernel
On Thu, Mar 28, 2002 at 11:45:42AM -0500 I heard the voice of Ricardo SIGNES, and lo! it spake thus: The question of which is right is probably flame material. We both have our reasons to say we're right. Based on something like Bach's Design of the UNIX Operating System, the kernel is technically the OS. Based on the definition of GNU, many user-space applications are also the OS. And based on the marketting of Sun, the network IS the OS. *inno* O;- -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: M$ Outhouse E. for UNIX
On Wed, Mar 27, 2002 at 09:08:50AM + I heard the voice of
Dave Smith, and lo! it spake thus:
On Tue, Mar 26, 2002 at 08:31:07PM +0100, [EMAIL PROTECTED] wrote:
Just logged into a solaris box. Having set my prompt to 'user@machine'
it says that only root may run 'uname'. My response: 'exit'.
That could just be a local configuration issue.
tabby(21)% uname -a
SunOS tabby 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-5_10
I think he actually means 'hostname', not 'uname'; hostname, on any sane
system, displays the hostname when called with no args, and tries to set
it (requiring root at THAT point) when it has args. Solaris assumes that
you're always trying to set it, even to nothing.
Personally, I use tcsh, so I have a shell builtin for setting it in my
prompt. However, in my uber-.tcshrc, I end up having to work around
Solaris' braindamage in a number of ways. For instance, on every OTHER
OS (including pre-Solaris-renaming SunOS, HP/UX 9, NeXT Mach), I can use
id -u to get the EUID. Solaris?
setenv EUID `id | sed s/[a-z\(\)\=]//g | awk '{print $1}'`
Yippie. Yeah, I could use cut(1) and do it a bit more efficiently
probably, but...
--
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
The only reason I'm burning my candle at both ends, is because I
haven't figured out how to light the middle yet
Re: M$ Outhouse E. for UNIX
On Wed, Mar 27, 2002 at 08:17:05AM -0500 I heard the voice of
David T-G, and lo! it spake thus:
% it (requiring root at THAT point) when it has args. Solaris assumes that
% you're always trying to set it, even to nothing.
Really? I've never heard of that.
nfs5{43} uname -a
SunOS nfs5 5.8 Generic sun4u sparc
nfs5{44} id
uid=1236(dthorbur) gid=1012(u_it)
nfs5{45} hostname
nfs5
nfs5{46}
Or I could be completely talking out of my hat ;p
Most of my Slowaris experience was 2.5.1 (SunOS 5.5.1), before they
decided Hey, 2.6 + 1 = 7!, and I definately recall something that I
considered a pretty basic give me this bit of info command that Solaris
decided to interpret as set this info and yelled at me for not being
root. I THOUGHT that was hostname(1), but I can't say for sure (and I
don't have anything Solaris around to check. It works as expected on
SunOS 4.1.4.
--
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
The only reason I'm burning my candle at both ends, is because I
haven't figured out how to light the middle yet
Re: Don't mention MUAS to fight html email
On Fri, Jan 25, 2002 at 02:09:09PM -0800 I heard the voice of Michael Montagne, and lo! it spake thus: Isn't HTML just text? The tags are evaluated and formatted at the client. So is it just that there is more text than there needs to be? Or is it the links and scripts that are often included? Yes. I'm not even going to INCLUDE it here. http://www.over-yonder.net/~fullermd/misc/msghtml This came into a tech support alias I watch. -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: [OT] html email
On Thu, Jan 24, 2002 at 06:18:43PM -0500 I heard the voice of Brian Clark, and lo! it spake thus: :0: * ^From.*pc-html-user@domain\.com /dev/null Actually, I've found that this: if(/^Content-Type: text\/html/) to $MBOXDIR/crap catches more of my spam than any other of my off-the-cuff heuristics (I mean, like at factor of 2 more, and seemingly more than the rest combined). I read through my 'crap' mailbox every few days, and pretty much end up just hitting 'd' (granted, for about 5 minutes, but better 5 minutes every few days than a few seconds a few hundred times EVERY day, eh?). The only false positive I've had it get was a payment confirmation from the telco's online bill payment (in the rare case that it actually works). Note (for those of you not familiar with maildrop) that it's only doing a header search, so in the case of a HTML attachment or a multipart/alternative, this doesn't trigger; only when the sole part of the body is in text/html. -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: [OT] html email
On Wed, Jan 23, 2002 at 01:45:37PM -0700 I heard the voice of Rob 'Feztaa' Park, and lo! it spake thus: Just because they're the ones that spend the money, doesn't mean they know what to spend it on! 'Course not! That's why the helpful salesdroids send them the pretty fluffy friendly colorful drool-inducing HTML emails to tell them what to spend it on! :) -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: maildir over mbox?
On Sun, Jan 20, 2002 at 06:45:54PM -0800 I heard the voice of Michael Elkins, and lo! it spake thus: Mutt attempts to compensate for this by using quoted-printable encoding when it detects things that might break a signature, thus escaping the problem. But yes, mbox format is more susceptable to corruption of this form. Mutt also bypasses the problem by not doing From_-escaping when the message has its handy-dandy Content-Length: header (which makes it fun to parse the files if you don't think of it... Why does this 8-message folder show 12 messages?). Personally, I use maildir for all my 'active' mailboxes (read: the ones that mail gets delivered to and I read) because it's that much safer, easier and more efficient to alter, and roughly similar in speed to open. I use mbox for my archive mailboxes, because it's simpler and more compact (I don't need to blow a few million inodes on mail archives, thank you very much), and it's faster on the mailboxes with tens or hundreds of thousands of messages. And, having spent rather some time lately writing code to parse mbox's, I'd like to make the following general comment: Bah. -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: maildir over mbox?
On Mon, Jan 21, 2002 at 09:26:55PM -0500 I heard the voice of
Derek D. Martin, and lo! it spake thus:
Um... Oh, are you European? I seem to recall that Europeans switch
the meaning of '.' and ',' in numbers, as compared to us US types...
So perhaps you meant eighty-four thousand five hundred thirty-three
messages?
In which case I would ask, dude, why? I thought my counterpart at
work was a pack rat... ;-)
Hmmm
Well, my current archives have... *does some quick scripting*
(ttyp4):{920}% cat temp | dc
817181
So not quite a million messages, but still far more inodes than I'd care
to eat on /home.
I rotate my folders manually every few weeks; generally, once a mailbox
(in Maildir, being an active mailbox) reached 4000-7000 messages, and
starts taking more than 6 or 7 seconds to open, I tag-all and drop it
into a mbox, then slot that mbox into my archives.
So, does that make ME a packrat? ;)
For reference:
(ttyp4):{921}% du -sh .
2.5G.
--
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
The only reason I'm burning my candle at both ends, is because I
haven't figured out how to light the middle yet
Re: GPG-PGP
Just picking a random point here... On Mon, Dec 31, 2001 at 05:04:22AM -0500 I heard the voice of Philip Mak, and lo! it spake thus: I think that mutt is a good e-mail client, but the default configuration is sub-optimal (vim doesn't format paragraphs well by default, some of the Well, vim does whatever you've configured it to do, it's not a part of mutt :) Thus, either vim was doing the same bad formatting using it under pine (and I remember it being an IMMENSE pain to use an external editor in pine), or you were just using *twitch*shudder* pico, in which case you could *twitch*shudder* use pico for your editor in mutt just as easily. When I made the pine-mutt switch, back around 0.6 days, I was lucky in having a friend who used mutt, who thinks in ways vaguely like the ways I do, so I just snarfed his .muttrc and went with it. I still have pine-remnants in my config (my change-folder is still bound to 'l', for instance, but that works out to be more efficient anyway. Composing a new message is bound to 'c', and that is probably LESS efficient, but that point's more arguable). -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: Escaping From separator line in an mbox
On Wed, Dec 26, 2001 at 09:22:33PM -0500 I heard the voice of David T-G, and lo! it spake thus: Thus, it should be sufficient to match on any ^From_ line as long as you're working with an mbox file (which you can confirm by checking the very first line of the file, which should tell you one way or another regardless of whether or not the mbox file has one or more messages in it) and then also ignore any ^From_ that you might find, and not worry about ^From_ if you're not in an mbox file. Note that this can (also) break. I was just testing some mbox-parsing code the other day, and I needed a quick mbox of reasonable size to test it against. Hey, how about ~/mail/sent? But it's got bare ^From lines in mid-message where they 'naturally' appeared. So, either you need a bit more smarts than just ^From , or mutt doesn't write 'sent' as a true mbox. The 'mbox' manpage from qmail says: --- MESSAGE FORMAT A message encoded in mbox format begins with a From_ line, continues with a series of non-From_ lines, and ends with a blank line. A From_ line means any line that begins with the characters F, r, o, m, space: [...] --- Which seems to imply the POV that ^From should be a sufficient pattern (in which case, watch out for your sent box!) Mutt seems to use a bit more smarts. See is_from() in from.c for details. -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: Escaping From separator line in an mbox
On Thu, Dec 27, 2001 at 06:39:56AM -0500 I heard the voice of David T-G, and lo! it spake thus: % % I was just testing some mbox-parsing code the other day, and I needed a % quick mbox of reasonable size to test it against. Hey, how about % ~/mail/sent? One would think so... % % But it's got bare ^From lines in mid-message where they 'naturally' % appeared. So, either you need a bit more smarts than just ^From , or % mutt doesn't write 'sent' as a true mbox. And I trust that this all works when you open it with mutt, right? [Hey, it never hurts to check.] It works just fine with mutt. And your regex will break on it too. For instance: (from forwarding on a newsgroup post, some names changed to protect the guilty) --- From [EMAIL PROTECTED] Tue Jan 12 08:05:47 1999 Message-ID: [EMAIL PROTECTED] Date: Tue, 12 Jan 1999 08:05:47 -0600 From: Me [EMAIL PROTECTED] To: You [EMAIL PROTECTED] Subject: Numero Uno from Matt's Arhives Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i X-WorldsBestEditor: vi Status: RO Content-Length: 4877 Lines: 103 From [EMAIL PROTECTED] Mon Sep 7 19:35:34 1998 Path: news.futuresouth.com!news.futuresouth.com!dca1-feed3.news.digex.net!digex! newsfeed.axxsys.net!newspump.monmouth.com!newspeer.monmouth.com!intgwpad.nntp.te lstra.net!nsw.nntp.telstra.net!news.syd.connect.com.au!news.mel.connect.com.au!u nico.com.au!thorfinn From: [EMAIL PROTECTED] (Thorfinn) Newsgroups: alt.sysadmin.recovery [...] --- Mutt, I guess, outsmarts the mbox by reading Content-Length:, which you'd pretty much have to do I guess. To me, it just seems like putting too much trust in the LDA, whatever that may be, but... Then again, why not trust? mbox is fragile as hell anyway, what's one more shaky assumption? ;) -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: Escaping From separator line in an mbox
On Thu, Dec 27, 2001 at 06:54:57AM -0500 I heard the voice of David T-G, and lo! it spake thus: % And your regex will break on it too. For instance: [snipped] Because of the single space before the day in each header, right? If that's the case note that I noted it and didn't guarantee it ;-) No, because the first 'content' line of the body of the message is an unescaped otherwise-valid From_ line. Using your regex (or the more simplisting /^From /), it would be identified as a seperate message, rather than part of the actual message that it is. The ONLY way to 'get it right' that I can see is to trust the Content-Length: header. (The problem that cropped up in my test parse. Hey, this is my 'sent' folder... why are there messages from people OTHER than me? Waitaminute) -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Holy biff(1), Batman! (was Re: Checking new mail - The Solution)
On Fri, Dec 07, 2001 at 07:28:32AM -0500 I heard the voice of David T-G, and lo! it spake thus: % % The appalling biff program requires comsat to do it's job, so that % is why I guess Slackware has it enabled. So the real fix would be to modify /etc/profile rather than simply turn off comsat and have biff trying to run anyway. *bzzt* ;) The real fix is to turn off biff notification in your MTA. The pattern goes something like this: - MTA delivers, notifies comsat - comsat notifies terminals with 'biff y' set. Note that biff isn't a daemon of any sort; it's comparable to mesg(1), in that it just sets modes (looking at my /usr/bin/biff source, all 109 lines of it (including comments etc), all it does is change the u+x mode of the STDERR tty. See URL:http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.bin/biff/biff.c?rev=1.9content-type=text/x-cvsweb-markup ). So, turning off biff y, and comsat will still do everything except deliver the message to the tty. Turn off comsat, and you'll still (probably) get packets sent to it by the MTA. Turn off biff/comsat notification in the MTA (or maybe the MDA, not entirely sure), and you'll stop getting the packets and all the rest. -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: mbox Postmark Line vs. Message Date Header?
Sam, This is my experience, yes. Another advantage is peace of mind that you'll never again fall prey to a corrupted mailbox due to a delivery occurring at the wrong time. But shouldn't well-behaved MTAs and MUAs perform locking that prevents this from happening? Yes, they should perform locking. No, it won't prevent it. 1) System crashes in the middle of delivering mail. 2) Filesystem a few bytes from full. Open mbox, read messages. Sync mailbox; it starts rewriting a bunch of Status: headers, which ends up extending the file. *boom* filesystem full, you've lost/overwritten/corrupted stuff. I'm sure with a bit of effort, we could find a number of other failure modes. -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: line length
On Tue, Nov 13, 2001 at 11:48:59AM -0600 I heard the voice of David Champion, and lo! it spake thus: There is no tw/textwidth in vi -- use wm/wrapmargin instead. Set it to the width of your right-hand margin to auto-wrap text. (For example: set wm=8 to wrap at 72 columns on an 80-column screen.) The downside of this is that it then becomes highly dependant on your terminal width. For those of us who keep 30-40 xterms around, and fire up editors all over the place, that's not necessarily a fixed quantity :) I use the 'wraplength' property, which specifies ling length instead of something so ethereal as 'right margin size'. The DOWNSIDE is that (at least in the case of nvi) it doesn't keep re-wrapped as you add/remove text, but that doesn't particularly bother me; I map ^R to fmt foo if I do any major changes. -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: 2 Q's (my wishlist)
On Fri, Oct 26, 2001 at 01:18:32PM -0400 I heard the voice of
David T-G, and lo! it spake thus:
...and then Jeremy Hankins said...
%
% First of all, I'd like to see the hostname portion of the Message-ID in
...
% way to do this. I guess I could set up a procmail recipe to put it in
% the subject or something, but that seems rather ugly.
Yes, it does; I'd think that poking at the From: header would be better.
In either case, though, I don't know how you'd display in the index from
the MessageID.
See the {ignore,unignore,hdr_order} config params. Mine look something
like this:
ignore *# this means ignore all lines by default
unignore from: reply-to: to cc subject date x-mailer user-agent message-id
Resent-From: Resent-To: Resent-Date: Followup
hdr_order from: reply-to: to cc date subject x-mailer user-agent message-id
Resent-From: Resent-To: Resent-Date: Followup
--
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
The only reason I'm burning my candle at both ends, is because I
haven't figured out how to light the middle yet
Re: 2 Q's (my wishlist)
On Fri, Oct 26, 2001 at 01:55:37PM -0400 I heard the voice of
David T-G, and lo! it spake thus:
...and then Matthew D. Fuller said...
%
% See the {ignore,unignore,hdr_order} config params. Mine look something
% like this:
Index, not pager.
Ooh, ugh! Coffee BEFORE mail!
Well, you can display the full message ID easily enough (%i), but just
the host part would be tricky. I think the 'best' way to do this would
be at the source, not the destination. Sticking a `hostname` in the
subject would work, or having the From: address be set by hostname (%a in
index) would work. I don't think you'd be able to get just the hostname
out of message-id in the index without some sourcery, though...
--
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
The only reason I'm burning my candle at both ends, is because I
haven't figured out how to light the middle yet
Re: OT Procmail rule not working.
On Wed, Oct 24, 2001 at 07:13:57PM -0700 I heard the voice of Will Yardley, and lo! it spake thus: i use: #mutt :0 * ^Return-Path:.*mutt-users-owner.*@mutt\.org lists:mutt/ FWIW, I'd venture you'd be better off using the Sender: header. I moved over to maildrop for filtering a while back (too dang sick of procmail's various stupidities), and my rule looks like: # Mutt if(/^Sender: owner-mutt-users/) to $MBOXDIR/mutt-users Using the .*'s in the rule really kills the efficiency of it; with Sender:, you don't need any wildcards, so it's 'quicker'. Of course, whether it's a noticeable difference is questionable... -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: Managing PGP Keyrings
[400 messages later...]
On Fri, Oct 12, 2001 at 09:18:59PM -0400 I heard the voice of
David T-G, and lo! it spake thus:
At the moment I'm just catching all keys into catch-all-keys and moving
each one with my gpg--move script (available if anyone is interested;
it's brute force but it works); I plan to use some folder-hooks to
specify the proper mailing list ring so that when I'm reading =F.mutt and
mutt tells gpg to download a key it drops it into mutt instead of the
catch-all-keys bin, but I haven't gotten around to it yet :-)
Well, I just forced myself to make the switch to GPG, because of the
total lack of flexibility in the key management of PGP 5, and did this.
Example:
folder-hook mutt'set pgp_verify_command=~/.mutt/gnupg_verify.sh muttlists %s
%f;my_hdr From: [EMAIL PROTECTED]'
(ttyp0):{283}% cat ~/.mutt/gnupg_verify.sh
#!/bin/sh
exec
gpg --no-verbose --no-options --no-default-keyring \
--keyring ~/.gnupg/pubring.$1.gpg --secret-keyring /dev/null \
--keyserver wwwkeys.pgp.net --batch --output - --verify $2 $3
A bit hackish, but it works.
--
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
The only reason I'm burning my candle at both ends, is because I
haven't figured out how to light the middle yet
