> On 2022-08-11 02:22, Cameron Simpson wrote:
On 10Aug2022 11:10, todd zullinger wrote:
Fourhundred Thecat wrote:
When I delete my custom macro, and revert "q" to its default action,
then I get this message when exiting from mutt (case 2):
Purge 1 deleted message? ([yes]/no):
Aye, what
;>
>> When I create custom macro to sync automatically, I get the error on
>> read-only mutt, because it cannot be synced.
>>
>> So I need "q" that works in both cases.
>
>You may want to look at the $delete option. It's a
>quad-option which defaults to ask-yes
Fourhundred Thecat wrote:
> I am using mutt in 2 modes:
>
> 1) mutt -R -f folder
> 2) mutt-f folder
>
> In case 1), pressing "q" should simply exit. This is read-only mode and
> there are no messages to be deleted.
>
> In case 2), pressing &qu
On 2022-08-08 22:15, Derek Martin wrote:
On Fri, Jul 29, 2022 at 08:15:31AM +0200, Fourhundred Thecat wrote:
Hello,
I have custom macro "q" for exit:
macro index q ";"
but when I open mailbox read-only, I am not able to exit from mutt:
AFAICT this macro does nothin
On Fri, Jul 29, 2022 at 08:15:31AM +0200, Fourhundred Thecat wrote:
> Hello,
>
> I have custom macro "q" for exit:
>
> macro index q ";"
>
> but when I open mailbox read-only, I am not able to exit from mutt:
AFAICT this macro does nothing usef
Hello,
I have custom macro "q" for exit:
macro index q ";"
but when I open mailbox read-only, I am not able to exit from mutt:
Mailbox is read-only.
the key "q' does not work.
is there any workaround to solve this?
from mutt, telling me the
> > mailbox
> > is read-only.
>
> It may be that something is wrong with your mutt_dotlock program. Did
> you configure --with-mailpath=/var/mail? What are the permissions of
> /var/mail? Is your mutt_dotlock setgid?
>
> Also you may
On Wed, Nov 07, 2018 at 09:25:31PM -0500, benfi...@gmail.com wrote:
> My linux mail box is /var/mail/$USER, previously I had read and deleted mails
> from this mailbox, now I get an error message from mutt, telling me the
> mailbox
> is read-only.
It may be that something is wro
ail/$USER, previously I had read and deleted
> mails from this mailbox, now I get an error message from mutt, telling
> me the mailbox is read-only.
>
> Anyone know why this is? The permissions on /var/mail and the file itself
> do allow me to write to the file.
Hi,
on building the latest mutt from https://gitlab.com/muttmua/mutt.git I have one
odd problem.
My linux mail box is /var/mail/$USER, previously I had read and deleted mails
from this mailbox, now I get an error message from mutt, telling me the mailbox
is read-only.
Anyone know why
rewrite your mailbox out
from under you.
But, there's probably not really any good reason to read mail from a
read-only NFS mount, so just stop doing that, and your problem should
go away.
The main reason is to see non-text without IO-redirection.
I don't really understand what you mean
.
Actually the MTA just appends to the file. It can get messy when a
second mutt or so with write access changes the mbox more
arbitrarily.
But, there's probably not really any good reason to read mail from a
read-only NFS mount, so just stop doing that, and your problem should
go away.
The main
Hello,
I have a setup where my MTA delivers mail to an mbox file, which
then is in turn exported via nfs read only to the client where
mutt is running. Main purpose of this construction is viewing
certain attachments.
While all this works fine the first time mutt is started, after a
while
On Thu, August 23, 2012 08:53, Joerg Dorchain wrote:
I have a setup where my MTA delivers mail to an mbox file, which
then is in turn exported via nfs read only to the client where
mutt is running. Main purpose of this construction is viewing
certain attachments.
While all this works fine
On Thu, Aug 23, 2012 at 10:28:35AM +0200, Christian Brabandt wrote:
On Thu, August 23, 2012 08:53, Joerg Dorchain wrote:
I have a setup where my MTA delivers mail to an mbox file, which
then is in turn exported via nfs read only to the client where
mutt is running. Main purpose
On Thu, Aug 23, 2012 at 11:39:25AM +0200, Joerg Dorchain wrote:
If just seems that mutt does not check for new mails at all when
it considers a mailbox read only.
I need to correct myself: With an strace, I see that mutt does a
stat() on the mbox file with every keypress while in the index
in an
inconsistent state.
But, there's probably not really any good reason to read mail from a
read-only NFS mount, so just stop doing that, and your problem should
go away. If the mail is local, read it locally; if you must use NFS,
then there are some other considerations. You may want to swtich to
maildir
As title. With current behavior, mutt will mark email as read
immediately after I open it. I don't want this kind of automatic
behavior, intead, I like mutt marks mail automatically as read after I
open a short mail that fill whole page or, page down to the bottom of
a long mail that can't fill
Am 2007-01-25 13:55:22, schrieb [EMAIL PROTECTED]:
It's on a shell login account on a web hosting provider, it's not my
personal system. A 'uname -a' reports:-
Linux shell 2.4.23-grsec #1 Tue Dec 2 19:44:13 GMT 2003 i586 unknown
I think it's Debian. The mutt is mine though. It's not
* On Wed, Jan 24, 2007 [EMAIL PROTECTED] ([EMAIL PROTECTED]) muttered:
On Wed, Jan 24, 2007 at 04:32:26PM +0100, Michael Tatge wrote:
* On Wed, Jan 24, 2007 [EMAIL PROTECTED] ([EMAIL PROTECTED]) muttered:
I can 'mutt_dotlock any parameter /var/mail/cgreen' with no
errors, does that mean
On Thu, Jan 25, 2007 at 09:04:57AM +0100, Michael Tatge wrote:
* On Wed, Jan 24, 2007 [EMAIL PROTECTED] ([EMAIL PROTECTED]) muttered:
On Wed, Jan 24, 2007 at 04:32:26PM +0100, Michael Tatge wrote:
* On Wed, Jan 24, 2007 [EMAIL PROTECTED] ([EMAIL PROTECTED]) muttered:
I can 'mutt_dotlock
* [EMAIL PROTECTED] [EMAIL PROTECTED]:
On Thu, Jan 25, 2007 at 09:04:57AM +0100, Michael Tatge wrote:
* On Wed, Jan 24, 2007 [EMAIL PROTECTED] ([EMAIL PROTECTED]) muttered:
On Wed, Jan 24, 2007 at 04:32:26PM +0100, Michael Tatge wrote:
* On Wed, Jan 24, 2007 [EMAIL PROTECTED] ([EMAIL
oN tHU, Jan 25, 2007 at 02:26:56PM +0100, Patrick Ben Koetter wrote:
* [EMAIL PROTECTED] [EMAIL PROTECTED]:
On Thu, Jan 25, 2007 at 09:04:57AM +0100, Michael Tatge wrote:
* On Wed, Jan 24, 2007 [EMAIL PROTECTED] ([EMAIL PROTECTED]) muttered:
On Wed, Jan 24, 2007 at 04:32:26PM +0100,
On Thu, Jan 25, 2007 at 05:39:17PM +0100, Rado S wrote:
Moin,
check permissions per wiki-FAQ,
check 'mutt -v|grep -i lock' to you use proper locking.
Brilliant! That's the problem, /var/mail is:-
lrwxrwxrwx1 root root 10 Oct 16 1999 /var/mail
the group should be
On Thu, Jan 25, 2007 at 06:18:11PM +, [EMAIL PROTECTED] wrote:
Brilliant! That's the problem, /var/mail is:-
lrwxrwxrwx1 root root 10 Oct 16 1999 /var/mail
Are you sure? This is a symlink, look at the l at the beginning of your
line.
Where does it point to?
Shade
On Thu, Jan 25, 2007 at 08:48:16PM +0100, Stephan Seitz wrote:
On Thu, Jan 25, 2007 at 06:18:11PM +, [EMAIL PROTECTED] wrote:
Brilliant! That's the problem, /var/mail is:-
lrwxrwxrwx1 root root 10 Oct 16 1999 /var/mail
Are you sure? This is a symlink, look at the l
and write the file this way.
However when I try and delete (or move) a message using mutt it just
says Mailbox is read-only., what's the problem?
Sounds like a locking problem. Can you mutt_dotlock the file manually?
HTH,
Michael
--
Remember: While root can do most everything, there are certain
the file directly using (for example) vi and can delete a
message and write the file this way.
However when I try and delete (or move) a message using mutt it just
says Mailbox is read-only., what's the problem?
Sounds like a locking problem. Can you mutt_dotlock the file manually?
Well I
835067 Jan 24 09:38
/var/mail/cgreen
I can edit the file directly using (for example) vi and can delete a
message and write the file this way.
However when I try and delete (or move) a message using mutt it just
says Mailbox is read-only., what's the problem
mutt it just
says Mailbox is read-only., what's the problem?
Sounds like a locking problem. Can you mutt_dotlock the file manually?
Well I can 'mutt_dotlock any parameter /var/mail/cgreen' with no
errors, does that mean it's OK?
I assume so. You have not by any chance aliased
cgreen mail 835067 Jan 24 09:38
/var/mail/cgreen
However when I try and delete (or move) a message using mutt it just
says Mailbox is read-only., what's the problem?
Sounds like a locking problem. Can you mutt_dotlock the file manually?
I can 'mutt_dotlock any parameter /var
is /var/mail/cgreen, permissions are:-
-rw-rw1 cgreen mail 835067 Jan 24 09:38
/var/mail/cgreen
However when I try and delete (or move) a message using mutt it just
says Mailbox is read-only., what's the problem?
Sounds like a locking problem. Can you
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
* 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
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
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 .
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
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
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
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
* 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
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.
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
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
* 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
01-May-02 at 10:38, Willy S ([EMAIL PROTECTED]) wrote :
hi,
Yesterday I was playing with my procmailrc, and spambouncer. Since then, I can
not delete the mail in my mailbox (/var/spool/mail/sutrisno). The message at
the bottom of Mutt says: Mailbox is read-only.
There is a toggle read-only
* David T-G ([EMAIL PROTECTED]) wrote:
Let's back up for a moment... Has your mail always been in /var/mail,
or have you been working with a mailbox under your home directory?
Have you used mutt for a long time, or switched to it only recently from,
say, PINE? You really didn't build and
). The message at
% the bottom of Mutt says: Mailbox is read-only.
%
% If I do:
% $ ls -l /var/spool/mail/sutrisno
% $ -rw-rw1 sutrisno mail 13239 Apr 30 11:24 /var/spool/mail/sutrisno
This looks fine. I expect that
ls -lFd /var/spool/mail
will show that only the mail group has
* David T-G ([EMAIL PROTECTED]) wrote:
% Yesterday I was playing with my procmailrc, and spambouncer. Since then, I can
Were you playing with mutt, too, by chance? Did you compile and install
a new version?
I dont think so. I never touch muttrc, neither do I compile it again. I just
play
Willy --
...and then Willy Sutrisno said...
%
% * David T-G ([EMAIL PROTECTED]) wrote:
% % Yesterday I was playing with my procmailrc, and spambouncer. Since then, I can
%
% Were you playing with mutt, too, by chance? Did you compile and install
% a new version?
% I dont think so. I never
* David T-G ([EMAIL PROTECTED]) wrote:
Aha! While mutt_dotlock is group mail, it does not have the sgid bit
set, so it gets run as the calling user. You need root to
chmod g+s /usr/local/bin/mutt_dotlock
The above command really solved my problem. Thx man for the help!
I can't believe
Willy --
...and then Willy Sutrisno said...
%
% * David T-G ([EMAIL PROTECTED]) wrote:
% Aha! While mutt_dotlock is group mail, it does not have the sgid bit
% set, so it gets run as the calling user. You need root to
%
%chmod g+s /usr/local/bin/mutt_dotlock
% The above command really
hi,
Yesterday I was playing with my procmailrc, and spambouncer. Since then, I can
not delete the mail in my mailbox (/var/spool/mail/sutrisno). The message at
the bottom of Mutt says: Mailbox is read-only.
If I do:
$ ls -l /var/spool/mail/sutrisno
$ -rw-rw1 sutrisno mail 13239 Apr
Vincent, et al --
...and then Vincent Lefevre said...
%
% On Thu, Apr 25, 2002 at 23:12:58 +0200, Rocco Rutte wrote:
% It doesn't really matter, I think. The dotlock program is the
% last which is to be installed. if chgrp fails, who cares since
% (at that point) everything else is
Rocco, et al --
...and then Rocco Rutte said...
%
% Hi,
%
% * David T-G [04/25/02 19:14:01 CEST] wrote:
% ...and then Vincent Lefevre said...
% % too. :( I have to remove mutt_dotlock from my bin directory each
% % time I want to install a new version of Mutt.
%
% So which is easier, to
Hi!
On Fri, Apr 26, 2002 at 05:49:14AM -0500, David T-G wrote
As a normal user, you shouldn't be able to remove a privileged
mutt_dotlock, since it will be owned by root; the only way for that
to happen is if it was world-writable anyway. If you can remove it,
Or the directory is writable.
On Fri, Apr 26, 2002 at 13:12:31 +0200, Stephan Seitz wrote:
On Fri, Apr 26, 2002 at 05:49:14AM -0500, David T-G wrote
As a normal user, you shouldn't be able to remove a privileged
mutt_dotlock, since it will be owned by root; the only way for that
to happen is if it was world-writable
Stephan --
...and then Stephan Seitz said...
%
% Hi!
Hello!
%
% On Fri, Apr 26, 2002 at 05:49:14AM -0500, David T-G wrote
% As a normal user, you shouldn't be able to remove a privileged
% mutt_dotlock, since it will be owned by root; the only way for that
% to happen is if it was
Vincent --
...and then Vincent Lefevre said...
%
% On Fri, Apr 26, 2002 at 13:12:31 +0200, Stephan Seitz wrote:
% On Fri, Apr 26, 2002 at 05:49:14AM -0500, David T-G wrote
% As a normal user, you shouldn't be able to remove a privileged
% mutt_dotlock, since it will be owned by root; the
On Fri, Apr 26, 2002 at 07:50:09 -0500, David T-G wrote:
Now *that* one is a new one on me. I don't recall having run across that
before. Very interesting, and certainly a compelling reason to not build
mutt_dotlock. Why didn't you say so in the first place? ;-)
Because I noticed the
Hi all,
I just started using Mutt last week, and have really loved it.
I was using 1.2.5, but I wanted %E in index_format, so I grabbed 1.3.28i.
Now I have a new problem, which is that my mailbox is considered read-only. I
am just using my spoolfile over NFS. Everything was working great
On Tue, Apr 23, 2002 at 13:38:56 -0600, Brett H. Williams wrote:
Now I have a new problem, which is that my mailbox is considered
read-only. I am just using my spoolfile over NFS. Everything was
working great before the upgrade.
I have the same problem when I want to install Mutt
a security hole.
%
% Now I have a new problem, which is that my mailbox is considered read-only. I
% am just using my spoolfile over NFS. Everything was working great before the
% upgrade.
While it could be an NFS locking issue, it's probably a mutt_dotlock
issue. You will probably find that you don't
Vincent, et al --
...and then Vincent Lefevre said...
%
% On Tue, Apr 23, 2002 at 13:38:56 -0600, Brett H. Williams wrote:
% Now I have a new problem, which is that my mailbox is considered
% read-only. I am just using my spoolfile over NFS. Everything was
% working great before the upgrade
On Thu, Apr 25, 2002 at 10:59:29 -0500, David T-G wrote:
% This is quite annoying. A configure option to prevent it from being
% installed would be a good idea IMHO.
While I agree that it isn't a bad idea, I don't know that it's a terribly
good idea; you can already tell mutt to not use
Hi!
On Don, Apr 25, 2002 at 06:13:54 +0200, Vincent Lefevre wrote
I think you haven't understood. There is already a mutt_dotlock
installed here (in /usr/...) with correct permissions. But I also
want to install more recent versions of Mutt in my home directory,
and make install installs a
a sendmail
misconfiguration and all of these emails popped out days after I sent them :(
So I got some help here for the read only problem. Now I understand why
installing the new version messed it up though.
[snip]
%
%
% P.S.
%
% I wanted to use the $hide_missing, but even under 1.3.28i
Vincent --
...and then Vincent Lefevre said...
%
% On Thu, Apr 25, 2002 at 10:59:29 -0500, David T-G wrote:
% % This is quite annoying. A configure option to prevent it from being
% % installed would be a good idea IMHO.
%
% While I agree that it isn't a bad idea, I don't know that it's a
On Thu, Apr 25, 2002 at 12:14:01 -0500, David T-G wrote:
So which is easier, to remove a file or to tell configure to not put it
there in the first place?
The latter. :) I use a shell alias to configure mutt, because I need
several other options (which may depend on the architecture). So, all
Vincent --
...and then Vincent Lefevre said...
%
% On Thu, Apr 25, 2002 at 12:14:01 -0500, David T-G wrote:
% So which is easier, to remove a file or to tell configure to not put it
% there in the first place?
%
% The latter. :) I use a shell alias to configure mutt, because I need
Well,
Hi,
* David T-G [04/25/02 19:14:01 CEST] wrote:
...and then Vincent Lefevre said...
% too. :( I have to remove mutt_dotlock from my bin directory each
% time I want to install a new version of Mutt.
So which is easier, to remove a file or to tell configure to not put it
there in the first
On Thu, Apr 25, 2002 at 23:12:58 +0200, Rocco Rutte wrote:
It doesn't really matter, I think. The dotlock program is the
last which is to be installed. if chgrp fails, who cares since
(at that point) everything else is sucessfully where it should
be. Just remove the binary.
But some users
Hi,
* Vincent Lefevre [04/25/02 23:27:08 CEST] wrote:
On Thu, Apr 25, 2002 at 23:12:58 +0200, Rocco Rutte wrote:
It doesn't really matter, I think. The dotlock program is the
last which is to be installed. if chgrp fails, who cares since
(at that point) everything else is sucessfully
On Fri, Apr 26, 2002 at 00:26:51 +0200, Rocco Rutte wrote:
If you have no privileged access to a machine, you're probably
the wrong person to install software systemwide. But every
user may install a copy of mutt in $HOME. In this case, 'make
install' is called without root permissions and
Ng said...
%
% Hi!
Hello!
%
% I have just set up my mail server using postfix. Then I read the mail by using
Mutt. After I read the mails and want to delete it, I press 'd' or '^d'. But, I got
'Mailbox is read-only' message. Why?
It sounds like mutt was not installed as a member
Hi!
I have just set up my mail server using postfix. Then I read the mail by using Mutt.
After I read the mails and want to delete it, I press 'd' or '^d'. But, I got
'Mailbox is read-only' message. Why?
I have checked the permission by typing:
ls -ld /var/spool/mail/ngterry
and I get
Quick question. I just upgraded mutt from 1.2.5i to Mutt 1.3.25i Because of
the security change. Problem is that my main inbox (my spoolfile I belive)
is now giving me Mailbox is read-only. when ever I try to do any
operations on it.
The important part of my .muttrc is here:
set spoolfile
Thus spake Troy Heber ([EMAIL PROTECTED]):
Quick question. I just upgraded mutt from 1.2.5i to Mutt 1.3.25i
Because of the security change. Problem is that my main inbox (my
spoolfile I belive) is now giving me Mailbox is read-only. when ever
I try to do any operations
Troy --
...and then Troy Heber said...
%
% Quick question. I just upgraded mutt from 1.2.5i to Mutt 1.3.25i Because of
% the security change. Problem is that my main inbox (my spoolfile I belive)
% is now giving me Mailbox is read-only. when ever I try to do any
...
% set spoolfile=/var/spool
on opening
her mailboxes read-only. Even if I, as root, su to her account and
explicitly run /usr/local/bin/mutt to make totally certain I'm not hitting
an alias, with read_only explicitly set to no in .muttrc, the mailbox is
still opened read-only. File ownership and permissions on the mailbox
? Can she see it? Can she run it?
%
% I set up two accounts for a new user yesterday. Mutt insists on opening
% her mailboxes read-only. Even if I, as root, su to her account and
% explicitly run /usr/local/bin/mutt to make totally certain I'm not hitting
What if you copy /var/spool/mail/user
Matthew D. Fuller mutt [08/11/01 06:46 -0600]:
I'd guess the mail directory was 1777 before.
I've had this happen on my systems (FreeBSD) where, during the
'installworld' process (which installs a fresh system from binaries just
built from source, a common means of upgrading) the system runs
Hi,
I want to run two Mutts in parallel.
1. Is there any problem except writing mailboxes?
2. Does '-R' read-only all mailboxes or just the one I name in the
command line? Is there another way to do it?
tia,
Thorsten
--
They that can give up essential liberty to obtain a little
temporary
On 2001-10-31 Thorsten Haude wrote:
I want to run two Mutts in parallel.
1. Is there any problem except writing mailboxes?
No, I often do that.
2. Does '-R' read-only all mailboxes or just the one I name in the
command line? Is there another way to do it?
Only the named ones.
But you
Moin,
so trifft man sich wieder.
* Christoph Maurer [EMAIL PROTECTED] [01-10-31 17:43]:
On 2001-10-31 Thorsten Haude wrote:
1. Is there any problem except writing mailboxes?
No, I often do that.
Do you have any special provisions in this respect?
2. Does '-R' read-only all mailboxes or just
Thorsten Haude wrote:
1. Is there any problem except writing mailboxes?
No, I often do that.
Do you have any special provisions in this respect?
I'm not Christoph, but I often use several mutt's at the same time, too.
I even modify mails in both of the mut's, and I never got problems. I
Hi,
* Volker Moell [EMAIL PROTECTED] [01-10-31 18:18]:
Thorsten Haude wrote:
1. Is there any problem except writing mailboxes?
Do you have any special provisions in this respect?
I'm not Christoph, but I often use several mutt's at the same time, too.
I even modify mails in both of the mut's,
Thorsten Haude wrote:
I can see me appending mail, eg. when I send one; but I usually don't
modify the mails in my mboxes. What do I miss here?
Argh... ok, this was confusing. What I really meant was, you can get
into trouble, when you append two mails to one mailbox *at the same
time*. But
Hi,
* Volker Moell [EMAIL PROTECTED] [01-10-31 18:50]:
Argh... ok, this was confusing. What I really meant was, you can get
into trouble, when you append two mails to one mailbox *at the same
time*. But this is very implausible. Normal operations like delete
and add mails are harmless (in my
Thorsten Haude wrote:
You do that without excessive sync-mailbox's?
Of course *with*. I often forget that somewhere else on another screen
another mutt is open... ;-)
OK then, I'm game.
Good luck! :-)
-volker
--
http://die-Moells.de/ * http://Stama90.de/ *
written by
mutt, but you only asked about parallel mutts so that shouldn't affect
you.
% 2. Does '-R' read-only all mailboxes or just the one I name in the
% command line? Is there another way to do it?
You could use the alternative read-only muttrc that you mentioned or just
use the -R flag; you
Hello all,
I've just recently upgraded to mutt 1.3.22 and it seems I can no longer
delete mail from my inbox - /var/spool/mail/doug
Could someone point me to the relevant documentation ?
Thanks,
Doug
Doug Kearns mutt [21/09/01 19:25 +1000]:
I've just recently upgraded to mutt 1.3.22 and it seems I can no longer
delete mail from my inbox - /var/spool/mail/doug
Could someone point me to the relevant documentation ?
Check the permissions of your mailbox - and see if there's a mutt dotlock
to toggle read-only with '%'.
If you have your old mutt, run
/usr/bin/ls -lF /path/to/old/mutt
and see what group it is and what the group permissions are -- are they
just r-x or the special r-s that means set group-id on execution?
Check the same thing for an old mutt_dotlock program.
Now
On Fri, Sep 21, 2001 at 02:55:44PM +0530, Suresh Ramasubramanian wrote:
Doug Kearns mutt [21/09/01 19:25 +1000]:
I've just recently upgraded to mutt 1.3.22 and it seems I can no longer
delete mail from my inbox - /var/spool/mail/doug
Could someone point me to the relevant documentation ?
Hi all!
So, what's a "mutt_dotlock"?
It's a program (part of the Mutt package) that implements NFS-safe file
locking. To ensure that different programs do not write to the same
mailbox at once (thus corrupting it), mutt_dotlock creates a lock file
in the same directory (that's why
On Thu, Jul 06, 2000 at 08:47:46AM +0200, Dirk Ruediger wrote:
I user mutt on a nfs-mounted dir. But unfortunatly the systen crashed
during a mutt session (mutt was innocent ;-) and now I can't write to
this dir, mutt always says, that this folder is write-only. I can't find
a lock file.
that the file is
read only??
Elm likes it fine. What would cause this?
Mike
--
Michael P. Soulier, 1Z22, SKY Tel: 613-765-4699 (ESN: 39-54699)
Optical Networks, Nortel Networks, SDE Pegasus
"...the word HACK is used as a verb to indicate a massive amount
of nerd-like e
msoulier
And yet, mutt won't modify the contents, because it says that the file is
read only??
Elm likes it fine. What would cause this?
Locking. For Mutt's dotlocking to work, your /var/spool/mail directory
should be writable by group `mail', and your `mutt_dotlock' should be
sgid
On Wed, Jul 05, 2000 at 08:39:47PM +0200, Marius Gedminas wrote:
Locking. For Mutt's dotlocking to work, your /var/spool/mail directory
should be writable by group `mail', and your `mutt_dotlock' should be
sgid mail.
Where can I find information on this? I just grepped through the
1 - 100 of 126 matches
Mail list logo
