Re: Display Errors
Thomas, et al -- ...and then Thomas Huemmler said... % ... % What I have noticed is, that if you continue a mutt directive in another % line, you have to put not only a backslash (\) at the end of the line, % but also enter a space before ( \). Sometimes I forget this and then I % always get some kind of visual effects. This makes sense when you think about it; the backslash simply escapes the newline and has the effect of sucking the next line up onto the current one... If you don't have a space before your escape and newline, then it is the same as running two keywords together. What many people do is indent their continued lines, which not only gives a visual indication of two (or more) lines belonging together but which also has the delightful side effect of adding the extra space that you've noticed one must have. How convenient! :-) % % What works for me is to /modularize/ the rc-files of mutt. So if % something strange happens, I could /unsource/ the various modules and % localize the misbehaviour more easily by sourcing one after another. Excellent idea. How do you unsource, though? I can only figure that you comment out the source line(s) and then restart mutt, no? % % HTH, % Thomas HTH & HAND % % -- % Thomas Hümmler * [EMAIL PROTECTED] * http://www.huemmler.de :-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.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg24471/pgp0.pgp Description: PGP signature
Re: forwarding attachments (PLEASE READ before replying)
Aleks -- ...and then Aleks Owczarek said... % % On Tue, Feb 12, 2002 at 10:24:47PM -0500, David T-G wrote: % > Sure; that's fair, and you're entitled to your HO. So write it :-) % % well I suppose the point of my question was to inspire someone with % the know-how to do just that ... and you sound like such a clever % fellow David ... Heh... You wish :-) I am *definitely* not a C programmer! % % anyway, thanks for taking an interest Happy to help! % % % > % > P.S. -- Your M-F-T: was broken on this message, too % > % % > % ps: not sure what is happening with my M-F-T: they appeared as % > % Mail-followup-to: Aleks Owczarek <[EMAIL PROTECTED]>, % > % Mutt Users' List <[EMAIL PROTECTED]> % > % > That's quite interesting; I didn't know they gave out gbnet accounts to % > mailing list members ;-) % % I don't think I have one - just that it appears that way. Right. It must have been an interesting side effect of your having a bare username. Now that you've told mutt that you're subscribed to mutt-users, I doubt we'll see a malformed M-F-T: header even if the underlying problem isn't fixed. That's one way to fix it :-) but keep an eye out for it as you reply to other list mail where you're not subscribed just in case your setting $from didn't get it. HTH & HAND :-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.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg24472/pgp0.pgp Description: PGP signature
Header Limitations
Hi, I'm in charge of a student organization at my university and am required to send weekly newsletter-emails to near 1000 addresses. I've been trying to use mutt to send these emails, but I can't seem to fit all one thousand address on a single bcc: line; only about 250 fit, and the rest just get chopped off. Does anyone know what the exact limits are for fitting addresses in the header lines? It seems that there's a maximum number of addresses you can fit, as well as a maximum number of characters you can put in the line. Better yet, does anyone know of a good way to send mass emails without using a 3rd-party service? Thanks, Alan __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com
forground color of the indicator
hi freaks. Is it possible to set the indicator foreground color to none? I mark new, old mails with colors and so i don't want to let the indicator change it. TIA marc(..)
Re: Header Limitations
Alan -- ...and then Alan Lue said... % % Hi, Hello! % % I'm in charge of a student organization at my % university and am required to send weekly % newsletter-emails to near 1000 addresses. I've been % trying to use mutt to send these emails, but I can't % seem to fit all one thousand address on a single bcc: % line; only about 250 fit, and the rest just get % chopped off. Can you break it into multiple bcc: headers, perhaps? % % Does anyone know what the exact limits are for fitting % addresses in the header lines? It seems that there's % a maximum number of addresses you can fit, as well as % a maximum number of characters you can put in the % line. Dunno about this one; sorry. % % Better yet, does anyone know of a good way to send % mass emails without using a 3rd-party service? Does "3rd-party" include mailing lists from your own server? Let ezmlm or majordomo or mailman handle it for you. I presume that, even though you have a yahoo ID, you don't want to use Yahoo's EGroups. I don't blame you ;-) % % Thanks, % Alan HTH & HAND :-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.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg24475/pgp0.pgp Description: PGP signature
Re: setting the the name of the sender of the mail
* Georges Roig <[EMAIL PROTECTED]> [13-02-2002 15:31]: > I'm trying to set the name of the sender of the mail with mutt as > we can do it with sendmail and the option -f. It sounds there is no > option with mutt, but could you just confirm me that or tell me if > can bypass by another way. First of all, these questions should be directed to mutt-users in stead of mutt-dev. You can specify the from address by pressing 'f' in the compose menu (the menu you enter after composing the email). Alternatively, you can set $edit_hdrs, which will allow you to edit the headers together with the body of the message. The last thing I'll come up with is starting mutt with: mutt -e "my_hdr From: Your Name <[EMAIL PROTECTED]>" > Many thanks Georges HTH, -- René Clerc - ([EMAIL PROTECTED]) Experience is a hard teacher because she gives the test first, the lesson afterward. -Vernon Law, baseball pitcher msg24476/pgp0.pgp Description: PGP signature
Re: "incorrect" date for attribution
Ah, apparently I did not look far down enough in that section of the
manual (6.3.80 btw in my version) when I read it :)
Using %{ } instead gives the behavior I wanted (as seen in my
attribution below :)
Also, in my original mail I had included the envelope From header,
but it was missing in the mail delivered to the list? This is probably
some safeguard to prevent breaking mboxes (since it is used as
delimiter), but it would be better if the line was escaped than
silently removed.
Thanks,
Stefan
Quoting Aaron Schrab <[EMAIL PROTECTED]> [12 Feb-02 12:33]:
> At 11:48 +0100 12 Feb 2002, Stefan Alfredsson <[EMAIL PROTECTED]> wrote:
> > As my attribution string, I have a simple
> > set attribution="Quoting %n <%a> [%(%d %b-%y %H:%M)]:"
>
> > However, the date and time seems to be taken from the mbox From
> > (no, not From:) header, instead of the Date: header field.
>
> This is documented behaviour. The section of the manual on $index_format
> (6.3.79), to which the documentation for the $attribution setting refers says
> in part:
>
>%(fmt)
> the local date and time when the message was received.
>
> See the documentation for %{fmt} and %[fmt] in the same section.
Re: Display Errors
Hallo David, * David T-G <[EMAIL PROTECTED]> [020213 11:30]: > also has the delightful side effect of adding the extra space that you've > noticed one must have. How convenient! :-) indeed :-) > Excellent idea. How do you unsource, though? I can only figure that you > comment out the source line(s) and then restart mutt, no? that´s correct. Therefore I have put /unsource/ in italics. But I think it is not so difficult to get such a feature. It should be possible to unsource by sourcing the default value, e.g. for a macro (untested): macro index "|/home/thomas/.mutt/bin/kill-by-subject\n"\ "Toggle new messages of thread as read" #unsource: bind index noop or bindindex q query #unsource: bind index q quit :-) Thomas -- Thomas Hümmler * [EMAIL PROTECTED] * http://www.huemmler.de
Re: forground color of the indicator
On Feb 13, Marc Bruenink [[EMAIL PROTECTED]] wrote: > Is it possible to set the indicator foreground color to none? > I mark new, old mails with colors and so i don't want to let the > indicator change it. Currently there isn't, but Mike Schiraldi has a patch which is also in the CVS version that allows the indicator to just reverse the current colors on a message, which may be better for you than nothing. msg24479/pgp0.pgp Description: PGP signature
Re: forground color of the indicator
On Feb 13, Jeremy Blosser [[EMAIL PROTECTED]] wrote: > On Feb 13, Marc Bruenink [[EMAIL PROTECTED]] wrote: > > Is it possible to set the indicator foreground color to none? > > I mark new, old mails with colors and so i don't want to let the > > indicator change it. > > Currently there isn't, but Mike Schiraldi has a patch which is also in the > CVS version that allows the indicator to just reverse the current colors on > a message, which may be better for you than nothing. Ok, technically you could set $arrow_cursor, but this isn't really what you want I'm guessing. msg24480/pgp0.pgp Description: PGP signature
Re: Header Limitations
Quoting Alan Lue <[EMAIL PROTECTED]> [13 Feb-02 09:16]: > Better yet, does anyone know of a good way to send mass emails > without using a 3rd-party service? Why not just use a mailing list manager and set up a moderated list (so that none of the recipients can send to the list)? (darren) -- The awful thing about getting it right the first time is that nobody realizes how hard it was.
Re: forground color of the indicator
> Is it possible to set the indicator foreground color to none? > I mark new, old mails with colors and so i don't want to let the > indicator change it. The latest CVS version of mutt makes the default indicator (i.e. "mono indicator reverse") simply the reverse of whatever color the message would be if it were not currently selected. Or you can search the list archives for a message from me with an "indicator patch" attached. There's currently no way to just have the indicator set the foreground or just the background, but that sounds like a pretty good idea. We're working on redesigning mutt's color system, but it's rather difficult to come up with something that's simple in syntax yet powerful enough to do what you requested. Plus (hopefully) backwards-compatible. -- Mike Schiraldi VeriSign Applied Research msg24482/pgp0.pgp Description: PGP signature
Re: setting from on compose
Once upon a time darren chamberlain shaped the electrons to say... > Quoting Daniel Sully <[EMAIL PROTECTED]> [12 Feb-02 15:53]: > > [-- snip --] > > > How is this? > > OK, not to sound dense, but does one apply this diff? I get > diffs, how to create them, and am aware of patch, but just have > no first hand experience using diffs. write the diff out to a file, change to your mutt dir (i patched against 1.3.27) run: patch -p1 < askfrom.diff Recompile, etc. Add: 'set askfrom' to your .muttrc -D -- This is your life and it's ending one minute at a time.
Re: forground color of the indicator
And I heard Mike Schiraldi exclaim: > just the background, but that sounds like a pretty good idea. We're working > on redesigning mutt's color system, but it's rather difficult to come up > with something that's simple in syntax yet powerful enough to do what you > requested. Plus (hopefully) backwards-compatible. > -- > Mike Schiraldi I imagine this has already been thought of, but one option would be to simply let the mono attribute work on top of the color one. Then the desired behavior from this original posting could be to set the mono to none, and not specify the color attribute, of the indicator--which would be understood by mutt to mean 'leave the colors alone, but apply the color attribute "none" on top of that'. This would also allow using underlining to mark the indicator (which is something I had asked about in a previous post). Of course, that may not fit other situations--I don't know. And naturally, no complaints. Just an idea. Complaints should always be accompanied by patches, eh? --Daniel T.
Re: setting from on compose
Quoting Daniel Sully <[EMAIL PROTECTED]> [12 Feb-02 15:53]: [-- snip --] > How is this? OK, not to sound dense, but does one apply this diff? I get diffs, how to create them, and am aware of patch, but just have no first hand experience using diffs. (darren) -- The ultimate metric that I would like to propose for user friendliness is quite simple: if this system was a person, how long would it take before you punched it in the nose? -- Tom Carey
Re: Header Limitations
Alan Lue wrote: > Better yet, does anyone know of a good way to send > mass emails without using a 3rd-party service? You might look at smartlist+procmail. I run a mailing list out of my account using this software. However, to do it right you will either need an alias for the mail list, or the MTA needs to support the user+extra (sendmail style) or user-extra (qmail style) forms of addresses.
Re: forground color of the indicator
Daniel Farnsworth Teichert wrote: > I imagine this has already been thought of, but one option would be to simply > let the mono attribute work on top of the color one. Then the desired behavior > from this original posting could be to set the mono to none, and not specify > the color attribute, of the indicator--which would be understood by mutt to > mean 'leave the colors alone, but apply the color attribute "none" on top of > that'. I had the same thought at first, but I figure in the end this might cause more confusion than its worth. I worry we will get people complaining that they can't use different attributes for mono vs. color. Also, the way its implemented currently thsi would be difficult. If you have a color term, the mono commands are basically ignored because there is only one table for attributes.
Re: Header Limitations
You should use a mailing list manager, I think mailman is best IMHO because it's easy to set up, has an automatic web interface and archiving, and is used by RedHat and SourceForge. You can use an aliases file but then people who reply may end up sending an email to everyone via your server. :-( Simon. On Tue, Feb 12, 2002 at 03:04:19PM -0800, Alan Lue wrote: > Hi, > > I'm in charge of a student organization at my > university and am required to send weekly > newsletter-emails to near 1000 addresses. I've been > trying to use mutt to send these emails, but I can't > seem to fit all one thousand address on a single bcc: > line; only about 250 fit, and the rest just get > chopped off.
killing and scoring
Hi, I've just re-subscribed to this list!
I would like to use the same keystroke to add senders to my
procmail killfile and score them to 0 in mutt.
My setup (below) tells procmail to source the addresses in
~/.procmail/spam, and add the message to my spam/ Maildir:
#~/.procmailrc
FROM=`formail -xFrom: | sed -e 's/ *(.*)//; s/>.*//; s/.*[:<] *//'`
:0
* ? fgrep -qxis "$FROM" $HOME/.procmail/spam
{
LOG="Spam from $FROM"
:0:
spam/
}
I add to the killfile using :
#~/.muttrc
macro index "|grep "^From:" | grep -v lists.debian | grep -v uzscd5 | grep -v
berger.150 | grep -v andre.berger | sed -e 's/ *(.*)//; s/>.*//; s/.*[:<] *//' >>
$HOME/.procmail/spam && echo Add sender to killfile\n;d\n" "kill sender"
macro pager "|grep "^From:" | grep -v lists.debian | grep -v uzscd5 | grep -v
berger.150 | grep -v andre.berger | sed -e 's/ *(.*)//; s/>.*//; s/.*[:<] *//' >>
$HOME/.procmail/spam && echo Add sender to killfile\n;d\n" "kill sender"
Now, couldn't I extend the macro somehow to also add the sender to
~/.mutt.score, like
score '~f [EMAIL PROTECTED]' -
^^^sender
at the same time the address is added to ~/.procmail/spam?
-Andre
msg24489/pgp0.pgp
Description: PGP signature
Re: killing and scoring
On 2002.02.13, in <[EMAIL PROTECTED]>, "Andre Berger" <[EMAIL PROTECTED]> wrote: > > My setup (below) tells procmail to source the addresses in > ~/.procmail/spam, and add the message to my spam/ Maildir: Looks like you have a file (~/.procmail/spam) containing e-mail addresses of people you want to block. So... > Now, couldn't I extend the macro somehow to also add the sender to > ~/.mutt.score, like > > score '~f [EMAIL PROTECTED]' - > ^^^sender > > at the same time the address is added to ~/.procmail/spam? ... I'd create a script like this: $ cat muttscore.sh #!/bin/sh cat $HOME/.procmail/spam | while read addr; do echo "score '~f $addr' -" done ... and source that from your muttrc: source "muttscore.sh|" -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago Colons and slashes and dots, oh my!
Re: forwarding attachments (PLEASE READ before replying)
On Tue, Feb 12, 2002 at 10:22:34PM -0500, David T-G wrote: > ...and then Gary Johnson said... > % On Tue, Feb 12, 2002 at 05:46:09AM -0500, David T-G wrote: > % > % > Please help me clarify... Is it the case that $mime_forward does not > % > work at all for you, or simply that you do not want to forward the > % > message, with its attachments, in its own single attachment container? > % > % OK, let me try to explain this by an example. Someone sends me a > > I just wanted to make sure I understood the problem; lots of people > started pointing to $mime_forward when I didn't think that that was the > answer Aleks sought. I'm sorry if my tone was impolite. I was exasperated by the apparent need to explain again what I thought Aleks had already made clear. One reason for replying in such detail was that I wanted to be sure that I understood the problem myself before criticizing mutt's behavior, so I tried all the ways I knew of forwarding as I was writing the reply. I learned some stuff. > ... > % twice to select both parts of the message, then type ';f' to forward > % both parts. After answering "n" to "Forward MIME encapsulated? > % ([n]/y):", mutt starts my editor with the text/plain part already there. > > So you (or you in Aleks's shoes) want to be able to edit the text body as > though it were a reply. OK. I guess this is habit as much as anything else. Mutt's default forwarding behavior, as well as that of a lot of other mailers, judging from the mail I receive, is to include the original message in the new message's body. So that's what I've come to expect. > % in the message. Again great! This is exactly the behavior I want. But > % I want it as easily as I get the other forwarding behaviors, in one > % keystroke, maybe two. > > So $mime_forward and putting any prologue in your envelope isn't good > enough. Hey, if you want it, then that's fine. It seems useless to me > but that's why we have a configurable MUA :-) The $mime_forward behavior is OK, but it's not what I've been conditioned to expect when I forward a message. I would expect the basic behavior of forwarding to be consistent, whether or not I chose to include the original message's attachments. > I repeat that it's time for a feature patch, so one of you guys either > start coding one or find someone who will. I wasn't as frustrated with mutt not having the feature as I was with feeling that the feature wasn't being understood. Nevertheless, I suppose its time that I took a look at the code to see how difficult adding such a feature might be. Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Spokane, Washington, USA http://www.spocom.com/users/gjohnson/mutt/ |
Re: forground color of the indicator
On 09:41 13 Feb 2002, Michael Elkins <[EMAIL PROTECTED]> wrote: | Daniel Farnsworth Teichert wrote: | > I imagine this has already been thought of, but one option would be to simply | > let the mono attribute work on top of the color one. Then the desired behavior | > from this original posting could be to set the mono to none, and not specify | > the color attribute, of the indicator--which would be understood by mutt to | > mean 'leave the colors alone, but apply the color attribute "none" on top of | > that'. | | I had the same thought at first, but I figure in the end this might cause | more confusion than its worth. I worry we will get people complaining that | they can't use different attributes for mono vs. color. set mix_mono_color=yes ? -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ Don't put off for tomorrow what you can do today. If you enjoy it today, you can do it again tomorrow...
Re: killing and scoring
* David Champion <[EMAIL PROTECTED]>, 2002-02-13 14:11 -0500: > On 2002.02.13, in <[EMAIL PROTECTED]>, > "Andre Berger" <[EMAIL PROTECTED]> wrote: > > > > My setup (below) tells procmail to source the addresses in > > ~/.procmail/spam, and add the message to my spam/ Maildir: > > Looks like you have a file (~/.procmail/spam) containing e-mail > addresses of people you want to block. So... Right > > Now, couldn't I extend the macro somehow to also add the sender to > > ~/.mutt.score, like > > > > score '~f [EMAIL PROTECTED]' - > > ^^^sender > > > > at the same time the address is added to ~/.procmail/spam? > > ... I'd create a script like this: > $ cat muttscore.sh > #!/bin/sh > cat $HOME/.procmail/spam | while read addr; do > echo "score '~f $addr' -" > done > > ... and source that from your muttrc: > source "muttscore.sh|" Perfect! Thank you very much -Andre msg24493/pgp0.pgp Description: PGP signature
