Re: mbox opened read only after update to mutt 1.4i
jochen issing wrote: > So you suggest me to setgid for mutt and/or mutt_dotlock and reset the > /var/mail directory again? chmod 1777 /var/mail should work too. whether you do this or make mutt_dotlock setgid mail is pretty much up to you. -- Will Yardley input: william < @ hq . newdream . net . >
Re: mbox opened read only after update to mutt 1.4i
On Thu, Sep 26, 2002 at 10:54:48AM +0200, Nicolas Rachinsky wrote: > * jochen issing <[EMAIL PROTECTED]> [2002-09-26 09:44 +0200]: > > On Wed, Sep 25, 2002 at 06:47:01PM +0200, Sven Guckes wrote: > > > * jochen issing <[EMAIL PROTECTED]> [2002-09-25 16:25]: > > > > > after my recent update to 1.4i, I am not able able to remove any mails > > > > > out of my spool files. I can open /var/mail/jochen with vim and can > > > > > write it, but mutt refuses writing. > > Because vim does not create a lockfile. > > > > > Ah, I have solved the Problem!! > > > > It was the directory access to /var/mail, which was rwxrwxr-x > > > > and I have been "other". Hence, I actually was not able to write > > > > into the directory. I find it quite interesting that mutt 1.4i > > > > has a problem with it and vim and my old mutt (1.3.28?) not. > > Either the old mutt or the old mutt_dotlock binary were setgid mail. > > > no, its owned by root,root. There are no suid bits set as > > for vim and I changed permission of the directory and everything > > works fine. > > If there are other users on your machine, your created a security hole > by this. > > Nicolas So you suggest me to setgid for mutt and/or mutt_dotlock and reset the /var/mail directory again? jochen -- jochen issing mailto:[EMAIL PROTECTED] http://www.mcf-music.de GPG:0A121BC
Re: mbox opened read only after update to mutt 1.4i
* jochen issing <[EMAIL PROTECTED]> [2002-09-26 09:44 +0200]: > On Wed, Sep 25, 2002 at 06:47:01PM +0200, Sven Guckes wrote: > > * jochen issing <[EMAIL PROTECTED]> [2002-09-25 16:25]: > > > > after my recent update to 1.4i, I am not able able to remove any mails > > > > out of my spool files. I can open /var/mail/jochen with vim and can > > > > write it, but mutt refuses writing. Because vim does not create a lockfile. > > > Ah, I have solved the Problem!! > > > It was the directory access to /var/mail, which was rwxrwxr-x > > > and I have been "other". Hence, I actually was not able to write > > > into the directory. I find it quite interesting that mutt 1.4i > > > has a problem with it and vim and my old mutt (1.3.28?) not. Either the old mutt or the old mutt_dotlock binary were setgid mail. > no, its owned by root,root. There are no suid bits set as > for vim and I changed permission of the directory and everything > works fine. If there are other users on your machine, your created a security hole by this. Nicolas
Re: mbox opened read only after update to mutt 1.4i
On Wed, Sep 25, 2002 at 06:47:01PM +0200, Sven Guckes wrote: > * jochen issing <[EMAIL PROTECTED]> [2002-09-25 16:25]: > > > after my recent update to 1.4i, I am not able able to remove any mails > > > out of my spool files. I can open /var/mail/jochen with vim and can > > > write it, but mutt refuses writing. > > Ah, I have solved the Problem!! > > It was the directory access to /var/mail, which was rwxrwxr-x > > and I have been "other". Hence, I actually was not able to write > > into the directory. I find it quite interesting that mutt 1.4i > > has a problem with it and vim and my old mutt (1.3.28?) not. > > check the permissions on the binary of mutt 1.3.28 then. > is it owned by root:other? no, its owned by root,root. There are no suid bits set as for vim and I changed permission of the directory and everything works fine. > as for vim - if it allows writing to the mail spool > then you can have lots of fun with it... If you think about using vim as a mail client, I don't think about fun ;-) jochen -- jochen issing mailto:[EMAIL PROTECTED] http://www.mcf-music.de GPG:0A121BC
Re: mbox opened read only after update to mutt 1.4i
* jochen issing <[EMAIL PROTECTED]> [2002-09-25 16:25]: > > after my recent update to 1.4i, I am not able able to remove any mails > > out of my spool files. I can open /var/mail/jochen with vim and can > > write it, but mutt refuses writing. > Ah, I have solved the Problem!! > It was the directory access to /var/mail, which was rwxrwxr-x > and I have been "other". Hence, I actually was not able to write > into the directory. I find it quite interesting that mutt 1.4i > has a problem with it and vim and my old mutt (1.3.28?) not. check the permissions on the binary of mutt 1.3.28 then. is it owned by root:other? as for vim - if it allows writing to the mail spool then you can have lots of fun with it... Sven
Re: mbox opened read only after update to mutt 1.4i
On Wed, Sep 25, 2002 at 02:33:24PM +0200, jochen issing wrote: > Hi List, > > after my recent update to 1.4i, I am not able able to remove any mails > out of my spool files. I can open /var/mail/jochen with vim and can > write it, but mutt refuses writing. > I found in the internet the configure switch --enable-extern-dotlock > and compiled it once more, but this did not help. > I am using debian woody stable. Ah, I have solved the Problem!! It was the directory access to /var/mail, which was rwxrwxr-x and I have been "other". Hence, I actually was not able to write into the directory. I find it quite interesting that mutt 1.4i has a problem with it and vim and my old mutt (1.3.28?) not. Thanks so far to Sven and David!! -- jochen issing mailto:[EMAIL PROTECTED] http://www.mcf-music.de GPG:0A121BC
Re: mbox opened read only after update to mutt 1.4i
On Wed, Sep 25, 2002 at 04:34:57PM +0200, jochen issing wrote: > On Wed, Sep 25, 2002 at 03:37:12PM +0200, Sven Guckes wrote: > > * jochen issing <[EMAIL PROTECTED]> [2002-09-25 12:39]: > > > after my recent update to 1.4i, I am not able able to remove > > > any mails out of my spool files. I can open /var/mail/jochen > > > with vim and can write it, but mutt refuses writing. > > > > sounds like a locking problem.. > > > > > I found in the internet the configure switch --enable-extern-dotlock > > > and compiled it once more, but this did not help. > > > I am using debian woody stable. > > > > but do you mind sharing more info than > > "mutt 1.4 on debian woody stable"? > > perhaps something like "mutt -v"? > > > > Sven > > Here you are: > > System: Linux 2.4.19 (i686) [using ncurses 5.2] > Einstellungen bei der Compilierung: > -DOMAIN > -DEBUG > -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE > +USE_FCNTL -USE_FLOCK > -USE_POP -USE_IMAP -USE_GSS -USE_SSL -USE_SASL > +HAVE_REGCOMP -USE_GNU_REGEX > +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET > +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM > +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT > +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET > +HAVE_LANGINFO_YESEXPR > +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID -HAVE_GETADDRINFO > ISPELL="/usr/bin/ispell" > SENDMAIL="/usr/sbin/sendmail" > MAILPATH="/var/mail" > PKGDATADIR="/usr/share/mutt" > SYSCONFDIR="/usr/etc" > EXECSHELL="/bin/sh" > -MIXMASTER And still more: -rwxr-xr-x1 root root 412136 25. Sep 12:07 /usr/bin/mutt* -rwxr-xr-x1 root root 7116 25. Sep 12:07 /usr/bin/mutt_dotlock* drwxrwsr-x2 root mail 4096 25. Sep 17:05 /var/mail/ -rw-rw1 jochen mail79673 25. Sep 17:05 /var/mail/jochen -- jochen issing mailto:[EMAIL PROTECTED] http://www.mcf-music.de GPG:0A121BC
Re: mbox opened read only after update to mutt 1.4i
On Wed, Sep 25, 2002 at 03:37:12PM +0200, Sven Guckes wrote: > * jochen issing <[EMAIL PROTECTED]> [2002-09-25 12:39]: > > after my recent update to 1.4i, I am not able able to remove > > any mails out of my spool files. I can open /var/mail/jochen > > with vim and can write it, but mutt refuses writing. > > sounds like a locking problem.. > > > I found in the internet the configure switch --enable-extern-dotlock > > and compiled it once more, but this did not help. > > I am using debian woody stable. > > but do you mind sharing more info than > "mutt 1.4 on debian woody stable"? > perhaps something like "mutt -v"? > > Sven Here you are: System: Linux 2.4.19 (i686) [using ncurses 5.2] Einstellungen bei der Compilierung: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP -USE_IMAP -USE_GSS -USE_SSL -USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID -HAVE_GETADDRINFO ISPELL="/usr/bin/ispell" SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" PKGDATADIR="/usr/share/mutt" SYSCONFDIR="/usr/etc" EXECSHELL="/bin/sh" -MIXMASTER -- jochen issing mailto:[EMAIL PROTECTED] http://www.mcf-music.de GPG:0A121BC
Re: mbox opened read only after update to mutt 1.4i
* jochen issing <[EMAIL PROTECTED]> [2002-09-25 12:39]: > after my recent update to 1.4i, I am not able able to remove > any mails out of my spool files. I can open /var/mail/jochen > with vim and can write it, but mutt refuses writing. sounds like a locking problem.. > I found in the internet the configure switch --enable-extern-dotlock > and compiled it once more, but this did not help. > I am using debian woody stable. but do you mind sharing more info than "mutt 1.4 on debian woody stable"? perhaps something like "mutt -v"? Sven
Re: mbox opened read only after update to mutt 1.4i
Jochen -- ...and then jochen issing said... % % after my recent update to 1.4i, I am not able able to remove any mails What, it's still that way an hour later? See my reply to your first post :-) HTH & HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg31196/pgp0.pgp Description: PGP signature
Re: mbox opened read only after update to mutt 1.4i
Jochen -- ...and then jochen issing said... % % Hi List, Hello! % % after my recent update to 1.4i, I am not able able to remove any mails How did you install mutt? Were you root, or just jochen? % out of my spool files. I can open /var/mail/jochen with vim and can % write it, but mutt refuses writing. % I found in the internet the configure switch --enable-extern-dotlock % and compiled it once more, but this did not help. % I am using debian woody stable. Please show us what ls -lFd /var/mail /var/mailjochen `which mutt` `which mutt_dotlock` mutt -v gives you. I suspect that /var/mail is writable only by owner (root) and group (mail) and that either mutt (if it is -DL_STANDALONE) or mutt_dotlock (if mutt is +DL_STANDALONE) is not installed with the SGID bit set and mail groupship. % % Thanks, Sure thing! % % jochen HTH & HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg31195/pgp0.pgp Description: PGP signature
mbox opened read only after update to mutt 1.4i
Hi List, after my recent update to 1.4i, I am not able able to remove any mails out of my spool files. I can open /var/mail/jochen with vim and can write it, but mutt refuses writing. I found in the internet the configure switch --enable-extern-dotlock and compiled it once more, but this did not help. I am using debian woody stable. Thanks, jochen -- jochen issing mailto:[EMAIL PROTECTED] http://www.mcf-music.de GPG:0A121BC
mbox opened read only after update to mutt 1.4i
Hi List, after my recent update to 1.4i, I am not able able to remove any mails out of my spool files. I can open /var/mail/jochen with vim and can write it, but mutt refuses writing. I found in the internet the configure switch --enable-extern-dotlock and compiled it once more, but this did not help. I am using debian woody stable. Thanks, jochen -- jochen issing mailto:[EMAIL PROTECTED] http://www.mcf-music.de GPG:0A121BC
