Is there an option with which I can prevent Mutt adding those
fields to messages, _at least_ when the message is not read or
whatever? If not, do you also consider this a useful feature?
You can always open the folder in read-only mode or just disable writing
by hitting `%' before
Jos Vos [EMAIL PROTECTED] wrote on Sun, 13 Feb 2000:
Thanks for your suggeston, but this is not an option for me. I want it
to work ok for daily use, not for a special case where I explicitly have
to open folders in R/O mode or have to give extra commands.
This probably won't qualify for you
Hi Lars!
On Sun, 13 Feb 2000, Lars Hecking wrote:
You are correct Lars, I thought he was having a problem using GPG and not
the warning, DOH!
I thought so too, but because the original poster's error description was
unclear and incomplete, I focused on the warning part instead. Both
How do I get off this list, I have tried every unsubscribe list command
I know.
Mike
How would I reply to the mailing list? When I use `L`, I get "No mailing
lists found"
On Sat, Feb 12, 2000 at 20:29:55 +0100, Horacio MG wrote:
Hi,
I just realized that I can specify more than one recipient in the
reply-to header.
1- is this allowed (conforming to whatever rfcs)?
Yes, it is allowed in RFC 822.
--
Byrial
On 13-Feb-2000, Jason Helfman wrote:
How would I reply to the mailing list? When I use `L`, I get "No mailing
lists found"
That's what the variable "lists" is for. Check the manual.
Ronny
Does someone have a nice slrn config file to share?
Hi! Here's a short list of features that I would love to see in the next
release:
1) stop printing extra \n on exit. I'm one of those anal types that
can't stand extra white space. You can't imagine how happy I was when
vim stopped doing this.
2) a shortcut for "current mailbox". I would
Hi
On my computers I have mounted my home directories with nfs. This because I thinks
this is a good thing to do. When I exiting mutt it askes me:
Move read messages to /home/haagen/Mail/old ([n]/y):
If i type "y" here i get the following errors:
lockd: failed to monitor
On Sun, 13 Feb 2000, Martin Bertilsson Haagen wrote:
lockd: failed to monitor 192.168.2.1
fcntl: No locks available (errno 37)
I have used this NFS configuration for quite a while without any
problems at all, so my conclutions is that it is mutt thats causing
it.
Is there any
Roland Rosenfeld [EMAIL PROTECTED] wrote on Sun, 13 Feb 2000:
To get rid of all these problems, you can alternatively install a nfs
server with locking support on the server like the Linux knfsd.
... Or switch to Maildir, a folder format designed so that it doesn't
require locking, and is thus
Brian Kimball [EMAIL PROTECTED] wrote on Sun, 13 Feb 2000:
4) better memory of which mailboxes have New and "Old" messages. I
don't like how viewing a mailbox will make mutt forget that it contains
unread mail.
This is probably folder-type specific. I don't have any problems like
this with
On Fri, Feb 11, 2000 at 09:58:26PM -0500, Michael Tatge
([EMAIL PROTECTED]) wrote:
On Fri, Feb 11, 2000 at 04:00:57PM +0200, Mikko Hänninen wrote:
Well then, you need to somehow find out what's the difference in headers
between the emails that work and which don't.
There doesn't seem to
Hello Jason!
On Sun, 13 Feb 2000, Jason Helfman wrote:
Does someone have a nice slrn config file to share?
...with mutt?
bye - Wilhelm
--
Wilhelm Wienemann, Amselweg 10, D-47546 Kalkar/Germany
== E-Mail: [EMAIL PROTECTED] ===
"And since you are the future keepers of
Jos --
...and then Jos Vos said...
% Is there an option with which I can prevent Mutt adding those
% fields to messages, _at least_ when the message is not read or
% whatever? If not, do you also consider this a useful feature?
%
% You can always open the folder in read-only mode or
Could someone explain where or how the BUFFY_SIZE option got its name?
And does it cycle through incoming mailboxes only at the 'c' (change-folder)
prompt? And is that it's only function?
--
// [EMAIL PROTECTED] //
17 matches
Mail list logo
