Re: Question about "message status flag"
On 1999-10-12 08:47:00 +0200, Norbert Gruener wrote: > But I think, if Mutt is able to know that a mail is signed, then it > should be able to register that the mail includes a PGP key. No, it's not that easy. When parsing a message for the first time, mutt tries to parse as little of that message as possible. A multipart/signed or multipart/encrypted on the top level is recognized at this point, an application/pgp-keys which is hidden deeply in some multipart structure is _not_.
Re: Editing a bounced message
When using unstable, "resend-message" essentially behaves like the
recalling of a postponed message. Actually, it shares lots of code
with that function. Thus, you can just re-send the message.
The problem with this is that the message will be sent depending on
the headers, that is, every recipient gets the message again.
You can work around this by changing the To and CC headers of the
submission to ORig-To and Orig-CC or something like that, and by
adding a To header of your own. As an alternative, it should be not
too difficult to implement a send-to function on the compose menu,
which sends a message with the given headers to recipients which are
entered on a prompt.
Would this fit your needs?
On 1999-10-10 14:54:21 -0700, rex wrote:
> Date: Sun, 10 Oct 1999 14:54:21 -0700
> From: rex <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: 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: WOB: telnet via port 80 (java?)
Ken W writes: > Sorry for the WOB, but at my new job I only have access via the > firewall through port 80 and I am goig insane not having my email up. I'd say your company has a serious policy problem. > Does anyone know of any way to telnet via port 80, as in maybe a > java-based telnet in a web browser? Check out GNU httptunnel at http://www.nocrew.org/software/httptunnel.html. But it requires that someone outside the firewall sets up the other end.
Re: Editing a bounced message
On Tue, Oct 12, 1999 at 09:52:44AM +0200, Thomas Roessler wrote:
> When using unstable, "resend-message" essentially behaves like the
> recalling of a postponed message. Actually, it shares lots of code
> with that function. Thus, you can just re-send the message.
>
> The problem with this is that the message will be sent depending on
> the headers, that is, every recipient gets the message again.
>
> You can work around this by changing the To and CC headers of the
> submission to ORig-To and Orig-CC or something like that, and by
> adding a To header of your own. As an alternative, it should be not
> too difficult to implement a send-to function on the compose menu,
> which sends a message with the given headers to recipients which are
> entered on a prompt.
>
> Would this fit your needs?
Thanks for the response.
LISTSERV(tm) has a moderation option that sends messages to be posted
to the editor for approval. Approval requires that the MUA insert
"Resent-From: the_editor", and "Resent-To: the_list" header lines and
to leave the "From: ..." line as is. Mutt does this when a message is
"bounced", but it does not offer the opportunity to edit the bounced
message. However, with the help of members of this list, I've now got
a shell script that allows editing after bounce is selected. Normally,
it simply calls sendmail. However, if a message is bounced, the
presence of "Resent-From: the_editor" in the headers results in a call
to an editor so any excess quoting, etc., can be fixed. Since there
may be a large number of messages to be approved that need no editing,
minimizing the number of keystrokes is important, and this solution
does that. All that's required is "b", the alias for the list address,
"Enter" to confirm, and the editor exit key(s). Here's the current
version of the script "bounce":
(.muttrc has set sendmail="/home/rex/bin/bounce")
#! /bin/sh
# uses ideas from a script by Winfried Szukalski <[EMAIL PROTECTED]>
from_file=${HOME}/.sendit_pre
to_file=${HOME}/.sendit_post
POSTTOOL=/usr/lib/sendmail
POSTARGS="-oi -oem -t"
EDITARGS="-tmp -f mail_mode"
cat > ${from_file}
if (grep ^"Resent-From: $USER@" ${from_file})
then
sed '/Delivered-To: '$USER'@/d' ${from_file} > ${to_file}
mv ${to_file} ${from_file}
$VISUAL ${from_file} ${EDITARGS}
fi
${POSTTOOL} ${POSTARGS} < ${from_file}
#rm -f ${from_file}
This seems like a reasonable solution that doesn't require adding code
to Mutt. I am concerned that by calling sendmail with the "-t" option
instead of passing parameters as Mutt does I may be causing a problem
that hasn't shown up yet. OTOH, perhaps the only reason for Mutt's
passing parameters is to pass "--" (which I do not need or want).
Regards,
-rex
test send
test - please ignore
how to show mailboxes only per default?
When i am typing c, to switch to another mailbox, then i see all files and i can press TAB to only see mailboxes. How can i change the default? Thus no need to press TAB to see mailboxes only? Thanks, jan
Re: test send
On Tue, Oct 12, 1999 at 01:25:38PM +0100, John Poltorak wrote: > test - please ignore > > Sender: [EMAIL PROTECTED] Precedence: bulk I'm not sure what I've changed but, I've suddenly got Mutt actually sending out mail. This has been a real struggle, but it looks as though elm is getting very close to being obsolete on my system. -- John
Re: how to show mailboxes only per default?
Jan Houtsma <[EMAIL PROTECTED]> wrote on Tue, 12 Oct 1999: > How can i change the default? Thus no need to press TAB > to see mailboxes only? I don't know about the default, I'm not sure if there is a way -- but I use the following macro: macro index i "c?\t" "show (change to) incoming folders" And I can just press i to see my mail folders. Note that Mutt can't really determine which files (or directories) are mail folders in a directory, but you can specify a list of "incoming mail folders" with the mailboxes command. 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 / 145 = 1! + 4! + 5!
Re: sending mail
On Mon, Oct 11, 1999 at 2:00 PM, Tim Walberg ([EMAIL PROTECTED]) typed: > nope... 'sendmail=cat' will likely result int all kinds > of error messages about cat not recognizing the command > line options that sendmail uses and not being able > to find files and such. I think 'sendmail="echo --"' is > probably best - to get past echo complaining about invalid > arguments too... > > tw At the risk of beating this to death, why not just an easy shell script, something like #!/bin/csh -f echo my command line args were: $* echo my stdin was: /bin/cat - and then set sendmail to the script name. -- -e
managing folders
Is there any way to expire messages in selected folders similar to the way messages in newsgroups are expired? Or to limit the number of messages a folder will hold, so when new messages are added old messages scroll off? Larry Fletcher Redondo Beach, CA USA
checking POP mail
I looked at my .muttrc and it looks as if I deleted a line that says something like 'set check every=5' or something like that. I figured at one time it was to check my pop mail every 5 minutes but when I uncommented the line it made no difference, I still had to check mail with G. Is there something else I have to do for that line to work? -- Loren Due to the confusion from too many genres of music, we have decided to put both country music and rap music into the genre of Crap music.
Re: New Mail in the file Browser?
On Mon, 11 Oct 1999, David DeSimone wrote: > Richard Hitier <[EMAIL PROTECTED]> wrote: > > > > [Mutt doesn't show new messages if you look at the folder, then quit, > > leaving messages marked as new.] > > For mbox folders, that is true. It's considered too slow to open and > rummage through the folders every time you are curious if there is new > mail in the browser. So Mutt simply looks at the time-stamp on the > folder file, and if it is newer than the last time the folder was > examined, Mutt considers there to be new mail. Ok, but when mutt closes a folder with new mail in it, it should actually restore the access time so that the folder is still marked "new". Walter PGP signature
Hey! Where'd that color come from??
Strange, my mutt is normal, with normal xterm color on my BSD xterms. But I ssh'd into it from a Solaris box and, guala!(sic) real color all over the place like it should be! Wha? Maybe I should be using something else besides xterm for color mutt. -- Loren Jury: Twelve people who determine which client has the better lawyer.
Re: checking POP mail
It only checks for local mail, not remote. Mutt's pop3 support is
limited, and there's no such option.
On Tue, Oct 12, 1999 at 11:50:54AM -0500, Loren Schooley wrote:
> I looked at my .muttrc and it looks as if I deleted a line that
> says something like 'set check every=5' or something like that.
>
> I figured at one time it was to check my pop mail every 5 minutes
> but when I uncommented the line it made no difference, I still had to check
> mail with G. Is there something else I have to do for that line
> to work?
--
Frederic L. W. Meunier | fredlwm@{olympiquedemarseille.org,urbi.com.br}
IRC: _19751127!date | ICQ: 49149663 | Tel: +55-21-620-7173 (Brasil)
AppWatch staff - http://appwatch.com/ - {fredlwm,staff}@appwatch.com
+-Open Source with quality-+
Re: Hey! Where'd that color come from??
On [19991012 21:06], Loren Schooley ([EMAIL PROTECTED]) wrote: >Strange, my mutt is normal, with normal xterm color on my >BSD xterms. But I ssh'd into it from a Solaris box and, guala!(sic) >real color all over the place like it should be! Wha? > >Maybe I should be using something else besides xterm for color mutt. Why? I had no problems using `real' colours under my (Free)BSD box, xterm and mutt. So obviosuly you have done something wrong. *chuckle* Seriously, try aterm. Does it well too. -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai> Network/Security SpecialistBSD: Technical excellence at its best For dust thou art, and unto dust shalt thou return.
Re: New Mail in the file Browser?
Walter Hofmann <[EMAIL PROTECTED]> wrote: > > Ok, but when mutt closes a folder with new mail in it, it should > actually restore the access time so that the folder is still marked > "new". Actually, I sort of disagree, but maybe that's just because I'm used to the current behavior, and it doesn't bother me. Mutt has a configure option, --enable-buffy-size, which is supposed to tell it to ignore timestamps, and actually check the folder for new messages. But I don't know if that works for the browser. Does anyone know? -- 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
Re: Editing a bounced message
Thomas Roessler <[EMAIL PROTECTED]> wrote:
>
> As an alternative, it should be not too difficult to implement a
> send-to function on the compose menu, which sends a message with the
> given headers to recipients which are entered on a prompt.
Seems like it would be just as easy to use edit-message, change the
message around, then when you're done, go ahead and the
resulting edited message. Doesn't sound too difficult, and works with
current code.
rex <[EMAIL PROTECTED]> wrote:
>
> #! /bin/sh
> # uses ideas from a script by Winfried Szukalski <[EMAIL PROTECTED]>
> from_file=${HOME}/.sendit_pre
> to_file=${HOME}/.sendit_post
> POSTTOOL=/usr/lib/sendmail
> POSTARGS="-oi -oem -t"
> EDITARGS="-tmp -f mail_mode"
> cat > ${from_file}
> if (grep ^"Resent-From: $USER@" ${from_file})
> then
> sed '/Delivered-To: '$USER'@/d' ${from_file} > ${to_file}
> mv ${to_file} ${from_file}
> $VISUAL ${from_file} ${EDITARGS}
> fi
> ${POSTTOOL} ${POSTARGS} < ${from_file}
> #rm -f ${from_file}
This doesn't look right. "sendmail -t" is going to read the message's
headers, and if there are Cc: recipients, they will get a second copy of
the message sent to them, because of your bounce mechanism.
> I am concerned that by calling sendmail with the "-t" option instead
> of passing parameters as Mutt does I may be causing a problem that
> hasn't shown up yet.
Mutt passes the recipients to your script, and you should go ahead and
pass them on to sendmail; then the message will go only to the recipient
specifies in your command.
POSTARGS should have "-t" removed, and your call to ${POSTTOOL} should
look like this:
${POSTTOOL} ${POSTARGS} "$@" < ${from_file}
Actually, Mutt's arguments that it passes to your script might already
include -oi and -oem, so you probably could forget ${POSTARGS} entirely.
Having said all that, perhaps you should give and
another try.
--
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
Re: Editing a bounced message
David DeSimone hat ueber "Re: Editing a bounced message" geschrieben: > Seems like it would be just as easy to use edit-message, change the > message around, then when you're done, go ahead and the > resulting edited message. Doesn't sound too difficult, and works with > current code. Thats not the way (I think) rex wanted it. And I could need this feature too. If I edit a message and send it, I get a second X-Mailer-Header (mine) and don't have those "resent-from|date|to" Headers in it .-( Maybe someone could make it clear to me, what David mean with "and the resulting editing message" How could I bounce that message? Changing the To-Header? TiA -- \o/ Michael Thies --- [EMAIL PROTECTED] Auf, auf und auf! Laßt uns von Tonne zu Tonne eilen! Wir wollen dem Müll eine Abfuhr erteilen! Heinz Erhardt
Re: New Mail in the file Browser?
Hi, On Tue, Oct 12, 1999 at 15:30 -0500, David DeSimone wrote: > Mutt has a configure option, --enable-buffy-size, which is supposed to > tell it to ignore timestamps, and actually check the folder for new > messages. But I don't know if that works for the browser. Does anyone > know? Yep, it works in the browser. Ciao, Stefan
Re: how to show mailboxes only per default?
On Tue, Oct 12, 1999 at 02:33:58PM +0200, Jan Houtsma wrote: > When i am typing c, to switch to another mailbox, then i > see all files and i can press TAB to only see mailboxes. > > How can i change the default? Thus no need to press TAB > to see mailboxes only? I'm using this (got it from this list) in my .muttrc: macro index C "c?\t" you only need to press "C" instead of "c", and get what you want. -- David
Re: Editing a bounced message
On Tue, Oct 12, 1999 at 03:37:27PM -0500, David DeSimone wrote:
> Thomas Roessler <[EMAIL PROTECTED]> wrote:
> >
> > As an alternative, it should be not too difficult to implement a
> > send-to function on the compose menu, which sends a message with the
> > given headers to recipients which are entered on a prompt.
>
> Seems like it would be just as easy to use edit-message, change the
> message around, then when you're done, go ahead and the
> resulting edited message. Doesn't sound too difficult, and works with
> current code.
Yes, this would be an easy solution, but it doesn't work for me (95.3i).
If the message is edited ("e"), the bounce function is disabled, and "b"
results in a Bcc: query instead of bouncing the message as it normally
would.
> rex <[EMAIL PROTECTED]> wrote:
> >
> > #! /bin/sh
> > # uses ideas from a script by Winfried Szukalski <[EMAIL PROTECTED]>
> > from_file=${HOME}/.sendit_pre
> > to_file=${HOME}/.sendit_post
> > POSTTOOL=/usr/lib/sendmail
> > POSTARGS="-oi -oem -t"
> > EDITARGS="-tmp -f mail_mode"
> > cat > ${from_file}
> > if (grep ^"Resent-From: $USER@" ${from_file})
> > then
> > sed '/Delivered-To: '$USER'@/d' ${from_file} > ${to_file}
> > mv ${to_file} ${from_file}
> > $VISUAL ${from_file} ${EDITARGS}
> > fi
> > ${POSTTOOL} ${POSTARGS} < ${from_file}
> > #rm -f ${from_file}
>
> This doesn't look right. "sendmail -t" is going to read the message's
> headers, and if there are Cc: recipients, they will get a second copy of
> the message sent to them, because of your bounce mechanism.
>
> Mutt passes the recipients to your script, and you should go ahead and
> pass them on to sendmail; then the message will go only to the recipient
> specifies in your command.
I knew there was a reason I didn't like "-t". Thanks.
> POSTARGS should have "-t" removed, and your call to ${POSTTOOL} should
> look like this:
>
> ${POSTTOOL} ${POSTARGS} "$@" < ${from_file}
>
> Actually, Mutt's arguments that it passes to your script might already
> include -oi and -oem, so you probably could forget ${POSTARGS} entirely.
I've looked at $@. Mutt passes "--", then the address(es), and .muttrc
includes "-oi -oem" in the sendmail call, so they may be needed (I
have no idea what they do, and couldn't find them in the sendmail docs
I have).
I'll remove the "-t" and use "$@", as you suggest, however I want to
dump the first argument ("--") first, as it makes premail choke. A
shift command should handle that, eh?
> Having said all that, perhaps you should give and
> another try.
I did, just before writing this. It still doesn't work for me. Does
it work for you?
Thanks,
-rex
Re: Editing a bounced message
Michael Thies <[EMAIL PROTECTED]> wrote on Tue, 12 Oct 1999: > Maybe someone could make it clear to me, what David mean with "and > the resulting editing message" > > How could I bounce that message? Changing the To-Header? My guess is this: 1. Edit the message you want to bounce (with the edit-message function), change it to your liking, and use w(write) to write it back to the same or some other folder. 2. Find that *edited* message (in the same folder, or by changing to that other folder where you saved it in step 1) and bounce that with the normal bounce function. I think that's a bit awkward, but probably works. If you write the message back to the same folder, you may have difficulty in determining which is the original and which is the edited copy. If you save it to some other folder, you need to change there before you can bounce. 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 / "It's just a shadow of the people we should be" -- Big Country
Re: Hey! Where'd that color come from??
On Tue, Oct 12, 1999 at 01:13:53PM -0500, Loren Schooley wrote: > Strange, my mutt is normal, with normal xterm color on my > BSD xterms. But I ssh'd into it from a Solaris box and, guala!(sic) > real color all over the place like it should be! Wha? [...] Especially, if mutt is linked against ncurses (at least in my experience), it depends heaviliy on how your TERM variable is set and/or on the installed terminfo informations about the terminal you're using. In your case I'd check TERM on both machines - might be different on the Solaris box for some odd reasons. I myself use the XFree colour xterm as well as rxvt under Solaris, both compiled to set TERM to xterm-color. Works fine for me. Cheerio, Thomas -- - Thomas Ribbrockhttp://www.bigfoot.com/~kaytanICQ#: 15839919 "You have to live on the edge of reality - to make your dreams come true!"
Tagged messages when changing mailboxes
I skimmed through the manuals and couldn't find a configuration option for this one. Can there be a warning when changing to another mailbox when there are tagged mails in this mailbox (if someone has done the effort to tag them, he might want to do something with them before going on to another mailbox). Kris,
Re: Editing a bounced message
Mikko Hänninen hat ueber "Re: Editing a bounced message" geschrieben: > My guess is this: > > 1. Edit the message you want to bounce (with the edit-message function), > change it to your liking, and use w(write) to write it back to the same > or some other folder. And quit that message without postponing it. .-) > 2. Find that *edited* message (in the same folder, or by changing to > that other folder where you saved it in step 1) and bounce that with > the normal bounce function. thx, that works, but as You mentioned, it is an arghful method .-( Maybe it will be in some future release one feature for mutt. CU -- \o/ Michael Thies --- [EMAIL PROTECTED] Was heißt Zeugnis auf arabisch? - Der-wisch!
