Re: folder problem
Hi, On Sun, Oct 10, 1999 at 02:12 +0200, Walter Hofmann wrote: > I'm looking for a setting or a keyboard macro so that mutt still > highlights the first new message, but scrolls it up so that I can see > the other new messages as well (if at all possible). Any ideas? Try folder-hook . "exec current-middle" or folder-hook . "exec current-top" This will display the currently highlighted message in the middle or at the top of the screen. Ciao, Stefan
Re: Emacs mutt mode?
Once upon a time Mark Weinem <[EMAIL PROTECTED]> told us: > On Thu, Sep 23, 1999 at 08:19:41PM +0200, Thomas Wolmer HG/EHS/OM/DE > wrote: > > > But if it was the same "mutt mode" that I once tried (post.el?), it > > does not work very well with gnuclient. Or even not at all... > > Why not (what are the problems)? It works well here [1] > [1] with XEmacs 20.4 and post.el (Version 1.6.3.7) Duh. Maybe I should have refreshed my memory first - there was no major problem with gnuclient, just that xemacs beeps at me and says that their is no *Composing* buffer, after I have finished editing and closed the frame. [Another problem was that the defface function was _somewhat_ inadequately defined, and not being any elisp guru I had to replace the font face selections] This was with XEmacs 19.14 and post.el 1.6.3.6. -- Thomas Wolmer | Mail at work: [EMAIL PROTECTED] HG/EHS/OM/DE| ECN Web: http://vksun25.ericsson.se:8001/~ehswolm/ These opinions may | Other mail: [EMAIL PROTECTED] deviate from EHPT's | WWW: http://www.student.nada.kth.se/~d90-two/
Re: Random Sigs
Hi Loren, you wrote on Sat, Oct 09 1999: >Trying to compile with random sigs. Anyone have luck with that? I have randoms sigs, but with an externel perl-script. Was in my Debian distribution, it's called 'signify'. Also works for my newsreader. Simply allocates ~/.signature as a fifo and feeds it with random sigs. Give it a try. Kind regardsFrederick -- The difference between a buddhist and a cow? The buddhist goes "Ommm" the cow goes "M"
Re: how to play a soundfile for incoming mail?
On Sat, Oct 09, 1999 at 01:09:37PM -0700, Shawn D. McPeek wrote: > > xbuffy can do this. > > Check out http://www.fiction.net/blong/programs/#xbuffy > > Shawn > > Previously, Jan Houtsma wrote: > :> Is it possible to play a soundfile when email comes in. > :> > :> Even more can i play a different sound for each mailbox that > :> i have listed in my .muttrc? > :> > :> thanks, > :> > :> jan > > -- > Xerox never comes up with anything original. Well, i think mutt already checks the mailboxes, since it already beeps when mail comes in, so why have another program check it as well? Doesnt mutt allow some hook to define a soundfile i.s.o. the beep? thanks, jan
Re: how to play a soundfile for incoming mail?
Jan Houtsma <[EMAIL PROTECTED]> wrote: > > Doesnt mutt allow some hook to define a soundfile i.s.o. the beep? No. -- 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
mutt with Qmail
Is anyone using this combination, on their Linux system? Qmail is delivering the mail to ~/Maildir, as it is supposed to. I want to read the mail. How do I configure mutt to read these notes? Thank you in advance. Subba Rao [EMAIL PROTECTED] == Disclaimer - I question and speak for myself. http://pws.prserv.net/truemax/ __
Re: Random Sigs
Yet another good one. Thanks for all the angles, guys!
On Sun, Oct 10, 1999 at 03:49:51PM -0500, Erick Kinnee wrote:
>On Sun, Oct 10, 1999 at 04:46:20PM +0200, Frederick Page wrote:
>> Hi Loren,
>>
>> you wrote on Sat, Oct 09 1999:
>>
>> >Trying to compile with random sigs. Anyone have luck with that?
>>
>> I have randoms sigs, but with an externel perl-script. Was in my
>> Debian distribution, it's called 'signify'. Also works for my
>> newsreader. Simply allocates ~/.signature as a fifo and feeds it with
>> random sigs. Give it a try.
>>
>> Kind regardsFrederick
>>
>> --
>> The difference between a buddhist and a cow? The buddhist goes
>> "Ommm" the cow goes "M"
>>
>
>set signature="/usr/games/fortune -n 20|" in .muttrc
>
>Erick
>--
>We were happily married for eight months. Unfortunately, we were
>married for four and a half years.
>-- Nick Faldo
--
,-,-.
Loren Schooley /.( +.\
FlashNet Communications\ {. */
`-`-'
Always remember you're unique, just like everyone else.
Re: mutt with Qmail
Subba Rao <[EMAIL PROTECTED]> wrote on Sun, 10 Oct 1999: > Is anyone using this combination, on their Linux system? I am. Works great. :-) > Qmail is delivering the mail to ~/Maildir, as it is supposed to. > I want to read the mail. How do I configure mutt to read these > notes? Well, there are many ways to do it. I set my MAIL environment variable: MAIL=~/Mail/INBOX (You would, naturally, use MAIL=~/Maildir) Another way would be to use the $spoolfile variable in your .muttrc, set spoolfile=~/Maildir But I think it's better to make sure the MAIL variable is pointing to the right place. 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 / ==/==/==/== Police tagline ==/==/== Do not cross ==/==/==/==
Re: Editing a bounced message
On Fri, Oct 08, 1999 at 12:44:09PM -0500, Jeremy Blosser wrote:
> rex [[EMAIL PROTECTED]] wrote:
> > The (I think) ideal solution would be for Mutt to offer the option to
> > edit the message after "bounce" is selected.
>
> In the stable branch there is an 'edit-message' function that may do what
> you want. This is being reworked currently in the unstable (dev) branch to
> include separate 'edit-message' and 'resend-message' functions -- that
> 'resend-message' is going to be what you want, but the existing
> 'edit-message' may do it for you.
Thanks, but it doesn't work. If the message is edited ("e") before the
attempted bounce, "b" brings up a "Bcc:" query rather than bouncing
the message as it would had the message not been edited. In other words,
there is apparently no way to bounce after editing.
I'd change the sendmail call in .muttrc to call a shell script to allow
me to edit the message before calling sendmail, but I don't know how
to pass the message to the shell script. IOW, I don't know how/where
sendmail is getting the message. The line in .muttrc is
set sendmail="usr/lib/sendmail -oi -oem"
I can't find any docs on what "-oi" and "-oem" do.
-rex (frustrated, again)
Re: Editing a bounced message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, rex <[EMAIL PROTECTED]>,
I use the script you are looking for together with
the naive and clueless PINE. PINE allows in '.pinerc'
to configure a:
sendmail-path=/usr/local/sbin/sendit.sh
In '.muttrc' I use:
set sendmail="/usr/local/sbin/sendit.sh"
I use this script to delete the 'root' from the header
of my mail to satisfy the sysadmin of 'uni-mainz.de'.
The script is still under construction:
- ---
#! /bin/sh
#
# $Id:$
#
#T H EP I N EM A I L S Y S T E M
#
# Mike Seibel
# Networks and Distributed Computing
# Computing and Communications
# University of Washington
# Administration Building, AG-44
# Seattle, Washington, 98195, USA
# Internet: [EMAIL PROTECTED]
#
# Please address all bugs and comments to "[EMAIL PROTECTED]"
#
#
# Pine and Pico are registered trademarks of the University of
Washington.
# No commercial use of these trademarks may be made without prior
written
# permission of the University of Washington.
#
# Pine, Pico, and Pilot software and its included text are Copyright
# 1989-1996 by the University of Washington.
#
# The full text of our legal notices is contained in the file called
# CPYRIGHT, included with this distribution.
#
#
# Simple script to expedite mail posting at the expense of timely
# error reporting and 8BITMIME support.
#
# NOTE: If for any reason POSTFILE below is created on an nfs mounted
# file system, the trap statement below must get removed or
# altered, and the last line must get replaced with:
#
# ( ${POSTTOOL} ${POSTARGS} < ${POSTFILE} ; rm -f ${POSTFILE} ) &
#
###POSTFILE=/tmp/send$$
###POSTTOOL=/usr/lib/sendmail
###POSTARGS="-oi -oem -t"
###
###umask 077
###trap "rm -f ${POSTFILE}; exit 0" 0 1 2 13 15
###
###cat > ${POSTFILE}
###${POSTTOOL} ${POSTARGS} < ${POSTFILE} &
the above originates from PINE ##
to_file=${HOME}/.sendit_post
from_file=${HOME}/.sendit_pre
args_file=${HOME}/.sendit_args
POSTTOOL=/usr/sbin/sendmail
POSTARGS="-oi -oem -t -B8BITMIME -f [EMAIL PROTECTED]"
any_args=$*
echo $any_args > ${args_file}
cat > ${from_file}
cat ${from_file} \
| /usr/bin/sed -e "s/From: winfried szukalski <[EMAIL PROTECTED]/From:
|winfried szukalski
<[EMAIL PROTECTED]/g" \
| /usr/bin/sed -e "s/Sender: szukw000@localhost/Sender: szukw000@localhost/g"
\
| /usr/bin/sed -e "s/Sender: szukw000@localhost/Sender: szukw000@localhost/g"
\
| /usr/bin/sed -e "s/@localhost/@localhost/g" \
| /usr/bin/sed -e "s/From: winfried szukalski <[EMAIL PROTECTED]>/From:
|winfried szukalski
<[EMAIL PROTECTED]>/g" > ${to_file}
${POSTTOOL} ${POSTARGS} < ${to_file} &
#rm -f ${from_file} ${to_file} ${args_file}
- - ~/.sendit_pre --
Date: Mon, 11 Oct 1999 06:22:58 +
From: winfried szukalski <[EMAIL PROTECTED]>
To: szukw000@localhost
Subject: sendit.sh instead of sendmail
Message-ID: <19991011062258.A12860@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
test
- - ~/.sendit_post --
Date: Mon, 11 Oct 1999 06:22:58 +
From: winfried szukalski <[EMAIL PROTECTED]>
To: szukw000@localhost
Subject: sendit.sh instead of sendmail
Message-ID: <19991011062258.A12860@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
test
- --
As you can see: it works with 'mutt-1.0pre3i'.
The 'sendmail' I use is the one of POSTFIX:
-t Extract recipients from message headers. This
requires that no recipients be specified on the
command line.
-f sender
Set the envelope sender address. This is the
address where delivery problems are sent to, unless
the message contains an Errors-To: message header.
Options '-oi -oem' seem to be silently ignored.
winfried
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: Made with pgp4pine 1.62
iEYEARECAAYFAjgBjMIACgkQdoAGL0q6k7pDrgCfYYPHRlC+wfTIoCg+tiGYi/Ro
5DsAn111AwLbDgiqW+6naYNP3igzo6qJ
=ubji
-END PGP SIGNATURE-
