slrn error
I'm trying to get slrn working on my Redhat 6.2 system and I receive the following error when I execute the program: Reading startup file /usr/lib/slrn/slrn.rc. Unable to open score file /home/dlm/News/Score slrn fatal error: Error processing score file /home/dlm/News/Score. I'm using a cable connection and have NNTP variable set like this: export NNTPSERVER=news.lvcablemodem.com in my .bash_profile file. Currently I'm using emacs to read news with. I tried the .slrnrc file that was listed on a 'hack'website I saw on a post in this ng, but still had the same problem. Thanks -- dale
Re: slrn error
Dale Morris proclaimed on mutt-users that: I'm trying to get slrn working on my Redhat 6.2 system and I receive the following error when I execute the program: Reading startup file /usr/lib/slrn/slrn.rc. Unable to open score file /home/dlm/News/Score slrn fatal error: Error processing score file /home/dlm/News/Score. Try creating the file using touch. You apparently _need_ a score file, even though you haven't set scores for any posts. -- Suresh Ramasubramanian + [EMAIL PROTECTED] Truth will be out this morning. (Which may really mess things up.)
Re: slrn error
Thanks! It worked. Now I just need to get some decent colors in slrn. At 10 June, 2000 Suresh Ramasubramanian wrote: Dale Morris proclaimed on mutt-users that: I'm trying to get slrn working on my Redhat 6.2 system and I receive the following error when I execute the program: Reading startup file /usr/lib/slrn/slrn.rc. Unable to open score file /home/dlm/News/Score slrn fatal error: Error processing score file /home/dlm/News/Score. Try creating the file using touch. You apparently _need_ a score file, even though you haven't set scores for any posts. -- Suresh Ramasubramanian + [EMAIL PROTECTED] Truth will be out this morning. (Which may really mess things up.) -- "Make voyages, attempt them, there's nothing else." --Tennessee Williams
Re: news with mutt
Hello Janek!
On Sat, 10 Jun 2000, Janek Richter wrote:
i want to know if it is possible to read newsgroups in mutt.
AFAIK there is a patch for an older version of mutt, but I
prefer a solution which will use slrn in combination with
mutt (reply and forwarding). This was posted by Thomas Roessler
[EMAIL PROTECTED] on the end of january 2000 on this list.
It's using the attached slrn macro file, plus the attached shell
script wrapper.
Note that this solution requires formail (1) from the procmail
package.
Thank you very much, Thomas!! :-)))
--- cut here -
%
% replacement forward and reply functions for slrn.
% these will drop you to your normal mail user agent.
%
variable mua_script="/home/roessler/bin/slrn-mua";
define my_reply_to_article ()
{
pipe_article (Sprintf ("%s -reply", mua_script, 1));
}
define my_forward_article ()
{
pipe_article (Sprintf ("%s -forward", mua_script, 1));
}
definekey ("my_reply_to_article", "r", "article");
definekey ("my_forward_article", "F", "article");
##
#!/bin/sh --
#
# A small script which is used to reply to or forward an
# article from within slrn.
#
# The article is expected to come on stdin, while $1 is either
# -reply or -forward.
#
# where is mutt located?
MUTT=/usr/local/bin/mutt
# where is formail?
FORMAIL=/usr/bin/formail
TMPDIR=${TMPDIR-/tmp}/`basename $0`.$$
mkdir -m 0700 $TMPDIR || { echo "can't create $TMPDIR!" 2 ; exit ; }
trap "rm -rf $TMPDIR; trap '' 0; exit" 0 1 2 3 4
cat $TMPDIR/article
# get various headers
SUBJECT="`formail -z -x Subject: $TMPDIR/article`"
DATE="`formail -z -x Date: $TMPDIR/article`"
FROM="`formail -z -x From: $TMPDIR/article`"
REPLY_TO="`formail -z -x Reply-To: $TMPDIR/article`"
MESSAGE_ID="`formail -z -x Message-ID: $TMPDIR/article`"
REFERENCES="`formail -z -x References: $TMPDIR/article`"
exec $TMPDIR/template
#
# functions
#
prepare_reply () {
if [ -n "$REPLY_TO" ] ; then
echo "To: $REPLY_TO"
else
echo "To: $FROM"
fi
if [ -n "$MESSAGE_ID" ] ; then
echo "In-Reply-To: $MESSAGE_ID"
echo "References: $REFERENCES $MESSAGE_ID"
fi
echo -n "Subject: "
if [ -z "$SUBJECT" ] ; then
echo "Re: your mail"
else
echo -n "Re: "
echo "$SUBJECT" | sed -e 's/^Re: *//'
fi
echo
echo "On $DATE, $FROM wrote:" | fmt
sed -e 's/^/ /' $TMPDIR/article
}
prepare_forward () {
echo "Subject: Fwd: $SUBJECT"
echo
echo "- Forwarded message -"
cat $TMPDIR/article
echo
echo " End forwarded message-"
}
#
# main
#
case "$1" in
-reply)
prepare_reply
;;
-forward)
prepare_forward
;;
*)
echo "usage: `basename $0` {-reply|-forward}" 2
exit 1
;;
esac
exec /dev/tty
$MUTT -H $TMPDIR/template /dev/tty
--- cut here -
Enjoy it!
bye - Wilhelm
--
Wilhelm Wienemann __
/ /__ _ _ _ _ __ __
(° (o- / /__ / / / \// //_// \ \/ / -°) -°)
//\ //\ // /_/ /_/\/ /___/ /_/\_\ /\\ /\\
V_/_ v_/_ # Enjoy Linux and the Power of Open Source # _\_V _\_V
Re: Managing multiple accts with mutt + fetchmail
On Sat, Jun 10, 2000 at 01:37:59AM +0300, Mikko Hänninen wrote: Marius Gedminas [EMAIL PROTECTED] wrote on Fri, 09 Jun 2000: Use `set from=...' instead of `my_hdr From: ...'. Right, this is the way to go. $realname takes precedence over $from, but not over my_hdr. Oops! I wanted to say $reverse_name, not $realname. g Marius Gedminas -- When in trouble or in doubt, run in circles, scream and shout.
Re: Mail delivery and GZIP patch
On Sat, Jun 10, 2000 at 12:02:09PM +0200, Nils Vogels wrote: Hi all! I have a simple question to ask: For obvious reasons I have gzipped some mailinglist folders, but I kinda ran into a problem now .. The problem isnt mutt, since mutt handles the .gz folders perfectly .. the problem is my mail delivery .. how do I tell procmail to add the mail in .gz format to the other mails ? Maybe ask on the procmail list Grtz, Nils. -- -BEGIN GEEK CODE BLOCK- Version: 3.12 Comment: Take a look at http://www.geekcode.com for more info on geek code GCS/CC d--- s++: a-? C+++ UL(US)$ P+++ L++ !EE? W+ N+ o+ K? w--- O- M-- V-- PS PE++ Y++ PGP++ t+ 5++ X+ !R tv- b DI+ D- G+ e+++ h+ r y+*+++* --END GEEK CODE BLOCK-- -- John
Re: Mail delivery and GZIP patch
Nils Vogels [EMAIL PROTECTED] wrote on Sat, 10 Jun 2000: The problem isnt mutt, since mutt handles the .gz folders perfectly .. the problem is my mail delivery .. how do I tell procmail to add the mail in .gz format to the other mails ? First off, I would tell you not to deliver mail to gzipped mailboxes. If you want to keep your archived mail in gzipped folders, I'd keep those separate from the incoming folders, and then you can move all email to the archive folder with Mutt once you've read it. You can even do "set move=yes" and set $record in folder-hooks to get folder-specific archive folders, and automatic archiving of read messages. If you still insist on doing delivery from procmail into a gzipped folder, here's how: | gzip -c folder.gz You can just append gzipped data at the end of previously gzipped data, and it will work. However, you *do* need to take care of some precautions to make sure the folder is locked somehow. You may want to write a shell script for gzip delivery that takes care of locking before it writes to the folder, and then use that shell script to deliver from procmail. (Or maybe you could use procmail's ":lockfile" method on the rule specification line, I don't know.) 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 / All I ask is a chance to prove that money can't make me happy.
Re: news with mutt
This is wonderful, but I am a bit of a newbie when it comes to scripting
and whatnot. Is the first part of this a patch? How would I go about
exectuing all of this...?
On Sat, Jun 10, 2000 at 07:36:50AM +0200, Wilhelm Wienemann muttered:
| Hello Janek!
|
| On Sat, 10 Jun 2000, Janek Richter wrote:
|
| i want to know if it is possible to read newsgroups in mutt.
|
| AFAIK there is a patch for an older version of mutt, but I
| prefer a solution which will use slrn in combination with
| mutt (reply and forwarding). This was posted by Thomas Roessler
| [EMAIL PROTECTED] on the end of january 2000 on this list.
| It's using the attached slrn macro file, plus the attached shell
| script wrapper.
|
| Note that this solution requires formail (1) from the procmail
| package.
|
| Thank you very much, Thomas!! :-)))
|
| --- cut here -
| %
| % replacement forward and reply functions for slrn.
| % these will drop you to your normal mail user agent.
| %
|
| variable mua_script="/home/roessler/bin/slrn-mua";
|
| define my_reply_to_article ()
| {
| pipe_article (Sprintf ("%s -reply", mua_script, 1));
| }
|
| define my_forward_article ()
| {
| pipe_article (Sprintf ("%s -forward", mua_script, 1));
| }
|
| definekey ("my_reply_to_article", "r", "article");
| definekey ("my_forward_article", "F", "article");
|
| ##
|
| #!/bin/sh --
|
| #
| # A small script which is used to reply to or forward an
| # article from within slrn.
| #
| # The article is expected to come on stdin, while $1 is either
| # -reply or -forward.
| #
|
| # where is mutt located?
| MUTT=/usr/local/bin/mutt
|
| # where is formail?
| FORMAIL=/usr/bin/formail
|
| TMPDIR=${TMPDIR-/tmp}/`basename $0`.$$
| mkdir -m 0700 $TMPDIR || { echo "can't create $TMPDIR!" 2 ; exit ; }
|
| trap "rm -rf $TMPDIR; trap '' 0; exit" 0 1 2 3 4
|
| cat $TMPDIR/article
|
| # get various headers
|
| SUBJECT="`formail -z -x Subject: $TMPDIR/article`"
| DATE="`formail -z -x Date: $TMPDIR/article`"
| FROM="`formail -z -x From: $TMPDIR/article`"
| REPLY_TO="`formail -z -x Reply-To: $TMPDIR/article`"
| MESSAGE_ID="`formail -z -x Message-ID: $TMPDIR/article`"
| REFERENCES="`formail -z -x References: $TMPDIR/article`"
|
| exec $TMPDIR/template
|
| #
| # functions
| #
|
| prepare_reply () {
| if [ -n "$REPLY_TO" ] ; then
| echo "To: $REPLY_TO"
| else
| echo "To: $FROM"
| fi
|
| if [ -n "$MESSAGE_ID" ] ; then
| echo "In-Reply-To: $MESSAGE_ID"
| echo "References: $REFERENCES $MESSAGE_ID"
| fi
|
| echo -n "Subject: "
|
| if [ -z "$SUBJECT" ] ; then
| echo "Re: your mail"
| else
| echo -n "Re: "
| echo "$SUBJECT" | sed -e 's/^Re: *//'
| fi
|
| echo
|
| echo "On $DATE, $FROM wrote:" | fmt
|
| sed -e 's/^/ /' $TMPDIR/article
| }
|
| prepare_forward () {
| echo "Subject: Fwd: $SUBJECT"
| echo
| echo "- Forwarded message -"
| cat $TMPDIR/article
| echo
| echo " End forwarded message-"
| }
|
| #
| # main
| #
|
|
| case "$1" in
| -reply)
| prepare_reply
| ;;
| -forward)
| prepare_forward
| ;;
| *)
| echo "usage: `basename $0` {-reply|-forward}" 2
| exit 1
| ;;
| esac
|
| exec /dev/tty
|
| $MUTT -H $TMPDIR/template /dev/tty
|
| --- cut here -
|
| Enjoy it!
|
| bye - Wilhelm
|
| --
| Wilhelm Wienemann __
| / /__ _ _ _ _ __ __
| (° (o- / /__ / / / \// //_// \ \/ / -°) -°)
| //\ //\ // /_/ /_/\/ /___/ /_/\_\ /\\ /\\
| V_/_ v_/_ # Enjoy Linux and the Power of Open Source # _\_V _\_V
--
/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! 1024D/D75E0A36
[sureshr@staff.juno.com: Re: How do I make pop support do polling?]
Timothy Ball proclaimed on mutt-users that: Fetchmail is frowned upon because of the fact that fetchamil basically runs as a deamon. What's wrong with that? Andy Eichmann
executing URL's and Image files
How do I get slrn and mutt to execute images automatically? I assume this is a function of the .mailcap file and I'm including mine to see if someone can help me with it. Also, how do I get slrn to call up Netscape for URL's? It works fine with mutt and control b, but I haven't found out how to make it work with slrn. thanks in advance -- dale
No from name when sent
Hi, I am using mutt version 0.95.3i. It does not sent my name but only the email address in the from header. My .muttrc says this: set realname='Suresh Kumar. R' my_hdr From: [EMAIL PROTECTED] my_hdr Reply-To: [EMAIL PROTECTED] Any ideas? I am using qmail as my mta. I didnt have this problem when I was using pine -- Suresh -- Suresh Kumar.R, Email: [EMAIL PROTECTED] Dept of Electronics Communication College of Engineering, Trivandrum - 695 016, INDIA Phone: (O) 91 471 414634/418379, (R) 91 471 443496
Re: No from name when sent
Use this as your my_hdr: my_hdr From: Name Here [EMAIL PROTECTED] # Real Name On Sat, Jun 10, 2000 at 01:29:35AM +, [EMAIL PROTECTED] muttered: | Hi, | | I am using mutt version 0.95.3i. | | It does not sent my name but only the email address in the from | header. | | My .muttrc says this: | | set realname='Suresh Kumar. R' | my_hdr From: [EMAIL PROTECTED] | my_hdr Reply-To: [EMAIL PROTECTED] | | Any ideas? | | I am using qmail as my mta. I didnt have this problem when I was using | pine | -- | Suresh | -- | Suresh Kumar.R, Email: [EMAIL PROTECTED] | Dept of Electronics Communication | College of Engineering, Trivandrum - 695 016, INDIA | Phone: (O) 91 471 414634/418379, (R) 91 471 443496 -- /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! 1024D/D75E0A36
Re: news with mutt
Hello Jason!
On Sat, 10 Jun 2000, Jason Helfman wrote:
On Sat, Jun 10, 2000 at 07:36:50AM +0200, Wilhelm Wienemann muttered:
This is wonderful, but I am a bit of a newbie when it comes to
scripting and whatnot. Is the first part of this a patch?
No, it's a macro-file. On my box I've all my macros in the
$HOME/.slrn directory and here it is called .slrn-mua.sl
To load (interpret) it with my $HOME/.slrnrc file I have to
add a line like
interpret ".slrn/.slrn-mua.sl"
--- cut here -
%
% replacement forward and reply functions for slrn.
% these will drop you to your normal mail user agent.
%
variable mua_script="/usr/local/bin/slrn-mua.sh";
define my_reply_to_article ()
{
pipe_article (Sprintf ("%s -reply", mua_script, 1));
}
define my_forward_article ()
{
pipe_article (Sprintf ("%s -forward", mua_script, 1));
}
definekey ("my_reply_to_article", "r", "article");
definekey ("my_forward_article", "F", "article");
-
How would I go about exectuing all of this...?
The following shell script wrapper is located as slrn-mua.sh
in the directory /usr/local/bin/
---
#!/bin/sh --
#
# A small script which is used to reply to or forward an
# article from within slrn.
#
# The article is expected to come on stdin, while $1 is either
# -reply or -forward.
#
# where is mutt located?
MUTT=/usr/bin/mutt
# where is formail?
FORMAIL=/usr/bin/formail
TMPDIR=${TMPDIR-/tmp}/`basename $0`.$$
mkdir -m 0700 $TMPDIR || { echo "can't create $TMPDIR!" 2 ; exit ; }
trap "rm -rf $TMPDIR; trap '' 0; exit" 0 1 2 3 4
cat $TMPDIR/article
# get various headers
SUBJECT="`formail -z -x Subject: $TMPDIR/article`"
DATE="`formail -z -x Date: $TMPDIR/article`"
FROM="`formail -z -x From: $TMPDIR/article`"
REPLY_TO="`formail -z -x Reply-To: $TMPDIR/article`"
MESSAGE_ID="`formail -z -x Message-ID: $TMPDIR/article`"
REFERENCES="`formail -z -x References: $TMPDIR/article`"
exec $TMPDIR/template
#
# functions
#
prepare_reply () {
if [ -n "$REPLY_TO" ] ; then
echo "To: $REPLY_TO"
else
echo "To: $FROM"
fi
if [ -n "$MESSAGE_ID" ] ; then
echo "In-Reply-To: $MESSAGE_ID"
echo "References: $REFERENCES $MESSAGE_ID"
fi
echo -n "Subject: "
if [ -z "$SUBJECT" ] ; then
echo "Re: your mail"
else
echo -n "Re: "
echo "$SUBJECT" | sed -e 's/^Re: *//'
fi
echo
echo "On $DATE, $FROM wrote:" | fmt
sed -e 's/^/ /' $TMPDIR/article
}
prepare_forward () {
echo "Subject: Fwd: $SUBJECT"
echo
echo "- Forwarded message -"
cat $TMPDIR/article
echo
echo " End forwarded message-"
}
#
# main
#
case "$1" in
-reply)
prepare_reply
;;
-forward)
prepare_forward
;;
*)
echo "usage: `basename $0` {-reply|-forward}" 2
exit 1
;;
esac
exec /dev/tty
$MUTT -H $TMPDIR/template /dev/tty
--- cut here -
Note: The Shell-script needs the executable permissions for
its users. This is usually done by a 'chmod -v 755 slrn-mua.sh'
as root in the destination directory.
Now every time you use a 'r' to do a reply or a 'F' to do a
forwarding in slrn it will use 'mutt'.
Enjoy it! :-))
bye - Wilhelm
--
-- _ _ __ __ Wilhelm Wienemann [EMAIL PROTECTED]
| (_)_ __ _ _\ \/ / - For a better taste - Linux Inside
| | | '_ \| | | |\ /- Blue screens for Linux background only
| | | | | | |_| |/ \- Enjoy Linux and the Power of Open Source
|_|_|_| |_|\__,_/_/\_\ Registered-Linux-User: 70712 http://counter.li.org/
Re: No from name when sent
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote on Sat, 10 Jun 2000: set realname='Suresh Kumar. R' my_hdr From: [EMAIL PROTECTED] The my_hdr From: is overriding the $realname setting. If you want to use my_hdr From:, you need to provide the full From header. Like this: my_hdr From "Suresh Kumar. R" [EMAIL PROTECTED] 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 / Periodically spray diskettes with insecticide to prevent bugs from spreading.
Re: imap and message stati
Brendan, et al -- ...and then Brendan Cully said... % On Friday, 09 June 2000 at 08:08, David T-G wrote: % % confirm, once again, that making an imap connection and then exiting (not % quitting), without even reading any messages, will change all of my 'N'ew % message flags to 'O'ld. % % Unfortunately there really isn't anything you can do about this. The Oh, darn. I know that it used to work, though. Are there some servers that force this and some that don't, or is the a configure-time flag, or anything like that? % IMAP spec gives clients no control over the \Recent flag, which is % what distinguishes between New and Old messages. Most servers remove Hmmm... So there are never-seen, seen-but-never-read, and read (perhaps replied) message states, then, right? And there's no way to get out of that connection without having the never-seen changed to seen? % the \Recent flag from all messages as soon as you open their mailbox, % automatically. RFC 2060 disallows clients to restore that flag. So, if % you find this behaviour annoying, I'd recommend that you unset % mark_old. That's what I do, anyway. Well, that doesn't do me any good when I need to be able to pop into my wife's mailbox, check on a message that just came in which she can't download at the moment, and then make it new again for her POPping later... % % -Brendan 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! 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: Backing up Mail, suggestions
Jason -- ...and then Jason Helfman said... % % How would I setup a crontab entry to zip every 15 days of the month... Well, for crontab instructions, there's the crontab manual page... % % Some have 30, some 28, some 31...? Do you really mean every fifteen, so you'd do your backing and zipping on 1/1, 1/16, 1/31, 2/15, 3/2 (non-leap), 3/17, ... Or do you just mean the 15th and the last? % % And I want the dates to correspond to the actual date of the archive... That sounds like a shell scripting, or perl, or whatever, question. Still easy. % % Thanks very much... % % Here is my crontab entry. % % 1 0 1 1-12 * $HOME/backup-mail |mail deklown -s "Cron: Mail Backed Up Looks like you're backing up every first of the month in the first 12 months (hmmm, that 1-12 could become * happily). Keep your life simple; back up on the 1st and 16th with 1 0 1,16 * * $HOME/backup-mail | mail deklown -s "Cron: Mail Backed Up" instead of messing with those "is today (or tomorrow) the last day?" questions... Besides, you can then use mutt's limiting to pull out only the stuff thru yesterday (15th/last) to drop into your archive. If you really wanted to have the "last day" functionality, I have both shell and perl scripts for that sort of thing that I could share. :-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: Mail delivery and GZIP patch
Nils -- I never saw the original of this go by, so ... ...and then John Poltorak said... % On Sat, Jun 10, 2000 at 12:02:09PM +0200, Nils Vogels wrote: % % I have a simple question to ask: For obvious reasons I have gzipped some mailinglist folders, but I kinda ran into a problem now .. Yay for you -- but you really shouldn't be gzipping active delivery folders. % % The problem isnt mutt, since mutt handles the .gz folders perfectly .. the problem is my mail delivery .. how do I tell procmail to add the mail in .gz format to the other mails ? You have to run the email through a compress program, such as gzip (in much the same way that you pipe through formail to mush it around), and then append the output to your folder. The key here is locking; it's entirely possible that you'll have two procmail processes trying to append to the same file at once, and the best that that could be is bad. % % Maybe ask on the procmail list That's a good idea, too:-) % % Grtz, % % Nils. % % -- % -BEGIN GEEK CODE BLOCK- % Version: 3.12 % Comment: Take a look at http://www.geekcode.com for more info on geek code % GCS/CC d--- s++: a-? C+++ UL(US)$ P+++ L++ !EE? W+ N+ o+ K? w--- % O- M-- V-- PS PE++ Y++ PGP++ t+ 5++ X+ !R tv- b DI+ D- G+ e+++ h+ r y+*+++* % --END GEEK CODE BLOCK-- -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS/CM/IT !d-? s:- a C++$ UBLVHS+++$ P++$ L$ !E--- W++$ N++(+++)$ o+++$ K w(--) !O- !M-(--) V-(--) !PS+++(+) PE++(+) Y+ PGP++ t+ !5(+) !X !R !tv b+++$ DI$ !D- G e++ h r+++ y* --END GEEK CODE BLOCK-- :-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: news with mutt
This worked out wonderful. I wonder though, when I replied to a message,
it did use mutt fine, but all the headers from slrn news file went into
the reply. Is their a way to filter this out?
Also what feature of mutt can be used? It looked like it just used mutt
to deliver, is this correct?
On Sat, Jun 10, 2000 at 10:28:54PM +0200, Wilhelm Wienemann muttered:
| Hello Jason!
|
| On Sat, 10 Jun 2000, Jason Helfman wrote:
| On Sat, Jun 10, 2000 at 07:36:50AM +0200, Wilhelm Wienemann muttered:
|
| This is wonderful, but I am a bit of a newbie when it comes to
| scripting and whatnot. Is the first part of this a patch?
|
| No, it's a macro-file. On my box I've all my macros in the
| $HOME/.slrn directory and here it is called .slrn-mua.sl
| To load (interpret) it with my $HOME/.slrnrc file I have to
| add a line like
|
| interpret ".slrn/.slrn-mua.sl"
|
| --- cut here -
| %
| % replacement forward and reply functions for slrn.
| % these will drop you to your normal mail user agent.
| %
|
| variable mua_script="/usr/local/bin/slrn-mua.sh";
|
| define my_reply_to_article ()
| {
| pipe_article (Sprintf ("%s -reply", mua_script, 1));
| }
|
| define my_forward_article ()
| {
| pipe_article (Sprintf ("%s -forward", mua_script, 1));
| }
|
| definekey ("my_reply_to_article", "r", "article");
| definekey ("my_forward_article", "F", "article");
|
| -
|
| How would I go about exectuing all of this...?
|
| The following shell script wrapper is located as slrn-mua.sh
| in the directory /usr/local/bin/
|
| ---
| #!/bin/sh --
|
| #
| # A small script which is used to reply to or forward an
| # article from within slrn.
| #
| # The article is expected to come on stdin, while $1 is either
| # -reply or -forward.
| #
|
| # where is mutt located?
| MUTT=/usr/bin/mutt
|
| # where is formail?
| FORMAIL=/usr/bin/formail
|
| TMPDIR=${TMPDIR-/tmp}/`basename $0`.$$
| mkdir -m 0700 $TMPDIR || { echo "can't create $TMPDIR!" 2 ; exit ; }
|
| trap "rm -rf $TMPDIR; trap '' 0; exit" 0 1 2 3 4
|
| cat $TMPDIR/article
|
| # get various headers
|
| SUBJECT="`formail -z -x Subject: $TMPDIR/article`"
| DATE="`formail -z -x Date: $TMPDIR/article`"
| FROM="`formail -z -x From: $TMPDIR/article`"
| REPLY_TO="`formail -z -x Reply-To: $TMPDIR/article`"
| MESSAGE_ID="`formail -z -x Message-ID: $TMPDIR/article`"
| REFERENCES="`formail -z -x References: $TMPDIR/article`"
|
| exec $TMPDIR/template
|
| #
| # functions
| #
|
| prepare_reply () {
| if [ -n "$REPLY_TO" ] ; then
| echo "To: $REPLY_TO"
| else
| echo "To: $FROM"
| fi
|
| if [ -n "$MESSAGE_ID" ] ; then
| echo "In-Reply-To: $MESSAGE_ID"
| echo "References: $REFERENCES $MESSAGE_ID"
| fi
|
| echo -n "Subject: "
|
| if [ -z "$SUBJECT" ] ; then
| echo "Re: your mail"
| else
| echo -n "Re: "
| echo "$SUBJECT" | sed -e 's/^Re: *//'
| fi
|
| echo
|
| echo "On $DATE, $FROM wrote:" | fmt
|
| sed -e 's/^/ /' $TMPDIR/article
| }
|
| prepare_forward () {
| echo "Subject: Fwd: $SUBJECT"
| echo
| echo "- Forwarded message -"
| cat $TMPDIR/article
| echo
| echo " End forwarded message-"
| }
|
| #
| # main
| #
|
|
| case "$1" in
| -reply)
| prepare_reply
| ;;
| -forward)
| prepare_forward
| ;;
| *)
| echo "usage: `basename $0` {-reply|-forward}" 2
| exit 1
| ;;
| esac
|
| exec /dev/tty
|
| $MUTT -H $TMPDIR/template /dev/tty
|
| --- cut here -
|
| Note: The Shell-script needs the executable permissions for
| its users. This is usually done by a 'chmod -v 755 slrn-mua.sh'
| as root in the destination directory.
|
| Now every time you use a 'r' to do a reply or a 'F' to do a
| forwarding in slrn it will use 'mutt'.
|
| Enjoy it! :-))
|
| bye - Wilhelm
|
| --
| -- _ _ __ __ Wilhelm Wienemann [EMAIL PROTECTED]
| | (_)_ __ _ _\ \/ / - For a better taste - Linux Inside
| | | | '_ \| | | |\ /- Blue screens for Linux background only
| | | | | | | |_| |/ \- Enjoy Linux and the Power of Open Source
| |_|_|_| |_|\__,_/_/\_\ Registered-Linux-User: 70712 http://counter.li.org/
|
--
/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! 1024D/D75E0A36
