macro for ezmlm confirms
I administer an ezmlm mailing list. I would like to make answering YES to confirm requests easier. Ezmlm encodes administrative commands as part of the mail address, and you confirm by replying to a special one time email address (placed into the Reply-To: field). I have never made a macro before, but this is what I would like it to do * Reply to the Reply-To: address * do NOT pop up the editor * unset Fcc * construct a message with no subject and no body * do not ask me the usual questions about subjectless messages * actually, if it is easier to put in a dummy subject than deal with subjectless messages, that is fine too. Subject is ignored. * all effects should last just for that message Can anyone help me build this macro? Or tell me something better than a macro (hooks?). Thanks, Dan
not showing lists lists
I was using mutt-1.0i. I just upgraded to mutt-1.1.10i. My index_format var is set index_format="%4C %Z %(%b %d %R) %15.15L [%5c] %s" The old mutt would show the list for %L (if sent to a defined list). The new mutt doesn't. It still recognizes the list when I do a list reply however. What's up? Also, is there a manual for version 1.1.10i yet? Thanks, Dan
Re: Problems with mutt and locking
On Fri, Feb 25, 2000 at 04:10:24PM -0600, Wes Barris wrote: I have been trying to get mutt working on a Linux/RedHat 6.1 system. The /var/spool/mail directory is NFS mounted from a FreeBSD system. Mutt keeps telling me that user's mail files are "Read Only". By running this command: mutt | tee junk cat junk I have found this error: fcntl: No locks available (errno = 37) We use both elm and pine without problems. We also succesfully use mutt on our SGIs which also mounts mail from this same FreeBSD system. I can make mutt work by properly making mutt_dotlock setgid AND by using the --disable-fcntl during a build (see -v output below). However, I know that I need fcntl locking so that is not a solution. Can someone tell me if the problems I am experiencing have something to with the RedHat client system or with how the mail directory is exported on the FreeBSD system? You need to make sure that lockd is running on the RedHad machine. (the standard RH install does not set this up) elm and pine are probably not using fcntl, which is why they work, just like mutt works when compiled with --disable-fcntl. You need lockd for fcntl. - Dan
Re: home/end/pageup/pagedown don't work
On Wed, Feb 23, 2000 at 10:06:30PM +0200, Marius Gedminas wrote: You should try hacking terminfo instead. Use $ infocmp $TERM and look at khome, kend, kpp and knp. They should match the sequences your term is generating for Home, End, PgUp and PgDn respectively. I just solved this for xterm on my RH 6.1 Linux box, by adding the following to the vt100 entry: khome=\EOH, kend=\EOF, knp=\E[6~, kpp=\E[5~, Those who do not have root permission or a cooperative sysadmin can add the following to their .muttrc as a work around: bind generic 'esc[5~' previous-page # Page Up bind generic 'esc[6~' next-page # Page Down bind generic 'escOH' first-entry # Home bind generic 'escOF' last-entry # End (In either case you must substitutes the actually codes that your term emulator is generating) (keystrings is a small program whose sole purpose in life is to display nicely formatted character sequences. I hacked it from examples in libc.inf). Another way to see the codes is to start up emacs in the xterm (use the -nw flag so it does not start up in its own window). Go to the scratch buffer and type ^Q followed by whatever key you want to see. The xterm on linux was kind enough pass along the Home, End, PgUp and PgDn keys to emacs so I could view them. The xterm on Solaris was greedy, grabbing them for itself, so this didn't work. - Dan
Re: NFS lockd problem
On Sun, Feb 13, 2000 at 09:44:21PM +0100, Martin Bertilsson Haagen wrote: On my computers I have mounted my home directories with nfs. This because I thinks this is a good thing to do. When I exiting mutt it askes me: Move read messages to /home/haagen/Mail/old ([n]/y): If i type "y" here i get the following errors: lockd: failed to monitor 192.168.2.1 fcntl: No locks available (errno 37) If you are on linux, you should make sure the lockd deamon is running on your client machine. It does not start up by default in the standard Red Hat 6.1 installation. See /etc/rc.d/init.d/nfslock - Dan
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/username 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/username _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: fcntl: No locks available (errno = 37)
On Tue, Nov 16, 1999 at 03:52:11PM -0600, Dan Lipofsky wrote: I am using mutt-1.0pre3us on Red Hat 6.1 Linux. When ever I try to save a message to a file on a network file system I get fcntl: No locks available (errno = 37) If the file does not exist it successfully creates it but leaves it length zero. If I try to save to a file on the local file system it works fine. Can anyone help me out here? With the help of every here, I did fix the problem. First I looked on the server, and saw the lockd process was defunct. We restarted that, but it did not help. Latter I thought to look on the client, saw there was no lockd, started it, and that fixed everything. While all this was going on, I noticed that I only get this error message when saving from a normal folder, not when saving from an IMAP folder. It failed in both cases, I just did not get notified when saving from an IMAP folder. I wonder why that is? I was saving to a regular file in both cases. Thanks, - Dan
Re: many questions
On Thu, Nov 18, 1999 at 05:20:13PM -0600, David DeSimone wrote: Dan Lipofsky [EMAIL PROTECTED] wrote: When new mail arrives, I get a message saying "New Mail" at the bottom of the screen. But all I actually see in the index are my old messages, because the new ones are off the bottom of the page. It would be useful to have mutt autoscroll to bring new messages onto the screen so that I could tell at a glance if I wanted to bother with the message. I think it would be annoying if Mutt moved my cursor around while I'm trying to find a message, just because some new mail happened to arrive. Well, it could certainly be optional. Most of the time I am not in mutt, but doing other work. So I was wanting it to scroll the index for me so I could at just glance and see what the new mail was. Perhaps it should only do this when the index was already showing what was previously the last message, i.e. don't move it from message 1 to message 678. - Dan
