UMASK problem
Hello, normaly I am using courier-imap on my fileserver but now I was using direct access and running into an UMASK problem. The ~/Maildir has permission 1775 and the UMASK is set to 002 within my ~/.procmailrc and is set right if new messages arrive. But if I access Mailfolders, mutt change the MODE back to 600 on files and 700 on directories (if new one are created) How can I solv this problem? Note: The messages must be accessibel from oter $USER too. Thanks, Greetings and nice Day Michelle Konzack Systemadministrator 24V Electronic Engineer Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 +49/177/935194750, rue de Soultz MSN LinuxMichi +33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
HOW to set the UMASK?
Hello, My system is setup to use a UMASK=002 on my Maildir (procmail do the right thing) but if I read the messages with mut, they are after reading 0600 and can not more read fro another account. How can this solved? Thanks, Greetings and nice Day Michelle Konzack Systemadministrator 24V Electronic Engineer Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 +49/177/935194750, rue de Soultz MSN LinuxMichi +33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: HOW to set the UMASK?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday, May 10 at 01:13 AM, quoth Michelle Konzack: Hello, My system is setup to use a UMASK=002 on my Maildir (procmail do the right thing) but if I read the messages with mut, they are after reading 0600 and can not more read fro another account. How can this solved? Well, mutt attempts to preserve the umask of any mailbox that it reads. The only reason I can think of that it would get that wrong is if the stat() call on the mailbox failed. Try running mutt in debug mode and see if you get a line that says stat failed on x (where x is the name of the mailbox you're reading). ~Kyle - -- In all affairs it's a healthy thing now and then to hang a question mark on the things you have long taken for granted. -- Bertrand Russell -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkgppS8ACgkQBkIOoMqOI15i0gCfewb0DyXNVFH35aieZzPhw+YG us0AoMFpZ1BuFUxl5ymGIYWx/SXvYIef =KGAr -END PGP SIGNATURE-
Re: speed of cacheing depends on terminal?
[...] That's why they recently added $time_inc (it's not in a released version of mutt yet; just in the current development tree). Here's the description from the development manual: Sweet. My INBOX opens nearly instantaneously now. And I thought that it's the hcache being slow. Thank you -- Vlad pgpKCEHb8bwr9.pgp Description: PGP signature
mutt freeze my machine with kern 2.6.25 amd64
Hello, mutt works perfectly with Kernel 2.6.22 amd64 in CM but with kernel 2.6.25-1-amd64 (package debian) it freezes definitively my box (in CM) the problem doesn't occur with xwindow. Is it a bug of mutt or a bug of the kernel 2.6.25-1-amd64 ? -- Gérard
Re: mutt freeze my machine with kern 2.6.25 amd64
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday, May 13 at 06:27 PM, quoth Gerard Robin: Hello, mutt works perfectly with Kernel 2.6.22 amd64 in CM but with kernel 2.6.25-1-amd64 (package debian) it freezes definitively my box (in CM) the problem doesn't occur with xwindow. Is it a bug of mutt or a bug of the kernel 2.6.25-1-amd64 ? It should be impossible for a user program to do anything that freezes the kernel. If the kernel freezes, it is a kernel bug. ~Kyle - -- If God can work through me, he can work through anyone. -- St. Francis of Assisi -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkgpwzoACgkQBkIOoMqOI148MwCfS5iFRgigBa7tpKcjl/NtKQOb P0AAoP0i9u/+JIp6rYsYd73jArQ2PzyP =C+ro -END PGP SIGNATURE-
Re: pass single-quoted arguments to external script
On May 10 17:31, David Champion wrote: So how do I properly escape the single quotes in the vim args Personally, as soon as I start having trouble figuring out how to quote things withing multiple layers of parser, I ditch the headache and put the command into an external script that accepts only the minimum arguments from mutt (i.e., the values that only mutt knows). In you case, I guess that would be approximately: send-hook ... 'set editor=mutt-xvim' $ cat mutt-xvim #!/bin/sh exec xterm -e vim '+/^--[ ]*$' -c 'read some_file' $@ I know that's a level of abstraction away from what you were aiming for, but time is just too precious to spend it on all the various (and they indeed vary) quoting idiosyncrasies, unless that sort of thing is fun or educational for you. And by putting mutt-specific scripts into a mutt namespace, as it were, you're not really causing any layering conflicts. Hi David Of course, that's always an option and I do that in other situations. In fact, the solution here would be even simpler: send-hook ... set editor=\xterm -e vim '+/^--[ ]*$' -c 'read some_file' The reasons for the whole stunt are: 1) I'm using this xvim script in other places fairly frequently and pass some additional args to xterm inside it. Since I want to keep these in one place, I wanted to use the script rather than duplicating the command xterm options -e vim in my muttrc. 2) In different hooks, I pass different args to vim and was really looking for a (nearly) drop-in replacement vim - xvim. Otherwise one would have to create a mutt-xvim script for each hook. I thought it can't be so hard to do it from within muttrc. I'll see which workaround I choose should I finally give up fighting with Mutt's escaping conventions. steve
IMAP Issues (error / speed)
I'm on a fresh install of OSX (Leopard), and did a macport install of mutt-devel, (see bottom of email for config opts). I had no issues on my OpenBSD machine, but in moving my .muttrc over to this new machine, there are the following problems. 1) When sending an email, it hangs for a while (probably until connect_timeout seconds), then gives me the following error (obviously, gmail as the smtp server):Could not connect to gmail.com (Can't assign requested address). 2) When starting mutt, it sits on Looking up imap.gmail.com... for about 20 seconds before taking me into my default inbox. I've tried toggling imap_check_subscribed and imap_list_subscribed, but to no avail. Any suggestions would be appreciated ! Thanks ! == Dylan - Mutt 1.5.17 (2007-11-01) System: Darwin 9.2.0 (i386) ncurses: ncurses 5.6.20061217 (compiled with 5.6) libiconv: 1.11 hcache backend: GDBM version 1.8.3. 10/15/2002 (built May 13 2008 22:49:47) Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_INODESORT +USE_POP +USE_IMAP +USE_SMTP -USE_GSS +USE_SSL_OPENSSL -USE_SSL_GNUTLS +USE_SASL +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/mail PKGDATADIR=/opt/local/share/mutt SYSCONFDIR=/opt/local/etc EXECSHELL=/bin/sh -MIXMASTER To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please visit http://bugs.mutt.org/. patch-1.5.17.sidebar.20071102.txt patch-1.5.17.rr.compressed.1
