David Champion:
Maybe the original poster (I forgot who...) would be OK with
"unbind * *" and "unmacro * *".
and, finalizing this thread, should this not be the default content of the
default fallback etc/Muttrc?
--
clemens [EMAIL PROTECTED]
On Sun, May 21, 2000 at 11:09:34PM -0300, thus spake Richard Spencer:
can I place instructions in the .muttrc
file to check two pop3 mailboxes?
--
No, they go in your .fetchmailrc. Mutt only plays with email
once it is delivered.
For a really good start-you-off
On Sun, May 21, 2000 at 08:37:21PM -0300, thus spake Richard Spencer:
created a .fetchmailrc like this...
poll pop3.uol.com.br proto pop3
user [EMAIL PROTECTED] pass secret1
fetchall keep
poll pop.a001.sprintmail.com proto pop3
user [EMAIL PROTECTED] pass secret2
fetchall
On Thu, May 25, 2000 at 01:21:50AM +0200, Marius Gedminas wrote:
Perhaps. I'm using 1.2. I don't remember when that was introduced.
in 1.1.11 it's also s and S ...
--
Christian Ordig | Homepage: http://thor.prohosting.com/~chrordig/
Germany |eMail:
Hi all,
Two short config questions:
- I have put "ignore (blabla)" into my .muttrc in order to keep the visible part of
the headers in incoming mail readable, but now I would like to sort the different
lines, too. Is this possible?
For example, right now most incoming messages show me the
On 2000.05.26, in [EMAIL PROTECTED],
"Manuel Arriaga" [EMAIL PROTECTED] wrote:
Hi all,
Two short config questions:
- I have put "ignore (blabla)" into my .muttrc in order to keep the visible part of
the headers in incoming mail readable, but now I would like to sort the different
Friday den 26.05.2000 um 13:12 CEST +0200, schrieb Manuel Arriaga:
Hi all,
Two short config questions:
- I have put "ignore (blabla)" into my .muttrc in order to keep
the visible part of the headers in incoming mail readable, but
now I would like to sort the different lines, too. Is
Hi, folks --
...and then David DeSimone said...
% Kristin Anne Igaki [EMAIL PROTECTED] wrote:
%
% I would very much like to use one instance of Mutt to get all my mail.
% However, I have 3 mail accounts on 3 different servers, 3 usernames, 3
%
% I believe Mutt supports the following syntax
On Fri, May 26, 2000 at 12:51:09AM +, Tom Gilbert wrote:
- * Jacob Davies ([EMAIL PROTECTED]) wrote:
- in my .muttrc. They all work OK, but the interface for dealing with multiple
- mailboxes in mutt doesn't seem that great. As I understand it, I will get
- notification that I have new
Timothy Ball:
I haven't gotten any mail from the mailing list in weeks now... I am I
unsubscribed or what?
i've been unsubbed for bounces. had to resubscribe. happens often these
days.
--
clemens [EMAIL PROTECTED]
Hi David,
- I have put "ignore (blabla)" into my .muttrc in order to keep the visible part
of the headers in incoming mail readable, but now I would like to sort the different
lines, too. Is this possible?
Read the manual regarding the hdr_order directive.
Thanks, now they look as I like
Hi Frank,
Thanks, setting alternates to my own address got the Fcc: mailbox to automatically
show the recipient.
Cheers,
Manuel
- Is it possible to set up your Fcc: mailbox (in my case
Mail/Sent) so that it displays the messages recipiend in the
index, instead of the sender (always
David T-G proclaimed on mutt-users that:
Do mutt and IMAP support
{user:pass@hostname:port}folder
instead? Of course, leaving your password(s) in your muttrc is probably
not a Good Thing (tm) anyway...
I haven't tried it but there is no reason why not. And re leaving your
password in
The Short:
I notice that when I 'resend-message' (ESCe) that it doesn't get
copied to my 'sent' folder.
The Long:
I'm a bad typist. Sometimes I mistype an address and send the
mail off. I get the bounce message.
Crack open mutt (v1.2) on my 'sent' folder where copies of all my
emails go. I
On Fri, May 26, 2000 at 10:35:16PM +0530, Suresh Ramasubramanian wrote:
- David T-G proclaimed on mutt-users that:
-
- Do mutt and IMAP support
-
- {user:pass@hostname:port}folder
-
- instead? Of course, leaving your password(s) in your muttrc is probably
- not a Good Thing (tm) anyway...
Since I upgraded to mutt 1.2, I haven't been able to get my
f1 help macros to work. These used to work for me:
# Show documentation when pressing F1
macro generic f1 "!less /usr/doc/mutt-1.0i/manual.txt\n" "Show Mutt documentation"
macro index f1 "!less /usr/doc/mutt-1.0i/manual.txt\n" "Show
Charles Curley proclaimed on mutt-users that:
Not necessarily. Your email server password may be different from your
login password. Mine are. You can, however, give only the user permission
to read or write to the two files, probably a good idea in general. An
other things we all know and
-kevin- [EMAIL PROTECTED] wrote on Fri, 26 May 2000:
I notice that when I 'resend-message' (ESCe) that it doesn't get
copied to my 'sent' folder.
I think that this is only because resend-message doesn't fill the Fcc
header by default. If you add a folder in there, it'll work...
But yes,
Thus spake Hardy Merrill ([EMAIL PROTECTED]):
Since I upgraded to mutt 1.2, I haven't been able to get my
f1 help macros to work. These used to work for me:
# Show documentation when pressing F1
macro generic f1 "!less /usr/doc/mutt-1.0i/manual.txt\n" "Show Mutt documentation"
macro
On Fri, May 26, 2000 at 02:24:34PM -0400 or thereabouts, Hardy Merrill wrote:
Since I upgraded to mutt 1.2, I haven't been able to get my
# Show documentation when pressing F1
macro generic f1 "!less /usr/doc/mutt-1.0i/manual.txt\n"
Telsa Gwynne [[EMAIL PROTECTED]] wrote:
On Fri, May 26, 2000 at 02:24:34PM -0400 or thereabouts, Hardy Merrill wrote:
Since I upgraded to mutt 1.2, I haven't been able to get my
# Show documentation when pressing F1
macro generic f1 "!less
Thomas Roessler [EMAIL PROTECTED] wrote:
To answer the original question: For mutt, no such thing
as a file extension exists when it looks at how to
interpret incoming data.
well, but attachments have a comment field or something
because i can see the name of the file being sent.
it also puts
David Champion [EMAIL PROTECTED] wrote:
Maybe the original poster (I forgot who...) would be OK with
"unbind * *" and "unmacro * *".
But there is no "unbind" nor "unmacro" command...
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is
On 2000.05.26, in [EMAIL PROTECTED],
"David DeSimone" [EMAIL PROTECTED] wrote:
David Champion [EMAIL PROTECTED] wrote:
Maybe the original poster (I forgot who...) would be OK with
"unbind * *" and "unmacro * *".
But there is no "unbind" nor "unmacro" command...
I know.
Carlos Puchol [EMAIL PROTECTED] wrote:
well, but attachments have a comment field or something
because i can see the name of the file being sent.
That's just a filename. MIME attachments also have a "Content-Type"
header which is supposed to tell the MUA exactly what type of document
is
Both of these revolve around the use of sig-dashes.
First, I have a corrspondent who (despite protests) uses the ``-- ``
sequence to separate his message from the text he is replying to.
Needless to say, this causes mutt to syntax hilight the first
paragraph of his reply as a signature. Perhaps
At 5:00 PM EDT on May 26 Anton Graham sent off:
Both of these revolve around the use of sig-dashes.
First, I have a corrspondent who (despite protests) uses the ``-- ``
sequence to separate his message from the text he is replying to.
Sounds pretty perverse. Maybe you could convince him
At 5:02 PM EDT on May 26 Rob Reid sent off:
At 5:00 PM EDT on May 26 Anton Graham sent off:
Both of these revolve around the use of sig-dashes.
First, I have a corrspondent who (despite protests) uses the ``-- ``
sequence to separate his message from the text he is replying to.
On Fri, May 26, 2000 at 03:59:19PM -0500, David DeSimone wrote:
Carlos Puchol [EMAIL PROTECTED] wrote:
well, but attachments have a comment field or something
because i can see the name of the file being sent.
That's just a filename. MIME attachments also have a "Content-Type"
header
On Fri, May 26, 2000 at 15:38:43 -0400, Hardy Merrill wrote:
In /etc/Muttrc, I only have the "mutt-1.0i" directory - I don't
have mutt-1.2. That was something I was wondering about - why
didn't the install give me a /usr/doc/mutt-1.2 directory?
If you didn't told the configure script to do
On Wed, May 24, 2000 at 04:08:55PM -0300, Richard Spencer wrote:
I wasn't able to install latest mutt rpm. According to the
error message, I _already_have_ the newest package :-(
# rpm -U /home/rks/ftp/mutt-1.2i-1.cfp.rhl6.i386.rpm
error: package mutt-1.0.1i-8 (which is newer then
On Fri, May 26, 2000 at 03:38:43PM -0400, Hardy Merrill wrote:
In /etc/Muttrc, I only have the "mutt-1.0i" directory - I don't
have mutt-1.2. That was something I was wondering about - why
didn't the install give me a /usr/doc/mutt-1.2 directory?
If you installed from tarball, it might be
Thomas Ribbrock ([EMAIL PROTECTED]) said:
I wasn't able to install latest mutt rpm. According to the
error message, I _already_have_ the newest package :-(
# rpm -U /home/rks/ftp/mutt-1.2i-1.cfp.rhl6.i386.rpm
error: package mutt-1.0.1i-8 (which is newer then
On 2000.05.26, in [EMAIL PROTECTED],
"Rob Reid" [EMAIL PROTECTED] wrote:
You mean strip sigs from quoted text in a reply? That's the editor's job
I strenuously disagree. I think we should rather say: it is the
established judgement of the Mutt development team that stripping
34 matches
Mail list logo
