Debian, Mutt, Eterm, Ncurses
Today I applied updates for my Debian box, running Sid, or unstable. So Ncurses was updated, and when running mutt in an Eterm, before I could get a transparent Eterm with mutt. But now mutt runs a standard looking black/white term. I guess this is because of the upgrade, so I recompiled mutt. Same issue. Is their a way to resolve this, other then go back to the previous ncurses version ? -- /Jason G Helfman "At any given moment, you may find the ticket to the circus that has always been in your possession." Fingerprint: 6A32 3774 E390 33B5 8C96 2AA1 2BF4 BD71 35A1 C149 GnuPG http://www.gnupg.org Get Private! 1024D/35A1C149
Changing subject line in received mail
Is there a simple way to change the subject line of an incoming message before saving it? It would be particularly useful to do this when saving the messages one gets when subscribing to mailing lists. I keep these in a single mailbox and because of the inconsistency of the subject lines used it's often quite hard to find the subscription details for a particular list. If I could just change the subject line before saving the message I could make my life much easier. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: Changing subject line in received mail
On Thu, Mar 08, 2001 at 09:37:25AM +, Chris Green wrote: : : Is there a simple way to change the subject line of an incoming : message before saving it? : : It would be particularly useful to do this when saving the messages : one gets when subscribing to mailing lists. I keep these in a single : mailbox and because of the inconsistency of the subject lines used : it's often quite hard to find the subscription details for a : particular list. If I could just change the subject line before : saving the message I could make my life much easier. For mailing lists, I usually add the mailing list address to my "subscribe" line and let 's' automatically save messages to a file usually named after the mailing list. -- Eugene Lee [EMAIL PROTECTED]
Re: Mutt as POP3 Cliient
On Wed, Mar 07, 2001 at 01:17:56PM -0600, Bill Andersen wrote: Sorry for such a basic question, but I don't want to get too involved in figuring out Mutt, if the answer to this quesstion is NO... If it is YES, I'll get some FAQs/Docs and do some reading before I ask any more questions... I was told that Mutt could be configured to run on the AIX box as a stand alone POP3 "client". In other words, configured to check my _ISP's_ POP3, thus elminiating the need for my AIX box to handle all the mail using sendmail and/or qmail, etc. You can set these up in muttrc: set pop_host=servername set pop_user=userid set pop_pass=password (only if you don't want to be prompted) Then you can use SHIFT-G to tell mutt to hit the pop server. The only problem is mutt is not a mail delivery agent. It has to pass the outgoing mail to some application. You also lose some mail parsing capability ( a la procmail ). -- David Rock [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- version 3.12 GIT$CS$ d-(?) s+:++: a- C++$ UL++ 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- PGP signature
Chaning the Return Address
I am using Debian Sid, with sendmail. I would like setup mutt so that the return address on my out going mail is my work email address and not the address on the machine. I tried looking around for how to do this and failed miserably. So any help would be invaluable... Thanks a Bunch -Geg-
Re: pipe command
Horace G. Friend III wrote: Hi, I already have the macros and when I execute them in X-Windows it automatically opens my Netscape viewer. Fine. Neat. But when I'm in Term and out of X-Windows, nothing happens. What should I do so that it opens Lynx, for instance. Thanks. Horace For me urlview works fine when I'm not in X. I took this straight out of my url_handler.sh for urlview # The lists of programs to be executed are https_prgs="/usr/bin/X11/netscape:PW" http_prgs="/usr/bin/X11/netscape:PW /usr/bin/lynx:XT" mailto_prgs="/usr/bin/mutt:VT /usr/bin/elm:VT /usr/bin/pine:VT /usr/bin/mail:VT" gopher_prgs="/usr/bin/gopher:XT /usr/bin/lynx:XT" ftp_prgs="/usr/bin/ncftp:XT /usr/bin/lynx:XT" If yours is different perhaps you could try my line, or perhaps check if you are on the most recent rpm/deb/src/whatever of urlview. -- Don't tell me I'm burning the candle at both ends -- tell me where to get more wax!! - Fingerprint : 869B 53DD 5E80 E1F0 93F6 9871 0508 0296 5957 F723 David Clarke [EMAIL PROTECTED] || [EMAIL PROTECTED] PGP signature
Re: Chaning the Return Address
John Averitt proclaimed on mutt-users that: I am using Debian Sid, with sendmail. I would like setup mutt so that the return address on my out going mail is my work email address and not the address on the machine. I tried looking around for how to do this and failed miserably. So any help would be invaluable... set envelope_from set use_from# always generate the `From:' header field my_hdr Reply-To: [EMAIL PROTECTED] (Suresh Ramasubramanian) my_hdr From: [EMAIL PROTECTED] (Suresh Ramasubramanian) -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
Re: Changing subject line in received mail
On Thu, Mar 08, 2001 at 01:51:20AM -0800, Eugene Lee wrote: On Thu, Mar 08, 2001 at 09:37:25AM +, Chris Green wrote: : : Is there a simple way to change the subject line of an incoming : message before saving it? : : It would be particularly useful to do this when saving the messages : one gets when subscribing to mailing lists. I keep these in a single : mailbox and because of the inconsistency of the subject lines used : it's often quite hard to find the subscription details for a : particular list. If I could just change the subject line before : saving the message I could make my life much easier. For mailing lists, I usually add the mailing list address to my "subscribe" line and let 's' automatically save messages to a file usually named after the mailing list. That doesn't really address my problem I don't think. I already have procmail set up to filter all my mailing list mail each to its own mailbox, that's not the problem. When I subscribe to a new mailing list I save the response(s) from the mailing list server into a mailbox called 'subscriptions' or some such. Then when I want to leave the list (or tell someone else how to subscribe/unsubscribe) I can go and look in my 'subscriptions' mail box to see how to do it. The problem is that the subject lines from the various different mailing list servers aren't consistent and many don't even have the name of the mailing list in them. Thus it isn't always easy looking at the index of my 'subscriptions' mailbox to see which message is the one I want. Even doing what you suggest won't help as 's' will save the message to a mailbox named after the From: line of the message from the mailing list server which I suspect will be just as inconsistent as the subject line is and won't always provide the mailing list name either. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: Debian, Mutt, Eterm, Ncurses
On Thu, 8 Mar 2001, Jason Helfman wrote: Today I applied updates for my Debian box, running Sid, or unstable. So Ncurses was updated, and when running mutt in an Eterm, before I could get a transparent Eterm with mutt. But now mutt runs a standard looking black/white term. I guess this is because of the upgrade, so I recompiled mutt. Same issue. Is their a way to resolve this, other then go back to the previous ncurses version ? what $TERM value are you using? (what does infocmp show, for instance). mutt is using that to decide if/how to display color. -- T.E.Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Re: Changing subject line in received mail
On Thu, Mar 08, 2001 at 09:50:17PM +1100, David wrote: Chris Green wrote: The problem is that the subject lines from the various different mailing list servers aren't consistent and many don't even have the name of the mailing list in them. Thus it isn't always easy looking at the index of my 'subscriptions' mailbox to see which message is the one I want. Even doing what you suggest won't help as 's' will save the message to a mailbox named after the From: line of the message from the mailing list server which I suspect will be just as inconsistent as the subject line is and won't always provide the mailing list name either. Perhaps you should write a procmail recipie to add the name of the mailing list to the subject it sounds like that would be the best solution for you. No, that won't help as I only want to do this on the one or two messages that come from the E-Mail request server not to messages that come from the list itself. Writing a procmail recipe to modify just one or two messages seems a little like overkill to me. I definitely don't want the name of the mailing list in the subject of normal messages from the mailing list as I already know which list they're from because they have been routed to a specific mailbox by procmail. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: Changing subject line in received mail
Chris Green wrote: The problem is that the subject lines from the various different mailing list servers aren't consistent and many don't even have the name of the mailing list in them. Thus it isn't always easy looking at the index of my 'subscriptions' mailbox to see which message is the one I want. Even doing what you suggest won't help as 's' will save the message to a mailbox named after the From: line of the message from the mailing list server which I suspect will be just as inconsistent as the subject line is and won't always provide the mailing list name either. Perhaps you should write a procmail recipie to add the name of the mailing list to the subject it sounds like that would be the best solution for you. -- Don't tell me I'm burning the candle at both ends -- tell me where to get more wax!! - Fingerprint : 869B 53DD 5E80 E1F0 93F6 9871 0508 0296 5957 F723 David Clarke [EMAIL PROTECTED] || [EMAIL PROTECTED] PGP signature
Re: Changing subject line in received mail
Maybe I'm a moron, but isn't what you want just to hit "e" when in the index, and then edit your message in the editor? Jesper -- "But how can one be warm alone?" Jesper Holmberg [EMAIL PROTECTED]
Re: Changing subject line in received mail
On Thu, Mar 08, 2001 at 11:15:10AM +, Chris Green wrote: : On Thu, Mar 08, 2001 at 09:50:17PM +1100, David wrote: : Chris Green wrote: : The problem is that the subject lines from the various different : mailing list servers aren't consistent and many don't even have the : name of the mailing list in them. Thus it isn't always easy looking : at the index of my 'subscriptions' mailbox to see which message is : the one I want. : : Even doing what you suggest won't help as 's' will save the message : to a mailbox named after the From: line of the message from the : mailing list server which I suspect will be just as inconsistent as : the subject line is and won't always provide the mailing list name : either. : : Perhaps you should write a procmail recipie to add the name of the : mailing list to the subject it sounds like that would be the best : solution for you. : : No, that won't help as I only want to do this on the one or two : messages that come from the E-Mail request server not to messages : that come from the list itself. Writing a procmail recipe to modify : just one or two messages seems a little like overkill to me. At the same time, trying to write a Mutt save-hook to save just one or two messages seems a little like overkill to me, too. :-) : I definitely don't want the name of the mailing list in the subject : of normal messages from the mailing list as I already know which list : they're from because they have been routed to a specific mailbox by : procmail. Based on the same observations you made above, that "subject lines from the various different mailing list servers aren't consistent", I prefer to add the mailing list email address to Mutt's "subscribe" setting and let Mutt come up with an appropriate mailbox filename. I then manually save messages from the mailing list server software to the same mailbox. -- Eugene Lee [EMAIL PROTECTED]
Re: Changing subject line in received mail
On Thu, Mar 08, 2001 at 01:02:09PM +0100, Jesper Holmberg wrote: Maybe I'm a moron, but isn't what you want just to hit "e" when in the index, and then edit your message in the editor? No, you're not a moron, that's pretty much what I need - thanks! -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: Changing subject line in received mail
On Thu, Mar 08, 2001 at 04:04:19AM -0800, Eugene Lee wrote: : I definitely don't want the name of the mailing list in the subject : of normal messages from the mailing list as I already know which list : they're from because they have been routed to a specific mailbox by : procmail. Based on the same observations you made above, that "subject lines from the various different mailing list servers aren't consistent", I prefer to add the mailing list email address to Mutt's "subscribe" setting and let Mutt come up with an appropriate mailbox filename. I then manually save messages from the mailing list server software to the same mailbox. OK, that would work. However my procmail destination mailboxes are not in my main mail saving hierarchy and I don't keep any mail in them, they are 'normally empty'. Thus putting the subscription stuff in there wouldn't fit my way of working too well. Using 'e' as suggested elsewhere in this thread is near enough to what I need. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: Help, cant send with mutt
On Mon, 05 Mar 2001, Suresh Ramasubramanian wrote: Dave Murray proclaimed on mutt-users that: I was able to set up the pop3 for my ISP's mail server and receive mail with mutt just fine. Now how do I set up sendmail for smtp to my ISP mail server? http://www.hserus.net/dlhowto.html [opps, sent it to Suresh instead of the list the 1st time] Thank you, I'm still stymied. 1. I removed and reinstalled sendmail from the .rpm, edited the .mc (best as I could), still didn't work. 2. I downloaded the latest tarball and compiled it, still doesn't work (but showed improvement, I'm becoming less enchanted with rpm with every attempt to use it). I can use mutt locally (mail from [EMAIL PROTECTED] to [EMAIL PROTECTED], etc.) I just can't figure out how to make it use my ISP's smtp address, and work. The verbose script says that it is using my ISP's smtp, but all outgoing mail goes to deadletter :0( I can read the mail just fine, pop3 works OK. This seems to be a sendmail configuration problem, as opposed to a mutt problem. Any suggestions on where to go for help with this? Regards and peace, Dave
nntp questions
I do my News with the nntp-patched mutt and the NNTP perl script by Waldemar Brodkorb, and have two questions. First, I want to use scoring. Is it possible to define an index-format command that applies on Newsgroups only? (Should be a regexp.) I dislike to see scores in my mail index... Second, can I mail my own Postings Bcc to myself automatically? Andre Berger[[EMAIL PROTECTED]]
Re: Help, cant send with mutt
Barry Mitchelson proclaimed on mutt-users that: I recently discovered a little script called install-sendmail, which helped me set up sendmail for use with mutt in a few minutes. That's Donncha O'Caoimh's script which can be found at http://cork.linux.ie you can download it from : http://members.nbci.com/xeer/index.html -s -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
Re: Changing subject line in received mail
On Thu, Mar 08, 2001 at 12:11:04PM +, Chris Green wrote: On Thu, Mar 08, 2001 at 01:02:09PM +0100, Jesper Holmberg wrote: Maybe I'm a moron, but isn't what you want just to hit "e" when in the index, and then edit your message in the editor? No, you're not a moron, that's pretty much what I need - thanks! I use a simple editor mapping to insert "[]" at the beginning of the subject and leave me in insert mode within the "[..]". E.g., for vim: map \S G/^Subject: CR:nohlsCREa []Esci -- Bill Brelsford [EMAIL PROTECTED]
Re: Changing subject line in received mail
On Thu, Mar 08, 2001 at 08:09:16AM -0700, W M Brelsford wrote: On Thu, Mar 08, 2001 at 12:11:04PM +, Chris Green wrote: On Thu, Mar 08, 2001 at 01:02:09PM +0100, Jesper Holmberg wrote: Maybe I'm a moron, but isn't what you want just to hit "e" when in the index, and then edit your message in the editor? No, you're not a moron, that's pretty much what I need - thanks! I use a simple editor mapping to insert "[]" at the beginning of the subject and leave me in insert mode within the "[..]". E.g., for vim: map \S G/^Subject: CR:nohlsCREa []Esci I was wondering whether to get that clever but for the number of times I need it I doubt if it's worth it really - apart from the "isn't that clever" apect of it of course. :-) -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: Debian, Mutt, Eterm, Ncurses
Well the term is xterm. I have tried to export vt100 and linux, but I am getting the same issue. When I compose a message, though, the window is transparent. I am confused. On Thu, Mar 08, 2001 at 05:56:24AM -0500, Thomas E. Dickey muttered: | On Thu, 8 Mar 2001, Jason Helfman wrote: | | Today I applied updates for my Debian box, running Sid, or unstable. So | Ncurses was updated, and when running mutt in an Eterm, before I could | get a transparent Eterm with mutt. But now mutt runs a standard looking | black/white term. I guess this is because of the upgrade, so I | recompiled mutt. Same issue. Is their a way to resolve this, other then | go back to the previous ncurses version ? | | what $TERM value are you using? | (what does infocmp show, for instance). | mutt is using that to decide if/how to display color. | | -- | T.E.Dickey [EMAIL PROTECTED] | http://dickey.his.com | ftp://dickey.his.com | -- /Jason G Helfman "At any given moment, you may find the ticket to the circus that has always been in your possession." Fingerprint: 6A32 3774 E390 33B5 8C96 2AA1 2BF4 BD71 35A1 C149 GnuPG http://www.gnupg.org Get Private! 1024D/35A1C149
sending attachments
Hi- I'm having problems sending attachments to non mutt users. It appears to be stemming from their not being able to recognize the boundaries between attachments (I've noticed that other mailers use a "boundary" variable, and my mutt is adding an asterisk to this.) I'd really appreciate any help on this. Tony Mullen
Re: Debian, Mutt, Eterm, Ncurses
On Thu, 8 Mar 2001, Jason Helfman wrote: Well the term is xterm. Eterm has its own terminfo, which differs from "xterm". (The 'bce' and 'op' strings in particular are what the screen library looks at in the terminfo to decide if it can use "default" colors). I have tried to export vt100 and linux, but I am getting the same issue. When I compose a message, though, the window is transparent. I am confused. On Thu, Mar 08, 2001 at 05:56:24AM -0500, Thomas E. Dickey muttered: | On Thu, 8 Mar 2001, Jason Helfman wrote: | | Today I applied updates for my Debian box, running Sid, or unstable. So | Ncurses was updated, and when running mutt in an Eterm, before I could | get a transparent Eterm with mutt. But now mutt runs a standard looking | black/white term. I guess this is because of the upgrade, so I | recompiled mutt. Same issue. Is their a way to resolve this, other then | go back to the previous ncurses version ? | | what $TERM value are you using? | (what does infocmp show, for instance). | mutt is using that to decide if/how to display color. | | -- | T.E.Dickey [EMAIL PROTECTED] | http://dickey.his.com | ftp://dickey.his.com | -- T.E.Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
send-hooks and save_name
Hi, I'm having trouble figuring out how to change the behavior of mutt's save_name feature. What I'm trying to do is to get mutt to do the save_name thing, except instead of having it save in =username, I want it to save in =work/username if any recipient's address contains "concordia.ca", and in =personal/username if no recipient's address contains "concordia.ca". I tried playing with changing the value of "folder" with a send-hook, but since it doesn't reset immediately after, it mungs up normal operations (since I still want "folder" to just be "~/mail/"). Is there a straightforward way to do such a thing? -Rich -- -- Rich Lafferty --- Sysadmin/Programmer, Instructional and Information Technology Services Concordia University, Montreal, QC (514) 848-7625 - [EMAIL PROTECTED] --
Re: send-hooks and save_name
On Thu, Mar 08, 2001 at 11:02:03AM -0500, Rich Lafferty wrote: I tried playing with changing the value of "folder" with a send-hook, but since it doesn't reset immediately after, it mungs up normal operations (since I still want "folder" to just be "~/mail/"). Is there a straightforward way to do such a thing? If your send-hooks work except for the resetting problem, the solution is easy. Just add the following lint to your muttrc _above_ the other send-hooks so that it will be executed before the others. send-hook . 'set folder=~/Mail' Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | RF Communications PGU http://www.spocom.com/users/gjohnson/mutt/ | Spokane, Washington, USA
Re: sending attachments
On Thu 08-Mar-2001 at 04:23:35PM +0100, Mullen A.J. wrote: I'm having problems sending attachments to non mutt users. It appears to be stemming from their not being able to recognize the boundaries between attachments (I've noticed that other mailers use a "boundary" variable, and my mutt is adding an asterisk to this.) You need to give some examples. Your Content-Type header is a bit of a mess as well: Content-Type: text/plain; charset*=ascii''ascii Bruno -- http://bruno.postle.net/
Re: send-hooks and save_name
On Thu, Mar 08, 2001 at 08:14:49AM -0800, Gary Johnson ([EMAIL PROTECTED]) wrote: On Thu, Mar 08, 2001 at 11:02:03AM -0500, Rich Lafferty wrote: I tried playing with changing the value of "folder" with a send-hook, but since it doesn't reset immediately after, it mungs up normal operations (since I still want "folder" to just be "~/mail/"). Is there a straightforward way to do such a thing? If your send-hooks work except for the resetting problem, the solution is easy. Just add the following lint to your muttrc _above_ the other send-hooks so that it will be executed before the others. send-hook . 'set folder=~/Mail' Well, with that I end up with send-hook . 'set folder=~/Mail' send-hook concordia.ca 'set folder=~/Mail/conu' send-hook !concordia.ca 'set folder=~/Mail/personal' and, as you can see, that first condition never happens. :-) But this helped me realize what the problem is -- with your default send-hook, it resets "folder" as soon as I go to *send* again. What I need is for "folder" to be set as I go to send, and to be reset to "~/Mail/" as soon as the message I'm sending is on its way. Hrm. This gets me very close: folder-hook . 'set folder=~/mail' send-hook concordia.ca 'set folder=~/mail/conu' send-hook !concordia.ca 'set folder=~/mail/personal' except that going from the send screen to the index doesn't trigger a folder-hook. (That'd be handy if it did, though, wishlist folks.) I'm beginning to think that there *is* no hook that takes place after a message is sent, so I can't think of any way to improve on the above. -Rich -- -- Rich Lafferty --- Sysadmin/Programmer, Instructional and Information Technology Services Concordia University, Montreal, QC (514) 848-7625 - [EMAIL PROTECTED] --
Re: send-hooks and save_name
On Thu, Mar 08, 2001 at 11:29:23AM -0500, Rich Lafferty wrote: folder-hook . 'set folder=~/mail' send-hook concordia.ca 'set folder=~/mail/conu' send-hook !concordia.ca 'set folder=~/mail/personal' how about: send-hook . 'set folder=~/mail/personal' send-hook concordia.ca 'set folder=~/mail/conu' Peter -- Peter D. Kovacs [EMAIL PROTECTED] Software Developer Webmachines, Inc. http://webmachines.com
Re: send-hooks and save_name
On Thu, Mar 08, 2001 at 11:47:00AM -0500, Peter Kovacs ([EMAIL PROTECTED]) wrote: On Thu, Mar 08, 2001 at 11:29:23AM -0500, Rich Lafferty wrote: folder-hook . 'set folder=~/mail' send-hook concordia.ca 'set folder=~/mail/conu' send-hook !concordia.ca 'set folder=~/mail/personal' how about: send-hook . 'set folder=~/mail/personal' send-hook concordia.ca 'set folder=~/mail/conu' I think I'm actually going to have to just actively set Fcc as I go. The problem with your suggestion is that with that the folder is *never* reset to ~/mail, and I've a lot more subdirectories than just conu/ and personal/ (it's just that those two are the only ones I'd want mail *automagically* saved into). -Rich -- -- Rich Lafferty --- Sysadmin/Programmer, Instructional and Information Technology Services Concordia University, Montreal, QC (514) 848-7625 - [EMAIL PROTECTED] --
Re: send-hooks and save_name
How about using Procmail rules to put your mail where you like? * Rich Lafferty ([EMAIL PROTECTED]) [010308 08:56]: =On Thu, Mar 08, 2001 at 11:47:00AM -0500, Peter Kovacs ([EMAIL PROTECTED]) wrote: = On Thu, Mar 08, 2001 at 11:29:23AM -0500, Rich Lafferty wrote: =folder-hook . 'set folder=~/mail' =send-hook concordia.ca 'set folder=~/mail/conu' =send-hook !concordia.ca 'set folder=~/mail/personal' = = how about: = send-hook . 'set folder=~/mail/personal' = send-hook concordia.ca 'set folder=~/mail/conu' = =I think I'm actually going to have to just actively set Fcc as I =go. The problem with your suggestion is that with that the folder is =*never* reset to ~/mail, and I've a lot more subdirectories than just =conu/ and personal/ (it's just that those two are the only ones I'd =want mail *automagically* saved into). = -- Ben Rosenberg mailto:[EMAIL PROTECTED] - If two men agree on everything, you can be sure that only one of them is doing the thinking.
Re: send-hooks and save_name
On Thu, Mar 08, 2001 at 11:29:23AM -0500, Rich Lafferty wrote: Well, with that I end up with send-hook . 'set folder=~/Mail' send-hook concordia.ca 'set folder=~/Mail/conu' send-hook !concordia.ca 'set folder=~/Mail/personal' and, as you can see, that first condition never happens. :-) But this helped me realize what the problem is -- with your default send-hook, it resets "folder" as soon as I go to *send* again. What I need is for "folder" to be set as I go to send, and to be reset to "~/Mail/" as I'm beginning to think that there *is* no hook that takes place after a message is sent, so I can't think of any way to improve on the above. OK, now I think I understand the problem. I can't think of any hooks that work the way you want, either. I did think of something else that might work, though. macro compose y "send-message:push :set folder=~/Mail" I have not tried that to see if it actually works. One problem with this approach is that you really need to create such macros for every command that leaves the compose menu, such as 'q' and 'P', and such a macro for 'q' would not work if 'postpone' was set to 'ask-yes' or 'ask-no'. Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | RF Communications PGU http://www.spocom.com/users/gjohnson/mutt/ | Spokane, Washington, USA
Re: Debian, Mutt, Eterm, Ncurses
So where would I go from this point? I have no issues with investigating, but if you could point me in the right direction, that could be cool. On Thu, Mar 08, 2001 at 10:51:56AM -0500, Thomas E. Dickey muttered: | On Thu, 8 Mar 2001, Jason Helfman wrote: | | Well the term is xterm. | | Eterm has its own terminfo, which differs from "xterm". (The 'bce' and | 'op' strings in particular are what the screen library looks at in the | terminfo to decide if it can use "default" colors). | | | I have tried to export vt100 and linux, but I am getting the same issue. | When I compose a message, though, the window is transparent. I am | confused. | | On Thu, Mar 08, 2001 at 05:56:24AM -0500, Thomas E. Dickey muttered: | | On Thu, 8 Mar 2001, Jason Helfman wrote: | | | | Today I applied updates for my Debian box, running Sid, or unstable. So | | Ncurses was updated, and when running mutt in an Eterm, before I could | | get a transparent Eterm with mutt. But now mutt runs a standard looking | | black/white term. I guess this is because of the upgrade, so I | | recompiled mutt. Same issue. Is their a way to resolve this, other then | | go back to the previous ncurses version ? | | | | what $TERM value are you using? | | (what does infocmp show, for instance). | | mutt is using that to decide if/how to display color. | | | | -- | | T.E.Dickey [EMAIL PROTECTED] | | http://dickey.his.com | | ftp://dickey.his.com | | | | | | -- | T.E.Dickey [EMAIL PROTECTED] | http://dickey.his.com | ftp://dickey.his.com | -- /Jason G Helfman "At any given moment, you may find the ticket to the circus that has always been in your possession." Fingerprint: 6A32 3774 E390 33B5 8C96 2AA1 2BF4 BD71 35A1 C149 GnuPG http://www.gnupg.org Get Private! 1024D/35A1C149
Re: sending attachments
On Thu 08-Mar-2001 at 05:42:11PM +0100, Mullen A.J. wrote: Here's an example of the full header and boundaries I'm sending which is not being properly decoded by other mailers (although it is by other mutt users). From [EMAIL PROTECTED] Thu Mar 8 15:20:13 2001 Date: Thu, 8 Mar 2001 15:20:13 +0100 From: "Mullen A.J." [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: att Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary*="ascii''0lnxQi9hkpPO77W3" Content-Disposition: inline User-Agent: Mutt/1.3.8i Status: RO Content-Length: 175926 Lines: 2879 --0lnxQi9hkpPO77W3 Content-Type: text/plain; charset*=ascii''ascii Content-Disposition: inline msg txt --0lnxQi9hkpPO77W3 Content-Type: application/postscript Content-Disposition: attachment; filename*=ascii''braustac%2Eps %!PS-Adobe-2.0 %%Creator: dvips(k) 5.85 Copyright 1999 Radical Eye Software et cetera... It is messed-up, I don't know why :-) Bruno -- http://bruno.postle.net/
sending attachments
To elaborate on my earlier question about including attachments, the following is what I'm sending out. This is the raw text of the mail. When Mutt receives this, it's able to parse it without a problem and treat the attachments and text appropriately. When other mailers (so far tried with emacs and hotmail, among others) they fail. Thanks, T Mullen From [EMAIL PROTECTED] Thu Mar 8 15:20:13 2001 Date: Thu, 8 Mar 2001 15:20:13 +0100 From: "Mullen A.J." [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: att Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary*="ascii''0lnxQi9hkpPO77W3" Content-Disposition: inline User-Agent: Mutt/1.3.8i Status: RO Content-Length: 175926 Lines: 2879 --0lnxQi9hkpPO77W3 Content-Type: text/plain; charset*=ascii''ascii Content-Disposition: inline msg txt --0lnxQi9hkpPO77W3 Content-Type: application/postscript Content-Disposition: attachment; filename*=ascii''braustac%2Eps %!PS-Adobe-2.0 %%Creator: dvips(k) 5.85 Copyright 1999 Radical Eye Software et cetera...
Re: sending attachments
Mullen A.J. writes: To elaborate on my earlier question about including attachments, the following is what I'm sending out. This is the raw text of the mail. When Mutt receives this, it's able to parse it without a problem and treat the attachments and text appropriately. When other mailers (so far tried with emacs and hotmail, among others) they fail. You are running mutt-1.3.8, right? Then you should post to mutt-dev, not mutt-users. 1.3.8 is ultimately outdated. I'd recommend to upgrade to the latest devel version 1.3.16 (or use 1.2.5, the latest stable release). The problem you observe was fixed in mutt-1.3.9. 1.3.8's handling of character set conversion (iconv) was broken. I had a very similar problem with 1.3.8 on Solaris.
Re: Line length using EDITOR=emacs
On 03/08/01, 09:42:49AM +1100, Robert Martinovic wrote: Hello, I know that there are mutt users using emacs as their editor. I would like to know how to set line length at 72 chars in my .emacs It infuriates many to have messages longer that 72 chars to a line One can use post.el v.1.6.3.10. This sets up post mode for mail and news when emacs is invoked. Once that has been done one can set up a line length peculiar to mail messages. For example: ;; -- ;; Set fill to 65 (default) columns post-mode, but 70 in ;; text/related modes (defun my-post-mode-setup () (setq fill-column 65)) (add-hook 'post-mode-hook 'my-post-mode-setup) (defun my-text-mode-setup () (setq fill-column 70)) (add-hook 'text-mode-hook 'my-text-mode-setup) ;; -- Hope this helps. Many regards, Richard Mahoney -- Richard Mahoney - 78 Jeffreys Rd +64-3-351-5831 Christchurch New Zealand --- mailto:[EMAIL PROTECTED]
mutt 1.3.16i build problem
i have been trying to build mutt 1.3.16 on my machine (RH 7.0) and when i run ./configure i get the following error message: sed: can't read ./doc/instdoc.sh.in: no such file or directory can anyone help. marcelo martinelli.
Re: mutt 1.3.16i build problem
Marcelo Martinelli writes: i have been trying to build mutt 1.3.16 on my machine (RH 7.0) and when i run ./configure i get the following error message: sed: can't read ./doc/instdoc.sh.in: no such file or directory can anyone help. http://groups.yahoo.com/group/mutt-dev/message/10239
Re: mutt 1.3.16i build problem
On Thu, Mar 08, 2001 at 08:14:39PM +, Lars Hecking wrote: Marcelo Martinelli writes: i have been trying to build mutt 1.3.16 on my machine (RH 7.0) and when i run ./configure i get the following error message: sed: can't read ./doc/instdoc.sh.in: no such file or directory can anyone help. http://groups.yahoo.com/group/mutt-dev/message/10239 it worked fine. thanks!
Re: Debian, Mutt, Eterm, Ncurses
Jason Helfman [[EMAIL PROTECTED]] wrote: Well the term is xterm. Try xterm-color. When I compose a message, though, the window is transparent. I am confused. Mutt tends to be fairly picky about what capabilities it believes the terminal has, your editor is apparently not so picky. -- Jeremy Blosser | [EMAIL PROTECTED] | http://jblosser.firinn.org/ -+-+-- the crises posed a question / just beneath the skin the virtue in my veins replied / that quitters never win
Re: Pager binding to advance to next-new in thread
Christian R Molls muttered: is it possible to make the tab key advance to the next-new message in the current thread, if any, and return to the index if the last new message in the current thread has been reached? AFAICS no. Mutt isn't capabale of conditioned executions ie. there's not "if" construct. HTH, Michael -- "We all know Linux is great...it does infinite loops in 5 seconds." (Linus Torvalds about the superiority of Linux on the Amterdam Linux Symposium) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: Pager binding to advance to next-new in thread
On 03/08, Michael Tatge rearranged the electrons to read: Christian R Molls muttered: is it possible to make the tab key advance to the next-new message in the current thread, if any, and return to the index if the last new message in the current thread has been reached? AFAICS no. Mutt isn't capabale of conditioned executions ie. there's not "if" construct. Maybe this isn't what he's looking for, but I have Tab bound to next-new, and when it reaches the end of new messages (not only in a single thread, just overall) it returns to the index. bind pager \t next-unread
mutt_dotlock problems
Hi All, Can anyone explain how mutt_dotlock works and where its settings are kept. Mutt tries to write to my outbox and tries to dotlock a file named "outbox." in the same directory. It cant (for some reason I cant quite see). But can I change the place it tries to write the lock file to instead? /usr/local/bin/mutt_dotlock is uid:root and gid:mail So it should be able to write to my home directory, but who knows sometimes (nfs, nis setups)! Thanks for any help, -- Murray Maxwell Dancey, [EMAIL PROTECTED] icq. 106790920
Re: Help, cant send with mutt
Dave Murray proclaimed on mutt-users that: Thanks for the help. After lot's of stuff. Fixed DNS, ran install-sendmail script, ... I've got it to where when I send this, it won't actualy go. Repeat, gets same result, then repeat again gives [ OK ][ OK ] Then the mail gets sent! I'm getting close, any ideas? Something flaky with your sendmail install / the system's under very high memory load because of something. Reinstall sendmail (preferably compiling it). And next time, use # kill -HUP `head -n1 /var/run/sendmail.pid` to restart sendmail. [tip thanks to Per Hadeland on comp.mail.sendmail] -s -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin