Re: HTML Mail
Ian Chilton <[EMAIL PROTECTED]> wrote: > > [ian@buzz:~]$ cat .mailcap > text/html; /usr/bin/links %s > > and these in .muttrc > set mailcap_path="~/.mailcap" > auto_view text/html > > But I get this: > mailcap entry for type text/html not found Auto_view only looks for mailcap entries with the "copiousoutput" tag. If you want to use an interactive browser like links, you must press 'v' and press 'return' on the html attachment. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: NFS problems
Rocco Rutte <[EMAIL PROTECTED]> wrote: > > The situation so far is that sending mail doesn't work because mutt > does not show up again after returning from the editor (saving works). Use 'strace' to watch the mutt process and log system calls, then find out what mutt is trying to do when it hangs. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: "update encoding?"
Adam Shostack <[EMAIL PROTECTED]> wrote: > > The client's clock is running a few minutes behind the server. You > write the file at local noon, which the server sets to be 12:03. Mutt > checks the file, sees that its mtime is in the future (12:03 being > later than 12:00), and warns you. I guess I had always assumed that Mutt took the timestamp from the file, not from looking at the current time. Interesting.. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: "update encoding?"
Sadiq Al-Lawatia <[EMAIL PROTECTED]> wrote: > > "~/Mail/tmp/mutt-csce-4803-30 [#1] modified. Update encoding? > ([yes]/no): " This message indicates that the time-stamp on the file has been changed since Mutt last saw you write to the file. That is, when Mutt launches your editor, and your editor finishes writing, the timestamp is set to a certain time, and Mutt makes note of it. Then, when you press "y" to send, Mutt looks at the timestamp again, and notices that it has changed. Mutt thinks that you did something behind his back, and so it asks you what's going on, should it check the file again to see if it should change the encoding (us-ascii, iso-8859-1, etc). So, the mystery here is, why does Mutt think that you're changing the file behind his back? Does your editor run in parallel with Mutt, like does it launch a separate X-window for you to edit in, while in the xterm where you ran Mutt, it thinks you are finished editing? That's the only thing I can think of. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Why is http address attachet to header?
Patrik Modesto <[EMAIL PROTECTED]> wrote:
>
> I create new message, then to the first empty line under header i
> write http://www.something.com and send this mail. This address is
> send as a part of email's header and body of this mail is empty. Why?
> Is this correct?
The other posters on this thread are correct, that you must leave a
blank line after the headers of your message.
A header is always of the form "Identifier: text". Mutt knows this, so
if you mess up, and just start typing "Hello" without leaving a blank
line, Mutt will look at it, roll his eyes, mumble "stupid user", and
then insert the blank line for you, that you should have put there
yourself. Mutt can tell there's a mistake, because the line has no
colon (":") characters in it.
However, when you type just "http://www.something.com"; at the beginning
of the first line, well, there is a colon there! So Mutt thinks you are
adding a new header to your message, "http: //www.something.com". So
Mutt does not fix your mistake in this case, because it does not look
like a mistake.
--
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
Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Mutt ignoring 'From ' lines in mailbox
James Greenwood <[EMAIL PROTECTED]> wrote: > > I looked more carefully at the From lines of the messages > it was picking up compared to those it wasn't, and in the > ones mutt can see, the sender is an e-mail address, e.g. : > > From [EMAIL PROTECTED] Tue Oct 16 12:48:57 2001 > > whereas in the messages mutt is ignoring, it is a name, e.g.: > > From Bruce Smith Wed Oct 17 17:08:13 2001 > > and just removing the space like this solves the problem: > > From BruceSmith Wed Oct 17 17:08:13 2001 This is exactly the problem. Mutt uses a more stringent definition for the mailbox separator, namely "From ". Mutt has some heuristics for recognizing date stamps, but if the userid is more than one word, the heuristics fail. Technically it shouldn't be multiple words anyway. > I don't know enough about the mailbox format to know whether > this is a bug in mutt, or a bug in the LibDBX program I used > to translate the Outlook files into mailbox format. It's a bug in the tool that wrote the mailbox, LibDBX, I suppose. But it's hard to fault it, since the mailbox format is so loosely defined. Mutt chooses to be picker about the "From " syntax because some mailers don't properly escape a "From " that is inside the body of the message. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Scrolling the Index -> current-{top,middle,bottom}
Sven Guckes <[EMAIL PROTECTED]> wrote:
>
> there is no command which scrolls the index by one line - sorry.
What about these?
Index bindings:
< previous-line scroll up one line
> next-line scroll down one line
If you were to combine these in a macro...
macro index {
macro index }
Then the cursor would sit still, while the index scrolls around it.
--
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
Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Using Mutt with a Local Spool *and* Multiple IMAP Servers: (rocky@umuc.edu)
Rocky Giannini <[EMAIL PROTECTED]> wrote: > > account-hook . 'unset imap_user ; set folder=~/Mail' This is problematic. The problem is that, when you enter a pathname like "=folder" into a send-hook or a $record variable, you might expect that Mutt simply stores the "=folder" string in the hook or variable, and then when it is needed, performs some type of dynamic expansion, using the current value of $folder, and accesses the path specified. However, that's not how Mutt works. Instead, at the time that you create (instantiate?) the hook or at the time you set the variable, that is when the current value of $folder will be read, and the full path expanded at that time. set folder=/dir1 folder-hook =folder 'set var=value' set folder=/dir2 folder-hook =foobar 'set var=value' In this example, two send-hooks are created, one on the folder "/dir1/folder", and the other on "/dir2/foobar". If you are expecting that the second setting of $folder will cause the first hook to be redefined, so that it is triggered when you switch to "/dir2/folder", you will be sadly mistaken. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Can I use mutt to notify a message to all PC users running MS Windows on the network?
J. Effendi <[EMAIL PROTECTED]> wrote: > > Can I use mutt to replace this kind of notification messages to all > users easily? Where can I get more information about it? Others have answered your first question, but I have a suggestion. You may wish to install and make use of the Samba package for this purpose. I noticed that the "smbclient" program (that comes as part of Samba) has this option in its help screen: -M host send a winpopup message to the host So it sounds like this program, with some clever scripting, could be used to send pop-up messages to all the users you'd like to notify. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: experience/questions : switching from Netscape to mutt
Wim Kerkhoff <[EMAIL PROTECTED]> wrote: > > I'm so used to having a 3 way split in my mail program: folders on > the left side, message list in the top right, and preview in the > bottom right. With that setup, it's a breeze to drag and drop > messages to any of my 138 folders. Mutt gives you more rewards, the more you teach it. With save-hooks, for instance, you can teach Mutt that when it sees messages with certain patterns to them, that they belong in a particular folder. When you've done that, you can read a message, press 's', and save it to the right place most of the time. You can always override the choice though. Of course, if you can teach Mutt to do that, then you can also teach procmail to put the mail in that folder to begin with. The secret to productivity: Get the computer to do the work! That's what it's there for. :) -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: VVV-NNTP patch send-hook
Drew Raines <[EMAIL PROTECTED]> wrote: > > I believe the suggestion was something to the effect of > >send-hook ! . 'my_hdr Blah: foo' That won't quite work. Internally, Mutt translates the simple pattern "." into ~A, which matches everything. Negating that matches nothing, which is the effect you see. A more specific pattern, such as '~t .' might work better, since it is not a simple pattern and may avoid the internal translation. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: ~/Mailbox oddness?
J. Scott Dorr <[EMAIL PROTECTED]> wrote: > > The only problem with this is that if I let other apps do it, then my > status line in mutt won't be accurate, and mutt won't offer ~/Mailbox > as an option to change to when I hit 'c'. There's something strange about all this... A program other that Mutt should really end up checking your mailbox in the same way that Mutt does. That is, other programs (I'm pretty sure "tf" does it this way) will simply look at the time stamps on the mailbox, and if the write time is later than the read time, it reports "new mail." If the latter is later (??), then it's assumed that some other program read the mail, so mail is no longer reported for that mailbox. The thing is, checking the time stamps will not cause other programs to see things any differently. That is to say, all the programs that check mail in this manner should see things the same way, without interfering with each other. The only thing that messes up this scheme is when a program not only wants to tell you that you have new mail, but also wants to show you something about that mail. For instance, a program that wants to notify you of new mail, AND tell you whom the new mail is from, and what the subject is... well, that program needs to OPEN the mailbox and read it, and that causes the "last read" timestamp to change, and this will cause other programs (like Mutt and tf) that only look at the time stamps, to stop reporting new mail. So you need to take a look at how each program that detects mail for you is doing the detection, and if you don't like the way they are doing it, maybe there is some way you can put a stop to it. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Displaying all mail after a limit command
Martin Karlsson <[EMAIL PROTECTED]> wrote: > > > Limit to ~A (all) does it for me. > > Or why not to . (a dot)? > Fewer keystrokes :-) As I understand it, Mutt internally translates the search pattern "." into "~A", so they are one and the same. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: NetBSD build problems - -lcposix?
Ken Weingold <[EMAIL PROTECTED]> wrote: > > Would that cause make to error out? > > /tmp/hazmat/mutt-1.3.27/pgpkey.c:701: undefined reference to `beep' > resize.o: In function `mutt_resize_screen': > /tmp/hazmat/mutt-1.3.27/resize.c:79: undefined reference to > `resizeterm' > collect2: ld returned 1 exit status > gmake[2]: *** [mutt] Error 1 > gmake[2]: Leaving directory `/tmp/hazmat/mutt-1.3.27' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/tmp/hazmat/mutt-1.3.27' > gmake: *** [all-recursive-am] Error 2 You are not supplying sufficient information for this list to tell you what is wrong. All the above messages mean is that function beep() could not be found. It doesn't tell us WHY it could not be found. Perhaps it is not found because you are linking to a deficient curses library. Perhaps your ncurses is not up to date. Perhaps the correct location of ncurses has not been determined. These are things that are very difficult to tell from so far away out on the net, as we are. Perhaps you could post the entire output from "make", or maybe even the output from "configure" if you so desire. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: inadvertent undeletions
N. Thomas <[EMAIL PROTECTED]> wrote: > > I'm thinking I might have inadvertently hit some keystroke that did > this. Is there a function that will do something like this? If you hit the "%" key, it will toggle the folder to read-only mode. None of your changes will be saved when you exit the folder. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: FCC to a program/pipe?
David G. Andersen <[EMAIL PROTECTED]> wrote: > > I've been digging around for a bit trying to figure out the best way > to do this: How can I set mutt up to pipe an auto-FCC of my outgoing > mail to a program, instead of a file? Mutt already sends every mail you send to a program... The MTA! The variable that sets the program that will be launced is called "sendmail" and has the default value "/usr/sbin/sendmail -oem -oi". You could, however, write your own script, and simply have your script capture the outgoing message, do whatever you want with it, and then ALSO call the real "sendmail" program, so that your mail still gets delivered. Then you'd set $sendmail to point to your script. After suitable testing, of course. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Saving a read E-Mail into an imap-folder -> O-flag
Heiko Heil <[EMAIL PROTECTED]> wrote: > > whenever I save a *read* message into an imap-folder the message is > marked as "old" (O). What can I do against this behaviour? This is documented as a known bug in IMAP: * Server copy currently doesn't take into account uncommitted changes in messages about to be copied. Sync first. The advice works. When you sync (hit "$") the folder, the changes made by Mutt are sent to the server (Messages are marked as Read), and then when you ask Mutt to save/copy the message to another folder, the flags will be correct. This annoys me, too. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Deleting text in subject "flea"
Simon White <[EMAIL PROTECTED]> wrote: > > This seems to happen specifically when I have input more than 8 > characters, which is usual for filenames with full paths and email > addresses. I wonder if you could try running "stty -tabs" before you start Mutt. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: spam tricks updated
Gerhard Häring <[EMAIL PROTECTED]> wrote:
>
> Here's one trick I've learnt from this list:
>
> send-hook . 'set editor=vim; set record={gargamel}INBOX.Sent'
> send-hook spamcop 'set editor=/bin/true ; set record='
I understand what the variable settings are for, but I can't figure out,
what does this do?
--
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
Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: set Folder
Todd Kokoszka <[EMAIL PROTECTED]> wrote: > > If I change from my home directory and try to use tab > completion it won't complete the folder name. But when > I try and manually choose it, mutt is in the correct > folder. I'm guessing that you mean you have a folder in ~/Mail that you are trying to complete via . But your current directory is probably not ~/Mail when you run Mutt. When you are at a folder prompt, and you type some letters and hit , Mutt will try to complete from files in your current directory, not the folder directory. You can force Mutt to look in the folder directory by typing the folder character (either "+" or "=") before the folder name. It's a good habit to get into. However, when you press "?" to browse for a folder, Mutt recognizes that the most likely place you'll want to look for a folder, is in your folder directory, so it begins browsing from there. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Hi
Gary Johnson <[EMAIL PROTECTED]> wrote: > > I don't know how mutt chooses the encoding type for an attachment Mutt chooses the encoding that causes the least increase in size for a file. Files that are mostly ASCII will increase only slightly when encoded with quoted-printable, whereas base64 incurs a fixed 33% increase in size. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Hooks & order of precedence
Rob Reid <[EMAIL PROTECTED]> wrote: > > I thought that was what . is for, matching any folder, as in: > > folder-hook . unset save_empty Maybe I should explain it a little clearer: Suppose you have a set of hooks like this: folder-hook . 'set variable=AAA' folder-hook +folder 'set variable=BBB' send-hook'~C user@domain''set variable=CCC' Now, given this, I believe the original poster in this thread expects that $variable would be set to "AAA" when he is sending to some other user, and not in +folder, and expects it to be set to "BBB" if he sends to another user while in +folder, and expects it to be set to "CCC" when he sends to , regardless of the folder. In fact, though, only the last statement is true. The others are true SOMETIMES. Depending on what has happened before. Folder-hooks only trigger when the folder is entered. If the user enteres folder "+folder", $variable gets set to "BBB" at that time. As long as the user sends mail to anybody but , $variable will stay set to "BBB". But when he sends mail to , at that time, $variable gets set to "CCC", and it stays that way. So from then on, if he sends mail to any other user, $variable remains set to "CCC" because there is nothing to reset it to anything else. Only when the user changes folders again, will $variable change back to either "AAA" or "BBB". Now, if we were to add a new send-hook before the other: send-hook ~A 'set variable=DDD' This wouldn't have the desired effect either, because the variable would no longer depend on the folder that was entered. When sending to , $variable has the value "CCC". When sending to anyone else, it has the value "DDD". Regardless of folder. So you see, mixing folder-hooks and send-hooks that set the same variable, is not a good idea. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Hooks & order of precedence
Erik Rothwell <[EMAIL PROTECTED]> wrote: > > However, the default-hooks.muttrc does not properly reset my signature > (nor message headers) to the default... You seem to have a misunderstanding about when hooks are run. A folder-hook is only run when you change folders. Not every time you send a message while you are in that folder. Just at the time you enter the folder. A send-hook runs whenever you send, of course. So you can see that if you have a folder-hook that sets your signature, and a send-hook that also sets your signature, after you send, there is no hook to set the signature back to what the folder-hook would have set it to. The only way I can think of to handle this is to have a set of folder- hooks which recreate the default send-hook each time you enter a new folder. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Deleted attachment
Adam Byrtek <[EMAIL PROTECTED]> wrote: > > IMHO it sucks... mutt isn't a file manager, and it shouldn't allow > deleting files on my HD. The biggest user of the (u)nlink feature of Mutt.. is Mutt itself. Every mail that you send has some form of temporary attachment (even if it's just the main attachment), and this temporary file needs to be deleted. So Mutt marks any temp files it creates, with the "-" flag, so that it will be deleted after the compose is done. Even if you quit. You still want the temp files to be deleted. If you mark an attachment with the unlink flag, then you are telling Mutt that your file has the same disposition as any of its temp files. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: The & operator for patterns?
Danie Roux <[EMAIL PROTECTED]> wrote: > > ~C (domain & !user@domain) > > i.e. Match everyone from domain except a certain user. You have to be careful about patterns like this. What if the recipient is ? Since that contains the string "user@domain", it would be rejected by the pattern, even though it's a different user. What if the message has two recipients, one of which is in @doman, the other is user@domain? Do you want to reject the message because it contains user@domain, or do you want to accept it because it ALSO contains a user who is not user@domain, but still from @domain? The inclusive behavior of ~C makes it hard to write patterns that get exactly what you want. :/ -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Deleted attachment
Adam Byrtek <[EMAIL PROTECTED]> wrote: > > Help! I was composing a new msg today and I wanted to inlude one of my > mailboxes as an attachment. I attached the file, and them resigned, > pressing q and no to postpone question, and I've found that my whole > attached mailbox was deleted! Help, it has a great meaning to me! > > ps. I might have pressed some other keys after 'a' and before 'q'... You may have pressed 'u', which toggles the delete flag on an attachment. If an attachment is marked for deletion, it will be deleted, whether or not you send the mail. The reason for this behavior is that Mutt uses the delete feature for its own internal use. Many of the attachments Mutt creates (such as the message body itself) are placed in temporary files, and Mutt marks them for deletion. If you were to decide not to send the mail, you would still want those temporary files deleted. However, any attachments that you set the delete flag on, will also be deleted if you quit the message, since Mutt doesn't know the difference. Beware of this behavior! -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Form Letters on Mutt
johnathan spectre <[EMAIL PROTECTED]> wrote: > > PS. Sorry to hear your terminal can't word-wrap beyond 80 columns, > but not everyone uses an 80 column terminal (I ditched my VT100 ages > ago). When you send E-mail, it's intended to be read on other people's screens. Which are probably a different size from yours. Be kind, and write your mail to display nicely somewhere else. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: HELP: How do I change my from address format?
Suresh Ramasubramanian <[EMAIL PROTECTED]> wrote: > > Which I suspected ... the [EMAIL PROTECTED] (Me) is depreciated, and seems to > be more common on usenet than on e-mail. If you configure Mutt with --enable-exact-address, it will not rewrite the address in the preferred format. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: multilingual text
Baurjan Ismagulov <[EMAIL PROTECTED]> wrote: > > can i create messages in two different languages using overlapping > 8-bit charsets simultaneously? i need, for example, mix koi8-r and > iso-8859-9 in one message. How about one message with two attachments, one attachment using koi8-r, and the other using iso-8859-9? I don't think Mutt can create any multipart type besides multipart/mixed, though.. you might have wanted multipart/alternative? -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: charset override
Baurjan Ismagulov <[EMAIL PROTECTED]> wrote: > > how can i override the charset specified in the Content-Type: field > of an incoming message? Use the edit-type function, bound to Ctrl-E by default. It lets you edit what Mutt thinks the Content-Type of a message is. The charset information in included in what you can edit. > the problem is, some muas send 8-bit text in messages marked with > charset=iso-8859-1. What's wrong with that? iso-8859-1 is an 8-bit character set. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: how to change the default encoding method?
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > As i have "unset allow_8bit" in /etc/Muttrc, the mails i send are > always encoded as "quoted-printable"! Can i change it to "base64"? You can change it by pressing Ctrl-E in the compose menu, but I don't think you can change the default. And, why would you want to? The reason Mutt chooses quoted-printable is because it encodes to a smaller result than base64. If the base64 encoding had come out smaller, Mutt would have chosen that. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: resend-message and FCC
-kevin- <[EMAIL PROTECTED]> wrote: > > It also seems to preserve the date of the original email, instead of > giving it a new date. Yes, 'Date:' is correct but the 'From' line > without a colon contains the date of the original email, which happens > to be what tagging by date looks at. Not quite. The "From " header (ie, the "envelope separator") contains the date/time when the mail was received by the final delivery agent. That time is usually close to the time that the message was sent, but it is not the same. And Mutt does not look at that timestamp unless you sort by "date-received". Likewise, when tagging by date, ~d examines the Date: header, while ~r examines the enevelope separator time. > Once again, IMHO, if the edited mail is sent, this date should be > changed as well. I tend to agree with this sentiment. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: handling text/plain based on extension of the file
Carlos Puchol <[EMAIL PROTECTED]> wrote: > > well, but attachments have a comment field or something > because i can see the name of the file being sent. That's just a filename. MIME attachments also have a "Content-Type" header which is supposed to tell the MUA exactly what type of document is contained, and thus the mailer should know what to do with it. If the content-type is "text/plain", but the filename matches "*.gif", for instance, then the mailer that *sent* the message is clearly broken. It's not Mutt's fault that it tries to display an image as a text attachment, because that's what it was told by the sender to do! You should complain to the person who sent you the mail, and tell them to fix their mailer so that it sends things out correctly. That will help everyone. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Binding bug + minor annoyance.
David Champion <[EMAIL PROTECTED]> wrote: > > Maybe the original poster (I forgot who...) would be OK with > "unbind * *" and "unmacro * *". But there is no "unbind" nor "unmacro" command... -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: attempt to build mutt-1.3i failed
Dr. Charles E. Campbell <[EMAIL PROTECTED]> wrote: > > I tried to build mutt-1.3i on an old Indigo^2 (SGI, Irix 5.3). Others have helped you with your immediate problem, but you should realize that Mutt 1.3 is a *development* version of Mutt. As such, all problems with it should be reported to mutt-dev, not mutt-users. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Binding bug + minor annoyance.
Mikko Hänninen <[EMAIL PROTECTED]> wrote: > > That's good as an option, but then the problem would be that you can't > have an independent stand-alone binary that works even with no > resource files... Is this really one of the design goals of Mutt? I don't see a problem with getting people used to the idea that there must be a system-Muttrc, and it should be copied wherever Mutt gets copied. That way, if a site has policies like domain-names and hidden-hosts, they won't get lost just because someone copies the Mutt binary somewhere else. Perhaps Mutt should simply fail to start without some sort of configuration input. :) -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: corrupt mail
Michael Soulier <[EMAIL PROTECTED]> wrote: > > Hey guys. I'm using mutt 1.2 on HP/UX 10.20, and I keep running into > problems with corrupt mailboxes. My inbox is having problems. It's > like an incoming mail is overwriting portions of a previous mail. How is your incoming mail arriving? Via the standard "rmail" receiver program, or is "procmail" doing the mail delivery? If you don't know what I'm talking about, it's probably "rmail". You need to use correct locking methods on the mail spool, or incoming mail might overwrite or get overwritten by Mutt if they both decide to update the folder at the same time. You can see Mutt's locking features in the "mutt -v" output. For HP-UX, I believe you should see "+USE_SETGID", "+USE_DOTLOCK", "+USE_FCNTL", and "-USE_FLOCK". That is, dot-locking and fcntl-locking should be enabled. If they aren't, you could be in trouble. > At first I thought it might be Netscape attempting to access the > files, so I've redirected my mailbox to a new directory that Netscape > wouldn't access, but it's still happening. How did you redirect your mail? -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Binding bug + minor annoyance.
David T-G <[EMAIL PROTECTED]> wrote: > > One way might be to have mutt ship with no bindings and let you roll > all of your own ;-) This tongue-in-cheek comment is actually not a bad idea: Do not hard-code any of the keybindings in the Mutt source, but instead set the defaults in the system Muttrc. This way, it is possible for a site to implement their preferred keybinding policies, without having to "un-Elm-ify" Mutt every time you want to get proper generic bindings. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Multiple IMAP Servers
Kristin Anne Igaki <[EMAIL PROTECTED]> wrote:
>
> I would very much like to use one instance of Mutt to get all my mail.
> However, I have 3 mail accounts on 3 different servers, 3 usernames, 3
> passwords... Is there any way to configure the setup so that I can
> browse all 3 using "c"?
I believe Mutt supports the following syntax for imap folder specifications:
{user@hostname:port}folder
Where "user@", ":port", and "folder" are all optional. So you could
specify some mailboxes like so:
{user1@host1}
{user2@host2}
{user3@host3}
However, I'm not sure how you would specify the passwords; if they all
have the same password, setting $imap_pass should work; otherwise you
might have to type each password as Mutt asks for it.
--
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
Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: qmail-inject
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > every once in a while, but rarely, i get "qmail-inject: illegal option -- B" > when handing off a mail for outbound delivery. the number is "100". i let > mail be handled by: Doesn't anyone read the manual anymore? 6.3.196. use_8bitmime Type: boolean Default: no Warning: do not set this variable unless you are using a version of sendmail which supports the -B8BITMIME flag (such as sendmail 8.8.x) or you may not be able to send mail. When set, Mutt will invoke ``sendmail'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP negotiation. So, you have $use_8bitmime set somewhere. Unset it. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Forcing a rescan of folder
Mikko Hänninen <[EMAIL PROTECTED]> wrote: > > I use Maildir over NFS. I find myself frequently in a situation where > I see in my incoming mail log that I've gotten mail in a particular > folder while I'm reading it, but Mutt doesn't seem to notice it. It > certainly takes much longer than the 5 seconds that the $mail_check > value would indicate, assuming I understood its meaning correctly... > I wonder if this could possibly be some sort of NFS caching issue or > something? That would be quite unfortunate, as NFS is one of the main reasons to prefer maildir over other mailbox formats. Mutt does, though, appear to pay attention to the modified time on the directory, as an optimization for checking for new messages. So it looks like that could well be the issue. Try playing around with storing files in a directory from one NFS client, then examining the modified time of the directory from another client. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Forcing a rescan of folder
Benjamin Korvemaker <[EMAIL PROTECTED]> wrote: > > Can I force mutt to rescan the current folder (I'm using maildirs)? $ > only commits the changes, but doesn't pick up the new mail in the box, > yet gbuffy lets me know there's more mail. There isn't a function to cause a re-scan, because Mutt is simply supposed to do it without being told. There is a variable $timeout which tells Mutt how often to do it while waiting for commands, and there is another variable $mail_check which determines how often to do it when you are entering commands. They should have reasonable defaults, though. Anyway, Mutt is supposed to notice new mail without being told to look for it. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: sendmail question & mutt
Jason Helfman <[EMAIL PROTECTED]> wrote: > > Running both of these at home. Q, though. I am polling my mail from > my isp via fetchmail. Is it really even necessary to run sendmail as > a daemon? Since fetchmail, by default, connects to your listening sendmail daemon, you would need to reconfigure fetchmail if you decided to turn off the listening sendmail. Also, one of sendmail's other functions is to retry failed deliveries every so often. If you don't run the daemon, then a failed delivery will be queued, and then never retried again. You should probably run a cron job that launches "sendmail -q" at some interval if you decide not to run the daemon. That being said, I see no problem in leaving the daemon running, if you simply firewall the SMTP port from external traffic. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Compile On NCR
Williams, James A (James) <[EMAIL PROTECTED]> wrote: > > Error sending message, child exited 127 (Exec error.). This message ususally indicates a syntax error on the sendmail command line that Mutt creates. Things that can affect the sendmail command line are $dsn_notify and $dsn_return. Try disabling these, if you have somehow enabled them. Also, Mutt uses the convention "--" to indicate to sendmail when it is about to give a mail address. Try using a command like this: sendmail -oem -oi -- [EMAIL PROTECTED] And see if sendmail complains about that. If it complains about the "--" option, you can either upgrade your sendmail or edit Mutt's source and remove the code that appends the "--" option. Also complain to mutt-dev if you have to do this. :) -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Some IMAP questions
Chris Green <[EMAIL PROTECTED]> wrote: > > 3 - Is there any way to get mutt in *non-IMAP* mode to 'see' maildir > directories starting with a '.'? Mutt normally doesn't show files that start with "." because of this default setting: set mask="!^\.[^.]" If you unset it, I suppose you would see everything. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Recognizing such threads, How?
Axel Thimm <[EMAIL PROTECTED]> wrote: > > set reply_regexp="^(((re(\\[[0-9]+\\])?|fwd):|\\[[a-z0-9-]+\\])[ \t]+)+" > > Thanks, but this does not fully work for me. That is odd. > Further more replying to your message yielded a subject line > (corrected by hand) of "Re: Re: Recognizing such threads, How?" which > further indicates that mutt thinks the Re: belongs to the subject. My regexp makes use of several non-standard extensions to regular expressions. I was given to understand that Mutt would use its own regexp-parsing library if it decided that the system's library wasn't "good enough", and as such, complicated regexps like the above could be passed around between Mutt users without having to worry about whether the "+" character works, or the "?" character, or even the "|" character... Does your "mutt -v" output say "+USE_GNU_REGEX"? If not, it's using your system's regexp library, which may not support all the extensions being used. If that's the case, it would be possible to rewrite the regexp in some cases, but it would become even uglier than it already is. :) -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: 2 mutt-users lists ?!?!?!
Steffan Hoeke <[EMAIL PROTECTED]> wrote: > > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > Can anyone tell me what's the difference between the 2 ? One of them is right, and the other one is wrong. :) (mutt.org is the right one) -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Recognizing such threads, How?
Axel Thimm <[EMAIL PROTECTED]> wrote: > > one list I am subscribed to adds a prefix of "[TheList] " even for replied > messages leading to threads of the sort: > [TheList] Subject > [TheList] Re: Subject I use lists like this, too. I don't like them. :) > How can mutt be told to recognize this? Here's my reply_regexp: set reply_regexp="^(((re(\\[[0-9]+\\])?|fwd):|\\[[a-z0-9-]+\\])[ \t]+)+" This looks for patterns like "Re:", "Re[2]:", "Fwd:", and "[tag-name]", in any order, and as many times as they appear, at the beginning of a subject. So a subject like this: Subject: Fwd: Re[3]: [Mailing-List] Re: What the heck? will be treated as the subject "What the heck?" And if I reply to it, my reply looks like this: Subject: Re: What the heck? I like it that way. :) -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: DSN error
Rishi Maker <[EMAIL PROTECTED]> wrote: > > Is it true that Mutt does not send mail directly like Pine does. Mutt does not speak SMTP like Pine does. Mutt expects the various components of your Unix system to be configured correctly, as it uses them. Pine doesn't. > I mean i keep geting errors like DSN errors Does your version of sendmail even support DSN? Maybe you should turn off the dsn_* options in your .muttrc. > Which file do i need to edit to rectify it You need to set up your sendmail.cf file. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: From/To in sent index
Jean-Sebastien Morisset <[EMAIL PROTECTED]> wrote:
>
> I'd like to see the To: addresses when I'm in my sent folder. Right
> now, I see the From:. Kinda redundant since it's always from me. :-)
> Is there a setting in my muttrc I can use to change this?
Fix your "alternates" setting, so to that Mutt recognizes that the
messages are from you.
> I also had a similar problem when defining an address as a "list".
> All I'd see in the index was the To: address. Kinda redundant again,
> since every message in that folder (put there by procmail) was To:
> the same address.
Mutt doesn't know that you're filtering your mail. So you'd need some
way to tell it how to list your mail in particular folders.
Folder-hooks are good for this.
Example:
folder-hook . 'set \
sort=threads \
index_format="%4C %Z %{%b %e} %-15.15n (%4l) %s"'
This sets the default sort-order to threads, and simply shows the
sender's name in the index listing (%-15.15n).
folder-hook ! 'set \
index_format="%4C %Z %{%b %e} %-15.15L (%4l) %s"'
For my main spool, I leave sorting set to threads, and change the index
format to contain (%-15.15L), so that list-names will be shown. I don't
sort all lists into folders, only the high-traffic lists.
folder-hook < 'set \
sort=date-sent \
index_format="%4C %Z %{%b %e} %-15.15t (%4l) %s"'
For my 'sent' folder, I want messages sorted by date, and the recipient
(%-15.15t) shown in the index. Note that this would fix your first
problem, as well, but it is still a good idea to fix your "alternates",
so that your address won't show up in group-replies and followup-to's.
folder-hook > 'set \
sort=date-sent'
For my 'received' folder, I like to sort by date. Index format remains
the same.
Hope this helps,
--
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
Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: printing & octet-stream attachments
David Ellement <[EMAIL PROTECTED]> wrote: > > application/octet-stream; mutt.octet.filter %s; copiousoutput > > This works great for viewing octet-stream attachments. However, if I > print a message that includes a octet-stream attachment, the > attachment also gets dumped to the printer. I believe there is a mailcap syntax to specify commands for printing. I also believe that Mutt pays attention to these. Perhaps adding a command "; print=/bin/true" will cause octet-stream attachments to be skipped? Or an alternate filter could be run? -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Multipart/alternative and default attachments
Clint Olsen <[EMAIL PROTECTED]> wrote:
>
> I'm getting multipart/alternative emails from friends/family, and the
> default seems to be html, but the non-HTML version appears there in
> the attachments menu.
You can choose preferred alterative views with the alternative_order
command. By default, Mutt will choose a view from this list. If you
don't give a list, Mutt will choose from whatever types it considers to
be "auto-viewable". That is, a type which has a "copiousoutput" tag in
your .mailcap. If none of these are found, Mutt will choose text/plain,
text/enriched, or text/html, in that order. Beyond that Mutt will
choose whatever it can make sense out of.
> Is there a way to read the ASCII version by default in Mutt so I don't
> have to spin up lynx?
It sounds like someone has set up the alternative_order differently on
your system. Here's how mine is set in .muttrc:
alternative_order text/enriched text/plain text/html
--
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
Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Q: Mutt and Email Lists
Charles Cazabon <[EMAIL PROTECTED]> wrote: > > -if you're using qmail, try setting a Return-Path: header containing > only your email address (no quoted name, etc). This is really a problem best solved in the MTA, rather than with an MUA like Mutt or Pine. The MTA is best suited to handle the task of making your E-mail appear to come from a particular domain or pseudo-domain. And, once configured properly, ALL of your E-mail, no matter what MUA (even /bin/mail) will have proper headers. Wouldn't that be nice? -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Any suggestion on mailling list?
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > My idea is to use Mutt to encode the attachments and produce the > headers. This is not a bad idea, but Mutt is really designed more for interactive use, and thus, there may be other tools better suited. Have you looked at the "mpack" utility? It encodes attachments and sends them in a batch mode. > the subscriber will find To: header is not for them, a bit confusing. They shouldn't be confused if the header says that it was addressed to a list of people... ah well, I think mpack will send individual messages if you wish it to do so. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Any suggestion on mailling list?
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I want to create "mailling lists" using mutt, that's to say, sending > news to some users, but the users need not reply my mails. As i want > to implement the list using scripts, I can not invoke mutt > interactively, all i can do is to use commandline options. Is there some reason you need to use Mutt? Compose your message in a file, with full headers and all. You need not insert the recipients into the To: header, though you should have one in the headers. You can have a fake To: header, such as "To: my-list", even if there is no such list as "my-list". Once you have composed the file, send it directly via sendmail: sendmail [EMAIL PROTECTED] [EMAIL PROTECTED] \ [EMAIL PROTECTED] < mail.file As you can see, sendmail will take the contents of mail.file and distribute it to all of the senders you name on the command line. You can even put the list of names into a file, and insert them thusly: sendmail `cat users.list` < mail.file Voila! A mutt-less solution (on the mutt mailing list, no less)! :) -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: How to resend a mail?
Mikko Hänninen <[EMAIL PROTECTED]> wrote: > > First save the email to a separate file. > Then just call sendmail on the file: > sendmail -t [EMAIL PROTECTED] < /path/to/folder/file What you describe is exactly what the (b)ounce command does in Mutt. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: default save folder
Jean-Charles Bagneris <[EMAIL PROTECTED]> wrote: > > Of course, each time I press 's', I have to give the name of the > folder I want to save to. So my question is : is there a way to give > (in a folder-hook may be) a default name for the archive folder ? You can also simply tag all the messages that you want to save, then save them using a grouped command, and they will all be saved to the single folder that you specify. Use the tag-prefix (default ";") before the save command, to specify saving all tagged messages. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: How could i deal with this in Procmail or Mutt?
Jason Helfman <[EMAIL PROTECTED]> wrote: > > How would I work with this and kill the messages that I send? Er.. > #By default, copies of your own submissions will be returned This text suggests to me that, perhaps, the easiest way would be to tell the list software that you do NOT want copies of your own submissions returned back to you. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Trouble getting indicator to point to first message
Mikko Hänninen <[EMAIL PROTECTED]> wrote: > > folder-hook . 'push "1"' A bit more efficient: folder-hook . 'push ' -- 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: Invoking Procmail
Charles Curley <[EMAIL PROTECTED]> wrote:
>
> Since I already have a call to procmail in my sendmail.cf, all I need to
> do to use procmail is write a .procmail.
Maybe, maybe not...
> ##*##
> ### PROCMAIL Mailer specification ###
> ##*##
>
> # @(#)procmail.m48.11 (Berkeley) 5/19/1998 #
>
> Mprocmail,P=/usr/bin/procmail, F=DFMSPhnu9, S=11/31, R=21/31,
>T=DNS/RFC822/X-Unix,
> A=procmail -Y -m $h $f $u
That's a correct definition of the procmail mailer, BUT, the normal mail
delivery method for local users is a mailer called "local", not
"procmail". You should search for the "Mlocal" definition and see if it
makes use of procmail.
For instance, on my HP-UX box here, procmail is not used by the local
mailer:
Mlocal, P=/usr/bin/rmail, F=lsDFMAw5:/|@m, S=10/30, R=20/40,
T=DNS/RFC822/X-Unix,
A=rmail -d $u
But on my Linux box at home, procmail is used:
Mlocal, P=/usr/bin/procmail, F=lsDFMAw5:/|@qShP, S=10/30, R=20/40,
T=DNS/RFC822/X-Unix,
A=procmail -a $h -d $u
So your answer is "It depends." :)
--
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: Help about hidden destination
Thomas Roessler <[EMAIL PROTECTED]> wrote: > > This is not true. Try using the bcc header, and set nowrite_bcc. Hmm, the manual doesn't make this function clear to me. It says: write_bcc Controls whether mutt writes out the Bcc header when preparing messages to be sent. Exim users may wish to use this. Does this mean that the Bcc header will be written to my saved copy of the message? The terminology "write" implies this to me, but the manual doesn't say. Or does it simply mean that the Bcc header will not be fed to the MTA? Since it mentions an MTA, this might be. But there's not enough information given to tell me why I would *ever* want to feed my Bcc header to an MTA. Why is the default value "yes"? -- 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: Help about hidden destination
Bennett Todd <[EMAIL PROTECTED]> wrote: > > So in that case, I suppose the original question could be answered > really sadistically, with "compose the message, then postpone it, then > change to the postponed folder, then select the message, then > repeatedly bounce it by hand to each of the recipients". Love those > nice user-friendly solutions:-). Actually, Mutt is in a unique position here, to be able to specify sender addresses to sendmail without putting those names into the headers. That is, Mutt could easily feed sendmail a message with a "To: undisclosed-recipients:;" header, and then give sendmail a command line such as "sendmail -(options) user1@host1 user2@host2 ...". So, sendmail would have the correct envelope addresses, but they would not appear in the message. But there is no code to do this in Mutt currently. -- 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: File locking (was: Mutt 1.1.9 about 3-4x slower than mutt 1.0)
Vincent Lefevre <[EMAIL PROTECTED]> wrote: > > This is safer for incoming mailboxes. But for archive boxes, that are > accessed from only one machine, it is useless. So, could the locking > mechanism be chosen from the .muttrc? If the mailbox is only accessed from one machine, why is it on an NFS server? Just put the mailbox on the one machine that is going to access it. No more NFS slow-down. -- 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: Mutt 1.1.9 about 3-4x slower than mutt 1.0 (was Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!)
Eric Boehm <[EMAIL PROTECTED]> wrote: > > Yes, across NFS. I copied the file to a local drive and ran both > mutts. The time was about the same (1.8 sec). Both mutts were also > run from a local drive. Mutt wants to use fcntl-locking on the file. This forces NFS to use a non-caching mode, where all I/O is transfered directly to/from the server, instead of being cached on the local system. This slows things down, but it is also very safe. If you were to configure with --disable-fcntl, things would speed up, but it would also be unsafe. There could be conditions in which the mail server tries to update your mail spool while Mutt is also trying to update it, leading to mailbox corruption. Using the correct locking protocols would avoid this, although it would slow things down. -- 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: Mutt 1.1.9 about 3-4x slower than mutt 1.0 (was Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!)
Eric Boehm <[EMAIL PROTECTED]> wrote: > > I have found that mutt 1.1.9 is about 4x slower reading a 7.4 MB mail > file with 1451 messages in it than mutt 1.0. NFS? What type(s) of file locking? Differences in "mutt -v" output? > I don't know if you would consider this a show stopper but it was > enough for me to back out 1.1.9 and go back to 1.0. It would be incredible if such a slow-down escaped the notice of any of the developers. -- 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: mutt-1.1.9 is out - RELEASE CANDIDATE!
Gary Johnson <[EMAIL PROTECTED]> wrote:
>
> > > CPPFLAGS="$CPPFLAGS -I/usr/include/curses_colr"
> > > LIBS="$LIBS -lcur_colr"
> >
> > I have done this myself, and while the resulting Mutt does build, I
> > found that the color support does not work. I haven't tried it lately,
> > though. Do you get correct colors with this?
>
> I don't know--I've never tried to get colors to work in mutt.
Well, being the curious type, I just tried it, and the colors indeed
have problems. I don't know if this is HP's curses' fault, or my
terminfo's fault, or my xterm's fault, but I do know that Mutt+{ncurses/
slang}+{this-xterm} = working colors, so I suspect the curses library.
But you are correct that Mutt will successfully compile when built this
way, because symbols such as COLOR_BLACK will become defined. I guess
nobody has noticed that Mutt won't build with a curses library that
doesn't even comprehend colors? Oh well.
> Many of the text applications I've seen that have used color have used
> it in a way that I found either not useful, distracting or hideous.
I shared your opinion of colors, until I tried it with Mutt.
> I've also avoided color as a means to convey information because it's
> usually lost when printed or photocopied and because several of my
> co-workers are color blind.
I agree that color ability should never be assumed in one's colleagues,
but I find that, for me, the color helps me to visually separate parts
of messages more easily than I otherwise would. I can more easily scan
past quoted sections of text (because they are in a different color)
without accidentally missing new text that might have been added. I am
certainly still able to, say, distinguish a message's headers from its
body, or quoted text from non-quoted, but the color simply makes the
process easier and less error-prone.
--
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: mutt-1.1.9 is out - RELEASE CANDIDATE!
Gary Johnson <[EMAIL PROTECTED]> wrote: > > CPPFLAGS="$CPPFLAGS -I/usr/include/curses_colr" > LIBS="$LIBS -lcur_colr" I have done this myself, and while the resulting Mutt does build, I found that the color support does not work. I haven't tried it lately, though. Do you get correct colors with this? -- 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: mutt-1.1.9 is out - RELEASE CANDIDATE!
Ralf Hildebrandt <[EMAIL PROTECTED]> wrote: > > does GNUpg work on your HP-UX box? It runs fine here, on HP-UX 10.20. I don't remember having to do more than the usual contortions to build on HP-UX. -- 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: mutt-1.1.9 is out - RELEASE CANDIDATE!
Gary Johnson <[EMAIL PROTECTED]> wrote: > > I've had to hack the configure script of previous releases (0.95.4 and > 1.0) to get them to use the proper curses library on my HP-UX 10.20 > system. Is this still necessary? I've never had trouble with the --with-slang or --with-curses configure directives, on HP-UX 10.20. Building without slang or ncurses, though, has always failed, though. Is this what you refer to? -- 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: [jcm@dogma.freebsd-uk.eu.org: selecting deleted messages]
Peter Poeml <[EMAIL PROTECTED]> wrote: > > You can also go to the message just above the deleted one, and press > 'u'. Will not work when there is no undeleted mail above or when > there are too many other deleted mails above, though. This is really just a side-effect of the undelete operation, and it won't work with $resolve is not set. It is simpler to just use the default keys that are bound to previous-message and next-message (as opposed to previous-undeleted and next-undeleted, which the arrow keys are bound to). The default bindinds for these functions are "J" and "K", which are the shifted letters. VI users will find these bindings convenient. Others will likely not find them comprehensible. :) -- 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: %N in $folder_format
Drew Bloechl <[EMAIL PROTECTED]> wrote: > > $ ls -l Mail/livid-dev ; ls -lu Mail/livid-dev > -rw---1 drew drew 3219213 Mar 10 02:23 Mail/livid-dev > -rw---1 drew drew 3219213 Mar 8 12:05 Mail/livid-dev > > This particular folder has an mtime greater than its atime, but mutt > doesn't seem to realize that with or without BUFFY_SIZE. Can anyone come up with an explanation for this? I can't. -- 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: %N in $folder_format
Drew Bloechl <[EMAIL PROTECTED]> wrote:
>
> Yes, in the index there are messages marked as new. That part of it
> has always worked.
When reading the folder, Mutt can tell which messages are new, by
reading the Status: headers. However, that's only done when opening a
folder; when you just want to know if a folder has new mail in it, it's
much faster to simply check the time-stamp on the file, for mbox
folders.
So, Mutt checks the time to determine if it should put an 'N' for that
folder. You can check this yourself to see what the system has stored
as a time-stamp on the file:
ls -l /path/to/folder ==> This gives you the "modified" time.
ls -lu /path/to/folder ==> This gives you the "accessed" time.
If the folder was modified at a later time than it was accessed, the
folder is assumed to have new mail in it. Try this yourself on some
folders that have had new mail delivered to them, and see if you can
figure out why they aren't being set the way Mutt thinks they should be.
If the times are showing up as equal, you can use a script like this to
print out the exact times:
perl -e '@stat = stat("/path/to/mfolder"); print "Mod = $stat[9], Acc =
$stat[8]\n";'
This prints the exact times, to the second, which you can compare. This
is what Mutt actually does.
Using this technique, perhaps you can determine what the problem is.
--
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: signature send-hook problem
Byrial Jensen <[EMAIL PROTECTED]> wrote: > > Well, I would say the canonical way to match everything is the ~A > pattern. When referring to message patterns, ~A is the "true" way to match all messages, but other hooks refer to text strings, or pathnames, such as folder-hooks. For those, ~A matches the home directory of user "A". :) -- 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: why is mutt better?
J McKitrick <[EMAIL PROTECTED]> wrote: > > I just got in a debate over email clients, and my windows friend > argues anything i can do in mutt, he can do in TheBat! just as > easily. Such arguments rarely lead to a useful exchange of information. They more usually end up as "My computer can beat up your computer" type of "discussion." Is your friend actually interested in learning from this exchange, or does he just want to tell you how great his program is? > I checked the feature list, and it is extensive. Most of what mutt > offers, thebat offers. Why is the advantage of mutt, or any > text-based email client? If TheBat! does everything that he wants it to, then he should use it. Mutt isn't trying to take over the world. :) -- 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: question on saving of sent messages
J McKitrick <[EMAIL PROTECTED]> wrote: > > I've noticed that sometimes when i reply to a message in a saved > folder,or sometimes even the inbox, mutt complains that it cannot > write the sent message because /foldername/sent does not exist. I > assume this means i need to set the saved messages folder to one that > refers to the mail directory or home directory rather than the > directory i am in when i send, correct? You normally will want to refer to folders by putting the "=" or "+" prefix in front of the name. The "=" or "+" expands to the value of the variable $folder, which is an absolute path to the directory where you keep your folders. Then it doesn't matter what directory you're in. > Also, is there a problem with folder name TAB completion? When i > save, it asks for a folder name. I try 'f TAB' to select 'foldername' > but it complains it doesn't exist. Try "=f " > Yet the '?' brings up the list just fine. The default directory that "?" brings up is the $folder directory. There are times when I've found this annoying, but it seems to be traditional at this point. > Does mutt only display new mail messages when the keyboard is used? I > find that new mail only appears after i hit a key, if it has been > dormant for a while and new mail has been received. Yes, Mutt is not multi-threaded, so it does not poll for mail in the background while waiting for a keypress from you. However, there is a variable called $timeout which tells Mutt how long to wait for you to press a key. If you haven't pressed a key by then, it will stop waiting for the keypress, go and poll for mail, then come back and wait some more. So by setting this to a small value (30 seconds?) you can get near-instant notification of new mail. -- 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: Reading HTML Attachments
John P. Verel <[EMAIL PROTECTED]> wrote: > > Thanks for your script :) However, I'm getting the following error > messages: > > Executing: openurl > >'http://washingtonpost.com/cgi-bin/gx.cgi/AppLogic+FTContentServer?pagename=wpni/print&articleid=A64933-2000Mar2'... > /home/john/bin/openurl: =: command not found > /home/john/bin/openurl: die: command not found This script is a PERL script, but it is being interpreted by your shell instead. The first line needs to be something like this: #!/usr/bin/perl Of course, the indentation is merely for readability; there should be no whitespace before the "#!". -- 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: Installing Mutt
Lars Hecking <[EMAIL PROTECTED]> wrote: > > You could do a plain "make" first, and then make install. If make install > fails in docs, "touch" the files make fails on and try make install again. I thought the source of this particular problem came from doing a "make clean". The "manual.txt" file gets removed (because it is a product of the sgmltools), even if the tools do not exist to recreate it. > - install GNU make; some people will disagree with me, but HP's make >is just another example of dumbed-down, near-unusable vendor tools >(Sun's patch is another one, for that matter) I do disagree with you about HP's make having less features than GNU make, but I don't think that makes it "near-unusable". Nevertheless, installing GNU tools has never hurt anybody. :) -- 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: Reading HTML Attachments
John P. Verel <[EMAIL PROTECTED]> wrote:
>
> Question: How to get to launch Netscape if not open and/or same
> question for lynx?
Here's my entry:
~/.urlview:
REGEXP ((https?|ftp)://|www\.)[-a-z_0-9@#$%&+=:;'~,./?]+[a-z_0-9/]
COMMAND openurl
~/bin/openurl:
#!/usr/bin/perl
($url = shift) || die "Usage: openurl http://www.somewhere.com/whatever\n";
$url =~ s/,/%2c/g; # URL's with commas cause trouble.
if ($ENV{'DISPLAY'})
{
fork && exit;
if (! fork)
{
open(STDOUT, ">/dev/null");
open(STDERR, ">&STDOUT");
exec "netscape", "-noraise", "-remote", "openURL($url,newwindow)";
exit $!;
}
wait;
if ($?)
{
exec "netscape", $url;
die "netscape: $!\n";
}
}
else
{
exec "lynx", $url;
die "lynx: $!\n";
}
--
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: changing tag deleting behavior
Eugene Lee <[EMAIL PROTECTED]> wrote: > > Often I will tag lots of messages with certain subjects (usually when > the thread has become a flame fest), then do a ";d". But I'd like > that action to also untag the messages at the same time, which ";s" > does. I have always considered the 'untag-on-save' feature to be a bug. It is an inconsistency in the way Mutt handles tagged messages, because no other operation causes the tags to be removed after performing the operation. That means that, if I do tag-save a bunch of messages, there's no way for me to un-delete only those messages that I tagged, because the tags are removed for me. But I digress. :) > (Yes, I'm almost too lazy to do ";t" ;-) And also too lazy to install the development Mutt 1.1? It already has the feature that you want! :) I have been using the devel-versions of Mutt for over a year now, and I find them to be extremely stable and useful. Even moreso now, because the developers are targeting a final release, so things are stabilizing even more. > BTW, I noticed that if I try to ";s" to /dev/null, it fails! > > fcntl: Invalid argument (errno = 22) Yes, Mutt wants to lock '/dev/null' and cannot do so. I don't know whether to call that a bug or af eature. :) -- 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: home/end/pageup/pagedown don´t work
John E. Davis <[EMAIL PROTECTED]> wrote: > > > If I remember rightly, slang does not use terminfo > > It uses terminfo on systems that have it. For others, it uses termcap. Thanks, I'll stop spreading misinformation now. :) -- 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: changing tag deleting behavior
Eugene Lee <[EMAIL PROTECTED]> wrote: > > I know I can do this by setting up a new key, but I'd rather invent no > new keystrokes if possible. Or should I just start practicing the > habit of tag-save to /dev/null? :) Is this really what you do? Waste time writing messages to /dev/null (it isn't lightning-fast!), just to un-tag the messages? My favorite way to untag all tagged messages is ";t", which means "apply the 'tag' command to all tagged messages". It's quick and painless. :) -- 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: home/end/pageup/pagedown don´t work
Jens Wilhelm Wulf <[EMAIL PROTECTED]> wrote: > > I thought that the codes from terminfo are the ones programs see (if > they use it, no matter how it is done), and so it is important that > terminfo is correct. The codes you refer to in terminfo are actually strings, whereas the value KEY_NPAGE is simply a number. A number is much easier for a computer to handle than just a string. > Why does ncurses do a second translation? Keep in mind that there are two major methods for handling terminals: terminfo and termcap. Some curses systems do not use terminfo at all, and so that is another reason to create an abstraction layer above terminfo/termcap: So that a curses program does not need to know what the underlying terminal access method is, and is thus more portable. > But what about the fact that my mutt is linked against slang, not > curses? (I mentioned this in my first mail!) I can't remember every message sent to me. :) > slang defines: > #define SL_KEY_PPAGE0x105 > #define SL_KEY_NPAGE0x106 > #define KEY_PPAGE SL_KEY_PPAGE > #define KEY_NPAGE SL_KEY_NPAGE You are correct that these are the codes you should be paying attention to. My assumption that you were using ncurses was incorrect. > So I linked David's program to slang instead of curses and got: > > 412/415 for pageup/pagedown and 017 for home/end. THAT looks like > what mutt sees. If I remember rightly, slang does not use terminfo, but termcap instead. I suppose that means you should check for /etc/termcap, and see if you can find your terminal defined there. > My problem is that 0x105 is 261 and not 415 or 522. I (and Mikko) was using "octal" (base 8) representation for these numbers. Octal 412 is hex 0x10a, and 415 is 0x10D. Looking these up in slang.h, I find: #define SL_KEY_A3 0x10A #define SL_KEY_C3 0x10C I don't know offhand what those keys mean, or why slang wants to treat your page up/down keys with these codes. > I can't even do a quick hack to mutt, as it gets 017 for more than > one key. Octal 17 is the representation for -1, which is an error return from getch(). I guess that means it doesn't understand what key you pressed? Anyway, it seems to me that ncurses works the way you expect in this case, and slang does not. Either way, however, Mutt is not the source of the problem. -- 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: home/end/pageup/pagedown don´t work
Jens Wilhelm Wulf <[EMAIL PROTECTED]> wrote: > > now tried xkeycaps and changed keysym from next/prior to > KP_next/KP_prior. Doesn't help, too. That's probably because they were already set correctly. > To finally see what happens it must be possible to make mutt tell me > which key(sym/code) it sees Mutt does not see X-style keysyms. Mutt sees ncurses-style key codes, such as those found in /usr/include/ncurses.h: /* * Pseudo-character tokens outside ASCII range. The curses wgetch() * function will return any given one of these only if the * corresponding k- capability is defined in your terminal's * terminfo entry. */ [...] #define KEY_NPAGE 0522/* Next page */ #define KEY_PPAGE 0523/* Previous page */ As you can see, Mutt calls a function called wgetch(), to get a "key" from the keyboard. If that function returns 0522, then Mutt knows that you pressed the "next page" key, which Mutt calls "". So you see, it falls upon the curses subsystem to recognize the escape code for the key you have pressed, and return the proper code to Mutt. How is this done? Through the terminfo database. Curses knows that your terminfo database contains an entry called "knp" that determines the key sequences that represents "Key for Next Page". When that sequence of input characters is noticed, then the KEY_NPAGE value will be returned. So you see, if the terminfo database is correct, then this should all work. You have not demonstrated to anyone here that your terminfo database actually *is* correct, so we will continue to tell you that you should investigate that option. > Maybe there's a patch. Doesn't the maintainer read this list? I believe that nearly every person who has submitted code to the Mutt project is reading this list. The answer to your problem is still the same. Since we cannot see all the elements of your system that are coming together to create the interaction known as "your login session", we must guess at the most likely problems, and you must demonstrate that our guesses are not the source of your problem before we can produce more. -- 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: home/end/pageup/pagedown don't work
Jens Wilhelm Wulf <[EMAIL PROTECTED]> wrote: > > > That is, generate a file with infocmp, edit it, then compile that > > file with tic. Is that what you did? > > Yes, I think so: > --- > infocmp $TERM > tmp.dat > (edited the file) > tic -c tmp.dat > tic tmp.dat > --- Yes, but, you said this in your earlier message: > I changed terminfo to ^[[5~ and so on as Marius suggested. But > "infocmp $TERM" still gives the same codes. Since the change is not taking effect, you apparently aren't changing the terminfo database.. ?? -- 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: home/end/pageup/pagedown don't work
Jens Wilhelm Wulf <[EMAIL PROTECTED]> wrote: > > -- > infocmp $TERM: > khome=\EOH, kend=\EOF > knp=\E[6~, kpp=\E[5~ > > -- > cat > /dev/null: > ^[[H > ^[[F > ^[[5~ > ^[[6~ > -- > emacs -nw: > ^[OH > ^[OF > ^[[5~ > ^[[6~ > -- VT100 terminals have two "modes", application and normal mode. The application mode returns the "\EO" sequences, while normal mode returns the "\E[" sequences. I have no idea why this is done. Ask DEC what they had in mind. :) > So jed sees different codes for home/end (but they don´t work ;-) The mode of the terminal is controlled by escape sequences being sent. You probably have ncurses putting the terminal into one mode, and slang putting it into the other mode. > I changed terminfo to ^[[5~ and so on as Marius suggested. But > "infocmp $TERM" still gives the same codes. Did the change not work > or are these things just different notations for the same codes? In order to make changes to the terminfo database, you must run "tic". That is, generate a file with infocmp, edit it, then compile that file with tic. Is that what you did? -- 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: color index for list mail - changed to color of select bar
Eric Smith <[EMAIL PROTECTED]> wrote: > > | > ~N and ~l is bold yellow > | > ~l only is yellow > > I tried and still now try to put those two conditions into a single > color index command, I get: Error in /home/eric/.muttrc, line 343: > too many arguments This is the syntax you're probably looking for: color indexyellow default '~l' color index brightyellow default '~N ~l' I ran into a problem while testing this. If I put these statements in the opposite order, all list messages come out yellow, even if they are new. The reason must be that all color-index commands are scanned for matches, and a new, list message matches BOTH patterns, and the later one applies. So put the more specific pattern last, and it now works the way you want it to. Also, the pattern needs to be quoted if it has more than one element. Actually, quoting patterns seems to be always a good idea in .muttrc. -- 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: bind
Martin Keseg - Sun Slovakia - SE <[EMAIL PROTECTED]> wrote:
>
> Is here way to bind macro to or \c. I try it with
> mutt 1.1.4 but with no success.
A standard xterm does not generate different key sequences for shift-tab
or ctrl-tab. You would have to tell your xterm to generate a special
sequence, and then tell Mutt how to recognize it. For instance, in
.Xdefaults:
XTerm.vt100.translations: #override \
ShiftTab: string("\033\011")
Then in Mutt:
macro index \e "~F"
P.S. All untested! Caveat Hackor! :)
--
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: Oddball maildir behavior
David Shaw <[EMAIL PROTECTED]> wrote: > > I'm using set mark_old now, but I do miss the old mbox behavior. I > just don't feel good about trusting mboxes anymore. It actually is possible for a maildir folder to have messages with status "N", yet still not appear as "new" in the folder browser. If the message is renamed from the "new" subdir to the "cur" subdir, but the filename is changed to add ":N" as a status flag, then Mutt will still mark the message as "N" but won't notice the message when scanning for new mail in the folder. I did this once, manaually, when I really wanted that feature in one of my maildirs... Can't remember why, though. :) Anyway, since the maildir structure allows for it, it might be possible for Mutt to do it. But someone else will have to code the patch.. :) -- 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: Oddball maildir behavior
David Shaw <[EMAIL PROTECTED]> wrote: > > I just started using maildirs instead of mbox files. Now, whenever I > leave a maildir, whether or not I made any changes, it always reports > "New mail in " from the maildir I just left. Any ideas why? A maildir has new mail iff there are files in its "new" subdirectory. Did you leave the folder with some messages still marked as "N"? If so, they are in the "new" subdir, and thus the maildir has new mail, even if you just left it. Mboxes don't operate that way; new mail is detected by checking the timestamp on the mbox file. Some people (like me) prefer the mbox method, where leaving a folder with new mail means Mutt won't care about the folder anymore until new mail shows up in it. Others seem to want the maildir-ish behavior, where messages marked as "new" will always get Mutt's attention, even if you left them in the folder. Nice that people can have it whichever way they like. :) -- 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: w3m and text/html
Jason Helfman <[EMAIL PROTECTED]> wrote: > > I am using redhat, what is the file that you can specify for mutt to > use without sacrificing the integrity of netscape's mailcap It is unfortunate that Mutt and Netscape can't share a mailcap file. Your best bet is to maintain two different mailcap files. I name mine ".mailcap.mutt", and set Mutt to use it like this: set mailcap_path=~/.mailcap.mutt The main difference is that ~/.mailcap has entries in this format: video/*;xanim +Sr +B +Ae "%s" >/dev/null audio/x-pn-realaudio; raplayer "%s" application/pdf;acroread -tempFile "%s" application/postscript; ghostview "%s" while ~/.mailcap.mutt puts them in this format: text/html; lynx -dump -force_html %s; copiousoutput image/*;xv %s video/*;xanim +Sr +B +Ae %s >/dev/null audio/x-pn-realaudio; raplayer %s application/pdf;acroread -tempFile %s application/postscript; ghostview %s application/x-gzip; gzcat %s; copiousoutput application/x-gunzip; gzcat %s; copiousoutput application/octet-stream; octet-view %s; copiousoutput The main difference is that Netscape will not quote filenames correctly, so you must use "%s" to keep from getting errors on files with spaces in them. Also notice that formats Netscape can handle internally are not represented in the .mailcap file. -- 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: Charsets translation
Anatoly Vorobey <[EMAIL PROTECTED]> wrote: > > a) With charset=iso-8859-1 incorrectely written in Content-Type: header > b) With charset=koi8-r correctly written in Content-Type: header Messages of type (a) are broken, and you should inform the sender that their mail software is incorrectly configured. What is the point of having a Content-Type header if it is wrong a lot of the time? It might as well not be there. So you should try to get people to goad their administrators to fix things. In the meantime, you might consider a mail filter that will rewrite incorrect Content-Type headers into the correct values. For instance, you could detect mail from a particular sender, and rewrite headers that you know he sends out that are broken. -- 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: trouble with -[yZ]
Mikko Hänninen <[EMAIL PROTECTED]> wrote: > > And yes, mutt -y shouldn't exit silently... mutt -Z will likely start > to work too once you get mutt -y working. Mutt might not be exiting "silently"; it might actually be crashing, and wants to dump core, but can't for some reason. -- 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: Reply-To more than one recipient
Mikko Hänninen <[EMAIL PROTECTED]> wrote: > > My Mutt (1.1.3) behaves differently too. Pressing "r" and "y" will > reply to both addresses, "r" and "n" to just the iberia.es address. I think this behavior will make more sense if you instead look at it this way (and maybe you are, but it's not clear from reading here): If you say "yes", then Mutt will reply to the address(es) in the Reply-To: header. If you say "no", then Mutt will reply to the address in the From: header. I don't remember if it is legal to put more than one address in the From: header. -- 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: Content-Type: message/partial ?
Byrial Jensen <[EMAIL PROTECTED]> wrote: > > I will suggest that you copy the 5 parts in sequence to a new mbox > folder, and then reassemble the original message in an editor by > deleting the overhead from splitting it in parts: This is a cumbersome method, and while it works, if you end up doing this on a regular basis, it is no fun at all. The "mpack" tools know how to deal with multipart MIME messages, and will decode them for you. This means you would need to pipe each part as a separate message to "munpack" (set pipe_split, unset pipe_decode, tag all messages, and pipe them to the command "munpack"). Admittedly, this isn't much fun, either, but it's easier. -- 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: save-hook
A.V. Jayanthan <[EMAIL PROTECTED]> wrote: > > My question here is that, what do I do in .muttrc so that when I press > 's' to save a mail received from this mailing list, it should > automatically show =mutt, the folder into which I save all these > mails. save-hook '~C mutt-users' +mutt-users -- 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: Sample Color Schemes?
Adam Sherman <[EMAIL PROTECTED]> wrote: > > Does anyone have some good looking color schemes? I do. ;) > I tried a few that I found on the web, they were pretty awful... Well, try this: Colorization color indexwhite black ~F color header brightwhite black ^From: color header brightgreen black ^Subject: color body black green '^Good signature from user ".*"' color body black green '^gpg: Good signature from ".*"' color body black red '^Bad signature from user ".*"' color body black red '^gpg: BAD signature from ".*"' color body brightgreen black '[a-z0-9][-a-z_0-9/.%+]+@[-a-z_0-9.]+\.[-a-z]+' color body brightyellowblue '((https?|ftp)://|www\.)[-a-z_0-9@#$%&+=:;'~,./?]+[a-z_0-9/]' Non-Colorization mono index bold~F mono headerbold^From: mono headerunderline ^Subject: mono body bold'^(Good|Bad) signature from user ".*"' mono body bold'[a-z0-9][-a-z_0-9/.%+]+@[-a-z_0-9.]+\.[-a-z]+' mono body underline '((https?|ftp)://|www\.)[-a-z_0-9@#$%&+=:;'~,./?]+[a-z_0-9/]' -- 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: New mail notification
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Mutt does notify me when I run it (in the new=x, folders with new > mail). The problem is that when I change to that folder and leave > without having read all the new mail, mutt will tell me that I have no > folders with new mail. I think this is a limitation of mbox folders. The only 'easy' way to determine if there is new mail, is to check the access time, and reading the folder causes that time to be changed. Mutt could try to actually read every folder you tell it, and look for messages with the proper Status, but that would be slow, and you probably wouldn't like it. > Does anyone have know how could I get mutt to do what I want? Should > I change the mailbox format (MMDF, MH, Maildir) to do this? If you use Maildir folders, Mutt will always be able to easily tell if there is new mail. If this is feasible for you, you should go ahead and switch to Maildir format. -- 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: muttzilla
Jason Helfman <[EMAIL PROTECTED]> wrote: > > If anyone out there is using muttzilla, is their a way to have an > email open in alternative Xterm, like Konsole, or rxvt? I use a similar program called altmail_mutt, which is basically a hack of the altmail_elm program that somebody posted here several months ago. In that system, the "xterm" command is hard-coded into the library, so if you want to change it, you must edit the code. Not too hard, if you're a programmer. -- 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: Configuration Problem
dept4 <[EMAIL PROTECTED]> wrote: > > I am having problems with the From field of my header when I send out > a e-mail. I seems to have garbage infront of my e-mail address. What do you mean by "garbage"? Random characters? Something that just doesn't make sense? You might want to post the "garbage" here, so that we can see what you're talking about. It might be something important that you're simply not familiar with. -- 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: printing from mutt
Brad Cramer <[EMAIL PROTECTED]> wrote: > > Reply-To: > I am using a2ps to format [...] Your message starts with Reply-To: because you are always supposed to put a blank line between the message headers, and your text. Since you didn't, the empty Reply-To header is treated as part of your message. You should change your E-mail habits accordingly. :) -- 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
