-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, April 25 at 06:03 PM, quoth Rado S:
I use folder-hook to re-/set autoview: multipart/...
and have in ~/.mailcap:
-- QUOTE BEGIN --
multipart/alternative;cat;copiousoutput
multipart/mixed;cat;copiousoutput
--- QUOTE END ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, April 25 at 06:25 PM, quoth tannhauser:
Hi,
On Fri, 25.04, 10:11, Michael wrote:
Using vi here (default for OpenBSD), so will look at docs.
Using vim, :r!cat $file should do the trick for a text file.
That seems overly complicated.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, April 24 at 03:15 PM, quoth hce:
3. How can I setting a signature to attach a jpeg file or doc file?
Is it like following set in the muttrc? set
signature=~/mysignature.doc
That won't work, no. The standard signature settings are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, April 19 at 11:55 AM, quoth Romain JACQUET:
I'm using mutt to read my IMAP mailbox at free.fr (a french ISP) for
years.
Mutt has suddenly stop working.
You might want to ask on mutt-dev.
~Kyle
- --
Where all men think alike, no one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, April 17 at 12:41 PM, quoth Dirk Moolman:
just did. The manual says:
3.291. use_envelope_from
Type: boolean
Default: no
When set, mutt will set the envelope sender of the message. If
``$envelope_from_address'' is set, it will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, April 15 at 03:22 PM, quoth Ethan Mallove:
Is there a way in mutt to grep the body of mail messages, and
actually see the matching line from the mail message?
Within mutt? No, not really.
If this is not possible, is there a way to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday, March 30 at 11:23 PM, quoth Alain Bench:
The space there triggers mutt to replace everything you've typed
thus far with the name of whatever mailboxes contain new email.
To insert a literal space at the folder prompt, you can first
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, March 28 at 02:23 AM, quoth Stefan Wimmer:
Unfortunately this script does not work for me at all :-/
If I invoke it inside mutt with the ^b macro from your website (the
latest version) it throws out the list of URLs and freezes ... I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, March 27 at 02:22 PM, quoth Steffen Weise:
Hello Kyle,
On Sat, Mar 22, 2008 at 12:15:59AM -0500, Kyle Wheeler wrote:
After a bit of work, I've gotten a perl script that I think rivals
URLView. I call it extract_url.pl, and it's here
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, March 27 at 09:10 AM, quoth Vladimir Marek:
Hi Kyle,
After a bit of work, I've gotten a perl script that I think rivals
URLView. I call it extract_url.pl, and it's here:
http://www.memoryhole.net/~kyle/extract_url/
I wonder if it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, March 27 at 03:10 PM, quoth Chris G:
It's not just for html emails - it's for any email that may contain
a URL (for example, this one -- the extract_url web page's address
was in my original email, and is quoted up above). Rather
On Friday, March 14 at 10:50 PM, quoth Robert Svoboda:
This got me thinking about this:
1. pipe message through display_filter extracting and
numbering links
2. in the extracting step create macros for internal pager
which would correspond with numbered links
3. source those macros
4.
On Wednesday, March 26 at 09:59 AM, quoth Robert Svoboda:
* Kyle Wheeler [EMAIL PROTECTED] [2008-03-26 07:40]:
On the thought that just parsing a links would be
sufficient, I whipped up a little perl script based on what
I've done for extract_url.pl. I call this little script
tagurl.pl. I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 25 at 08:29 PM, quoth Andreas Pakulat:
Hi,
a long time ago I configured mutt to use firefox as browser when I
open an html attachment. Unfortunately I can't find the place anymore
and I'd like to change that back now. How does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 25 at 11:39 PM, quoth Wael Nasreddine:
I'm subscribed to a lot of mailing lists, and sometimes I'd like to
clean them up, but I want to keep any thread that I have at least
one reply to, how do I tag ALL except threads with my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 25 at 06:47 PM, quoth Alain Bench:
| send-hook . 'set [EMAIL PROTECTED]'
| send-hook ~l 'set [EMAIL PROTECTED]'
Does anything speak against this?
That's perfect for you, on the latest Mutt. But setting $from in
a send-hook
:
send-hook mutt-users@mutt.org \
my_hdr From: Kyle Wheeler [EMAIL PROTECTED]
~Kyle
- --
The next best thing to solving a problem is finding some humor in it.
-- Frank A. Clark
-BEGIN PGP SIGNATURE-
Comment: Thank you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, March 24 at 04:18 PM, quoth Dominik Meister:
Thanks Kyle, I think I've already once tried using a send-hook, but
that somehow messed up with the reverse_name setting. I give it
another try.
I just tried it and what happened is that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
After a bit of work, I've gotten a perl script that I think rivals
URLView. I call it extract_url.pl, and it's here:
http://www.memoryhole.net/~kyle/extract_url/
This is a Perl script that extracts URLs from correctly-encoded MIME
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 12:53 PM, quoth Chris G:
It seems to me that mutt is actually *encoding* the characters wrong
(or it's using a library that's doing that) as even if I save the
sentmail copy of a message with (for example) pounds signs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 02:14 PM, quoth Chris G:
Well I'm still not sure things are right, even after getting my
editor to do (approximately) the right thing.
Here are some incorrect pound signs:-
Those are all encoded as three bytes: 0xEF 0xBF
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 03:02 PM, quoth Chris G:
On Wed, Mar 19, 2008 at 02:57:19PM +, Chris G wrote:
If you look in the header of this message I *fear* you will see that
the charset is set to iso-8859-1. It's not my muttrc that's doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 03:15 PM, quoth Chris G:
How does mutt set about deciding what charset header to add?
Like this: mutt assumes that the file output by your editor conforms
to $attach_charset. It then uses iconv to convert that character
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 03:29 PM, quoth Chris G:
On Wed, Mar 19, 2008 at 03:14:43PM +, Michael Kjorling wrote:
On 19 Mar 2008 15:02 +, by [EMAIL PROTECTED] (Chris G):
Does something, somewhere *guess* the character set from the stream of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 03:42 PM, quoth Chris G:
http://www.mutt.org/doc/devel/manual.html#send-charset
On reading the manual I'm not sure I'm any the wiser, it says Mutt
will use the first character set into which the text can be converted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 02:22 PM, quoth Culley Harrelson:
I am ready to tackle this problem but when you pipe a message to a
script it looks like a new process is spawned and the new process
can't remain in control of the terminal. Can anyone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 05:08 PM, quoth Kyle Wheeler:
Eh? The new process remains in control of the terminal as long as it
wants (i.e. it can't give up control at any point). Here's the thing,
though: when you pipe a message to a script, you're
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 18 at 06:06 PM, quoth Vincent van Leeuwen:
All the messages have Message-ID's and References or In-Reply-To
headers which all seem to be correct. However, the Message-ID's from
person B do look a bit odd:
Message-ID: [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, March 15 at 11:52 AM, quoth Robert Svoboda:
This is relatively easy to do for typical text-based a href=URL
links and links listed in text/plain email, but what about things
like a href= links around images, or blockquote cite=URL or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, March 14 at 10:50 PM, quoth Robert Svoboda:
* Peter Münster [EMAIL PROTECTED] [2008-02-17 16:47]:
How can I tell mutt to fire up an external browser with some URL in the
message?
I use xclip way for this as mentioned earlier in this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 12 at 10:12 AM, quoth Matthias Apitz:
Well, is there some way to draw a magic vertical line in the xterm or
'vim' in column 72?
Kinda. Inside vim, try this:
:72vs
Of course, that's going to put a copy of your email over in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 12 at 10:06 PM, quoth Dilip M:
On Wed, Mar 12, 2008 at 5:29 PM, [EMAIL PROTECTED] wrote:
Does set ft=mail and sync=on activates it?
Well, if it isn't done automatically, it should ;)
I have set set editor=/usr/bin/vim -c 'set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 12 at 06:18 PM, quoth Christian Brabandt:
(By the way, I just tried setl fo+=a, but I did not like it, cause it
keeps on joining files that I want to keep separate)
Lines, you mean? Yeah, I know. I always use that auto-wrapping
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 12 at 08:23 PM, quoth Andreas Pakulat:
I'm trying to use mutt here with the imap service from
archiveopteryx and for some reason mutt stalls when I change the
mailbox from the inbox to some other after waiting a few seconds.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alain can correct me if I'm wrong about any of this. :)
On Wednesday, March 12 at 04:02 PM, quoth Jorge Luis:
set charset=iso-8859-1
Setting the $charset manually is usually a bad idea.
satyr's environment includes LANG=en_US.UTF-8; yekk's is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, March 13 at 12:06 AM, quoth Andreas Pakulat:
Aah, thanks. Looking at the output I don't see much, except the
following (towards the end of the file):
a0038 STATUS Spam (UIDNEXT UIDVALIDITY UNSEEN RECENT MESSAGES)
4 a0038 OK done
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, March 10 at 07:45 PM, quoth Didier BRETIN:
I setup the record variable to this pointer in my .muttrc:
set record=^
Something to keep in mind is this: shortcuts are resolved right away,
not later. $record is not re-interpreted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday, March 9 at 01:58 PM, quoth Francis Moreau:
My last example of screwed URL has been sent by outlook.
format=flowed was not set.
Ahh, yeah, then you're screwed.
Yeah... unfortunately, that macro (I've been trying it all
yesterday)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday, March 9 at 07:37 PM, quoth Francis Moreau:
OK, I though more about it and I think the situation is quite bad ;)
Here are the different use cases I can think of:
You forget, labeling is part of the issue. There's a difference
between how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday, March 9 at 10:04 PM, quoth Jörg Sommer:
| charset-hook ^iso-8859-1$ cp1252
Works! I don't understand why, because I read the manual as charset-hook
(re)defines iso-8859-1, but it works.
FYI it works beccause cp1252 is a superset of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, March 8 at 02:42 AM, quoth Gary Johnson:
But those steps tell mutt how to use an _external_ application, as
specified in the mailcap file, to view the message. Mutt doesn't
look at the content type associated with the extension to
On Saturday, March 8 at 02:10 PM, quoth Francis Moreau:
Actually it would be better to fix the source of the problem instead
of trying to find a workaround... But I don't know where these URLs
get splitted at first. Perhaps you could enlight me ?
Well, the SMTP RFC specifies a recommended
On Saturday, March 8 at 11:15 AM, quoth Kyle Wheeler:
Yeah... unfortunately, that macro (I've been trying it all
yesterday) doesn't *quite* work on all emails. Lynx sometimes gets
confused by the message headers, I think.
I just put together a perl script that would do the trick instead
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, March 7 at 10:26 AM, quoth Francis Moreau:
So my problem is that I often receive emails including some URLs.
But they're usually not displayed in one line but splitted into 2
parts. Then if I want to call urlview to extract URLs out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, March 7 at 10:50 PM, quoth Angel Olivera:
I am running Debian's 1.5.17+20080114-1 (which shouldn't matter) and
Dovecot 1.0, which maps my inbox to '=INBOX'.
Okay.
I have $folder and $spoolfile set appropriately,
Heh, well, it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, March 7 at 04:20 PM, quoth Gary Johnson:
(Sigh.) I just received a message containing a forwarded message as
an attached .eml file. Mutt doesn't seem to know what to do with
it.
Mutt will only use file-extensions if you tell it to.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, March 8 at 07:30 AM, quoth Amit Finkler:
I run an openSuSE 10.3 box with mutt installed as a built .rpm
package from the developers of openSuSE. Mutt comes configured (and
compiled) with the -USE_SMTP flag. Nevertheless, is it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, March 8 at 08:48 AM, quoth Amit Finkler:
Kyle Wheeler wrote:
On Saturday, March 8 at 08:37 AM, quoth Amit Finkler:
Meaning the USE_SMTP flag does not have to be on?
Correct. The USE_SMTP flag indicates whether mutt can speak SMTP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, March 6 at 10:27 AM, quoth Jörg Sommer:
If you get a broken message that says it is iso-8859-1, but is
cp1252. You don't want to edit the MIME header every time, but save
it to the mailbox after the first time. It's obvious this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 5 at 12:00 PM, quoth Bill Moseley:
Most of the time I get HTML email that also has a text/plain part,
and that's what I reply to.
I've been getting mail from someone using Thunderbird that is
text/html only.
What I've been doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 5 at 03:39 PM, quoth Claude Rubinson:
Once I've changed the MIME type for a given attachment (edit-type), is
there a way to write that change to the file so that the change isn't
lost?
What do you mean? MIME types are only stored
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 5 at 04:12 PM, quoth Bill Moseley:
Is there anyway to say use auto_view and the .mailcap entry for the
pager, but in the attachment menu use a different mailcap entry? I
didn't see in 3.3.1 Optional Fields a way to have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 4 at 08:45 AM, quoth Bill Moseley:
I need a cron job to do this automatically, but every so often I want
to move old messages out of my mailbox (it's a bit slow loading my IMAP
folders when they go over 20K messages or so). So
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 4 at 12:49 PM, quoth Bill Moseley:
On Tue, Mar 04, 2008 at 10:50:55AM -0600, Kyle Wheeler wrote:
If your IMAP connection is slow, though, you may want to consider
using mutt's hcache support, which will dramatically speed things
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, February 29 at 10:21 AM, quoth Dilip M:
How can I get this work for emails I replying?
A send-hook doesn't work? Huh, that's odd. Perhaps a reply-hook will
work.
I'm having, below setting in .muttrc.
unmy_hdr CC
send-hook st.com 'my_hdr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, February 29 at 03:49 PM, quoth Nathan Huesken:
I am changing my from in a send-hook. But if my .muttrc looks like
this in example:
set from=[EMAIL PROTECTED]
send-hook . '[EMAIL PROTECTED]'
The first message I write is send from [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, February 29 at 05:00 PM, quoth wishi:
I'm going to use mutt as MUA... but I'm new here, and so I have got
3 questions. Hopefully, it's possible:
Glad to have you aboard! Let's see what we can do.
1. I'm using mailing lists, and a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, February 29 at 10:21 PM, quoth Dilip M:
Kyle Wheeler [EMAIL PROTECTED] wrote:
A send-hook doesn't work? Huh, that's odd. Perhaps a reply-hook
will work.
No luck with that too :(
Very strange. I would think *both* would work. I just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, February 29 at 02:53 PM, quoth Chris Sussmann:
Mutt then replies that Mail is not a folder. Now the macro works
with Spam or Drafts because they don't have a space in the name of
the folder.
It's a bug. One I've been pretty annoyed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, February 29 at 04:19 PM, quoth Kyle Wheeler:
The only workaround I've found is to use tab-completion to make mutt
insert the space for you. Assuming none of your other mailboxes begin
with Sent, something like this would work:
macro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, February 29 at 10:55 PM, quoth Michael Kjorling:
On 29 Feb 2008 16:19 -0600, by [EMAIL PROTECTED] (Kyle Wheeler):
The space there triggers mutt to replace everything you've typed thus
far with the name of whatever mailboxes contain new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, February 28 at 03:40 PM, quoth Dilip M:
Hi,
I'm using Mutt version 1.5.10i. Is there any option to set a email id
automatically in CC field?
I know, this is odd. But just want to back up all office emails in PST :(
I tried set my_hdr,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, February 28 at 10:14 PM, quoth Ad. Teixera:
Hello,
This macro is working:
macro index ESCf :unset wait_key\n;!~/myScript\n;:set wait_key\n \
menu for fetching mail
this one works also, but it is not setting the wait_key at the end of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, February 29 at 12:46 AM, quoth Nathan Huesken:
So the script needs to get the eMail from stdin, but also be
intaractive with the user (utilizing the read command).
If I do:
pipe-messagescriptenter
The reason the read command exits is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday, February 24 at 07:46 PM, quoth Arnaudo Massimo:
i would to choose what type of dictionary to spellcheck the outgoing
mails (i use vim 7.1.245), but i can not understand how to pass my choice.
Can you suggest me how i have to do?
Well,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, February 22 at 09:34 PM, quoth Matt Richards:
I use a shell-escape to invoke fetchmail aswell as other things and
it always says Press any key to continue at the end.
Is it possible to just return to mutt without this halt?
From the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, February 22 at 05:01 PM, quoth Patrick Shanahan:
* Matt Richards [EMAIL PROTECTED] [02-22-08 16:32]:
I use a shell-escape to invoke fetchmail aswell as other things and it
always says Press any key to continue at the end.
Is it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, February 18 at 11:48 AM, quoth Breen Mullins:
For others who may want to try this, I had to make some changes to
get it to work.
You changed my definition. I actually do type comma-d-s to trim the
message. (All of my macros tend to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, February 18 at 09:04 PM, quoth Dave Evans:
On Fri, Feb 15, 2008 at 10:35:07AM -0600, Kyle Wheeler wrote:
Where is that header defined? Why not use the OpenPGP header (defined
here: http://josefsson.org/openpgp-header/)
Is it just me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, February 16 at 09:19 AM, quoth Benjamin Buch:
H... and these are all local folders? The next task is to
figure out why mutt isn't seeing new mail in them. What sort of an
environment are we working with? Are these folders mbox's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, February 15 at 01:09 PM, quoth Vladimir Marek:
I recently switched from evolution to mutt, and I wonder how to
deal with new mail. In evolution, all received mail was sorted in
diffenrent folders, but I had a special folder where all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, February 15 at 05:45 AM, quoth Joseph:
I added a header like this: X-PGP-Key:
http://www.ekn.com/~tech_gpg.asc for my key. What clients if any
support this format? Are their clients that can use that to confirm
the key validity?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, February 14 at 03:35 PM, quoth Dongsheng Song:
When I use the example gpg.rc, mutt can't sign in attachment like
signature.asc, why ?
What do you mean? It doesn't give the signature a filename, true, (and
to my knowledge, can't) but why
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, February 13 at 04:52 PM, quoth Ad. Teixera:
If I press e in the index menu, it will open the raw mail in the
editor. Is it also possible, to see the raw mail in the pager or
pipe it into an external one?
Yes. Piping a message (by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, February 12 at 08:58 PM, quoth SK:
I can almost use this, except for a small hurdle. I need to set the
fcc file name based on the mailbox folder. Currently I use
'folder-hook' to do that. Is there anyway I can tweak this macro to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, February 12 at 08:19 PM, quoth SK:
Do you want to press a key to make mutt save messages to a specific
folder, but to not do so if you do not press this key?
Yes, exactly, without even having to answer the Yes/No question (if
I set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, February 12 at 08:06 PM, quoth SK:
Thanks for the informative reply Kyle. I think I will use the fcc-hook
way but before that, just to reconfirm - there is no simple option
(say a key binding) that is equivalent to checking the Save
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, February 12 at 07:10 PM, quoth SK:
As far as I read the amanual, set copy allows one to specify
whether to keep a copy of all sent emails. Is there any way in which
I can disable this behavior by default (i.e. unset copy) but in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, February 12 at 03:03 PM, quoth [EMAIL PROTECTED]:
Hi,
Thanks for your reply. ldap is running on my vServer. But I am not sure how to
setup lbdb to use ldap and mutt to use lbdb.
Any advise where to look?
http://www.spinnaker.de/lbdb/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, February 11 at 03:00 PM, quoth senator galt:
On Feb 11, 2008 2:18 PM, Kyle Wheeler [EMAIL PROTECTED] wrote:
But since you're having a problem between versions, I'd look into what
version of ncurses/slang/iconv are they linked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, February 11 at 01:45 PM, quoth senator galt:
Hello,
I'm using mutt 1.5.15 and the threads are shown with└─
now, I compiled the pristine source of mutt 1.5.17 and the threads are
shown with �~T~T�~T~@
Any suggestions on how to fix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, February 7 at 12:01 AM, quoth [EMAIL PROTECTED]:
I think the point that the people on the Postfix mailing list were trying
to make is that the MUA (in this case mutt) should not be sending
something to the MTA that is marked as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, February 5 at 03:27 PM, quoth [EMAIL PROTECTED]:
The summary of this is that since I am running on Linux text/plain
MUST have unix line endings rather than DOS and so Mutt should
convert the CRLF to LF before sending the file to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday, February 3 at 01:37 PM, quoth Arthur Dent:
I have looked at the Mutt manual, and man muttrc, but I cannot see
however any way to customise the view when in the folder browser.
You were right the first time, it's $folder_format.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, January 31 at 03:18 PM, quoth Dan H.:
On Thu, Jan 31, 2008 at 01:28:23AM +0100, Alain Bench wrote:
Is the number of the just delivered mail included on the
unseen: line of .mh_sequences? Otherwise it's to be
considered
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, January 31 at 03:40 PM, quoth [EMAIL PROTECTED]:
When sending mail from mutt I have begun getting the following message in
/var/log/mail.log:
Jan 31 07:02:37 bill-2 postfix/smtp[868]: E0F13CD105: to=[EMAIL PROTECTED],
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, January 31 at 03:40 PM, quoth Derek Yarnell:
So I have a user that is having a very hard time with mutt and connecting
to a IMAP mailbox. Once or twice a day his mutt will lock up for 5-10mins
when fetching a message and then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, January 30 at 11:41 AM, quoth Lucas J. González:
I see that other users of this list also show different domains in the
message-id field.
Possibly the error was due to special characters into $realname ?
It's a possibility, but I think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, January 30 at 08:21 AM, quoth Michael Kjorling:
On 30 Jan 2008 11:41 +0900, by [EMAIL PROTECTED] (Wilkinson, Alex):
folder-hook . \
set sort=reverse-threads ;\
This semicolon^
terminates the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, January 30 at 12:50 PM, quoth Michael Pobega:
How (in my .muttrc) do I tell Mutt to automatically scroll to the new
(i.e. non-quoted) content of the mail? What I mean is the equivalent of
S's keybinding when viewing mail.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, January 28 at 02:28 PM, quoth Dan H.:
1. I can't access encrypted mail that I send. When I try to read
it, I get Could not copy message.
That's by design (but it's a rather uninformative error message).
Encrypted email can only be read
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, January 28 at 09:28 AM, quoth Dan H.:
On Sat, Jan 26, 2008 at 04:05:10PM -0600, David Champion wrote:
It certainly supports this, but it depends on the mail source itself to
say what's read. Mutt can alter these flags, but so can other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, January 28 at 02:49 AM, quoth [EMAIL PROTECTED]:
Your suggestion below pointed out that .bash_profile is the
initialization file. But .bash_profile has no references to Path
in it. I can add PATH=$PATH:/sw/bin as you suggested,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, January 28 at 03:31 AM, quoth [EMAIL PROTECTED]:
Thanks for the thorough explanation. It helped me to grasp how the whole Path
thing works.
Since I would like to add /sw/bin to my /etc/profile I opened it, but only
discovered:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, January 25 at 09:27 AM, quoth Dan H.:
- Is it legal for Claws, according to the MH spec, to put
.mh_sequences in places that don't contain actual messages?
Yes, it's technically legal. By doing so, Claws is defining those
folders as MH
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, January 25 at 09:11 PM, quoth Leonardo Caldas:
Hey, it worked perfectly! In fact I've read mutt manual, and here and
there I read its changelog, and all... anyway, I'd never seen
'unmailboxes'...
:) Excellent!
For what it's worth, I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, January 25 at 03:40 PM, quoth Michael Pobega:
I'm wondering if there is some easy way to delete duplicate e-mails from
within Mutt; What I mean is, when Mutt is displaying my e-mails threaded
the mail is denotated with = instead of -.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, January 25 at 08:37 PM, quoth Leonardo Caldas:
I got a doubt and perhaps someone could help me out. Besides my
muttrc I have several other sourced config files (ie macros,
bindings, mailboxes, etc). For listing my mailboxes I've been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, January 24 at 03:36 PM, quoth [EMAIL PROTECTED]:
Recently, I switched from and older MacBook Pro to a new MacBook
using Apple's Migration Assistant. All User issues went well, but
unix issues did not fair so well. One of which was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, January 14 at 10:11 AM, quoth Francis Moreau:
On Jan 11, 2008 7:42 PM, Kyle Wheeler [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, January 11 at 06:19 PM, quoth Francis Moreau:
So now I'd like
601 - 700 of 1007 matches
Mail list logo
