Benjamin Michotte wrote:
> Oh my god...
> I just switched from mbox to maildir... and also reswitch to mbox...
>
> 2 minutes 38 to open my in.mutt maildir (± 6000 mails) instead of 18
> secondes to the same in mbox format
Mmh, sounds strange to me. I have one big maildir (it's a mailing
li
On Sun, Dec 02, 2001 at 07:24:45PM +0100, Elimar Riesebieter wrote:
> Hi all,
>
> I am using mutt since 4 weeks: It is fantastic! Now it is very easy
> to read usenets and other stuff!
I have searched the docs ... how can i pull specific usenets into my
mutt inbox?
aloha,
dave
msg20957/pgp0
Moin,
* Thomas Hurst <[EMAIL PROTECTED]> [01-12-03 00:24]:
>* Thorsten Haude ([EMAIL PROTECTED]) wrote:
>> I have different views on Maildirs (see other thread), and I would
>> move the mails thread-wise, but on all other points, I agree.
>Hm, thread-wise is conciderably more expensive - date-wis
Hi,
* Will Yardley <[EMAIL PROTECTED]> [01-12-03 01:08]:
>Thorsten Haude wrote:
>> I don't use ext2, but Reiser. The difference is less severe, but
>> noticeable. Maildir seems to have the problem that it only works with
>> certain file system types.
>i also just noticed your version string... if
I'm having an oddball problem with locking. Mutt 1.3.24i on RedHat 7.2
Linux 2.4.16. The mailboxes in question are mbox format on an NFS
server running Slackware 8.0 Linux 2.4.16.
When attempting to write to a box (say, ave a message), I get:
Couldn't lock /home/rnbwpnt/MAIL//spam?
I get this
hi,
i just installed mutt 1.3.23i on a woody box ... previously, i was using
1.2.5i on a potato box via xterm (i want to run a local mutt with
fetchmail)
the first thin i notice is that 1.2.5 allows my xterm background to show
through (which i like) but the 1.2.23i seems to force the white on bl
Aaron --
...and then Aaron Goldblatt said...
% I'm having an oddball problem with locking. Mutt 1.3.24i on RedHat 7.2
% Linux 2.4.16. The mailboxes in question are mbox format on an NFS
% server running Slackware 8.0 Linux 2.4.16.
...
% There are no obvious conflicts in /var/lock/. Manually op
Dave --
...and then Dave Price said...
% hi,
Hello!
%
% suggestions?
I'm sorry to say that I don't have any suggestions for your color
problems. Best of luck.
%
% also, any advice on copying my pgp key/user info over from the old box
% to the new one?
This should be as easy as tarring u
Magnus --
Did you ever get an answer for this? I was going back through my
mutt-users folder for anti-spam URLs and tripped on it.
...and then Magnus Bodin said...
%
% I did some experiments with send-hook, like this:
%
% send-hook . 'my_hdr Reply-By: `perl -e "print scalar(localtime(time+7
On Sat, Dec 01, 2001 at 08:59:24AM +0100, Sven Guckes wrote:
> * Paul Brannan <[EMAIL PROTECTED]> [011130 15:42]:
> > 1) When I start mutt, I see this message:
> > fcntl: No locks available (errno = 37)
> >How can I make it go away?
>
> use the file locking that goes along with your syst
On Sat, Dec 01, 2001 at 09:08:02AM +0100, Sven Guckes wrote:
> * Paul Brannan <[EMAIL PROTECTED]> [011130 15:45]:
> > 1) How can I refresh the current inbox?
>
> Use the command "sync-mailbox" - bound to '$' by default.
> And please use '?' to show the help screen
> and '/' to search within. The
On Mon, Dec 03, 2001 at 10:19:33AM -0500, Paul Brannan wrote:
> On Sat, Dec 01, 2001 at 09:08:02AM +0100, Sven Guckes wrote:
> > * Paul Brannan <[EMAIL PROTECTED]> [011130 15:45]:
> > > 1) How can I refresh the current inbox?
> >
> > Use the command "sync-mailbox" - bound to '$' by default.
> > A
* David T-G ([EMAIL PROTECTED]) wrote:
> ...and then Nicolas Rachinsky said...
> > On Sun, Dec 02, 2001 at 11:24:53PM +, Thomas Hurst
> > <[EMAIL PROTECTED]> wrote:
> > > * Thorsten Haude ([EMAIL PROTECTED]) wrote:
> > >
> > > > I have no solution, but will work on one based on Mail::Audit.
>
On Mon, Dec 03, 2001 at 10:24:04AM -0500, Dan Boger wrote:
> On Mon, Dec 03, 2001 at 10:19:33AM -0500, Paul Brannan wrote:
> > Pressing '$' does not appear to have any effect. As a test, I:
> > a) send a message to myself
> > b) return to my INBOX (which resides on an IMAP server)
> > c) wa
* Paul Brannan <[EMAIL PROTECTED]> [03-12-2001 16:16]:
| > use the file locking that goes along with your system?!
|
| Could you please point me to the documentation for specifying a
| different form of file locking? The mutt FAQ and mutt docs at mutt.org
| do not appear to contain such informa
On Monday, 03 December 2001 at 10:14, Paul Brannan wrote:
> On Sat, Dec 01, 2001 at 08:59:24AM +0100, Sven Guckes wrote:
> > * Paul Brannan <[EMAIL PROTECTED]> [011130 15:42]:
> > > 1) When I start mutt, I see this message:
> > > fcntl: No locks available (errno = 37)
> > >How can I make
* Thorsten Haude ([EMAIL PROTECTED]) wrote:
> * Thomas Hurst <[EMAIL PROTECTED]> [01-12-03 00:24]:
>
> > Hm, thread-wise is conciderably more expensive - date-wise involves
> > just scanning the maildir, grabbing all the time()'s, sorting them
> > and cutting off the top 1 week.
>
> I know, but I
Hi,
* Thomas Hurst <[EMAIL PROTECTED]> [01-12-03 16:28]:
>Unfortunately neither libmutt nor Mail::Mutt (which would provide an
>interface to mutt through scripting) exist :)
I found libmutt with Google.
Thorsten
--
They that can give up essential liberty to obtain a little
temporary safety dese
On Mon, Dec 03, 2001 at 10:31:53AM -0500, Brendan Cully wrote:
> > > * Paul Brannan <[EMAIL PROTECTED]> [011130 15:42]:
> > > > 1) When I start mutt, I see this message:
> > > > fcntl: No locks available (errno = 37)
> > > >How can I make it go away?
> > > > 2) When I go to the index, I s
Paul Brannan <[EMAIL PROTECTED]> writes:
> On Sat, Dec 01, 2001 at 09:08:02AM +0100, Sven Guckes wrote:
> > * Paul Brannan <[EMAIL PROTECTED]> [011130 15:45]:
> > > 1) How can I refresh the current inbox?
> >
> > Use the command "sync-mailbox" - bound to '$' by default.
> > And please use '?' to
On Mon, Dec 03, 2001 at 03:55:42PM +, Harold Sargeant wrote:
> Paul Brannan <[EMAIL PROTECTED]> writes:
>
> >
> I also have the same problem. '$' does nothing and I cannot find the sync-mailbox
>command.
>
> This problem only occurs in X-windows, via a terminal or menu. Outside of X it wor
Hi there,
is there a means to let mutt perform an action on the message it sends
out _when_ it sends it? All the documented hooks take place long before
this happens... To be more specific, I'm looking for a way to delay the
inserting of the signature until the moment the message goes off.
I kno
On Sat, Nov 17, 2001 at 01:06:14PM +0100, Nicolas Rachinsky wrote:
> On Fri, Nov 16, 2001 at 05:07:59PM +0100, Nicolas Rachinsky <[EMAIL PROTECTED]>
>wrote:
> > The second one adds a new command "tag-prefix-cond". It should behave
> > exactly the same as tag-prefix, with one difference. If there
On Mon, Dec 03, 2001 at 03:33:01PM +, Thomas Hurst wrote:
> * Thorsten Haude ([EMAIL PROTECTED]) wrote:
>
> > * Thomas Hurst <[EMAIL PROTECTED]> [01-12-03 00:24]:
> >
> > > Hm, thread-wise is conciderably more expensive - date-wise involves
> > > just scanning the maildir, grabbing all the ti
On Mon, Dec 03, 2001 at 05:52:41PM +0100, christophe barbé
<[EMAIL PROTECTED]> wrote:
> I've missed it the first time I read this mail but where comes from
> 'tag-prefix-cond' ?
It comes from a patch I've written, you find it under
www.rachinsky.de.
Nicolas
Hi there,
what is the rationale behind making the mail function unavailable in the
browser menu? The need to enter a mailbox just to send a mail has
bothered me for some time, and when I finally went to bind it, I
realized I was out of luck... :|
--
FreeBSD 4.4-STABLE
7:47PM up 41 days, 6:30, 1
> mutt -v
Okay.
bash-2.05$ mutt -v
Mutt 1.3.24i (2001-11-29)
Copyright (C) 1996-2001 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for de
Aaron --
...and then Aaron Goldblatt said...
% > mutt -v
%
% Okay.
%
% bash-2.05$ mutt -v
% Mutt 1.3.24i (2001-11-29)
...
% -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE
% +USE_FCNTL -USE_FLOCK
...
So that tells us how you can lock. Good.
%
%
% So I recompiled: ./configure -
Paul --
...and then Paul Brannan said...
% On Mon, Dec 03, 2001 at 10:31:53AM -0500, Brendan Cully wrote:
% > > > * Paul Brannan <[EMAIL PROTECTED]> [011130 15:42]:
% > > > > 1) When I start mutt, I see this message:
% > > > > fcntl: No locks available (errno = 37)
% > > > >How can I mak
Roman --
...and then Roman Neuhauser said...
% Hi there,
%
% is there a means to let mutt perform an action on the message it sends
% out _when_ it sends it? All the documented hooks take place long before
Not AFAIK.
% this happens... To be more specific, I'm looking for a way to delay the
%
> Date: Mon, 3 Dec 2001 15:04:22 -0500
> From: David T-G <[EMAIL PROTECTED]>
> To: "Mutt Users' List" <[EMAIL PROTECTED]>
> Subject: Re: a hook entered upon sending a message?
>
> Roman --
>
> ...and then Roman Neuhauser said...
> % Hi there,
> %
> % is there a means to let mutt perform an acti
On Mon, Dec 03, 2001 at 02:59:31PM -0500, David T-G wrote:
> ...and then Paul Brannan said...
> % This solves #2, but not #1 :(
>
> Interesting. What does
>
> mutt -v
>
> show you? Do you have dotlocking available? It looks to me as though
> mutt can only use fcntl locks but they are not s
I've got quite a few folders, but a number of them haven't had any new
mail for the last few days - is there a function similar to to
limit the folder view to, for instance, folders with a last modified
date < 24 hours?
--
Thomas 'Freaky' Hurst - [EMAIL PROTECTED] - http://www.aagh.net/
On Mon, Dec 03, 2001 at 03:04:22PM -0500, David T-G wrote:
> Roman --
>
> ...and then Roman Neuhauser said...
> % Hi there,
> %
> % is there a means to let mutt perform an action on the message it sends
> % out _when_ it sends it? All the documented hooks take place long before
>
> Not AFAIK.
>
Dave Price wrote:
>
> the first thin i notice is that 1.2.5 allows my xterm background to
> show through (which i like) but the 1.2.23i seems to force the white
> on black scheme no matter what console / xterm colors i have
> configured.
>
> suggestions?
what does your colors section look like?
* Paul Brannan <[EMAIL PROTECTED]> [03-12-2001 21:36]:
| > If you want the messages to be deleted when you sync, set it to "yes" in
| > your macro; if not, leave it at "no" and forget about the macro. If you
| > want to be asked then just set it to ask-no and forget about the macro,
| > and when
* Roman Neuhauser <[EMAIL PROTECTED]> [03-12-2001 21:22]:
| > From: David T-G <[EMAIL PROTECTED]>
[...]
| > If it really bothers you that much, unset $signature and $sig_dashes and
| > then modify your editor command to append your signature file onto the
| > temp file after the real editor com
File Locking + NFS = very bad news
It is inherently unreliable.
--
Regards
Cliff
Hi,
* Paul Brannan <[EMAIL PROTECTED]> [01-12-03 21:34]:
>> If you want the messages to be deleted when you sync, set it to "yes" in
>> your macro; if not, leave it at "no" and forget about the macro. If you
>> want to be asked then just set it to ask-no and forget about the macro,
>> and when y
Cliff --
...and then Cliff Sarginson said...
% File Locking + NFS = very bad news
Agreed. If he has to use an mbox, though, he may not have many choices
(my drop-in-mbox+run-razor+move-to-maildir kludge being one of them).
%
% It is inherently unreliable.
Always?
%
% --
% Regards
% Clif
Paul --
...and then Paul Brannan said...
% On Mon, Dec 03, 2001 at 02:59:31PM -0500, David T-G wrote:
% > ...and then Paul Brannan said...
% >
% > mutt -v
% >
% > show you? Do you have dotlocking available? It looks to me as though
...
%
% The relevant portion of mutt -v indicates:
% -HO
Roman --
...and then Roman Neuhauser said...
% >
% > ...and then Roman Neuhauser said...
% > %
% > % is there a means to let mutt perform an action on the message it sends
% > % out _when_ it sends it? All the documented hooks take place long before
% >
% > Not AFAIK.
%
% Any plans to imp
Rene ---
...and then Ren? Clerc said...
% * Roman Neuhauser <[EMAIL PROTECTED]> [03-12-2001 21:22]:
%
% | > From: David T-G <[EMAIL PROTECTED]>
%
% [...]
%
% | > If it really bothers you that much, unset $signature and $sig_dashes and
% | > then modify your editor command to append your signat
On Mon, Dec 03, 2001 at 07:17:14PM -0500, David T-G wrote:
> Cliff --
>
> ...and then Cliff Sarginson said...
> % File Locking + NFS = very bad news
>
> Agreed. If he has to use an mbox, though, he may not have many choices
> (my drop-in-mbox+run-razor+move-to-maildir kludge being one of them).
On Mon, Dec 03, 2001 at 07:28:15PM -0500, David T-G wrote:
> Roman --
>
> ...and then Roman Neuhauser said...
> % >
> % > ...and then Roman Neuhauser said...
> % > %
> % > % is there a means to let mutt perform an action on the message it sends
> % > % out _when_ it sends it? All the documented
* Cliff Sarginson ([EMAIL PROTECTED]) wrote:
> However these evil people who top-post mean that unless you want to
> complete addle the thread logic you also have to top post, in which
> case a sig at the end is a little weird.
If someone top posts I just nuke all their quotes and reply as norma
Cliff --
...and then Cliff Sarginson said...
% On Mon, Dec 03, 2001 at 07:17:14PM -0500, David T-G wrote:
% >
% > ...and then Cliff Sarginson said...
% > % File Locking + NFS = very bad news
...
% > % It is inherently unreliable.
% >
% > Always?
% >
% I would not design a production quality ma
On Mon, Dec 03, 2001 at 03:34:45PM -0500, Paul Brannan wrote:
>
> Perhaps this is a problem of the client being able to lock over nfs but
> the server not?
I think that this is exactly the problem... I dont know if you are on
linux, but in my mounts through NIS to an HPUX machine from linux, I u
On Mon, Dec 03, 2001 at 07:24:00PM -0500, David T-G wrote:
> % suggested in the other thread), and it successfully created
> % testfile.lock; mutt_dotlock -u testfile successfully removed the file as
> % well.
>
> And this was from your NFS client box? Interesting. I wonder why mutt
> doesn't
William,
On Mon, Dec 03, 2001 at 01:26:23PM -0800, Will Yardley wrote:
>
> what does your colors section look like? mine works fine, and i use the
> most recent release on both potato and woody with no problems. are you
> using 'default' for the background color? what TERM do you have set?
>
I've just noticed that if you are cycling through the command history
and abort with a ^G, the next time you invoke the line editor you are
placed at the point in history list at which you aborted.
example:
:command 1
:command 2
:command 3
:command 4
:command 5
cycle up the history to 'command
* Prahlad Vaidyanathan <[EMAIL PROTECTED]> [11/30/01 17:39]:
> > Or wait a little... I will rewrite the patch so that it can work along
> > with the new threading code.
Done.
> I'll take the latter option. Thanks !
You'll find the patch updated for the new threading implementation at
http://
the only quasi-official reference i've been able to find on the
Mail-Followup-To header is:
http://www.ietf.org/proceedings/98dec/I-D/draft-ietf-drums-mail-followup-to-00.txt
while i think that this becoming standard would be a Good Thing, since
the draft is from 1997, it would seem unlikely tha
Hi,
* Benjamin Michotte <[EMAIL PROTECTED]> [01-12-03 00:38]:
>Could I change my:
>find $HOME/mail -type f -print | grep -Ev '(outbox|trash|spam)' | sort
> | xargs
That part worked alright:
mailboxes `find ~/Mail -type d -print | grep -Ev
'(backup|sent|postponed|trash|/cur$|/tmp$|/new$|/Mail$|/
54 matches
Mail list logo
