Re: RSA keys with GPG
* Lars Hecking ([EMAIL PROTECTED]) [000327 08:22]: Terje Elde writes: Hi all, I've got a rather nice PGP setup with mutt, using the gpg-2comp prog as shown in the examples (1.1.9i IIRC), however when I'm trying to encrypt to RSA keys, I get the following: 1.1.9i doesn't use gpg-2comp anymore. Ahh, that explaing a lot :) gpg: writing to `-' gpg: DSA signature from: BC26460D Terje Elde (work) [EMAIL PROTECTED] gpg: NOTE: --no-literal is not for normal use! gpg: NOTE: --no-literal is not for normal use! usage: gpg [options] --encrypt [filename] Press any key to continue... Gnupg is using your DSA key here. What exactly are you trying to do? This was an attempt at sending a signed email encrypted to a RSA key. Everything works when encrypting to DSA keys tho. Do you have your RSA key in they key db? Yes. Thus I'm only able to use DSA/ElGamal keys, which is really a PITA. Am I the only one having these problems? Apparently :-) Just my luck ;) Can you post or email your .gnupg/options file? set pgp_decode_command="gpg %?p?--passphrase-fd 0? --no-verbose --batch -o - %f" set pgp_verify_command="gpg --no-verbose --batch -o - --verify %s %f" set pgp_decrypt_command="gpg --passphrase-fd 0 --no-verbose --batch -o - %f" set pgp_sign_command="gpg-2comp --no-verbose --batch -o - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f" set pgp_clearsign_command="gpg-2comp --no-verbose --batch -o - --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f" set pgp_encrypt_only_command="pgpewrap gpg-2comp -v --batch -o - --encrypt --textmode --armor --always-trust -- -r %r -- %f" set pgp_encrypt_sign_command="pgpewrap gpg-2comp --passphrase-fd 0 -v --batch -o - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f" set pgp_import_command="gpg --no-verbose --import -v %f" set pgp_export_command="gpg --no-verbose --export --armor %r" set pgp_verify_key_command="gpg --no-verbose --batch --fingerprint --check-sigs %r" set pgp_list_pubring_command="gpg --no-verbose --batch --with-colons --list-keys %r" set pgp_list_secring_command="gpg --no-verbose --batch --with-colons --list-secret-keys %r" #set pgp_getkeys_command="wrap.sh -g %r" set pgp_getkeys_command="" These should be direct copies from the example. Or at least the way the example was at one time :) Terje -- Xlehveh rhkau fudwuh få mydtemi dåh tk aqd rhkau jyt få kdyn (jyt == fudwuh?)
Re: Starting mutt with threads collapsed?
Ben Beuchler ([EMAIL PROTECTED]) wrote : I have searched through the manual and can't seem to track down a way to start mutt with threads already collapsed. Perhaps I'm missing something elemental about the way mutt works... Hello, try this: folder-hook . push \eV I don't know version of mutt when push come in, but it works in 1.1.9 -- Keso don't worry about glory
Re: mutt-1.1.9 refresh problem
Shao Zhang [EMAIL PROTECTED]: I am using mutt 1.1.9i. When using gnupg to verify the signature, the screen is not properly refreshed. ie. some of the characters from the index page are still displayed. So you're looking at the index listing and you press SPACE or RETURN to view the current message, and you then see a messed up display which still contains part of the index listing together with the output of gnupg and the message contents. Is that correct? Yes. Does the display become correct again if you then type C-l? Yes. Refresh will take away those chars from the index page. Scroll down and then up will do the trick as well. The only explanation I can think of is a bug in curses or slang which is manifested by some strange characters in the output of gnupg. In what language is the output of gnupg? Does the output of gnupg look normal? everything seems normal except some characters from the index page. Shao Zhang - Running Debian 2.1 ___ _ _ When I partially upgraded my system from Debian 2.1 to Debian 2.2, I lost colour and suffered some other nastinesses until I adjusted my ~/.Xdefaults to get TERM=xterm-debian again. Perhaps you have some similar sort of configuration confusion. You could try running mutt on some different types of terminal (Linux console, xterm, etc) to see if this helps diagnose a terminfo problem. You could try intercepting gnupg with a script to catch its output and check the output for any control characters. Recently I've had some experience of messed up displays because I was hacking newt and slang to understand UTF-8 and yesterday I was implementing my own simple virtual terminal to run them on, but I can't think how to diagnose your problem remotely ... Usually I just attach gdb and look at SLcurses_Stdscr and SL_Screen ... Edmund
Re: Solution: sender profiles
Mikko Hänninen [EMAIL PROTECTED]: This would be changed if there indeed were a command to change the current environment variables, like has been suggested. Maybe for 1.3... I did send out a patch which adds the command "setenv" to Mutt. Perhaps I should check it still works and ask Jeremy Blosser to add it to links.html ... Edmund
Re: Reading gzipped mailboxes
On Sun, Mar 26, 2000 at 06:12:43PM -0500, Fairlight wrote: I've wished for a gzipped mailbox read feature myself. I have a shell function that I use as a wrapper around mutt to handle gzipped mailboxes, but it's rather ugly. I'd much prefer that mutt could handle it internally. However, I'll politely disagree with you on PGP encrypted mailboxes being fantastic. In fact, it would be slow and cumbersome, for the simple reason that in the case of a mailbox you want to add onto, you'd have to know if it was PGP encrypted (which would likely mean creating an ASCII armoured file, which would then require a third layer of gzipping to get it BACK down to a reasonable size), and also have to unencrypt it to read it, write to it, and then reencrypt it entirely over again. Actually, I was thinking of something just a tiny bit simpler. I was thinking about writing a wrapper like the one I wrote for gzip, that would simply check the extension of the file loaded via 'mutt -f'. In which case, the file does not need to be ascii-armored, could use pgp's private key encryption, and should remain reasonable in size ( if I'm not mistaken, pgp compress it's files ). If I'm wrong about pgp compressing it's files, please let me know, that will greatly complicate things. From a development standpoint, that's very ugly and very messy, and I wouldn't be surprised if they say it will never happen...for the reasons listed above. Yeah, but I can always hope. Actually, I noticed in another reply that someone has a patch out. I'm looking forward to trying it out. I second the motion for a gzip-capable mutt though. (No wisecracks about, "Sure, just send in the patch!" either!) :) Thanks. B-) Sam
Re: Reading gzipped mailboxes
On Mon, Mar 27, 2000 at 01:11:58AM +0200, Sebastian Helms wrote: Hi Sam, * Sam Alleman wrote on 27 Mär 2000: I was wondering if there was any simple way to read gzipped mailboxes. Yes, Roland Rosenfeld has a patch which enables mutt to read, write and append to gzipped mailboxes. I am very happy about this ;-) http://www.spinnaker.de/mutt/ I hate to be a bother, but I wonder if someone can e-mail this patch to me? I'm currently on a survey boat off the coast of Japan, with no Internet access. Also, I hope this patch works with mutt-1.0.1i, that's the newest version that I have with me. Thanks. Sam
S/MIME
What is the status on the S/MIME implementation that was mentioned on the list a while ago? Is it in the current snapshot? /magnus
Re: Starting mutt with threads collapsed?
On Mon, Mar 27, 2000 at 10:34:24AM +0200, Martin Keseg - Sun Slovakia - SE wrote: I have searched through the manual and can't seem to track down a way to start mutt with threads already collapsed. Perhaps I'm missing something elemental about the way mutt works... Hello, try this: folder-hook . push \eV I don't know version of mutt when push come in, but it works in 1.1.9 Excellent! Thanks. Ben -- "There is no spoon" -- The Matrix
Viewing other mailboxes...
I am using mutt 1.1.9. I have $mbox set to "=read" and it does indeed save all read messages there. However, when I attempt to change to that folder, it just shows me the actual mail file rather then a list of messages. Actually, it's doing this with every box except my actual inbox. I'm using mutt on a local mail spool, however the .muttrc I am using is a modified form of the .muttrc I use to access my IMAP box at home. Is it possible that I missed a couple of settings that should've been changed when I switched from IMAP to a local mail spool? Ben -- "There is no spoon" -- The Matrix
Re: RSA keys with GPG
On Sat, Mar 25, 2000 at 09:38:58PM +, Lars Hecking wrote: Terje Elde writes: I've got a rather nice PGP setup with mutt, using the gpg-2comp prog as shown in the examples (1.1.9i IIRC) Fine. 1.1.9i doesn't use gpg-2comp anymore. If one of the message recipients is using PGP-2, it won't work without gpg-2comp. gpg: writing to `-' gpg: DSA signature from: BC26460D Terje Elde (work) [EMAIL PROTECTED] gpg: NOTE: --no-literal is not for normal use! gpg: NOTE: --no-literal is not for normal use! usage: gpg [options] --encrypt [filename] Press any key to continue... Gnupg is using your DSA key here. What exactly are you trying to do? Do you have your RSA key in they key db? Seems that this is your default key. If you want to use something else here, either specify the key in the gpg-2comp script (better if your are going to use it regularly) or choose a key with the "sign as" function in the pgp submenu of the compose menu. Gero
Re: RSA keys with GPG
On Mon, Mar 27, 2000 at 10:09:31AM -0600, Jason Helfman wrote: however last week some mentioned a gnu.rc file sent out with mutt. I browsed through the file system and found nothing of the sort. A gpg.rc is in the contrib directory of the 1.1.x versions, don't know about a gnu.rc . I am wondering, however, when I sign an email, it is appended to the bottom. What is this I see when there is ---SHA something or other --- at the top, then the included message, then the closing of the pgp information. How is this being done? Is this through a clearsign? How would I take advantage of these options in mutt? You see the hash algorithm there, indeed followed by a clear-sign signature. The format can't be altered by the user, it must conform to RFC 2015. The pgp menus in mutt should provide all what you need, the only thing mutt can't figure out always is which key an encryption software uses by default. Gero
changing To: in a reply
How might the To: be changed in a reply to a particular address, other than manually? I'm aware of the send-hook/my_hdr limitation specified in 3.17 :/ -- Patrick Walsh Edmonton AB CA
resend-message, $copy
Why does resend-message (ESC-e) not respect $copy? Presumably if $copy is set, one wants a copy saved, of all messages sent. (this function is not listed in the 1.1.9i manual.txt) -- Patrick Walsh Edmonton AB CA
Re: S/MIME
2000-03-27-06:06:50 Magnus Stenman: What is the status on the S/MIME implementation that was mentioned on the list a while ago? I've not been interested in it much myself, but as best I can recall from what I saw on the list, S/MIME would be trivial to do, might not even require any mods to mutt itself, just config files, if only there were a helper program, after the style of pgp or gpg, to do the actual work. And we're waiting for someone to step up with such a helper program. I recall rumours that some of the hard parts of the job might be handled already by some of the less-well-documented nether reaches of OpenSSL. But nothing sufficiently detailed to start testing with:-). -Bennett PGP signature
keeping new flag
Hello,
I'm using mutt 1.0.1i.
Every time i quit a mailbox containing new mails, the "N" flag of this
mailbox is gone (in the mailbox index).
Is there a way to keep this flag, so you can always see in which mailbox
new (or unreaded) mails are (or change it to "O")?
BTW: is it possible to see in the index if there are marked messages
("!" flag) in a mailbox?
thx!
--
greetings . . supio ( Marc Noller ) | [EMAIL PROTECTED] | http://oipus.net |
Re: keeping new flag
supio writes: Hello, I'm using mutt 1.0.1i. Every time i quit a mailbox containing new mails, the "N" flag of this mailbox is gone (in the mailbox index). Is there a way to keep this flag, so you can always see in which mailbox new (or unreaded) mails are (or change it to "O")? E(x)it instead of (q)uit. Other than that, check out the set-flag/clear-flag commands, by default bound to w/W.
Re: Reading gzipped mailboxes
Sam -- ...and then Sam Alleman said... % On Mon, Mar 27, 2000 at 01:11:58AM +0200, Sebastian Helms wrote: % Hi Sam, Yeah, what he said :-) % % * Sam Alleman wrote on 27 Mär 2000: % % I was wondering if there was any simple way to read gzipped mailboxes. % % http://www.spinnaker.de/mutt/ % % I hate to be a bother, but I wonder if someone can e-mail this patch to me? Have you already gotten it? If not, I'll send it to you -- or whoever beats me to it will either send the patch to the list as well (it's not terribly large, but it's about 45k uncompressed or 11k compressed) or at least send a note to the list letting us know that you have a copy :-) % I'm currently on a survey boat off the coast of Japan, with no Internet % access. Also, I hope this patch works with mutt-1.0.1i, that's the newest % version that I have with me. Thanks. Yep; the version that I have, at least, is revved to 1.0. I have no word yet whether there's a newer version for 1.1.x where x is high... % % Sam :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: Reading gzipped mailboxes
Mark -- ...and then Fairlight said... % On Mon, Mar 27, 2000 at 03:32:15AM +0900, Sam Alleman thus spoke: % % In fact, if mutt could handle some sort of encrypted mailbox seamlessly % that would be *EXCEPTIONALLY* cool! Pgp encrypted mailboxes would be % fantastic. Thanks in advance for any help you can provide. % % I've wished for a gzipped mailbox read feature myself. Then you probably need to check out Roland's patch if you haven't already :-) % % However, I'll politely disagree with you on PGP encrypted mailboxes being % fantastic. In fact, it would be slow and cumbersome, for the simple reason It would definitely be slow, but probably not terribly slower than .gz mailboxes... % that in the case of a mailbox you want to add onto, you'd have to know if % it was PGP encrypted (which would likely mean creating an ASCII armoured file, % which would then require a third layer of gzipping to get it BACK down to a % reasonable size), and also have to unencrypt it to read it, write to it, % and then reencrypt it entirely over again. I must politely disagree :-) The compressed-folders patch works based on folder extensions, so you name your zipped folders *.gz and then tell mutt how to read (gunzip), append (gzip -c ), and write (gzip) the folder style. Along those same lines, you should be able to specify a *.pgp folder type and tell mutt how to read and write the folder (and leave off append, since I don' think that applies). Admittedly, this is untested, but I've been casually contemplating for quite a while now encrypting an entire mailbox -- and, thanks to this discussion, remembered that I didn't have to get fancy and hope that the patch could handle *.gz.pgp mailboxes since pgp does compress :-) Since it's just a file extension and a few command specs, it ought to be easy (and no, you don't want to store the decrypt passphrase in your .muttrc file! ;-) % % From a development standpoint, that's very ugly and very messy, and I This is pretty true, it seems to me, and it looks like the existing patch *won't* be integrated into the main distribution (though it's such a favorite that RPMs are even distributed with it patched in and configured!) as long as Roland maintains it and the user community can get it from his site and thus not bug the developers for support. % wouldn't be surprised if they say it will never happen...for the reasons % listed above. % % I second the motion for a gzip-capable mutt though. (No wisecracks about, % "Sure, just send in the patch!" either!) :) Sure, just go get the patch! ;-) % % mark- % -- % Fairlight- |||[EMAIL PROTECTED] | Fairlight Consulting % __/\__ ||| "I'm talking for free... | http://www.fairlite.com % ||| It's a New Religion..." | [EMAIL PROTECTED] % \/||| PGP Public Key available via finger @iglou, or Key servers :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: Viewing other mailboxes...
Ben -- ...and then Ben Beuchler said... % I am using mutt 1.1.9. I have $mbox set to "=read" and it does indeed % save all read messages there. However, when I attempt to change to that That's good; it's behaving :-) % folder, it just shows me the actual mail file rather then a list of % messages. This is good, too, unless you've specifically set up your =read "folder" (more on that) as a Maildir or MH folder instead of an mbox "folder" -- which, as you've probably found, is a file. Then, again, I don't use those formats and so I don't know how they look in the browser... AFAIU, mutt folks use the terminology "folder" and "file" pretty interchangeably; although $folder is definitely a directory where all of your mail stuff lives, folder-hooks apply to mailboxes (in whatever format) themselves. As such, it's tricky to tell whether you are specifically talking about mailbox formats (controlled for *creation* of new mailboxes by $mbox_type, since mutt saves to a box in whatever form it has) or user mailbox management. For my humble dissertation on the latter, see below. offtopic-to-other-thread Hey, I bet that you could define a *.tar folder type for the compressed patch and compress your maildir and mh folders that way :-) /offtopic-to-other-thread % % Actually, it's doing this with every box except my actual inbox. % % I'm using mutt on a local mail spool, however the .muttrc I am using is a % modified form of the .muttrc I use to access my IMAP box at home. Is it % possible that I missed a couple of settings that should've been changed % when I switched from IMAP to a local mail spool? The way I read your note, you have your incoming mail somewhere (and probably conveniently shortcutted to !), you have a mail folder like $HOME/Mail that is assigned to $folder and expands the '=' shortcut, and you currently have a single mbox-format file "read" in your "=" dir ($HOME/Mail in this example) containing all of the messages you've ever read all jumbled together. You want, however, to have "read" be a subdirectory with user mailboxes underneath, so everything from joe gets saved to =read/joe and so on. I'm starting to experiment with this myself, and think that you want to look at the save-hook setting with the %o expando (as I understand it, this supplies the 'o'riginal save filename when you're rewriting the location -- like stuffing it down a directory level). I don't know if that's only available by patch, though, and haven't done any experimentation with it. I expect a followup from Mikko shortly :-) % % Ben % % -- % "There is no spoon" % -- The Matrix :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: keeping new flag
Marc / supio --
...and then supio said...
% Hello,
Hi there!
%
% I'm using mutt 1.0.1i.
% Every time i quit a mailbox containing new mails, the "N" flag of this
% mailbox is gone (in the mailbox index).
Well, that's the function of quit as defined by default, so the
developers are pretty happy with your statement :-) At least, as long as
the "N" changes to "O" rather than changing to " ".
% Is there a way to keep this flag, so you can always see in which mailbox
% new (or unreaded) mails are (or change it to "O")?
I know of one way for sure and think I know of another -- perhaps only
available by patch.
The first way is to just e'x'it instead of 'q'uit when you want to get
out of mutt; all changes (like flags) are thrown away. If you want
deleted messages to be purged and previously new mails that have been
read to stay read, you can use '$' to sync the mailbox before you exit.
I have a terrible habit of accidentally hitting 'q' while reading $MAIL
and thus trashing all of my N flags, so I added
folder-hook . bind index q quit
folder-hook $MAIL bind index q sync-mailbox
to my .muttrc since I *do* like syncing the mailbox (I do it often and
automatically, just like esc-W-a in vim to run my "write file" macro and
start editing again). Works for me.
The other way is to set nomark_old (I think) so that new messages are not
changed to old messages when you quit. I haven't played with it, and I
*think* that mark_old is part of the standard mutt distro and therefore
can be unset as above or with "unset mark_old", but I haven't played with
it.
%
% BTW: is it possible to see in the index if there are marked messages
% ("!" flag) in a mailbox?
Before you open the mailbox with mutt, you mean? Not to my knowledge,
since mutt doesn't scan message headers until it's actually opening the
mailbox (much to the chagrin of many folks who want to see boxes with new
mail that are being touched by other things like biff).
If you want highlighting of flagged/marked messages once you're in the
mailbox, that's easy.
%
% thx!
HTH HAND
%
% --
% greetings . . supio ( Marc Noller ) | [EMAIL PROTECTED] | http://oipus.net |
:-D
--
David T-G * It's easier to fight for one's principles
(play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
The "new millennium" starts at the beginning of 2001. There was no year 0.
Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh*
PGP signature
Re: Upgrading?
Jason -- ...and then Jason Helfman said... % I am very happy with my version of mutt 1.0.1i Glad to hear it! So are lots of folks, in fact :-) % % Is their reason to upgrade, and if I were to, how would I go about it? There's always a reason to upgrade :-) I haven't checked the NEWS file for 1.1.9, but I expect general added stability as well as enhanced IMAP support to top the list of advancements. % I am more familiar with upgrading through rpm packages, but I assume % you go through a standard building of a tarball and the binarys get % written over... If you want to wait for 1.2 (the next stable release, for which 1.1.9 is a candidate), then [I understand that] you can expect to see RPMs and not have to sweat building from sources... % % thanks HTH HAND % % --- % /helfman % "At any given moment, you may find the ticket to the circus that has % always been in your possession." % % Fingerprint: 2F76 2856 776A 3E07 9F3E 452A 17D9 9B28 D75E 0A36 % GnuPG http://www.gnupg.org Get Private! :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: resend-message, $copy
Patrick -- ...and then Patrick Walsh said... % Why does resend-message (ESC-e) not respect $copy? Presumably if % $copy is set, one wants a copy saved, of all messages sent. While I accept your argument, I think that the general premise is that you already have a copy of the message (since you're resending it) and you're not making any changes (like adding the recipient to the headers) and so a copy would be superfluous. Now, I don't have esc-e in my copy, so that must be new (as alluded to below), and maybe I don't understand the resend-message function yet. I'm thinking of bounce-message at the moment, but could also consider edit (for editing an existing message and then shipping -- but I believe that edit - send *does* honor $copy). % % (this function is not listed in the 1.1.9i manual.txt) Can't help ya with that; haven't been there yet :-) % % -- % Patrick Walsh % Edmonton AB CA :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
screen flipping in gnome-terminal
I think this is a mutt question and not a gnome-terminal question, but please correct me if I'm wrong. When I run mutt in a normal xterm, composing a new message (in emacs via emacsclient) leaves whatever I was viewing in mutt intact until I tell emacs I'm done. When I run mutt in gnome-terminal (the one distributed recently in the Helixcode GNOME release), mutt screen flips so that I see what was in the terminal window before I invoked mutt (and not what I was seeing in mutt). After a while, all I see is a whole lot of lines that say "Waiting for Emacs..." or something like that. This is annoying, and I'd like it to stop, but I couldn't find anything in the manual that helped. Any suggestions? Tia. -- - Jeff Abrahamson [EMAIL PROTECTED] 610/270-4845
Re: keeping new flag
On Mon, Mar 27, 2000 at 07:05:24PM +0200, supio ([EMAIL PROTECTED]) said:
Hello,
I'm using mutt 1.0.1i.
Every time i quit a mailbox containing new mails, the "N" flag of this
mailbox is gone (in the mailbox index).
Is there a way to keep this flag, so you can always see in which mailbox
new (or unreaded) mails are (or change it to "O")?
I would have thought the mails would be marked as 'O'...you seem to be
implying they cease to be marked at all. Anyway, I'm not sure if it's
what you want, but look up
set mark_old = no
BTW: is it possible to see in the index if there are marked messages
("!" flag) in a mailbox?
I don't think so.
--
Jim Toth
[EMAIL PROTECTED]
Re: Upgrading?
Jason Helfman [EMAIL PROTECTED] said: I am very happy with my version of mutt 1.0.1i Is their reason to upgrade, and if I were to, how would I go about it? I am more familiar with upgrading through rpm packages, but I assume you go through a standard building of a tarball and the binarys get written over... If you don't want to depend on RPMs I encourage you to take a look at the encap-system(1) which makes it easy to manage packages that you build on your own: installing, upgrading, uninstalling is all a breeze - and you could also play around with two different versions to find out if there's ample reason to make a final upgrade. (1) http://encap.cso.uiuc.edu/ (gen. information) http://encap.cso.uiuc.edu/epkg/ (encap package-manager) Morten
muttzilla.....trn
is it possible to use mutzilla for netscape for use for mail (mutt) and news (trn) or can only slrn be used??? also can it only be used for only news, or only mail i have tried to get it to only use mail, but unsuccessfull...I want to use it for both, though. --- /helfman "At any given moment, you may find the ticket to the circus that has always been in your possession." Fingerprint: 2F76 2856 776A 3E07 9F3E 452A 17D9 9B28 D75E 0A36 GnuPG http://www.gnupg.org Get Private!
Re: keeping new flag
On Mon, Mar 27, 2000 at 02:08:24PM -0500, David T-G wrote:
% Every time i quit a mailbox containing new mails, the "N" flag of this
% mailbox is gone (in the mailbox index).
Well, that's the function of quit as defined by default, so the
developers are pretty happy with your statement :-) At least, as long as
the "N" changes to "O" rather than changing to " ".
That's correct and works fine :)
But the real problem seems to be myself describing my wishes bg.
So with "quit" I actually meant changing to the "mailbox view" (with "c" and
tabtab by def., or -y on startup), where all mailboxes, given mutt with
"mailboxes (...)" in the muttrc, are listed.
% BTW: is it possible to see in the index if there are marked messages
% ("!" flag) in a mailbox?
Before you open the mailbox with mutt, you mean? Not to my knowledge,
since mutt doesn't scan message headers until it's actually opening the
mailbox (much to the chagrin of many folks who want to see boxes with new
mail that are being touched by other things like biff).
Yeah, thats also my real problem with the "N" flags. :)
So mutt only looks on the timestamp of the mailbox if there are new
mails and sets the N flag as long as it hasn't synced?
I have now 24 mailboxes and If there are new mails I often
only look into what's there and quit mutt to read them later.
To open each mailbox the next time seeking the new mails is a bit
annoying... ;)
If you want highlighting of flagged/marked messages once you're in the
mailbox, that's easy.
I know but all would be nice "outside"...
--
greetings supio ( Marc Noller ) | [EMAIL PROTECTED] | http://oipus.net |
-|
- Filstal.Online e.V. http://www.fto.de |
--- LinuxUserGroup Filstal http://lug.fto.de |
building mutt outside the source tree
Hello, I was wondering if it's possible to build mutt outside the source tree. Starting doing it I created a directory called `build-mutt' somewhere on my system and ran `/path/to/mutt-1.1.9/configure' with it's options, which semmed to work properly. But make stopped with the following output: -begin make output- make all-recursive make[1]: Entering directory `/home/bendus/muttsrc/build-mutt' Making all in m4 make[2]: Entering directory `/home/bendus/muttsrc/build-mutt/m4' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/bendus/muttsrc/build-mutt/m4' Making all in po make[2]: Entering directory `/home/bendus/muttsrc/build-mutt/po' make[2]: *** No rule to make target `../../mutt-1.1.9/keymap_alldefs.h', needed by `../../mutt-1.1.9/po/mutt.pot'. Stop. make[2]: Leaving directory `/home/bendus/muttsrc/build-mutt/po' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/bendus/muttsrc/build-mutt' make: *** [all-recursive-am] Error 2 --end make output-- It seems to me that make tries to build something in the source tree but there is no makefile for it there. However building `keymap_alldefs.h' by hand in the build tree requires to copy the OPS* files from the source to the build directory. This isn't done by configure or anything. After making `keymap_alldefs.h' this way it has to be copied to the source tree in order to make mutt properly, which works then fine. As I figured out, make looks in POTFILES for the sources and what to build or something like that. Could the entry for keymap_alldefs.h point to `top_builddir/keymap_alldefs.h' rather than to `keymap_alldefs.h'? I guess this would solve the problem. Or am I missing something here and it works without all this? Regards, Stefan. -- Test-tube babies shouldn't throw stones.
Re: keeping new flag
On Mon, Mar 27, 2000 at 07:05:24PM +0200, supio wrote: I'm using mutt 1.0.1i. Every time i quit a mailbox containing new mails, the "N" flag of this mailbox is gone (in the mailbox index). Is there a way to keep this flag, so you can always see in which mailbox new (or unreaded) mails are (or change it to "O")? Just type "x" instead of "q" to quit mutt Michael
Re: changing To: in a reply
On Mon, Mar 27, 2000 at 09:28:46AM -0700, Patrick Walsh wrote: How might the To: be changed in a reply to a particular address, other than manually? I'm aware of the send-hook/my_hdr limitation specified in 3.17 :/ This can't be done. There is no way to get it to modify either the to: or cc: list. You can only match on those fields. me -- pgp key available from http://www.cs.hmc.edu/~me/elkins-pgp-key.asc PGP signature
Re: keeping new flag
On Mon, Mar 27, 2000 at 07:05:24PM +0200, supio wrote:
Hello,
I'm using mutt 1.0.1i.
Every time i quit a mailbox containing new mails, the "N" flag of this
mailbox is gone (in the mailbox index).
Is there a way to keep this flag, so you can always see in which mailbox
new (or unreaded) mails are (or change it to "O")?
BTW: is it possible to see in the index if there are marked messages
("!" flag) in a mailbox?
For your first question add the following to your .muttrc
set nomark_old
As for your second question, I do not know.
/Duncan
--
Duncan Watson
nCube
Re: changing To: in a reply
On Mon, Mar 27, 2000 at 02:28:57PM -0800, Michael Elkins ([EMAIL PROTECTED]) said: On Mon, Mar 27, 2000 at 09:28:46AM -0700, Patrick Walsh wrote: How might the To: be changed in a reply to a particular address, other than manually? I'm aware of the send-hook/my_hdr limitation specified in 3.17 :/ This can't be done. There is no way to get it to modify either the to: or cc: list. You can only match on those fields. Best bet I guess would be to use procmail, a recipe like: :0 fw * ^FROM.*address-you-see | formail -i "Reply-To: address-you-want" Warning; not tested, and IANAPG[1]. That way, when you hit reply, mutt will substitute whatever you put in the Reply-To: field. [1] I am not a procmail guru -- Jim Toth [EMAIL PROTECTED] "And remember, Abraham Lincoln did not die in vain. He died in Washington, DC." --The Firesign Theatre
RPMs (was: Upgrading?)
On Mon, Mar 27, 2000 at 02:12:17PM -0500, David T-G wrote: [...] If you want to wait for 1.2 (the next stable release, for which 1.1.9 is a candidate), then [I understand that] you can expect to see RPMs and [...] Yes, I'm pretty certain there will be RPMs of 1.2 once (well, better: a short period after...) it's released. We've had a few testruns with 1.1.9 RPMs and should be almost ready for 1.2. Watch http://mutt.linuxatwork.at :-) Cheerio, Thomas -- - Thomas Ribbrockhttp://www.bigfoot.com/~kaytanICQ#: 15839919 "You have to live on the edge of reality - to make your dreams come true!"
Re: resend-message, $copy
David T-G [EMAIL PROTECTED] wrote on Mon, 27 Mar 2000: While I accept your argument, I think that the general premise is that you already have a copy of the message (since you're resending it) and you're not making any changes (like adding the recipient to the headers) and so a copy would be superfluous. Yes, except the resend-message drops you in the editor to edit the message text, and after that you're returned to the compose menu as usual. However Fcc is empty, even if you've modified the message contents. You can manuall add a Fcc but it would be nice if it was there automatically. There might be some tricky issues there with regards to fcc-hooks and such that I'm not thinking of here, though. Now, I don't have esc-e in my copy, so that must be new (as alluded to below), and maybe I don't understand the resend-message function yet. I'm thinking of bounce-message at the moment, but could also consider edit (for editing an existing message and then shipping -- but I believe that edit - send *does* honor $copy). Yes, this has changed in the developement versions. The functions of edit-message and resend-message have been separated. With edit-message you get the full message text and all headers in your editor, and when you exit the editor, the message is re-read and placed in the index. No more w(rite) function calling from the compose menu. It works much better this way. :-) Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / Who has the user's manual for Spaceship Earth -- please return it AT ONCE!
Re: keeping new flag
supio [EMAIL PROTECTED] wrote on Mon, 27 Mar 2000: But the real problem seems to be myself describing my wishes bg. I dunno, I thought "in the mailbox index" was clear enough... (As opposed to "message index".) Even if I admit it could be interpreted either way. So mutt only looks on the timestamp of the mailbox if there are new mails and sets the N flag as long as it hasn't synced? Yes. With other folder formats it can be a bit different in details, but it's still essentially the same. I have now 24 mailboxes and If there are new mails I often only look into what's there and quit mutt to read them later. To open each mailbox the next time seeking the new mails is a bit annoying... ;) I do this often too. I do have Maildir format incoming folders, but I think it should work with mbox folders too if you just make sure to do x (discard changes) instead of q to quit... I also make use of a patch which makes mark_old into a quadoption, so I get a nice "mark new messages as old?" prompt on folder exit. :-) Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / Stop reading here.
Re: Viewing other mailboxes...
Ben Beuchler [EMAIL PROTECTED] wrote on Mon, 27 Mar 2000: I am using mutt 1.1.9. I have $mbox set to "=read" and it does indeed save all read messages there. However, when I attempt to change to that folder, it just shows me the actual mail file rather then a list of messages. Do you mean that Mutt displays all of the contents of that mail folder as a flat file, instead of displaying a message index for that folder? That would indicate that Mutt isn't detecting that it's a mail folder. (Normally, Mutt will automatically detect a mail folder -- in fact there is no way to force Mutt to treat some file or dir as a mail folder, the auto-detection is always used.) If this is the case, then you need to find out why that is happening. The most likely reason is that the folder is corrupt. However I'm a bit surprised, because I think Mutt would refuse to even save messages to a mail folder if it can't detect the type correctly. If you save some message to a new (previously non-existing) mail folder and then open this with Mutt, do you get the message index or the folder file contents too? Is it possible that I missed a couple of settings that should've been changed when I switched from IMAP to a local mail spool? Unlikely, the folder type detection should be automatic like I said. The older folder-type related setting in Mutt is $mbox_type, which controls the folder format for *newly created* folders. Regards, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / Foolproof operation: All parameters are hard coded.
Stupid, simple PGP question
Okay. Stupid user question time. I say this because I'm sure the answer is something simple like "install this" or "set that" or something like that ... or worse yet, RTFM. I just can't figure it out. So, here goes: Every now and then, I get an email with no body. It just says, [-- application/pgp is unsupported (use 'v' to view this part) --] When I do, I don't see an email message, I just see: PGP is now invoked from different executables for different operations: pgpeExcrypt (including Encrypt/Sign) pgpsSign pgpvVerify/Decrypt pgpkKey management pgpoPGP 2.6.2 command-line simulator (not yet implemented) See each application's respective man page or the general PGP documentation for more information. metamail: Could not find end of mail headers. Press any key to continue... TIA!! -- Thanks, Jon Walthour, BSCD Cincinnati, Ohio ~~~ The 21st century begins on January 1, 2001
pgp/gpg password, temp file?
I notice then when pgp-signing something a mail message, I need to enter my password, respectively. However, if I send another message, pgp-signing, again. There is no need to enter my password. Is this being passed to a temp file? -- /helfman "At any given moment, you may find the ticket to the circus that has always beenin your possession." Fingerprint: 2F76 2856 776A 3E07 9F3E 452A 17D9 9B28 D75E 0A36 GnuPG http://www.gnupg.org Get Private! PGP signature
Re: Stupid, simple PGP question
* Jon Walthour ([EMAIL PROTECTED]) [000328 08:59]: Okay. Stupid user question time. I say this because I'm sure the answer is something simple like "install this" or "set that" or something like that ... or worse yet, RTFM. I just can't figure it out. So, here goes: Every now and then, I get an email with no body. It just says, [-- application/pgp is unsupported (use 'v' to view this part) --] What you are trying to view is a PGP/Mime message. It's been signed and/or encrypted using PGP. The reason you're getting the odd behaviour is that when mutt is trying to read the message, by piping it through pgp, it gets fed into the binary named "pgp", which would be correct if you were using pgp2, but because you've got (guessing) pgp5i, it's not correct and thus pgp prints usage information. You have two options really. One, you can downgrade to pgp2, or you can go the RightWay (tm) and set the pgp related variables correctly so that mutt will know how to use your version of PGP. Terje -- Xlehveh rhkau fudwuh få mydtemi dåh tk aqd rhkau jyt få kdyn (jyt == fudwuh?)
Re: keeping new flag
Marc --
...and then supio said...
% On Mon, Mar 27, 2000 at 02:08:24PM -0500, David T-G wrote:
% % Every time i quit a mailbox containing new mails, the "N" flag of this
% % mailbox is gone (in the mailbox index).
%
% Well, that's the function of quit as defined by default, so the
% developers are pretty happy with your statement :-) At least, as long as
% the "N" changes to "O" rather than changing to " ".
%
% That's correct and works fine :)
%
% But the real problem seems to be myself describing my wishes bg.
*grin*
%
% So with "quit" I actually meant changing to the "mailbox view" (with "c" and
% tabtab by def., or -y on startup), where all mailboxes, given mutt with
% "mailboxes (...)" in the muttrc, are listed.
Ah; OK. That's an easy one; after you sync your mailbox changes, press
'%' to toggle mailbox write status. When you then 'c'hange to another
mailbox, nothing new gets written to the one you're leaving.
If you liked this behavior all of the time, you could even create a macro
(perhaps replacing 'c') that syncs, toggles, and then calls the change --
and might even hit tab for you as well :-)
%
%
% % BTW: is it possible to see in the index if there are marked messages
% % ("!" flag) in a mailbox?
%
% Before you open the mailbox with mutt, you mean? Not to my knowledge,
% since mutt doesn't scan message headers until it's actually opening the
I might have to correct myself on this one, though the "to my knowledge"
part is still true. It's my understanding that Maildir folders write the
status info at the end of the name of the mail file rather than *in* it,
and so you don't have to open n files to see the stati but instead
merely scan the directory. I dunno if mutt supports this type of looking
and whether or not it's time consuming, but it's a better chance (if it
really exists as herein specified ;-) than an mbox...
% mailbox (much to the chagrin of many folks who want to see boxes with new
% mail that are being touched by other things like biff).
%
% Yeah, thats also my real problem with the "N" flags. :)
Ah. Gotcha.
%
% So mutt only looks on the timestamp of the mailbox if there are new
% mails and sets the N flag as long as it hasn't synced?
For the mail folder browser, that's basically it; mutt compares the
modification time (like when mail last dropped in) and the access time
(like when something -- including, and here's the kicker, a shell mailbox
watcher or biff or something like that -- last looked into the mailbox;
only if the mod time is newer does the box show as 'N' (which, from
another point of view, makes sense; the list isn't about unread mails in
the mailbox, since you've at least seen them, but about mail newer than
the last time you visited -- and so if you can't get through all of the
new mails in a folder in one read, tough luck for you :-)
%
% I have now 24 mailboxes and If there are new mails I often
% only look into what's there and quit mutt to read them later.
That's the problem :-)
% To open each mailbox the next time seeking the new mails is a bit
% annoying... ;)
Yep. I haven't figured out how to get around that, though, unless the
Maildir idea above might be useful...
%
%
% If you want highlighting of flagged/marked messages once you're in the
% mailbox, that's easy.
%
% I know but all would be nice "outside"...
Perhaps Maildir is the answer for this, too ... but it would very
probably require some coding on your own :-)
%
% --
% greetings supio ( Marc Noller ) | [EMAIL PROTECTED] | http://oipus.net |
% -|
% - Filstal.Online e.V. http://www.fto.de |
% --- LinuxUserGroup Filstal http://lug.fto.de |
:-D
--
David T-G * It's easier to fight for one's principles
(play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
The "new millennium" starts at the beginning of 2001. There was no year 0.
Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh*
PGP signature
