Re: Output when nothing changes
Won't setting timeout to be 0 fix your problem? Shawn Previously, Bennett Todd wrote: :> Thanks for adding the detailed explanation. I don't have anything to :> offer by way of assistence, but I'd like to second your request; I :> notice the same behavior in another context. :> :> I run in a screen(1) session on a raw console all the time, by :> strong preference. If mutt didn't do this, I could use screen's :> "monitor" function to give me a little notice, in the status area, :> whenever I get new mail, no matter what window is up at the time. As :> it is, mutt natters at the screen every time it checks, regardless :> of whether it has anything to say or not. :> :> -Bennett -- Next to being shot at and missed, nothing is really quite as satisfying as an income tax refund. -- F. J. Raymond
Mailboxes and fcc-save-hook in 0.95.4i / SunOS 5.7
Hi, I started using mutt on my university server and noticed two defects in its behavior, when compared to my previous usage on a different server (same .muttrc file): 1) mutt does not check the "mailboxes" for new mail. Their list pops up correctly after c-TAB-TAB. 2) the "fcc" part of fcc-save-hooks does not work, it always wants to save into the generic "record" folder. Save command works fine. I suspect it may have something to do with this server setup which I cannot change but maybe find some workarounds? Thanks for your insights. Petr harper:~>mutt -v Mutt 0.95.4i (1999-03-03) System: SunOS 5.7 [using slang 10202] Compile options: -DOMAIN -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_GPG +-BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/lib/sendmail" MAILPATH="/var/mail" SHAREDIR="/opt/pkgs/mutt-0.95.4i/lib/mutt" SYSCONFDIR="/opt/pkgs/mutt-0.95.4i/etc" ISPELL="/opt/bin/ispell" _PGPPATH="/opt/bin/gpg"
Re: Output when nothing changes
Thanks for adding the detailed explanation. I don't have anything to offer by way of assistence, but I'd like to second your request; I notice the same behavior in another context. I run in a screen(1) session on a raw console all the time, by strong preference. If mutt didn't do this, I could use screen's "monitor" function to give me a little notice, in the status area, whenever I get new mail, no matter what window is up at the time. As it is, mutt natters at the screen every time it checks, regardless of whether it has anything to say or not. -Bennett PGP signature
Re: New Mail Sent to different mailboxes
On Wed, Jan 12, 2000 at 02:56:44PM -0800, Shawn D. McPeek wrote: > > It's not a feature because it's not the job of a mail client to deliver > mail. There are a lot of things mail clients don't do - delivering mail > is one of them. Sorting mail is not delivering it, the mail is delivered once its in /var/spool/mail/ at that point, the mail client takes over as far as im concerned. -- - Nick Jennings Email: [EMAIL PROTECTED] Web : http://nick.namodn.com -
Re: New Mail Sent to different mailboxes
On Wed, Jan 12, 2000 at 02:59:52PM -0800, brian moore wrote: > On Wed, Jan 12, 2000 at 02:47:57PM -0800, Nick Jennings wrote: > > > > Argh! I despise procmail, yes its powerfull, and can do alot, but > > it's severly anoying. I think it _IS_ a mail clients job to do filtering, > > after all, it checks the /var/spool/mail/ for new mail and drops > > in in your inbox, if it drops it in the inbox, why not instead drop it in > > some other box and let you know? > > Um, but /var/(spool/)?mail/* -is- the inbox. My point was that at that point it sifts through the mail (i.e. perfect time to do basic filtering). > > Thats why I started writing my own mail client, so the filtering > > would be easy to use, and built into the client, so you dont have to hassle > > with procmail. Since I started using Mutt, I stopped developing this mail > > client, but now I might start again, or maybe add this feature to mutt, is > > there a reason why this is something that is continuously not a feature in > > UNIX mail clients? yes procmail is powerfull, but its far too much of a > > hassle for just setting up a simple filter, something in the muttrc like > > this: > > Because it's not as effective? > > Quite a bit of my mail triggers external programs on receipt. I don't > want that to wait until I get into work, login and start my mail client; > I want it to work 24 hours a day as the mail is received. Yes, I understand procmail is very efficient and configurable, but alot of people just use it for very simple filtering, and for that, procmail is an overkill as far as setup, and configuration goes. I know when I first tried to set it up, it was hell! > More successful would be a gui-frontend to procmail, along the lines > of the dotfile generator. Since I really hate using X, i'd probably write something is perl for the console, but just as well, its a good suggestion, I just might do something like that, and if I ever complete that mail program of mine (also written in perl) I can just incorporate the procmail frontend in it. -- - Nick Jennings Email: [EMAIL PROTECTED] Web : http://nick.namodn.com -
Re: New Mail Sent to different mailboxes
Nick Jennings <[EMAIL PROTECTED]> wrote on Wed, 12 Jan 2000: > Argh! I despise procmail, yes its powerfull, and can do alot, but > it's severly anoying. ... > yes procmail is powerfull, but its far too much of a > hassle for just setting up a simple filter, You could try maildrop instead, then. You might like that better than procmail (or maybe not). In any case I don't see what's so complex about essentially having the following: .forward: |/usr/bin/procmail .procmail: ### Mutt users list :0 * ^Sender.*owner-mutt-users@mutt\.org mutt-users-mail Two files, and not very long or complex ones at that. The setup using maildrop would be approximately the same I believe, if not even simpler. > I think it _IS_ a mail clients job to do filtering, > after all, it checks the /var/spool/mail/ for new mail and drops > in in your inbox, if it drops it in the inbox, why not instead drop it in > some other box and let you know? A MUA reads mail folders (some of which might incoming mail folders, or mail spool files). It doesn't transfer or move mail non-interactively, it does so only under the user's direction. Or no? Regardless, Mutt tries to follow the principle "use the right tool for each job", instead of trying to cram every feature into itself, which leads into large monolithic applications that are slow and bug-infested. For incoming email filtering, the right way to do this is at the mail delivery time with specilised mail filter applications, not when the MUA starts. 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 / I'm a shareware signature! Send $2 if you use me, $10 for a manual.
Re: New Mail Sent to different mailboxes
On Wed, Jan 12, 2000 at 02:47:57PM -0800, Nick Jennings wrote: > On Thu, Jan 13, 2000 at 12:20:23AM +0200, Mikko Hänninen wrote: > > Nick Jennings <[EMAIL PROTECTED]> wrote on Wed, 12 Jan 2000: > > > I've read the online documentation at www.mutt.org and I cant find specific > > > information on how to get new mail put in folders based on patterns. > > > > Mutt doesn't do this, it's not Mutt's job. You need to use a mail > > filtering tool such as procmail or maildrop. > > > > This is getting to, or is already a FAQ. Hmm. Anyone volunteer to > > write an entry about this for the FAQ list? :-) > > Argh! I despise procmail, yes its powerfull, and can do alot, but > it's severly anoying. I think it _IS_ a mail clients job to do filtering, > after all, it checks the /var/spool/mail/ for new mail and drops > in in your inbox, if it drops it in the inbox, why not instead drop it in > some other box and let you know? Um, but /var/(spool/)?mail/* -is- the inbox. Your mail client checks there for mail, your MDA drops mail there (it is your inbox, after all, and a delivery agent delivers it). Your client may move it to a 'working' mailbox after you've read an item, but the 'inbox' is still /var/(spool/)?mail/*. > Thats why I started writing my own mail client, so the filtering > would be easy to use, and built into the client, so you dont have to hassle > with procmail. Since I started using Mutt, I stopped developing this mail > client, but now I might start again, or maybe add this feature to mutt, is > there a reason why this is something that is continuously not a feature in > UNIX mail clients? yes procmail is powerfull, but its far too much of a > hassle for just setting up a simple filter, something in the muttrc like > this: Because it's not as effective? Quite a bit of my mail triggers external programs on receipt. I don't want that to wait until I get into work, login and start my mail client; I want it to work 24 hours a day as the mail is received. > newmail-hook ([EMAIL PROTECTED]) +mutt-users-mail > > would be simple enough and very easy to impliment. It could just search the > headers for that pattern, not even the body (since that would slow it down > more). Sure its not as powerfull as procmail can get, but its certainly > better for simple filtering wich is what most people need to do anyways. More successful would be a gui-frontend to procmail, along the lines of the dotfile generator. -- Brian Moore | Of course vi is God's editor. Sysadmin, C/Perl Hacker | If He used Emacs, He'd still be waiting Usenet Vandal | for it to load on the seventh day. Netscum, Bane of Elves.
Re: New Mail Sent to different mailboxes
On Wed, Jan 12, 2000 at 02:47:57PM -0800, Nick Jennings wrote: > Argh! I despise procmail, yes its powerfull, and can do alot, but > it's severly anoying. I think it _IS_ a mail clients job to do filtering, > after all, it checks the /var/spool/mail/ for new mail and drops > in in your inbox, if it drops it in the inbox, why not instead drop it in > some other box and let you know? It does not drop anything in your inbox. /var/spool/mail/ _IS_ your inbox. The mail is already there before the mail client starts, and it is there after the mail client exits, unless you tell it to save it elsewhere. - Dan
Re: New Mail Sent to different mailboxes
Previously, Nick Jennings wrote: :> :> Argh! I despise procmail, yes its powerfull, and can do alot, but :> it's severly anoying. I think it _IS_ a mail clients job to do filtering, :> after all, it checks the /var/spool/mail/ for new mail and drops :> in in your inbox, if it drops it in the inbox, why not instead drop it in :> some other box and let you know? Uh, no, a mail client _does not_ check for new mail and drop it in my inbox - a mail client has nothing at all to do with the delivery of mail. The MDA does that (sendmail, procmail, fetchmail, etc). :> Thats why I started writing my own mail client, so the filtering :> would be easy to use, and built into the client, so you dont have to hassle :> with procmail. Since I started using Mutt, I stopped developing this mail :> client, but now I might start again, or maybe add this feature to mutt, is :> there a reason why this is something that is continuously not a feature in :> UNIX mail clients? yes procmail is powerfull, but its far too much of a :> hassle for just setting up a simple filter, something in the muttrc like :> this: It's not a feature because it's not the job of a mail client to deliver mail. There are a lot of things mail clients don't do - delivering mail is one of them. :> :> newmail-hook ([EMAIL PROTECTED]) +mutt-users-mail What's so hard about: :0: * ^Sender: [EMAIL PROTECTED] mutt-users-mail I really don't think that was too hard. :> would be simple enough and very easy to impliment. It could just search the :> headers for that pattern, not even the body (since that would slow it down :> more). Sure its not as powerfull as procmail can get, but its certainly :> better for simple filtering wich is what most people need to do anyways. It may be simple and easy to impliment, but it would be bloat and you'd be making mutt do something it is not meant to do. Shawn -- Predestination was doomed from the start.
Re: New Mail Sent to different mailboxes
On Thu, Jan 13, 2000 at 12:20:23AM +0200, Mikko Hänninen wrote: > Nick Jennings <[EMAIL PROTECTED]> wrote on Wed, 12 Jan 2000: > > I've read the online documentation at www.mutt.org and I cant find specific > > information on how to get new mail put in folders based on patterns. > > Mutt doesn't do this, it's not Mutt's job. You need to use a mail > filtering tool such as procmail or maildrop. > > This is getting to, or is already a FAQ. Hmm. Anyone volunteer to > write an entry about this for the FAQ list? :-) Argh! I despise procmail, yes its powerfull, and can do alot, but it's severly anoying. I think it _IS_ a mail clients job to do filtering, after all, it checks the /var/spool/mail/ for new mail and drops in in your inbox, if it drops it in the inbox, why not instead drop it in some other box and let you know? Thats why I started writing my own mail client, so the filtering would be easy to use, and built into the client, so you dont have to hassle with procmail. Since I started using Mutt, I stopped developing this mail client, but now I might start again, or maybe add this feature to mutt, is there a reason why this is something that is continuously not a feature in UNIX mail clients? yes procmail is powerfull, but its far too much of a hassle for just setting up a simple filter, something in the muttrc like this: newmail-hook ([EMAIL PROTECTED]) +mutt-users-mail would be simple enough and very easy to impliment. It could just search the headers for that pattern, not even the body (since that would slow it down more). Sure its not as powerfull as procmail can get, but its certainly better for simple filtering wich is what most people need to do anyways. -- - Nick Jennings Email: [EMAIL PROTECTED] Web : http://nick.namodn.com -
Re: Output when nothing changes
On Wed, Jan 12, 2000 at 03:35:30PM -0600, David DeSimone wrote: > Larry Lipstone <[EMAIL PROTECTED]> wrote: > > > > I find with my mutt-1.0i running on UnixWare 2.1.3, with TERM=dtterm, > > every time the timeout (or whatever) period expires and it checks for > > new mail, the program emits a "make cursor visible", then stat()'s the > > mail drop, then sends "make cursor invisible". > > > > This causes my poor (yet expensive) ISDN connection to demand-dial on > > the timeout (or whatever) interval, even when I'm receiving no new mail. > > I can't see how this behavior would cause your modem to dial out and > initiate a connection. I can see how it would keep a connection open > when it would otherwise time out. > > Why do you think it's desirable that the connection time out? Then you > won't be notified of new mail anymore. And if you don't care that new > mail is coming in, then why are you wasting ISDN money by keeping the > connection active? > > I'm sorry that I don't understand your situation. It's not your fault, and thanks for your reply in spite of it. I have a perhaps slightly unusual situation, in two ways. Maybe if I explain it, it will inspire someone to answer. 1) My ISDN connection is demand-dialed bidirectionally. That is, when traffic wants to go either way, me to ISP or ISP to me, the link is brought up. This is very nice since it lets me use a small timeout but has the downside of being quite expensive if it stays up "all the time". As long as it's only up when I am actually passing traffic, it's fine. 2) My ISDN-homed machine is where mutt is running, and I am connecting to it from a remote site via ssh. Therefore when I receive mail the ISP dials the link and delivers the mail to me (SMTP). If I have mutt running from outside, mutt would shortly notice the new mail and display it - generally very shortly after it arrived. Perhaps now you can see why it is that this adversely affects me. If I leave mutt up, it keeps my ISDN link dialed full-time, which is otherwise not necessary for anything I do. I have used elm this way for years and it didn't do this. It doesn't produce any output at all unless the mailbox changes. So, any suggestions? Larry
Re: New Mail Sent to different mailboxes
Nick Jennings <[EMAIL PROTECTED]> wrote on Wed, 12 Jan 2000: > I've read the online documentation at www.mutt.org and I cant find specific > information on how to get new mail put in folders based on patterns. Mutt doesn't do this, it's not Mutt's job. You need to use a mail filtering tool such as procmail or maildrop. This is getting to, or is already a FAQ. Hmm. Anyone volunteer to write an entry about this for the FAQ list? :-) > another question I have is that I always hear of mutt cool ability to list > the threads so you can colapse entire threads and stuff, I was under the > understanding that this is enabled the minute you set it up with the lists > setting (as above) but It doesnt seem to be doing that for me. Threads is a sort order, try "set sort=threads" in your .muttrc. It's not specific to mailing lists in Mutt, it's just mostly useful for list mail. You can use "set sort_aux=date" or whatever order you prefer normally specify the sort order of threads. Hope this helps, 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 / Life is much too important to be taken seriously.
Re: New Mail Sent to different mailboxes
Nick Jennings [[EMAIL PROTECTED]] wrote: > Hello, new to mutt and due to the high volume of messages on this list I > have bumped the priority of this question up to the top. Huh? > I've read the online documentation at www.mutt.org and I cant find specific > information on how to get new mail put in folders based on patterns. can Mutt doesn't do this. Setup something like procmail. > another question I have is that I always hear of mutt cool ability to list > the threads so you can colapse entire threads and stuff, I was under the > understanding that this is enabled the minute you set it up with the lists > setting (as above) but It doesnt seem to be doing that for me. It has nothing to do with the lists command. Use 'set sort=threads'. -- Jeremy Blosser | [EMAIL PROTECTED] | http://jblosser.firinn.org/ -+-+-- "If Microsoft can change and compete on quality, I've won." -- L. Torvalds PGP signature
Re: Tagging IMAP mail and saving locally - difficult!
Hello.
I am using mutt 0.96.3i (on another Computer at work) and can't confirm to
what Mr. Green said:
On Mon, Jan 10, 2000 at 03:18:45PM +, Chris Green wrote:
> I am trying to copy some mail from a remote IMAP folder to a local
> folder (i.e. just a directory).
>
> In order to acces the IMAP server I have executed
> set folder={mailandnews.co.uk}
>
> This means it is well nigh impossible to navigate my local folders
> after I've tagged the messages I want to save. If I hit ? when asked
> for the folder to save to I of course get a list of the remote IMAP
> folders.
This i have too. You can not browse local Folders with this setting of
$folder.
>
> In addition, even if I enter the full path the to local folder I want
> to save to this fails as well because / gets changed to ., not very
> helpful.
Here my experience is different. For me it is possible to save the message
to a local file giving the full path. No translation / -> . .
Has this behaviour changed in recent versions of mutt?
My settings from .muttrc
set folder="{imap.at_work.de}Inbox."
set record={imap.at_work.de}Inbox.outmail
set spoolfile="{imap.at_work.de}Inbox"
System is Linux Kernel 2.0.36. Sorry no mutt -v for I'm at home at the
moment.
>
> I have just thought that maybe I can do a 'set folder=~/Mail' after
> tagging the messages, maybe that will help.
>
> --
> Chris Green ([EMAIL PROTECTED])
> Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED]
> WWW: http://www.isbd.co.uk/
--
Rainer Gubanski
[EMAIL PROTECTED]
Re: Output when nothing changes
On Wed, Jan 12, 2000 at 03:35:30PM -0600, David DeSimone wrote: > Larry Lipstone <[EMAIL PROTECTED]> wrote: > > > > I find with my mutt-1.0i running on UnixWare 2.1.3, with TERM=dtterm, > > every time the timeout (or whatever) period expires and it checks for > > new mail, the program emits a "make cursor visible", then stat()'s the > > mail drop, then sends "make cursor invisible". > > > > This causes my poor (yet expensive) ISDN connection to demand-dial on > > the timeout (or whatever) interval, even when I'm receiving no new mail. > > I can't see how this behavior would cause your modem to dial out and > initiate a connection. Is your point that mutt is running remotely, so the curses movement causes the connection to stay alive, where you'd just like the "new mail" message to do that? But if the connection drops, don't you lose your telnet/ssh/X/whatever, too? -- - Jeff Abrahamson [EMAIL PROTECTED] 610/270-4845
Re: Output when nothing changes
Larry Lipstone <[EMAIL PROTECTED]> wrote: > > I find with my mutt-1.0i running on UnixWare 2.1.3, with TERM=dtterm, > every time the timeout (or whatever) period expires and it checks for > new mail, the program emits a "make cursor visible", then stat()'s the > mail drop, then sends "make cursor invisible". > > This causes my poor (yet expensive) ISDN connection to demand-dial on > the timeout (or whatever) interval, even when I'm receiving no new mail. I can't see how this behavior would cause your modem to dial out and initiate a connection. I can see how it would keep a connection open when it would otherwise time out. Why do you think it's desirable that the connection time out? Then you won't be notified of new mail anymore. And if you don't care that new mail is coming in, then why are you wasting ISDN money by keeping the connection active? I'm sorry that I don't understand your situation. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
New Mail Sent to different mailboxes
Hello, new to mutt and due to the high volume of messages on this list I have bumped the priority of this question up to the top. I've read the online documentation at www.mutt.org and I cant find specific information on how to get new mail put in folders based on patterns. can someone provide some quick help on this? i know its fairly simple, just dont know the function name & syntax etc. This is what I have so far in my .muttrc (I'll use this list as the example) mailboxes +mutt-users lists [EMAIL PROTECTED] mbox-hook ([EMAIL PROTECTED]) +mutt-users as far as I know, this configuration sets +mutt-users as a valid inbox, sets all mail from [EMAIL PROTECTED] as a mailing list, and the mbox-hook sets _read_ messages matching the ([EMAIL PROTECTED]) to go to the +mutt-users file. I dont need that last one, what I need in place of that last one is a config that sends all new mail from [EMAIL PROTECTED] to +mutt-users. another question I have is that I always hear of mutt cool ability to list the threads so you can colapse entire threads and stuff, I was under the understanding that this is enabled the minute you set it up with the lists setting (as above) but It doesnt seem to be doing that for me. -- - Nick Jennings Email: [EMAIL PROTECTED] Web : http://nick.namodn.com -
Re: Saving tagged messages to a folder
According to Mark Andrews: > I've skimmed the manual for this, but can't find it. I've tagged a > number of messages from the mutt-users group. I want to save them all > to a folder called $HOME/Mail/mutt. How do I do it? I've tried what works > in elm, `s =mutt', but that only saves the current message to the mutt > folder. tag a bunch of messages, and then type ";s =mutt" without the quotes. -b -- Living is hazardous to your health.
Re: former elm user needs help with lists
On Wed, Jan 12, 2000 at 10:34:51AM -0500, [EMAIL PROTECTED] wrote: > As I said, I set this up for elm. Is there a "listify" command that I > can use on existing mailboxes so I can take advantage of the list > features. I subscribe to way to many lists to have them mixed up with > my personal messages. Use shift-t to tag the messages that belong to a certain list Use ;s to save all tagged messages to another mailbox What you need is a procmail recipe that filters all your mails to different mailboxes depending on adresses. mutt doesn't do this. Procmail does. -- Ralf Hildebrandt <[EMAIL PROTECTED]> www.stahl.bau.tu-bs.de/~hildeb When asked68% of corporate execs said a corporation "Who owns the Internet?": 23% said it was Microsoft 98% of 6th graders said: no one.
Re: former elm user needs help with lists
Hi! On Wed, Jan 12, 2000 at 10:34:51AM -0500, [EMAIL PROTECTED] wrote: > As I said, I set this up for elm. Is there a "listify" command that I > can use on existing mailboxes so I can take advantage of the list > features. I subscribe to way to many lists to have them mixed up with > my personal messages. The "lists" command is described in the Mutt manual sections 3.8, the list features in 4.8. I don't really understand what specific list features you want, but I think you will find there what you need. Gero
former elm user needs help with lists
This messages reflects a lot of mutt-newbie ingnorance. I have started using mutt and like it a lot. I switched from elm and still have many things configured from when I was using elm. One of them seems to be stopping me from taking full advantage of mutt's list handling. I have my .procmailrc file configured to catch most messages from lists and place it, in what I call my a files. That is a mailbox with "a-" in front so when I look through my Mail folders they're at the top. Then if I see something I need to save I save it to a folder with the list name. So responses to this message would first be place in the a-mutt-users mailbox and then if they solved my problem I'd save it in mutt-users. :0: * ^TOmutt-users a-mutt-users As I said, I set this up for elm. Is there a "listify" command that I can use on existing mailboxes so I can take advantage of the list features. I subscribe to way to many lists to have them mixed up with my personal messages. -- Josh Kuperman [EMAIL PROTECTED]
mutt and lynx
Hi, Is here a way to set mutt as mailer in lynx ? -- The messenger is not important!
Re: Encrypting without MIME
On Wed, Jan 12, 2000 at 06:37:27AM -0500, David T-G wrote:
>
> Thanks for your inline-encryption scripts. They both look handy.
Cool. BTW, after further testing, I added "umask 077" to the top of each
script. :-) I also fixed a bug in the Sign macro -- mutt didn't see the "y"
after coming back from the filter. I also had to modify the "wait_key" to
Sign-and-send as one function. Here are the new macro defs:
macro compose X "pf:set editor=\"mutt-vim -feast\"\nE:set \
editor=\"mutt-vim\"\ny" "Encrypt Message w/o MIME"
macro compose S "pf:unset wait_key\nFpgp -fast\n:set wait_key\niy" \
"Sign Message w/o MIME"
The only problem I've encountered using these macros is: you can't use
'set record="=sent"'. Since there's no application/pgp header, when you
read your sent messages, they're not decrypted automatically. To fix this,
I use a little kludge in procmail. After procmail adds the content-type,
I save messages Fcc'd to myself (use "set hdr Fcc:" in .muttrc) . i.e.:
:0
* !^Content-Type: message/
* !^Content-Type: multipart/
* !^Content-Type: application/pgp
{
:0 fBw
* ^-BEGIN PGP MESSAGE-
* ^-END PGP MESSAGE-
| formail \
-i "Content-Type: application/pgp; format=text; x-action=encrypt"
:0 fBw
* ^-BEGIN PGP SIGNED MESSAGE-
* ^-BEGIN PGP SIGNATURE-
* ^-END PGP SIGNATURE-
| formail \
-i "Content-Type: application/pgp; format=text; x-action=sign"
}
:0
* ^From: .*[EMAIL PROTECTED]
* ^Reply-To: .*[EMAIL PROTECTED]
* ^Sender: .*[EMAIL PROTECTED]
* !^Received: from .*
$MAILDIR/sent
> Have you seen Sec's patch to let you specify %s in a macro, created
> specifically for this sort of requirement? You create a macro much like
> you have but simply say "... -r %s ..." to specify the recipient, and
> mutt fills it in.
H... I could do away with the mutt-vim script then...
> Check out his patch site (you can certainly find him from the mut main
> page at
Thanks!
js.
--
Jean-Sebastien Morisset, Sr. UNIX Administrator
up2 technologies inc.
[EMAIL PROTECTED], www.up2me.com
PGP signature
Re: Saving tagged messages to a folder
Edmund GRIMLEY EVANS <[EMAIL PROTECTED]> wrote on Wed, 12 Jan 2000: > Prefix with ';': > > ;s =mutt Alternatively, do "set auto_tag" in the .muttrc, which makes Mutt behave in the elm way (all commands apply to all of the tagged messages, if there are any tagged). I prefer the ;-prefix method however, even though I migrated from elm originally. 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 / Warning: Dates in the calendar are closer than they appear.
Re: Saving tagged messages to a folder
Referring to Edmund GRIMLEY EVANS <[EMAIL PROTECTED]> on Jan 12, 2000: | Mark Andrews <[EMAIL PROTECTED]>: | | > I've skimmed the manual for this, but can't find it. I've tagged a | > number of messages from the mutt-users group. I want to save them all | > to a folder called $HOME/Mail/mutt. How do I do it? I've tried what works | > in elm, `s =mutt', but that only saves the current message to the mutt | > folder. | | Prefix with ';': | | ;s =mutt or in your .muttrc set auto_tag to always operate on tagged messages (if applicable). Have A Nice Day, Wolfgang -- Wolfgang W. Baumann / CFD Consultant @ ZIB Berlin / mailto:[EMAIL PROTECTED] Shouldn't we postpone Y2k celebrations until 2048?
Re: Saving tagged messages to a folder
Mark Andrews <[EMAIL PROTECTED]>: > I've skimmed the manual for this, but can't find it. I've tagged a > number of messages from the mutt-users group. I want to save them all > to a folder called $HOME/Mail/mutt. How do I do it? I've tried what works > in elm, `s =mutt', but that only saves the current message to the mutt > folder. > > There has to be a way to do this!! Prefix with ';': ;s =mutt
Re: [REPOST] y2k fix for mutt
On Wed, Jan 12, 2000 at 09:28:11AM +, Edmund GRIMLEY EVANS wrote:
> John Franklin <[EMAIL PROTECTED]>:
>
> > At least on my system, time_t is signed. Sometime in January 2038 it
> > flips back to sometime in January 1901. I think that's the common
> > implementation.
>
> I assume you mean December 1901.
>
> I've heard about this signed implementation, but never seen it in
> practice. Is it really that common? Most programs seem to treat
> negative values of time_t as invalid.
>
> By the way, Europeans who want to celebrate the end of the 31-bit era
> will have to stay up late. The last valid date is "Tue, 19 Jan 2038
> 03:14:07 +".
I get the same output below on both a Red Hat 5.1 system and a NetBSD 1.3.3
system. ISTR getting the same on a FreeBSD 2.x.x system some time ago,
too. Under Windows NT, the second gmtime() call returns NULL.
"Is it common?" is left as an exercise to the reader. :)
[9]% more foo.c
#include
#include
int main()
{
struct tm *tm;
time_t t;
t = 0x7fff;
tm=gmtime(&t);
printf("%s\n",asctime(tm));
t = 0x8000;
tm=gmtime(&t);
printf("%s",asctime(tm));
}
[10]% ./foo
Tue Jan 19 03:14:07 2038
Fri Dec 13 20:45:52 1901
[11]%
jf
--
John Franklin
[EMAIL PROTECTED]
ICBM: N37 12'54", W80 27'14" Z+2100'
Saving tagged messages to a folder
I've skimmed the manual for this, but can't find it. I've tagged a number of messages from the mutt-users group. I want to save them all to a folder called $HOME/Mail/mutt. How do I do it? I've tried what works in elm, `s =mutt', but that only saves the current message to the mutt folder. There has to be a way to do this!!
IMAP folder with . in name doesn't appear
On my IMAP account at mailandnews.co.uk I have a folder called computing.linux, this fails to show up at all in mutt. Presumably it's the '.' in the name causing the problem but I'm not sure if it's a problem with the IMAP server or with mutt. The folder shows up OK using the MailAndNews WebMail. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: Getting back to "spoolfile"
According to Jean-Sebastien Morisset: > When you're in the index of another mailbox, how do you get back to your > spoolfile? I can believe you'd have to do "c/var/spool/mail/username\n"! How I do it is to have my spool file listed as a mailbox. something like below works just great for me. just hit tab and go to your spool file. mailboxes "!" `echo $HOME/mail/lists/*` -b -- the best analogy between cracking and hacking seems to be a hacker can design a car, and a cracker knows how to crash it into a house. PGP signature
Re: Getting back to "spoolfile"
On Wed, Jan 12, 2000 at 02:17:02AM +, Telsa Gwynne wrote: -> On Wed, Jan 12, 2000 at 03:48:12AM +0200 or thereabouts, Mikko Hänninen wrote: -> > Jeremy Blosser <[EMAIL PROTECTED]> wrote on Tue, 11 Jan 2000: -> [summarised what I meant properly :)] -> > > It makes a lot of sense once you see how it works, but can be confusing at -> > > first. -> > -> > This made me think of something I've been wondering, related to the -> > default prompts but mostly for saving emails and attachements and -> > such, not changing folders. -> > -> > If I want to *add* something to the default prompt that -> > Mutt gives, how do I do that? For example, say if I'm at a mail -> > message and press s for save, I get the default value of =folder. -> > Now, I want to save the message to a folder called =folder-foo. -> > How do I do this without having to type in "=folder-foo"? -> -> To save something? Same as changing folder when you have -> =folder, =folder-foo, =folder-fod and =folder-fot. -> -> I hit "=f" then the tab key and get a prompt of "=folder". Then -> I either -> hit "-f" and get "=folder-foo" as a prompt if that was -> sufficiently unique. Then I hit return and it gets saved. -> or -> hit tab again, and get something like the file browser, -> only it restricts its list to =folder-fod, =folder-foo and -> =folder-fot. With numbers next to them. Either I hit the -> number or I move my cursor to the correct one and hit return -> to save it. Hitting "q" (in my settings, the default I believe) -> gets you out of that. -> -> I discovered this because every month or so I have a fit with -> tagging ~A and moving everything in =sent to =sent-YYMM and -> everything in =received to =received-YYMM and one day I was -> in bash-mode in my head and hit tab again to list the options. -> And it worked :) Yea, and I didn't need the manual or the -> list for once! -> -> Telsa I have found by accident and experimentation that a lot of Emacs keystrokes work in Mutt. For example, to solve Jeremy's problem, above, I tried control-e (got to the end of the line), and then start appending to the proposed folder name. It worked. Telsa, your BASH experience worked here because BASH also uses many Emacs keystrokes. Unless you set the vi option: "set -o vi". -- -- C^2 No windows were crashed in the making of this email. Looking for fine software and/or web pages? http://w3.trib.com/~ccurley
Re: Tagging IMAP mail and saving locally - difficult!
On Wed, Jan 12, 2000 at 11:39:22AM +, Chris Green wrote:
>
> Executing a "set folder=" while in mutt seems to do nothing at
> all.
>
Oops, not quite true, I've just spent some time playing with this.
You can "set folder=xxx" to any local folder without any problems and
it works as expected. However if you do a "set folder={xxx}" to an
IMAP folder and then try to get back to a local folder with "set
folder=xxx" mutt gets in a real mess.
So, it would appear that mutt doesn't handle the case where "set
folder=" changes from a remote IMAP folder back to a local folder
properly. If it *could* do this properly then my problem would be
solved.
--
Chris Green ([EMAIL PROTECTED])
Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED]
WWW: http://www.isbd.co.uk/
Re: Tagging IMAP mail and saving locally - difficult!
Chris --
...and then Chris Green said...
% On Wed, Jan 12, 2000 at 06:33:22AM -0500, David T-G wrote:
% >
% > Maybe a macro to change your $folder setting based on where you want to
% > save something or what folders you want to browse...
%
% What I have in the .muttrc I use when working with the IMAP server
% is:-
%
% set folder={mailandnews.co.uk}
Gotcha. And that makes sense.
%
% This means it's *very* difficult to do anything with the local folders
% at the same time. OK, so I could change the 'set folder=' to a local
% directory but then I lose the ability to navigate the IMAP folders.
Right. And I've seen you go through that already :-)
%
% I need to be able to navigate the remote IMAP folders to find a
% message and then save to a local folder, this is well nigh impossible
I was thinking that you could find your message as you usually do, say
"Hmmm, time to save that one locally", and execute your macro to change
your folder. You probably wouldn't even have to exit the pager to do it;
just press \Cfl to change your folder to local, save (maybe even make the
save keypress part of the macro), and then \Cfi to change your folder
back to imap.
% if the local folder is anywhere except in the 'current' directory
% level.
%
% Executing a "set folder=" while in mutt seems to do nothing at
% all.
Of course, if this is true (I mean, if the behavior is meant to be this
way or it is for some reason stuck this way at your site; I don't doubt
what you say), then it sorta knocks the whole idea out of kilter, no? :-(
%
% --
% Chris Green ([EMAIL PROTECTED])
% Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED]
% WWW: http://www.isbd.co.uk/
:-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!
"Why2k? Well, I didn't think at the time that I could charge any more!"
Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh*
PGP signature
linking to ! (was Re: Getting back to "spoolfile")
Hi, folks -- ...and then [EMAIL PROTECTED] said... % % I just did ln -s /var/spool/mail/staeci /home/staeci/Mail/incoming I was even lazier and linked =! to point to my spoolfile. But I had a different reason... There are times when I want to Fcc a message in my spool file, a sort of catch-all for stuff until I figure out whether I'll be talking back and forth with this address enough to give it its own mailbox (since I only have a jillion already and I don't need a bunch of little ones with one or two messages hanging around, too!) or can just can the email (hard to believe, for me, but I sometimes do :-) Other suggestions have included adding myself to the Bcc: header, but that's not only a PITA but doesn't make sense; if I want a Bcc to be mailed out and sent back to me, then I'll add myself, but that has nothing to do with the Fcc since the items are not the same (one is the message as composed, and the other is the message as delivered, with additional headers). Linking =! to my spoolfile works for me, and is pretty convenient; in a case as above I just add the simple Fcc: =! header and then start my note. But I'd save a keystroke if I could truly set it to '!' and it wouldn't be the obvious kludge it is to boot. So, I ask once again, could ! please be defined as a shortcut (just like the folder shortcut '=' is) everywhere, including in the compose and headers menus? :-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! "Why2k? Well, I didn't think at the time that I could charge any more!" Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: Set variables within mutt?
Mark -- ...and then Mark Andrews said... % % Is there a way to specify and save the sort order (and/or save the % status of other variables) within mutt? To put perhaps more clearly what other folks have said, mutt does not have a way of writing out a configuration file with the various settings you've chosen as elm does. The reason for this is because you can change things in a much more complex way with mutt; the config file you might write could be different based on how much mail you have, what folder you're in, or to whom you last sent mail thanks to hooks and macros. Each installation of mutt comes with some compiled-in defaults and should also come with a system-wide muttrc file; you can create your own (mutt looks, perhaps amongst other places, in $HOME/.muttrc and $HOME/.mutt/muttrc for its config) and set things the way you want, and mutt will behave that way from then on. % % Thanks :-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! "Why2k? Well, I didn't think at the time that I could charge any more!" Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: Tagging IMAP mail and saving locally - difficult!
On Wed, Jan 12, 2000 at 06:33:22AM -0500, David T-G wrote:
> % Yes, but with the above set command when you try and save ('s') and
> % *then* hit '?' to allow you to navigate the folders it navigates the
> % *IMAP* folders not your local folders. Alternatively if you give the
> % full path to the folder you want to save in the '/' characters get
> % changed to '.'.
>
> Is your $folder set to your local file? You probably lose the ability to
> browse your IMAP folders easily (at all?), but it will get you your local
> folders.
>
> Maybe a macro to change your $folder setting based on where you want to
> save something or what folders you want to browse...
>
What I have in the .muttrc I use when working with the IMAP server
is:-
set folder={mailandnews.co.uk}
set [EMAIL PROTECTED]
set record={mailandnews.co.uk}outbox
set spoolfile={mailandnews.co.uk}inbox
This means it's *very* difficult to do anything with the local folders
at the same time. OK, so I could change the 'set folder=' to a local
directory but then I lose the ability to navigate the IMAP folders.
I need to be able to navigate the remote IMAP folders to find a
message and then save to a local folder, this is well nigh impossible
if the local folder is anywhere except in the 'current' directory
level.
Executing a "set folder=" while in mutt seems to do nothing at
all.
--
Chris Green ([EMAIL PROTECTED])
Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED]
WWW: http://www.isbd.co.uk/
Re: Encrypting without MIME
Jean-Sebastien -- Thanks for your inline-encryption scripts. They both look handy. Have you seen Sec's patch to let you specify %s in a macro, created specifically for this sort of requirement? You create a macro much like you have but simply say "... -r %s ..." to specify the recipient, and mutt fills it in. Check out his patch site (you can certainly find him from the mut main page at www.mutt.org but I *think* his page is sec.42.org or maybe a subdir under that like /mutt) and see if the patch does what you need. :-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! "Why2k? Well, I didn't think at the time that I could charge any more!" Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: Tagging IMAP mail and saving locally - difficult!
Chris --
...and then Chris Green said...
% On Mon, Jan 10, 2000 at 12:16:32PM -0600, Vikram Adukia wrote:
% > What happens when you try something like:
% > set spoolfile="{mailandnews.co.uk}"
% >
% This is how I have it set up! :-)
That's a start :-)
%
% > This allows me to access both the remote spool and local directories.
% > However, I do not have remote directories to also test with.
% >
% Yes, but with the above set command when you try and save ('s') and
% *then* hit '?' to allow you to navigate the folders it navigates the
% *IMAP* folders not your local folders. Alternatively if you give the
% full path to the folder you want to save in the '/' characters get
% changed to '.'.
Is your $folder set to your local file? You probably lose the ability to
browse your IMAP folders easily (at all?), but it will get you your local
folders.
Maybe a macro to change your $folder setting based on where you want to
save something or what folders you want to browse...
%
% --
% Chris Green ([EMAIL PROTECTED])
% Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED]
% WWW: http://www.isbd.co.uk/
:-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!
"Why2k? Well, I didn't think at the time that I could charge any more!"
Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh*
PGP signature
Re: mutt & y2k
Michael -- ...and then Michael Sanders said... % Is the mutt-users list still alive? I have received no post since the % one referenced above. Yep; it sure is. % % Someone please send an answer directly to me. I don't know if you've gotten any yet, but here's one. And it's copied to the list, so you might get it twice or at least other folks will know that someone has sent a note :-) % % -- % (T.) Michael Sanders internet: [EMAIL PROTECTED] % Physics Department URL: http://www-personal.umich.edu/~sanders % University of Michigan phone: 734/936-0799 % Ann Arbor, MI 48109-1120 FAX: 734/764-6843 :-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! "Why2k? Well, I didn't think at the time that I could charge any more!" Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: Getting back to "spoolfile"
Referring to Jean-Sebastien Morisset <[EMAIL PROTECTED]> on Jan 11, 2000: | On Wed, Jan 12, 2000 at 03:48:12AM +0200, Mikko Hänninen wrote: | > | > If I want to *add* something to the default prompt that | > Mutt gives, how do I do that? For example, say if I'm at a mail | | Try pressing the right-arrow first. Pressing the TAB key works, too. Have A Nice Day, Wolfgang -- Wolfgang W. Baumann / CFD Consultant @ ZIB Berlin / mailto:[EMAIL PROTECTED] Shouldn't we postpone Y2k celebrations until 2048?
Re: Getting back to "spoolfile"
On Wed, Jan 12, 2000 at 02:17:02AM +, Telsa Gwynne wrote: > I discovered this because every month or so I have a fit with > tagging ~A and moving everything in =sent to =sent-YYMM and > everything in =received to =received-YYMM and one day I was You might want to think about something like the following in your .muttrc to save you some effort: folder-hook . set record= =sent-`date +%Y-%m` save-hook. =saved-`date +%Y-%m` Cheers, Dave -- Dave Holland | Our problems are mostly behind us. Systems Manager|What we have to do now is fight the solutions. Incyte Europe | Cambridge, UK |
Re: [REPOST] y2k fix for mutt
John Franklin <[EMAIL PROTECTED]>: > At least on my system, time_t is signed. Sometime in January 2038 it > flips back to sometime in January 1901. I think that's the common > implementation. I assume you mean December 1901. I've heard about this signed implementation, but never seen it in practice. Is it really that common? Most programs seem to treat negative values of time_t as invalid. By the way, Europeans who want to celebrate the end of the 31-bit era will have to stay up late. The last valid date is "Tue, 19 Jan 2038 03:14:07 +". Edmund
Output when nothing changes
I find with my mutt-1.0i running on UnixWare 2.1.3, with TERM=dtterm, every time the timeout (or whatever) period expires and it checks for new mail, the program emits a "make cursor visible", then stat()'s the mail drop, then sends "make cursor invisible". This causes my poor (yet expensive) ISDN connection to demand-dial on the timeout (or whatever) interval, even when I'm receiving no new mail. Which usually means it just stays up all the time while mutt is running across a remote ssh or whatever. I can't think of a timeout value that is long enough to keep the ISDN calls down yet short enough to satisfy my demand for seeing new mail arrive. Is there a benefit or reason to mutt's behaving this way? I know there must be a way to "fix" this in the source. I may undertake this if it seems appropriate and hasn't yet been done. Or I may just bump up the timeout and live with it. Thanks, Larry
