Re: Can't send mail
On Wed, May 02, 2001 at 12:06:15AM +0100, Barry Mitchelson wrote: Hi, all of a sudden I can't send email. Mutt gets to the point where it launches my editor to actually compose the email and just hangs. I'm guessing it may have something to do with the new version of vim I installed. My question is, how can I change mutts default editor to something like pico so that I can see if vim is causing the problem. I tried changing the EDITOR env var to pico, and adding 'set editor=pico' to my .muttrc but it still hangs. any ideas ? I don't know what might be causing mutt to hang, but I think it's safe to say that it isn't your editor. What you did correctly sets the editor to pico. And it's not a path issue, either. If the editor you specify doesn't exist, Mutt should just come back saying it's aborting the unmodified message. Good luck with finding the problem. -- Luke
Re: x-face
Have a look at http://www.spinnaker.de/mutt/view-x-face. this is fine! do you as well know a method to cleanly insert my x-face into my muttrc using my_hdr? which characters have to be quoted? i quoted [;'$`\] and i got a completely shafted face :( tx andré -- I am the greataxe of the Dwarf Father!
File permissions?
Hi, How do I set the file permissions for my saved mail? I've looked through the documentation and can't find any setting for this (there's nothing mentioning umask, perm or mode). When mail gets saved it creates files with 600 permissions whereas I want 660. Thanks, Mark Sheppard.
Re: mutt appends @hostname while using alias
ZHENG, You-Zhong ([EMAIL PROTECTED]) said something to this effect on 05/02/2001: I try the alias function, I define some, but each time I type an alias, mutt automatically append @myhostname for me. How to prevent mutt from doing this? Are you sourcing the file to which the aliases are being added ($alias_file)? If the file is not being sourced, then the alias is taken to be a local user, so the hostname is appended. # set alias_file=~/.muttrc # # Name: alias_file # Type: path # Default: ~/.muttrc # # # The default file in which to save aliases created by the # ``create-alias'' function. # # Note: Mutt will not automatically source this file; you must # explicitly use the ``source'' command for it to be executed. # Note the last paragraph. (darren) -- Elegance and truth are inversely related. -- Becker's Razor
Re: x-face
On (02/05/01 11:25), Andre Bonhote wrote: Have a look at http://www.spinnaker.de/mutt/view-x-face. this is fine! do you as well know a method to cleanly insert my x-face into my muttrc using my_hdr? which characters have to be quoted? i quoted [;'$`\] and i got a completely shafted face :( This really interests me. If anyone finds a way to include X-Face headers by default, please post it to the list so that I can take notes... I've never received mail with an X-Face header, but if I can spread the word among the people I converted to mutt, I might... Ailbhe -- Homepage: http://ailbhe.ossifrage.net/
Re: mutt appends @hostname while using alias
Don't forget to put a source .mail_aliases or whatever your alias file is to make sure mutt reads it upon starting up. Eric Hi everyone, I try the alias function, I define some, but each time I type an alias, mutt automatically append @myhostname for me. How to prevent mutt from doing this? zhengyz -- WorldCom Company=== Eric Ekong [EMAIL PROTECTED] Dial Systems Engineer Ann Arbor: 734-214-7435 http://www.worldcom.com Fax:734-214-7410 http://www.uu.net/ Pager: 888-806-8347 = Real Admins Use VIM
Re: File permissions?
mutt's umask is inherited from the environment that started mutt. In other words, its using your umask, so change your umask (umask 06). If you just want mutt's umask to be different, write a script to start mutt that sets the umask then execs mutt. --- umutt --- #!/bin/sh umask 06 exec mutt $* - Sam Quoting Mark Sheppard [EMAIL PROTECTED], who wrote: How do I set the file permissions for my saved mail? I've looked through the documentation and can't find any setting for this (there's nothing mentioning umask, perm or mode). When mail gets saved it creates files with 600 permissions whereas I want 660. -- Sam Roberts [EMAIL PROTECTED]
Re: File permissions?
Hi,
The umask in my shell is set to 022, meaning that any files created
should have permissions 644 (or 755 if executable) by default.
However this isn't happening with mutt. I just did an strace on mutt
and it shows that mutt is setting its own umask of 077 (the result of
the umask call is the old umask):
[...]
time(NULL) = 988818808
umask(077) = 022
ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0
[...]
Is there any way to tell mutt to use a different umask?
Mark.
On Wed, May 02, 2001 at 11:00:04AM -0400, Sam Roberts wrote:
mutt's umask is inherited from the environment that started mutt.
In other words, its using your umask, so change your umask (umask 06).
If you just want mutt's umask to be different, write a script to start
mutt that sets the umask then execs mutt.
--- umutt ---
#!/bin/sh
umask 06
exec mutt $*
-
Sam
Quoting Mark Sheppard [EMAIL PROTECTED], who wrote:
How do I set the file permissions for my saved mail? I've looked
through the documentation and can't find any setting for this (there's
nothing mentioning umask, perm or mode). When mail gets saved
it creates files with 600 permissions whereas I want 660.
--
Sam Roberts [EMAIL PROTECTED]
Re: File permissions?
On Wed, May 02, 2001 at 05:00:51PM +0100, Mark Sheppard ([EMAIL PROTECTED]) wrote: Hi, The umask in my shell is set to 022, meaning that any files created should have permissions 644 (or 755 if executable) by default. However this isn't happening with mutt. I just did an strace on mutt and it shows that mutt is setting its own umask of 077 (the result of the umask call is the old umask): Yep -- strangely enough, this came up in a conversation with a friend yesterday. Mutt sets umask 077 in main.c and doesn't touch it from thereon in; there was some talk back in 1998 of fixing that, and patches were submitted but not included. I suggested to said friend that he prepare a patch which introduces a mailbox_umask and file_umask variable (the former for mailboxes and the latter for anything that isn't, such as attachments), but I don't think he'll be able to put it together. It has always struck me that while doing umask 077 is a good thing in case a user is lazy with such things, that mutt isn't the sort of mailer to step around a lazy user. :-) On the other hand, having to set umask in the shell before launching Mutt is inconvenient too, so just pulling that umask call out of main.c isn't doing any favours either. -devvies, I couldn't pick up the whole history of the 1998 edition of Include That Umask Patch to determine the reasons that it didn't get put in; would such a patch be welcome? -Rich -- -- Rich Lafferty --- Sysadmin/Programmer, Instructional and Information Technology Services Concordia University, Montreal, QC (514) 848-7625 - [EMAIL PROTECTED] --
Re: File permissions?
That I would believe would just be the perms on the parent directory. On Wed, May 02, 2001 at 11:35:49AM +0100, Mark Sheppard muttered: | Hi, | | How do I set the file permissions for my saved mail? I've looked | through the documentation and can't find any setting for this (there's | nothing mentioning umask, perm or mode). When mail gets saved | it creates files with 600 permissions whereas I want 660. | | Thanks, | Mark Sheppard. -- /Jason G Helfman At any given moment, you may find the ticket to the circus that has always been in your possession. Fingerprint: 6A32 3774 E390 33B5 8C96 2AA1 2BF4 BD71 35A1 C149 GnuPG http://www.gnupg.org Get Private! 1024D/35A1C149
RE: debian-user save hook
see http://www.mutt.org/doc/manual/manual-4.html#ss4.2 Good stuff! HTH, George -Original Message- From: Dale Morris [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 01, 2001 11:17 PM To: [EMAIL PROTECTED] Subject: Re: debian-user save hook I do it like this in my muttrc, is there a better way, maybe one that works for all subscribed lists with a single command? subscribe mutt-users@ fcc-save-hook '~C mutt-users' =mutt-users What does '~C mean here? I want to save messages from from +debian-user mailbox to a +support mailbox subscribe debian@ fcc-save-hook '~C debian'=support ?? I'm confused. subscribe sawfish@ fcc-save-hook '~C sawfish'=sawfish Sam -- Sam Roberts [EMAIL PROTECTED]
Re: debian-user save hook
man muttrc ~C EXPR message is either to: or cc: EXPR So, messages with debian in To: or Cc: headers will go to =support mailbox. igor On Tue 01 May 2001, Dale Morris wrote: I do it like this in my muttrc, is there a better way, maybe one that works for all subscribed lists with a single command? subscribe mutt-users@ fcc-save-hook '~C mutt-users' =mutt-users What does '~C mean here? I want to save messages from from +debian-user mailbox to a +support mailbox subscribe debian@ fcc-save-hook '~C debian'=support ?? I'm confused. subscribe sawfish@ fcc-save-hook '~C sawfish'=sawfish Sam -- Sam Roberts [EMAIL PROTECTED]
How eliminate (same 2) *questions* when exit mutt?
How prevent mutt from always asking if I want to move email to mbox and if I _really_ want to delete the email I just deleted when I exit mutt? Does anyone else not want to answer the same 2 questions every day for the rest of their lives? (Especially when answer is always the same.) I love mutt, Chris -- === Dr. Christian Seberino === SPAWARSYSCEN D02P || (619) 553-2564 49330 ELECTRON DR || SAN DIEGO CA 92152-5451|| [EMAIL PROTECTED] ===
Re: How eliminate (same 2) *questions* when exit mutt?
On Wed, May 02, 2001 at 10:42:12AM -0700, Dr Christian Seberino wrote: How prevent mutt from always asking if I want to move email to mbox and if I _really_ want to delete the email I just deleted when I exit mutt? Does anyone else not want to answer the same 2 questions every day for the rest of their lives? (Especially when answer is always the same.) I have these in my .muttrc The middle option helps eliminate another question set confirmappend = no # set confirmcreate = no set delete=yes I love mutt, Me too! -- Phil Linux: Viagra for the PC Naomi's Fancy: http://naomisfancy.virtualave.net/ My page: http://naomisfancy.virtualave.net/phil.html Cyber Tionol: http://tionol.virtualave.net/
Re: How eliminate (same 2) *questions* when exit mutt?
Dr. Christian Seberino wrote: How prevent mutt from always asking if I want to move email to mbox and if I _really_ want to delete the email I just deleted when I exit mutt? Does anyone else not want to answer the same 2 questions every day for the rest of their lives? (Especially when answer is always the same.) Use the $delete aned $move variables. These are both quad-option variables, accepting values of 'yes', 'no', 'ask-yes', and 'ask-no'. For example, in ~/.muttrc (or another sourced file): set delete=yes # Really delete messages when closing or # synchronizing a mailbox, (without asking.) set move=no # Do not move (or ask to move) read messages from # $spoolfile to $mbox Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: File permissions?
On 2001-05-02 12:41:12 -0400, Rich Lafferty wrote: Yep -- strangely enough, this came up in a conversation with a friend yesterday. Mutt sets umask 077 in main.c and doesn't touch it from thereon in; there was some talk back in 1998 of fixing that, and patches were submitted but not included. First of all, I'm quite sure that mutt isn't the only mailer which is paranoid about umasks. Second, on many systems you'll find lots of users who have whatever loose umasks - which are frequently fine for most of the stuff they are storing on the system, except e-mail. Think about it as mutt failing on the safe side, that is, in favor of e-mail confidentiality. -- Thomas Roessler [EMAIL PROTECTED]
Re: File permissions?
On Wed, May 02, 2001 at 07:08:28PM +0200, Thomas Roessler ([EMAIL PROTECTED]) wrote: On 2001-05-02 12:41:12 -0400, Rich Lafferty wrote: Yep -- strangely enough, this came up in a conversation with a friend yesterday. Mutt sets umask 077 in main.c and doesn't touch it from thereon in; there was some talk back in 1998 of fixing that, and patches were submitted but not included. First of all, I'm quite sure that mutt isn't the only mailer which is paranoid about umasks. Second, on many systems you'll find lots of users who have whatever loose umasks - which are frequently fine for most of the stuff they are storing on the system, except e-mail. Think about it as mutt failing on the safe side, that is, in favor of e-mail confidentiality. I agree completely that it should fail on the safe side; I just want to see a don't fail option, and it seems straightforward to provide one. What I imagine is this: mbox_umask and attach_umask default to 077. If the user explicitly configures mbox_umask to be something else, that's used when creating mailbox files/maildirs. If the user explicitly configures attach_umask to be something else, then that's used when saving files which aren't mailboxes (and creating directories, should mutt ever do that outside of maildir/MH context). The exception to this would be temporary message files ready to be opened by an editor, which would always be 077. In other words, make it so that it can be configured user-by-user, rather than installation-by-installation as it is presently. Does that sound reasonable? -Rich -- -- Rich Lafferty --- Sysadmin/Programmer, Instructional and Information Technology Services Concordia University, Montreal, QC (514) 848-7625 - [EMAIL PROTECTED] --
Maildir folder summaries, hashes, etc.
I am subscribed to a LOT of mailing lists. 34, actually. And I find myself switching around between them fairly often as I try to keep up on the latest news with various projects. There are a couple things that I wish mutt could do: 1. Build a hash index of all of the info displayed in the index so it doesn't have to scan every file in the maildir (or read the whole mbox for those using mbox) every time I open the folder as well as check for new emails and only read those once to get the info for the hash index. I've never seen a Unix/Linux based mailreader that actually does this. They all seem to scan the whole folder every time. The info could be stored in a ~Maildir/.indexhash file or something and regenerated if it is deleted for some reason. 2. Display a summary of how many read/unread/etc. in the folder list. 3. A faster and easier way to switch from one folder to another. Currently I hit c ? j as many times as necessary to get to the next folder I want to read \n It would be nice if I could just hit N to go to the next folder. There may be a way to do this with macros already but I'm not sure how one would get the next folder name. This wouldn't be all that useful until the above mentioned has index was working anyway due to the slow speed of parsing the folders. -- Tracy Reed http://www.ultraviolet.org
Re: Maildir folder summaries, hashes, etc.
On Wed, May 02, 2001 at 12:19:29PM -0700, Tracy R Reed wrote: There are a couple things that I wish mutt could do: 1. Build a hash index of all of the info displayed in the index so it doesn't have to scan every file in the maildir (or read the whole mbox for those using mbox) every time I open the folder as well as check for new emails and only read those once to get the info for the hash index. I've never seen a Unix/Linux based mailreader that actually does this. This would be nice. I believe an early version of Netscape Mail did this. Jamie Zawinski wrote it (and about it at http://doc/mailsum.html). 3. A faster and easier way to switch from one folder to another. Currently I hit c ? j as many times as necessary to get to the next folder I want to read \n It would be nice if I could just hit N to go to the next folder. There may be a way to do this with macros already but I'm not sure how one would get the next folder name. This wouldn't be all that useful until the above mentioned has index was working anyway due to the slow speed of parsing the folders. Try c followed by space to cycle through all folders with new mail. This only displays the folder name, and only those folders listed in the mailboxes variable. It doesn't have to read the folder, so it's quick. Tim
Re: Maildir folder summaries, hashes, etc.
On Wed, May 02, 2001 at 12:19:29PM -0700, Tracy R Reed wrote: I am subscribed to a LOT of mailing lists. 34, actually. And I find myself switching around between them fairly often as I try to keep up on the latest news with various projects. There are a couple things that I wish mutt could do: 1. Build a hash index of all of the info displayed in the index so it doesn't have to scan every file in the maildir (or read the whole mbox for those using mbox) every time I open the folder as well as check for new emails and only read those once to get the info for the hash index. I've never seen a Unix/Linux based mailreader that actually does this. They all seem to scan the whole folder every time. The info could be stored in a ~Maildir/.indexhash file or something and regenerated if it is deleted for some reason. Would be nice... 2. Display a summary of how many read/unread/etc. in the folder list. Yeah, $folder_format should be able to do this. 3. A faster and easier way to switch from one folder to another. Currently I hit c ? j as many times as necessary to get to the next folder I want to read \n It would be nice if I could just hit N to go to the next folder. There may be a way to do this with macros already but I'm not sure how one would get the next folder name. This wouldn't be all that useful until the above mentioned has index was working anyway due to the slow speed of parsing the folders. typing: c =mutt and using tab completions are a faster way to switch. Or: c spacespace etc. will scroll through all your mailboxes with new mail. There are some pretty good ideas. Why don't you post them of the mutt-dev list and see what they say? -- Brian Nelson [EMAIL PROTECTED]
Re: Saving read messages to mbox over IMAP
On Tue, May 01, 2001 at 08:14:02AM -0400, Jim Toth wrote:
I did a little bit of experimentation, and set move worked ok with an
imap mbox and local spoolfile, but not ever with an imap spoolfile,
FWIW.
1.2.5 seems to have the same problem (I'm begining to suspect it's a
feature for set move not to work with an imap spoolfile) although I
didn't try all the possibilities. I'd try with 1.0.1, but the one I
have doesn't have imap support compiled in.
For anyone that cares, I discovered the work-around is to use URL
style formatting for the spoolfile variable:
set spoolfile=imap://bignachos.com/INBOX
instead of:
set spoolfile={bignachos.com}INBOX
Apparently, mutt uses URL formatting internally and fails to realize
that {bignachos.com}INBOX == imap://bignachos.com/INBOX.
--
Brian Nelson [EMAIL PROTECTED]
Re: Saving read messages to mbox over IMAP
goodday!
Apparently, mutt uses URL formatting internally and fails to realize
that {bignachos.com}INBOX == imap://bignachos.com/INBOX.
how do u do this for ssl'd imap [imaps/port 993].
have tried changing mail box by specifying
imaps://imapserver.domain/mailboxname
imap://imapserverver.domain/mailboxname:993
and did'nt work.
mabuhay! barryg
Re: Saving read messages to mbox over IMAP
On Thu, May 03, 2001 at 07:49:29AM +0800, Barry Dexter A. Gonzaga wrote:
goodday!
Apparently, mutt uses URL formatting internally and fails to realize
that {bignachos.com}INBOX == imap://bignachos.com/INBOX.
how do u do this for ssl'd imap [imaps/port 993].
have tried changing mail box by specifying
imaps://imapserver.domain/mailboxname
imap://imapserverver.domain/mailboxname:993
and did'nt work.
mabuhay! barryg
Use whatever appears in the %f field in $status_format
And, be sure to put quotes around it.
--
Brian Nelson [EMAIL PROTECTED]
easy way to hide messages?
Is there an easy way to get mutt to ignore messages that match a certain pattern? I figure I could use l with an inverse pattern, but I have not been able to figure out how to use multiple invocations of l multiple times with cumulative effect (like you can use t multiple times). jafager
Re: Saving read messages to mbox over IMAP
goodday!
and that did'nt work too ;(
this is the %f field of $tatus_format
{imapserver.domain/ssl}INBOX
so i tried
imap://imapserver.domain/ssl/INBOX
imap://imapserver.domain/993/INBOX
imap://imapserver.domain:993/INBOX
imap://imapserver.domain:ssl/INBOX
imap://imapserver.domain:imaps/INBOX
imaps://imapserver.domain/mailboxname
imap://imapserverver.domain/mailboxname:993
and yes i want to use my imap folder to store postponed
mails, it does store it, but creating new mail does not
prompt me of postponed mail already stored.
i already store my sent mails to the imap server.
mabuhay! barryg
On Wed, May 02, 2001 at 08:59:36PM -0400, Brian Nelson wrote:
snip
Use whatever appears in the %f field in $status_format
And, be sure to put quotes around it.
Re: Saving read messages to mbox over IMAP
goodday On Wed, May 02, 2001 at 09:32:34PM -0400, Brendan Cully wrote: I seem to recall this was disabled in 1.2. Brian is using mutt from the development series (1.3.x). Sorry about that... snip this should clear up things up, not that urgent to disturb the developers, im sure they have more bugs/features to code. thanks guys for clearing that up. and long live mutt! mabuhay! barryg
Re: easy way to hide messages?
Just put them all together like so: !~f Brian !~f Barry This would hide all messages from Brian and Barry (BTW I'm not picking on anyone in particular just names that happened to be on a lot of emails in the mutt box at the time I wrote this and tested it). On Wed, May 02, 2001 at 09:00:21PM -0400, Jason A . Fager wrote: Is there an easy way to get mutt to ignore messages that match a certain pattern? I figure I could use l with an inverse pattern, but I have not been able to figure out how to use multiple invocations of l multiple times with cumulative effect (like you can use t multiple times). -- Ben Reser [EMAIL PROTECTED] http://ben.reser.org Pool is a game of racism for it is the white ball eliminating all the other races off the green felt earth.
Re: easy way to hide messages?
Jason A . Fager wrote: Is there an easy way to get mutt to ignore messages that match a certain pattern? I figure I could use l with an inverse pattern, but I have not been able to figure out how to use multiple invocations of l multiple times with cumulative effect (like you can use t multiple times). jafager Read the section of the manual regarding Complex Patterns for that info. You can specify more than one criterion to have them logically ANDed. You can use parentheses for logical grouping. There are logical NOT and OR operators, etc. -- Linux: The Choice of the GNU Generation
What wrong with my from email
My from email different with my header from in muttrc. What wrong with that. Please help me Thanks
