Re: Text substitution
On Thu, Jan 20, 2000 at 14:07:36 -0500, Jon Walthour wrote: > The problem is that I can't send mail to others internally. > Here's why: they have no DNS entry for their POP3 server, just > an IP address. So, if I sendmail to [EMAIL PROTECTED], it > disappears; if I send it to [EMAIL PROTECTED], it works. > Like I said, strange. > > My question is this: Is it possible to set up an alias or a rule > in mutt such that every time I respond to an internal email from > Joe Blow with a return address of [EMAIL PROTECTED], it > automatically changes it to [EMAIL PROTECTED]? No. But your MTA may have such a function. > If anyone has any ideas, I'm all ears because this is driving me > crazy!! I would put a line like 198.203.127.3 cpsboe.k12.oh.us in my local /etc/hosts file (or ask the system administrator to do it). Many systems search this file before trying a DNS lookup, but it is a matter of configuration and it is system dependent. -- Byrial
Colour loss when running via an exec command...
Hi, folks, I've got a problem that I can't seem to figure out and was wondering if anyone had any input. What I'm basically hoping to be able to do is, in Xwindows, have an option for mutt in my menu that looks like this: Eterm --trans --shade "40%" -T Mutt -n "Electronic Mail" -e mutt Basically, just click the menu and have mutt open up in an Eterm with my transparency preferences, rather than having to open an Eterm and type mutt. (Oh, I'm so lazy!) What happens, though, is that mutt defaults to a monochrome colour scheme when I open it via an exec like that. (It does the same for rxvt terms, etc., as well.) Does anyone know how to get around this? It's rather annoying. Any suggestions would be greatly appreciated. - Jamie
Re: Colour loss when running via an exec command...
At 3:11 PM EST on January 20 Jamie Novak sent off: > Eterm --trans --shade "40%" -T Mutt -n "Electronic Mail" -e mutt > What happens, though, is that mutt defaults to a monochrome colour > scheme when I open it via an exec like that. (It does the same for rxvt > terms, etc., as well.) I do something similar and never had any problems. Are you running in 8 bit color and running out of colors, perhaps? If not, try compiling with SLang and setting COLORTERM and COLORFGBG. -- Do they sterilize the needles for lethal injections? - Jack Handey Robert I. Reid <[EMAIL PROTECTED]> http://astro.utoronto.ca/~reid/ PGP Key: http://astro.utoronto.ca/~reid/pgp.html
ansi colors without X
I have the latest version of Mutt on my FreeBSD 3.3 system. It works fine, except that color support doesn't seem to work. I don't have X on the system. But I continue to get these messages: Error in /usr/home/eugene/.muttrc, line 2: default: no such color Error in /usr/home/eugene/.muttrc, line 3: default: no such color Error in /usr/home/eugene/.muttrc, line 4: default: no such color The offending lines in my .muttrc are: color quoted green default color hdrdefault blue default color header magenta default ^(Subject|To|Date|From): Here's the pertinent verbose info: Mutt 1.0.1i (2000-01-18) Copyright (C) 1996-2000 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: FreeBSD 3.3-RELEASE [using ncurses 1.8.6/ache] Compile options: -DOMAIN -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" ISPELL="/usr/local/bin/ispell" To contact the developers, please mail to <[EMAIL PROTECTED]>. Am I just missing something obvious? -- Eugene Lee [EMAIL PROTECTED]
Re: ansi colors without X
On 20-Jan-2000, Eugene Lee wrote: > Error in /usr/home/eugene/.muttrc, line 2: default: no such color > color quoted green default > System: FreeBSD 3.3-RELEASE [using ncurses 1.8.6/ache] Please correct me if I'm wrong, I think you need to compile aginst the S-Lang library to use default, you can't use [n]curses. -- Ronny Haryanto
Re: ansi colors without X
On 03:05 PM 1/20/2000 , Eugene Lee wrote: >I have the latest version of Mutt on my FreeBSD 3.3 system. It works >fine, except that color support doesn't seem to work. I don't have X >on the system. But I continue to get these messages: > > Error in /usr/home/eugene/.muttrc, line 2: default: no such color > Error in /usr/home/eugene/.muttrc, line 3: default: no such color > Error in /usr/home/eugene/.muttrc, line 4: default: no such color > >The offending lines in my .muttrc are: > > color quoted green default > color hdrdefault blue default > color header magenta default ^(Subject|To|Date|From): > >Here's the pertinent verbose info: > > Mutt 1.0.1i (2000-01-18) > Copyright (C) 1996-2000 Michael R. Elkins and others. > Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. > Mutt is free software, and you are welcome to redistribute it > under certain conditions; type `mutt -vv' for details. > > System: FreeBSD 3.3-RELEASE [using ncurses 1.8.6/ache] Hi, This is a guess, since I've never used FreeBSD 3.3, but maybe your version of ncurses is too old. I'm not too sure what version of ncurses that the default color stuff first appeared. Try changing the default to an actual color in the 3 lines in your .muttrc and see if the errors go away. -Harold -- "Life sucks, deal with it!"
Re: ansi colors without X
Ronny Haryanto <[EMAIL PROTECTED]> wrote: > > Please correct me if I'm wrong You're wrong. ;) > I think you need to compile aginst the S-Lang library to use default, > you can't use [n]curses. The latest versions of ncurses do allow the use of the color "default", and Mutt will work with this. So upgrading to Slang or upgrading ncurses will do the trick. -- 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
sorry
My apologies for the double posting of the same question ; I thought one of them hadn't gone through. Thanks for all the replys. -- Bram Shirani <[EMAIL PROTECTED]> "UNIX *is* user-friendly, it's just selective of it's friends."
Re: Colour loss when running via an exec command...
Jamie Novak <[EMAIL PROTECTED]> wrote on Thu, 20 Jan 2000: > What happens, though, is that mutt defaults to a monochrome colour > scheme when I open it via an exec like that. (It does the same for rxvt > terms, etc., as well.) But it doesn't when you start it up in another Eterm? I'm guessing that the problem is that some environment variables or something like that are set different for the Eterm you start using that "email" button/menu option, as compared to when you start a "regular Eterm". Check out the environments... You may need a wrapper shell script or something like that. 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 / "I don't suffer from insanity, I enjoy every minute of it."
Re: folder-hooks, (un)ignore, and From_
On Thu, Jan 20, 2000 at 15:01:56 +0100, Byrial Jensen wrote: > > Except "unignore *" that just removes "*" from the ignore list > if it is there, and else does nothing -- it doesn't remove all > tokens from the ignore list as the manual says. Ups, in fact it does. And "ignore *" removes all tokens from the unignore list. Sorry for the confusion. -- Byrial
can't filter sent emails to sent box
I am very new to mutt, and by emailing back and forth with fellow mutt users, documentation and the like, I am unable to figure out -- based on my .muttrc file --- why email I send out want to go to the record of the name it is sent to...for instance, if i send an email to [EMAIL PROTECTED] mutt will want to create a mailbox for whatever...if I don't create the box, mail isn't sent I have specified in my muttrc file to, can't recall the syntax..i'm attaching the file itself, something to the extent of "set record=+sent" I would just like all sent email to be Fcc'd to sent, that is all, I am sure I am going to have this down pat in a few months, and hopefully I can help out other new mutters... thanks /jgh
forgot to attach the file
Reply-To:
see attached, regarding what I just sent, i did see that when I invoke
"mutt " it goes to fcc sent, however if I invoke mail
inside of mutt, it will want to go elsewhere...I'm sure this is due to a
.muttrc file that wasn't mine. Got it from the document maintainer.
##
## File:$HOME/.muttrc
## Purpose: Setup file for the Mail program "Mutt"
## I am using mutt-1.1.1i now
## which lists 195 configuration variables.
## Last update: Wed Nov 24 12:00:00 MET 1999
## Author: Sven Guckes [EMAIL PROTECTED]
## Availability: This file is available as
## http://www.math.fu-berlin.de/~guckes/mutt/muttrc>
##
## If you read this then please let me know how you like it!
## Send me an email at [EMAIL PROTECTED] - thanks! :-)
##
## Additional Info:
## Sven's pages: http://www.math.fu-berlin.de/~guckes/mutt/
## Current manual: http://www.math.fu-berlin.de/~guckes/mutt/doc/manual.txt
## News/Usenet:comp.mail.mutt (since 980401)
##
## This is new - and you should know about it:
set ignore_list_reply_to # ignore the "Reply-To" lines
# which point back to the mailing list - YES!
## FAQ: Startup mutt with collapsed threads:
## folder-hook . exec collapse-all
## TO show the number of messages in a collapsed thread
## you need to add "%M" to the "index_format", eg:
## set index_format="%4C %Z %2M %[!%y%m%d] %-17.17F (%3l) %s"
## NOTE: Please read the comment about "source" at the end of this file!
##
## VARIABLES :
## See http://www.math.fu-berlin.de/~guckes/mutt/mutt.manual.html#variables
## All variables are described with their type, the version number of MUTT
## when they were introduced, and their default value.
## NOTE: The names of variables are defined in "init.c" (struct rc_option).
## The variables pgp and pgp_autosign are only available in mutt-pgp.
##
## Valid variable types are: Boolean, Number, Format_String, String.
## Documentation: http://www.math.fu-berlin.de/~guckes/mutt/manual.html#types
##
##
## Options/Variable settings -
## the manual to mutt-1.1.1i lists 195 options.
## They are all listed here for your convenience.
## Please take a look at the various descriptions
## If you have suggestions for improvements
## then let us know on comp.mail.mutt!
##
## A
# 6.3.1. abort_nosubject
# 6.3.2. abort_unmodified
# 6.3.3. alias_file The file to use for *saving* new aliases
# It's a frequent misconception that this
# file gets automatically sourced - wrong!
set alias_file=~/.mutt.aliases
# 6.3.4. alias_format
# 6.3.5. allow_8bit unset: convert all 8bit data to 7bit before sending.
set allow_8bit
# 6.3.6. alternates list of the users' *personal* addresses
# used by mutt to determine "personal" mail.
# will be set in the file ~/.mutt.personal
# 6.3.7. arrow_cursor
# Affects the display of the folder index.
#set: Show current mail with an arrow ("->")
# *unset: Show current mail with an inverse bar.
unset arrow_cursor
# 6.3.8. ascii_chars
set ascii_chars # set: use ASCII characters to build the thread tree
# 6.3.9. askbcc
# 6.3.10. askcc
# 6.3.11. attach_format
# 6.3.12. attach_sep
# 6.3.13. attach_split
# 6.3.14. attribution
# 6.3.15. autoedit
# 6.3.16. auto_tag
# 6.3.17. beep
# 6.3.18. beep_new
# 6.3.19. charset
# 6.3.20. check_new
# 6.3.21. collapse_unread
# 6.3.22. confirmappend
# 6.3.23. confirmcreate
# 6.3.24. copy
# 6.3.25. date_format
# 6.3.26. default_hook
# 6.3.27. delete
# 6.3.28. dsn_notify
# 6.3.29. dsn_return
# 6.3.30. edit_headers
# 6.3.31. editor
# 6.3.32. escape
# 6.3.33. fast_reply
# 6.3.34. fcc_attach
# 6.3.35. folder
# 6.3.36. folder_format
# 6.3.37. followup_to
# 6.3.38. force_name
# 6.3.39. forward_decode
# 6.3.40. forward_decrypt
# 6.3.41. forward_format
# 6.3.42. forward_quote
# 6.3.43. forward_weed
# 6.3.44. hdrs
# 6.3.45. header
# 6.3.46. help
# 6.3.47. hidden_host
# 6.3.48. history
# 6.3.49. hostname
# 6.3.50. ignore_list_reply_to
# 6.3.51. imap_checkinterval
# 6.3.52. imap_pass
# 6.3.53. imap_user
# 6.3.54. in_reply_to
# 6.3.55. include
# 6.3.56. indent_string
# 6.3.57. index_format
# 6.3.58. ispell
# 6.3.59. locale
# 6.3.60.
folder-hooks, (un)ignore, and From_
I'm having a problem with folder hooks in which I have (un)ignore commands for From_ headers. After unignoring the From_ header in one mailbox, I can't ignore it in others. The reason I want to see the From_ line is that I am using mutt to read my procmail log. This file has for each delivered email an entry showing the `From ' and `Subject:' fields of the header and some other stuff. I wrote for .procmail/log: folder-hook procmail/log'unignore "from "' And this works. But because this is not turned off when you change to another mailbox, there has to be a default folder-hook . 'ignore "from "' And this works placed ahead of the other folder-hook in my .muttrc when I first enter mutt. The problem is after I have changed to .procmail/log, and then to another mailbox, it doesn't work. I get both From_ and From: lines. The ignore lines in my .muttrc: > # default list of header fields to weed when displaying > # > ignore "from " received content- mime-version status x-status message-id > ignore sender references return-path lines x-mailer priority precedence > ignore x-sender reply-to mail-followup-to in-reply-to comments > #my list > ignore x- date user-agent organi cc delivered-to approved-by > ignore resent- > list- importance newsgroups errors-to followup-to > ignore supersedes > -- Greg MathesonDoing things right is Chinmin College, Taiwan doing the right thing. [EMAIL PROTECTED] Doing things wrong is education.
Re: Coming back to previously _seen_ message
On Wed, Jan 19, 2000 at 13:31:09 -0200, Jorge Godoy wrote: > When in a folder with new messages you can go from one to the next new > message just pressing "TAB" key. How to come back to the previous new > message? Use the function "previous-new". It is default unbound, but you can bind to any key at your choice in your .muttrc. For instance: bind index P previous-new bind pager P previous-new > Another thing that would be very interesting it to come back to the > prior message you've seen. There is as far as I know no such function in Mutt. -- Byrial
Mutt Bug List
Hello, folks. I'm new to mutt, so you'll have to bear with me if I ask stupid questions. Sometimes when I receive mail from other users, I'm unable to read it in mutt. I would have thought that it was just some weird MIME type, but that doesn't seem to be the case. I know this is kind of a vague question, but I guess what I'm looking for is some pointers to help me start trouble-shooting this problem. Is there a known buglist somewhere I could double-check? I'm at wit's end. TIA, ~~ESP -- ~ ESP <[EMAIL PROTECTED]> ~
problem with colors [OT]
hi, This is quite offtopic. When I start an rxvt terminal, I get the foll. error: rxvt: can't load color "Red3" rxvt: can't load color "Red3" rxvt: can't load color "Green3" rxvt: can't load color "Green3" rxvt: can't load color "Yellow3" rxvt: can't load color "Yellow3" rxvt: can't load color "Blue3" rxvt: can't load color "Blue3" rxvt: can't load color "Magenta3" rxvt: can't load color "Magenta3" rxvt: can't load color "Cyan3" rxvt: can't load color "Cyan3" rxvt: can't load color "AntiqueWhite" rxvt: can't load color "AntiqueWhite" rxvt: can't load color "Grey25" rxvt: can't load color "Grey25" rxvt: can't load color "LightGray" rxvt: can't load color "#B2B2B2" rxvt: can't allocate Color_topShadow Due to this my mutt shows no color. I know this is more of an rxvt problem, but is there any solution for this? I am using rxvt-2.7.2 on Redhat linux 6.1 Thanks in advance, Raju
Re: problem with colors [OT]
On Thu, Jan 20, 2000 at 03:40:01PM +0530, [EMAIL PROTECTED] wrote: > hi, > > This is quite offtopic. > > When I start an rxvt terminal, I get the foll. error: > > rxvt: can't load color "Red3" > rxvt: can't load color "Red3" > rxvt: can't load color "Green3" > rxvt: can't load color "Green3" > rxvt: can't load color "Yellow3" > rxvt: can't load color "Yellow3" > rxvt: can't load color "Blue3" > rxvt: can't load color "Blue3" > rxvt: can't load color "Magenta3" > rxvt: can't load color "Magenta3" > rxvt: can't load color "Cyan3" > rxvt: can't load color "Cyan3" > rxvt: can't load color "AntiqueWhite" > rxvt: can't load color "AntiqueWhite" > rxvt: can't load color "Grey25" > rxvt: can't load color "Grey25" > rxvt: can't load color "LightGray" > rxvt: can't load color "#B2B2B2" > rxvt: can't allocate Color_topShadow netscape exhausts your colormap, I guess. > Due to this my mutt shows no color. I know this is more of an rxvt > problem, but is there any solution for this? rxvt has not install colormap option, I guess... -- Ralf Hildebrandt <[EMAIL PROTECTED]> www.stahl.bau.tu-bs.de/~hildeb "There are two major products that come out of Berkeley: LSD and UNIX. We don't believe this to be a coincidence." -- Jeremy S. Anderson
Re: Mutt Bug List
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote on Thu, 20 Jan 2000: > Sometimes when I receive mail from other users, I'm unable to read it in > mutt. I would have thought that it was just some weird MIME type, but that > doesn't seem to be the case. > > I know this is kind of a vague question, but I guess what I'm looking for is > some pointers to help me start trouble-shooting this problem. Is there a > known buglist somewhere I could double-check? I'm at wit's end. I don't know about a known buglist... Mutt doesn't have bugs. ;-) (j/k!) But, for starters, your could describe what happens when you try to view one of these "nondisplaying" messages in Mutt? What do you see on the screen? Second, in the case that this is a "weird MIME type", can you view the message if you pipe it to some external program, such as less? You can do this by typing "|less". If you don't have "less" installed, you can use the "more" program. With either of those, you will then be able to see the "raw" message contents. Third, for these non-displaying messages, what do you see when you press "v" (which shows you a list of the message components/attachements)? Particularly, what does the attachment info at the right edge say? For normal text it should be text/plain. Hopefully these will get you in the right track of solving the problem, or at least give us more info to work with. Regards, Mikko PS. The list's preferred email address is [EMAIL PROTECTED] -- // 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 / Dyslexics of the world, untie!
Re: folder-hooks, (un)ignore, and From_
Greg Matheson <[EMAIL PROTECTED]> wrote on Thu, 20 Jan 2000: > I'm having a problem with folder hooks in which I have (un)ignore > commands for From_ headers. After unignoring the From_ header in > one mailbox, I can't ignore it in others. I remember reading somewhere that you can't (re-)ignore a header which you have unignored. I'm not positive if that's so, but if yes, then this is probably the source of your problem. 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 / Any sufficiently advanced magic is indistinguishable from technology.
Re: Mutt Bug List
On Thu, Jan 20, 2000 at 12:21:06AM -0800 or thereabouts, [EMAIL PROTECTED] wrote: > Hello, folks. I'm new to mutt, so you'll have to bear with me if I ask > stupid questions. > > Sometimes when I receive mail from other users, I'm unable to read it in > mutt. I would have thought that it was just some weird MIME type, but that > doesn't seem to be the case. Can you read it in other mailers? > I know this is kind of a vague question, but I guess what I'm looking for is > some pointers to help me start trouble-shooting this problem. Is there a > known buglist somewhere I could double-check? I'm at wit's end. Well, there's one you can find by poking around www.mutt.org. It's http://www.math.fu-berlin.de/~guckes/mutt/bugs.html -- but it was last updated six months ago. The most recent entries are for mutt 0.96.3. There's been quite a few versions since then :) I would try reading it with other mailers, and try saving it and seeing whether I can use a pager like 'more' on it. If, from the index, you hit 'v' to view attachments, it should tell you what MIME types the attachments are, too. Checking your mimetypes file(s), both system (eg, perhaps /etc/mime.types) and local (I don't bother so I forget what most people call this one) might throw something up. If you don't have an entry for that particular mimetype, there are pages (again, from www.mutt.org) which have sample mimetypes which are huge. You might find a suitable entry in those. Does 'unable to read' mean you get a message about it being unsupported, or you view something that looks like random ASCII garbage, or what? Telsa
Mutt + colors
I have `color status black cyan' in my ~/.muttrc. Stepping through mutt ensures that ColorDefs[MT_COLOR_STATUS] is 0x0A00 where color-pair 10 was initialized with init_pair(10, 0, 6). This should produce normal black on cyan, however ncurses (version 4.2) for some strange reason outputs \e[0;10;1m\e[30m;\e[46m (reset everything, set bold, set foreground to black and background to cyan), making it look like `brightblack cyan'. Is this a bug in mutt (e.g. not specificallty resetting A_BOLD which was set by a previous attrset?), or a bug in ncurses (or maybe in terminfo?)? Note that the preceding sequences are \e[0;10m\e[?25l\e[H (reset everything, make cursor invisible, move cursor to 1,1), so bold is turned on purposedly just for displaying help line. Note that this affects both help and status line in the index, and only help in the pager. Status line in the pager displays normal black on cyan. This occurs both on the linux console and Eterm. Other colors seem to work as expected (with ncurses; there's a wholy different story with slang...). Marius Gedminas -- Favourite MAC error message: "Not enough memory to eject disk!"
Re: folder-hooks, (un)ignore, and From_
On Thu, Jan 20, 2000 at 17:50:03 +0800, Greg Matheson wrote: > X-Mailer: Mutt 0.95.7us It might help to upgrade to Mutt 1.0.1. There have been some fixes to ignore/unignore which make them work better. However don't trust the manual about this topic. Header weeding functions this way: Mutt stores internally two lists: the ignore list and the unignore list. A header is ignored if and only if it matches the ignore list and doesn't match the unignore list. So if you have these commands: ignore x- unignore x-mailer you will see x-mailer headers because it matches the unignore list. The manual says otherwise but is wrong. The ignore command adds its arguments to the ignore list and removes them from the unignore list if they are there. The unignore command adds its arguments to the unignore list and removes them from the ignore list if they are there. Except "unignore *" that just removes "*" from the ignore list if it is there, and else does nothing -- it doesn't remove all tokens from the ignore list as the manual says. -- Byrial
prompt for Fcc
How may I set mutt to prompt for an Fcc in the case that there is no Fcc hook or rule already? -- Eric Smith [EMAIL PROTECTED] 00 27 21 4265311 True wealth is measured not by what you accumulate, but by what you pass on to others - Larry Wall.
Re: prompt for Fcc -> default fcc-hook
* Eric Smith <[EMAIL PROTECTED]> [000120 14:15]: > How may I set mutt to prompt for an Fcc in the case > that there is no Fcc hook or rule already? There is no such prompt for Fcc. Workaround: Set a default fcc-hook. Sven
new to mutt, very new, one question for now
I love this program. I am using the .muttrc with some tweaks that I found off the mutt.org page, I have procmail and fetchmail working lovely, but everytime I send a msg, Mutt wants to create a mailbox for it. Am I able to get around this feature, or is this an imbedded feature of the program that can't be toggled?
Re: new to mutt, very new, one question for now
On Thu, Jan 20, 2000 at 11:04:36AM -0600, Jason Helfman wrote: > I love this program. I am using the .muttrc with some tweaks that I > found off the mutt.org page, I have procmail and fetchmail working > lovely, but everytime I send a msg, Mutt wants to create a mailbox for > it. > > Am I able to get around this feature, or is this an imbedded feature of > the program that can't be toggled? Look at the documenation for fcc-save-hook. At most simple, you could just say fcc-save-hook . =sent-mail or some such. But you could get fancier -- - Jeff Abrahamson [EMAIL PROTECTED] 610/270-4845
Text substitution
I've got a STRANGE problem at my new client site. They're using GroupWise (UGH!) and I'm using Mutt (Yeah!). I've gotten them to interface through their POP3 server. So, I can get mail from people on site. I can also sendmail out to the outside world (like you all) through the same server acting as am SMTP gateway. The problem is that I can't send mail to others internally. Here's why: they have no DNS entry for their POP3 server, just an IP address. So, if I sendmail to [EMAIL PROTECTED], it disappears; if I send it to [EMAIL PROTECTED], it works. Like I said, strange. My question is this: Is it possible to set up an alias or a rule in mutt such that every time I respond to an internal email from Joe Blow with a return address of [EMAIL PROTECTED], it automatically changes it to [EMAIL PROTECTED]? If anyone has any ideas, I'm all ears because this is driving me crazy!! -- Thanks, Jon Walthour, OCP Oracle Database Administrator (513) 241-5949 x271 (office) (513) 649-9488 (pager) [EMAIL PROTECTED] LÛCRUM INCORPORATED Digital Strategies That Improve Your Bottom Line 1999 Inc. 500 Award Winner One of America's Fastest Growing Companies
PGP / GPG in background
Hi all, I'm a user of mutt and like it but there are a few things I'd like to be able to do with it. So, It is possible to * Use Mutt with Usenet. I'm pretty sure we can't but is there a plan to program it ? Is it already in a patch ? Will this patch be included in the next version ? * I'd like to know whether we can put GnuPG in the background instead of waiting the 5 or 6 seconds each time we send an email. With Outlook, it directly signs & encrypt in the background, but with mutt, it does it while not allowing you to do anything else. * Is there an X frontend to mutt ? The problem isn't that I hate the console but that I'd like to be able to do several things at the same time. For example, when I reply to someong, I'd like to be able to read another message without opening a new console + re-opening the same mailbox... Thanks for helping me... -- _ _ _ _ _ _ | | (_)_ __ _ ___ __ | _ \ _ _| | ___ | | | | | | | | | | '_ \| | | \ \/ / | |_) | | | | |/ _ \_ / | | | | | | | |___| | | | | |_| |> <| _ <| |_| | | __// /|_| |_| |_| |_|_|_| |_|\__,_/_/\_\ |_| \_\\__,_|_|\___/___| (_) (_) (_)
Re: Text substitution
On Thu, Jan 20, 2000 at 02:07:36PM -0500, Jon Walthour wrote: > I've got a STRANGE problem at my new client site. They're using GroupWise (UGH!) and >I'm using Mutt (Yeah!). I've gotten them to interface through their POP3 server. So, >I can get mail from people on site. I can also sendmail out to the outside world >(like you all) through the same server acting as am SMTP gateway. The problem is that >I can't send mail to others internally. Here's why: they have no DNS entry for their >POP3 server, just an IP address. So, if I sendmail to [EMAIL PROTECTED], it >disappears; if I send it to [EMAIL PROTECTED], it works. Like I said, strange. > > My question is this: Is it possible to set up an alias or a rule in mutt such that >every time I respond to an internal email from Joe Blow with a return address of >[EMAIL PROTECTED], it automatically changes it to [EMAIL PROTECTED]? > > If anyone has any ideas, I'm all ears because this is driving me crazy!! You're on a unix workstation? Set up your own sendmail, even if it has to listen on a high port if you can't be root. Sendmail is the "right" way to deal with such things. -- - Jeff Abrahamson [EMAIL PROTECTED] 610/270-4845
