-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Friday, May 8 at 06:08 PM, quoth Luis A. Florit:
But I have three charsets:
$charset=//TRANSLIT
?charset=utf-8
What? That doesn't make any sense. Are those two lines actually in
your muttrc?
The only thing in my .muttrc is 'set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Friday, May 8 at 03:00 PM, quoth Aaron S.:
I have a mystery that I'm trying to solve to no avail.
Hopefully we can help!
I got a little sample XML (utf-8) encoded file that I'm trying to
send as attachment. When I attach it, mutt correctly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, May 7 at 09:14 AM, quoth Haines Brown:
I retrieve mail with fetchmail, which I have poll both mail
servers.
And it's delivered to different mail folders?
That's the problem. While I can tell mutt to read the mail in a
specific
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, May 7 at 01:31 PM, quoth Haines Brown:
I guess the most straightforward procedure would be to rely on
procmail to direct incoming mail to differet inboxes that rmail and
mutt can access.
Probably, yup.
You were kind to reply, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, May 7 at 05:00 PM, quoth Haines Brown:
So, either put mutt in a room with a corner (e.g. set up gpg
correctly) OR don't tell mutt to stand in a corner whenever messages
with signatures show up (e.g. set crypt_verify_sig=no).
Does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, May 7 at 09:40 PM, quoth Luis A. Florit:
On Monday, May 4 at 05:05 PM, quoth Luis A. Florit:
I use a ISO-8859-1 encoded xterm in maemo, but :set ?charset
gives me charset=utf-8.
Are you setting it in your config somewhere? (test it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, May 5 at 06:19 PM, quoth Michael Tatge:
* On Tue, May 05, 2009 05:33PM +0200 Christoph Kukulies (k...@kukulies.org)
muttered:
Yes, in .muttrc I have :
set charset=iso-8859-1# character set for your terminal
That's my output
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, May 6 at 03:33 PM, quoth Alex Huth:
Now i get the reverse sort as default, threads in freebsd-current
and the error unknown command for freebsd-acpi. It seems that
source is the problem. But if this is a unknown command in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, May 6 at 05:29 PM, quoth Haines Brown:
I started with the idea I could configure mutt to accomplish the goal
I describe below, but I'm not sure I can.
Why not?
I retrieve mail with fetchmail, which I have poll both mail servers.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, May 5 at 01:32 PM, quoth Christoph Kukulies:
During searching for a way to pretty print my Emails from mutt I found,
that all messages (or at least the message under concern)
are stored from ISO-8859-1 to quoted-printable.
I don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, May 4 at 05:05 PM, quoth Luis A. Florit:
I use a ISO-8859-1 encoded xterm in maemo, but :set ?charset
gives me charset=utf-8.
Are you setting it in your config somewhere? (test it my running `mutt
- -F /dev/null` and seeing what the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, April 30 at 09:12 PM, quoth Chengqi(Lars) Song:
Hi,
I always get this message when sending mail:
Apr 30 20:24:19 host=smtp.abc.com tls=on auth=on user=lars from=l...@abc.com
recipients=larsgg.tosp...@abc.com errormsg='TLS handshake
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, April 27 at 08:17 PM, quoth m...@coreland.ath.cx:
A problem seems to have started recently: Mutt seems to think
that my mailbox is always unchanged.
Why is that a problem?
I have around 100 read emails in my spool (and growing) and
when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, April 27 at 07:45 PM, quoth Grant Edwards:
As has been discussed extensively recently, when you sync (e.g.
with the $ key), mutt doesn't check for new messages, it just
pushes its changes to disk.
I think all of the confusion is due
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, April 27 at 09:07 PM, quoth m...@coreland.ath.cx:
On 2009-04-27 19:45:13, Grant Edwards wrote:
On 2009-04-27, Kyle Wheeler kyle-m...@memoryhole.net wrote:
On Monday, April 27 at 08:17 PM, quoth m...@coreland.ath.cx:
A problem seems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, April 27 at 10:48 PM, quoth Albert Shih:
Another question :
Some people send me mail directly to me (instead helpdesk), when I
answer it, I put «helpd...@mycompagny» in CC:
Is they are any solution to put
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday, April 26 at 06:59 PM, quoth Cameron Simpson:
On 26Apr2009 18:55, I wrote:
| Hmm. Still no joy. I copied a message into it from my mutt folder.
| Nothing. Went in with another mutt. Message visible (though not new).
| Marked it new. Synced.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday, April 26 at 10:15 AM, quoth Rocco Rutte:
Hmm, that's true. There's really no way to force new mail polling. I
think for mutt-ng I once hacked up a new option that would force a
full check together with buffy-list. Maybe we should add a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, April 24 at 03:33 PM, quoth Cameron Simpson:
But then, I also use Maildir instead of mbox, because it avoids
lots of this kind of silliness (it's also a more well-defined
mailbox format).
I find mutt doesn't notice new email in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, April 25 at 07:31 AM, quoth Cameron Simpson:
Well, if I've got my +me folder open and press '$', an strace shows
only this (all system calls with the string /me in them):
[pid 28316] stat(/home/cameron/mail/me, {st_mode=S_IFDIR|0755,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, April 23 at 09:54 PM, quoth Chris G:
I'm sure I should be able to find this in the documentation somewhere
but finding * isn't very productive! :-)
So, what does an asterisk against a mailbox name mean?
Against?
... in what context?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, April 23 at 10:32 PM, quoth Chris G:
-- Mutt: Directory [=Li], File mask: !^\.[^.]
- ../ Apr 23 21:45 4.0K
alug*Apr 23 21:15 4.2K
digikam*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, April 23 at 10:58 PM, quoth Chris G:
vile*Apr 23 21:15 4.1K
xm-l Apr 23 22:15 6.5K
What do those asterisks indicate?
Hmm, not sure. What's your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, April 23 at 11:17 PM, quoth Chris G:
I know mutt detects new mail in mbox format by comparing the last
access time with the modification time of the file. However I can't
find anywhere that tells me the exact logic.
In particular
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, April 21 at 03:21 PM, quoth jk...@kinz.org:
The script is a little slow. It has 14 or so spawned processes
which could be replaced by internal Bash parameter
expansions.
Lemme see if I can help with that. :)
Here is script I found on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, April 21 at 10:50 PM, quoth Zhengquan Zhang:
On Mon, Apr 06, 2009 at 10:39:17PM -0500, Kyle Wheeler wrote:
On Monday, April 6 at 09:56 PM, quoth Zhengquan Zhang:
macro index,pager G ! /usr/bin/getmail -v \n Invoke getmail
macro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, April 21 at 11:05 PM, quoth Zhengquan Zhang:
This has puzzling me for quite a while,
I saw in several muttrcs
they use
folder-hook . set sort=threads
but I don't understand why they don't use
set sort=threads
instead.
Basically
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday, April 19 at 02:26 PM, quoth Rocco Rutte:
The problem with hcache is (currently, without the patch attached to
ticket #2942) that it's written only once when initially parsing the
message. Thus, if the date is Epoch upon first parse,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday, April 19 at 04:07 PM, quoth Rocco Rutte:
* Kyle Wheeler wrote:
On Sunday, April 19 at 02:26 PM, quoth Rocco Rutte:
The problem with hcache is (currently, without the patch attached to
ticket #2942) that it's written only once when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, April 18 at 10:27 AM, quoth He Wen:
i wanna know how to highlight a specific field of a index item, for
example, the date field?
There's no good way, unfortunately. There may be a patch out there
somewhere that allows you to do it, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, April 18 at 10:43 AM, quoth Paul E Condon:
I had thought that I could edit into the email a Date: header with
the correct date,
Yup, that's the way to do it.
Let me guess: you edited the message outside of mutt, and you use
header
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, April 18 at 12:29 PM, quoth Paul E Condon:
What is a sync in this context?
Essentially, when mutt opens a mailbox, it builds a picture of the
mailbox's state in memory. When you mark messages as deleted, this
is done in memory, rather
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, April 18 at 02:12 PM, quoth Paul E Condon:
Nope. But mutt can cache the date header (if you told it to).
OK, header cache is the mysterious something that was stopping me.
Hardly mysterious... header caching isn't turned on by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, April 14 at 11:03 PM, quoth June Qiu:
Basically, I just want to access the mails via the mail interface.
The dovecot has been configured and running, just that I am not sure
how to send/receive mails via mutt if my mails are all located
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, April 15 at 09:23 AM, quoth Michael Maurer:
* J. Limon jli...@eml.cc [15.04.2009 08:46]:
On Wed, Apr 15, 2009 at 08:08:56AM +0200, Joost Kremers wrote:
On Wed, Apr 15, 2009 at 01:46:40AM -0400, J. Limon wrote:
Other ncurses based
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, April 15 at 08:23 AM, quoth June Qiu:
actully, i thought by default, mutt compiles wth imap support? Does
it?
Nope; that requires a bunch of extra libraries (for authentication and
such), so it's not enabled by default.
I've tried
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, April 15 at 07:34 PM, quoth jac...@gmail.com:
Is there a way to make it go up a line instead,
Not that I know of.
or at least disable the cursor-automove entirely?
Sure: set resolve=no
~Kyle
- --
You can get more with a kind word
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, April 15 at 10:21 PM, quoth Zhengquan Zhang:
On Wed, Apr 15, 2009 at 10:18:09PM -0500, Zhengquan Zhang wrote:
Dear mutt community,
I use
mailboxes `find ~/.muttmail/ -type d -name cur -printf '%h '`
Basically is there any ignore
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, April 13 at 12:42 PM, quoth Arthur Dent:
I have these entries in my .muttrc
set folder=imaps://192.168.123.101:12345
set spoolfile=imaps://m...@192.168.123.101:12345
set imap_user = mark
set imap_pass = mypass
The problem comes when I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, April 13 at 03:21 PM, quoth Arthur Dent:
The problem comes when I come to send mail with mutt. I now get
the message:
Could not connect to 192.168.123.101 (Connection refused)
and no mail is sent.
#Send Mail Through GMail:
set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, April 13 at 08:47 PM, quoth Arthur Dent:
set record=imaps://192.168.123.101/Sent
When I installed the SSL certificate I had to change the imaps folder
and spoolfile references to be ...192.168.123.101:12345 (with 12345
being the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday, April 12 at 08:49 PM, quoth June Qiu:
I can't figure out why I have the following errors when I am using
libiconv 1.12. Pls help!
:
checking iconv.h usability... yes
checking iconv.h presence... yes
checking for iconv.h... yes
checking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, April 10 at 12:33 PM, quoth J. Limon:
When I get my own email reply from a mailing list it shows up in the
Inbox listing as like this..
11 F Apr 10 To Ubuntu user ( 35) └─
(An example of me replying to something in Ubuntu Users)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, April 10 at 01:10 PM, quoth J. Limon:
Also, is it just me or does this list not have a proper reply-to ?
When I hit reply it tried to reply directly to you.
I never noticed. I think there's an argument to be had about reply-to
mangling
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, April 10 at 12:54 PM, quoth Ravi Uday:
hi
how can you make mutt enter the signature at 'cursor' position instead
of appending it at the end of mail
To do that, you'd add the following to your muttrc:
set sig_on_top=yes
But *please*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, April 10 at 02:49 PM, quoth Ravi Uday:
The problem is if its a lengthy email thread with many people
replying ontop of each other, when I now write a mail my sig., will
be the last line in that email, and doesn';t make sense as to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, April 8 at 02:29 PM, quoth Jeff Davis:
I'm looking for doc on how to incorporate formail into my mutt
configuration to tame the run-on text-widths of received mail
messages.
Why use formail?
That seems to be a question akin to I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, April 8 at 02:37 PM, quoth Zhengquan Zhang:
send-hook '~t ccl-tech' push
'edit-cc,o...@ccl.northwestern.eduenter'
But today when I was trying to use L to reply some mails from ccl-tech
mailing list, this send-hook does not work..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, April 7 at 02:09 PM, quoth zhang zhengquan:
I would like to auto cc somebody when I send mail to a recipient
Okay, easy enough.
I googled and put this in to my send_hooks file
send-hook a...@abc.edu \
push
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, April 7 at 02:47 PM, quoth zhang zhengquan:
When you do not specify a simple pattern operator, mutt uses the
value
of $default_hook to construct the pattern. I don't know what yours is,
but... the default value of $default_hook is ~f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, April 7 at 04:25 PM, quoth Zhengquan Zhang:
Sounds like mutt didn't recognize the \ at the end of the line.
(did you leave some extra spaces in there?) Try making them single
lines.
I made them single line and it still does not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, April 8 at 12:26 AM, quoth Zhengquan Zhang:
I tried this minimal muttrc
set edit_headers=yes
set folder=~/.muttmail
set spoolfile=+inbox #+is the shortcut of $FOLDER
set postponed=+postponed
set record=+sent
set mbox_type=Maildir
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, April 6 at 09:01 PM, quoth Dave Feustel:
I currently have the mutt editor set to vim. I would like to
use gvim instead, but when I specify gvim and start a reply
to an email, gvim starts with an empty screen. Is there a
way to get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, April 6 at 04:13 PM, quoth zhang zhengquan:
Dear mutt community,
here is a snippet of my muttrc
set spoolfile=+inbox
set mbox=+inbox
set mbox_type=Maildir
set folder=~/.muttmail
set move=yes
Both $spoolfile and $mbox may not be what you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, April 6 at 04:50 PM, quoth Zhengquan Zhang:
If that's your entire muttrc, it is meaningless. It would only have
any meaning if you use mbox-hooks elsewhere in your config.
Thanks, so is there any rationale behind how to set spoolfile
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, April 6 at 05:26 PM, quoth Zhengquan Zhang:
here is a snippet of my getmailrc
[destination]
type = MDA_external
path = /usr/bin/procmail
I use getmail to fetch mail from pop server and use procmail to
process the mails. I 'guess' I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, April 6 at 09:56 PM, quoth Zhengquan Zhang:
macro index,pager G ! /usr/bin/getmail -v \n Invoke getmail
to get mail from pop servers.
While simple-looking, it's generally a better idea to call the
functions you want to use directly from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, April 4 at 02:40 PM, quoth Wilkinson, Alex:
0n Thu, Apr 02, 2009 at 12:21:53PM -0500, Kyle Wheeler wrote:
in the .muttrc I have tried with different carset options:
- set charset=iso-8859-1
- set charset=utf-8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, April 4 at 03:39 PM, quoth Charles Howard:
I use `a' to take an address into an alias file.
But can I do this from a Cc address ?
This question must have been asked before, but I can't find it going back to
2004.
Try it! If it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, April 4 at 05:29 PM, quoth Charles Howard:
Very funny, I don't think.
So let me rephrase my question :
Is there a way to take an address from the Cc field to an alias file,
similar to how one uses `a' for the From field ?
Sure.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, April 3 at 09:24 AM, quoth Roger Casaponsa:
letter in the original mail -- letter when editing a reply
ó -- ó
ò -- ò
à -- Ã (with a space)
' -- â8099
H. Those look like UTF-8 characters that are being misunderstood
by your editor.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, April 2 at 06:54 PM, quoth Roger Casaponsa:
When I recieve an email with some accents it is displayed correct
Good!
but when I reply it, in the editor, they are changed to rares
characters.
rares? You mean invalid or incorrect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 31 at 10:38 AM, quoth Russ Urquhart:
I am trying to test the sending of an email to myself but i get the
following error message:
mutt SMTP session failed: 550 5.1.8 invalid/host-not-in-DNS return
address not allowed
Hmmm,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, March 30 at 10:38 AM, quoth russurquha...@verizon.net:
I've been trying to compile mutt to use SMTP. I've used the
following configure:
./configure --prefix=/usr/local --with-curses --with-regex
--enable-locales-fix \
--enable-pop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, March 30 at 01:18 PM, quoth russurquha...@verizon.net:
Thanks for the reply and the dressing down! :)
Well, it wasn't intended to be a serious dressing down... but you're
now saying something completely different from your original
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, March 28 at 01:20 PM, quoth Chengqi(Lars) Song:
hi,
the default forwarding in mutt is to attach the original mail as a
file, but i like to forward with quoting original mail text. How to
configure it? thanks
unset mime_forward
~Kyle
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 24 at 03:30 PM, quoth Michael Tatge:
Is it working? Somehow.
If I manually enter the score it works. If I put the line in muttrc it's
not. Even if I source that file in a folder-hook it seems the message
parsing comes too late for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, March 23 at 08:40 AM, quoth Joshua Tinnin:
Program received signal SIGSEGV, Segmentation fault.
0x080cb71f in safe_strdup ()
(gdb) backtrace
#0 0x080cb71f in safe_strdup ()
#1 0x080b4d6a in rfc822_cpy_adr_real ()
#2 0x080bc09c in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, March 20 at 12:03 PM, quoth W. Martin Borgert:
On 2009-03-19 21:03, Kyle Wheeler wrote:
You *might* be able to restore it, *if* you use an alternate temp
directory (i.e. if you set the $TMP environment variable, or the
$tmpdir muttrc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 18 at 09:14 PM, quoth John J. Foster:
On Wed, Mar 18, 2009 at 04:13:19PM -0500, Kyle Wheeler wrote:
and IMAP makes it possible for me to sue my own client when I can.
I'm so glad you're not my lawyer.
HA! Whoops, typo. :D
~Kyle
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, March 19 at 09:21 AM, quoth Marc Vaillant:
Sorry, but I think, here you are wrong. Good IMAP-Clients don’t
download the attachments without your interaction (at least you can
configure them in such a way). So the reading of the mails
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, March 19 at 09:19 AM, quoth Joshua Tinnin:
Any ideas?
Unfortunately, no... I think you need to take that to the
mutt-...@mutt.org list.
~Kyle
- --
I know that there are people who do not love their fellow man, and I
hate people like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, March 19 at 10:42 AM, quoth David Champion:
I think the best summary is that IMAP is a remote mailbox access
protocol, supporting all common mailbox operations at the protocol
level. POP is not: it supports full message retrieval,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You *might* be able to restore it, *if* you use an alternate temp
directory (i.e. if you set the $TMP environment variable, or the
$tmpdir muttrc configuration setting, or maybe if your editor keeps
draft files in a nonstandard place).
Here, I'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 18 at 09:01 PM, quoth Jan-Herbert Damm:
imap-issues are being discussed on this list quite frequently. i
wonder what the benefit of imap generally is?
The same as any network-accessible system: access.
Here's a comparable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 17 at 10:06 AM, quoth Asif Iqbal:
I have been accessing our microsoft exchange folder using IMAP. But
yesterday IT did a maintenance and now I cannot access it any more.
Yike.
[REFERRAL imap://iqbala;aut...@mx.example.com/INBOX]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 17 at 10:48 AM, quoth Asif Iqbal:
Looks like this is what I am experiencing
ftp://ftp.rfc-editor.org/in-notes/rfc2221.txt
How do I tell mutt to follow the imap referral ?
Mutt doesn't follow imap referrals; but it's relatively
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 17 at 10:58 AM, quoth Noah Sheppard:
Mutt doesn't follow imap referrals; but it's relatively easy to
simply update your muttrc to use the new location for your email.
I'm curious. Is there a specific reason why mutt doesn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 11 at 10:36 AM, quoth Joshua Tinnin:
Here it is:
Program received signal SIGSEGV, Segmentation fault.
0x080cb71f in safe_strdup ()
(gdb) backtrace
#0 0x080cb71f in safe_strdup ()
#1 0x080b4d6a in rfc822_cpy_adr_real ()
#2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 10 at 07:11 AM, quoth Haines Brown:
Mailboxes are normally set up based on UID. For example,
use...@domainname.org, use...@domainname.org. However, I need to set
up mailboxes (a debian etch machine) based on different domain
names
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 10 at 12:44 PM, quoth Haines Brown:
On Tuesday, March 10 at 07:11 AM, quoth Haines Brown:
Mailboxes are normally set up based on UID. For example,
use...@domainname.org, use...@domainname.org. However, I need to set
up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 10 at 11:58 AM, quoth Paul E Condon:
So is it correct to say that the difference between a 'folder' and a
'mailbox' is that a mailbox is a folder that is checked on occasion
for the arrival of new mail?
Unfortunately, its not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, March 9 at 11:47 AM, quoth Joshua Tinnin:
I should reiterate: this only happens through one of my mutt rc
files. I use two others which have no issues, but I can't see any
differences between them which might cause this.
Okay... what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, March 6 at 08:18 PM, quoth John J. Foster:
Hey Kyle - I've only been running on a Mac since January (former
Gentoo user). But I've not changed my environment, knowingly, to effect
this and my locale shows:
Huh - well, maybe it does get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, March 6 at 01:31 PM, quoth Joshua Tinnin:
I have a very similar muttrc for three different situations, but
they refer to different locations for the spool and inbox, and only
one is crashing. The other two have no issues. All three
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, March 6 at 02:15 PM, quoth Joshua Tinnin:
This may have nothing to do with your problem, but: setting the
$charset variable manually is ALMOST NEVER a good idea! I've only
ever seen *one* situation where it's even *useful*.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, March 5 at 08:25 AM, quoth Bill Moseley:
On Thu, Mar 05, 2009 at 01:54:26AM -0600, Kyle Wheeler wrote:
My point was that if you use some sort of hook for setting the From
header, you can use that same hook for changing whatever
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 4 at 05:01 PM, quoth ssiza...@gmail.com:
~h '^Envelope-to: u...@example.com'
works when I'm limiting messages once inside the folder, but
score '~h '^Envelope-to: u...@example.com'' 41
in my .muttrc doesn't.
Obviously. It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 4 at 05:33 PM, quoth ssiza...@gmail.com:
Well it would make sense if any of your examples worked, but
unfortunately they don't.
I've tried mixing and ' myself, except for the
escaping-quotes-trick. That's new, but gives me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 4 at 09:02 AM, quoth Bill Moseley:
Pinging this again. Specifically, about what kind of hook to use to
base setting one the email address *I'm* using to adjust config.
On Mon, Mar 02, 2009 at 03:01:30AM -0800, Bill Moseley
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 4 at 02:51 PM, quoth Bill Moseley:
(Sorry Grant -- that sentence didn't make any sense).
On Wed, Mar 04, 2009 at 11:21:19AM -0600, Kyle Wheeler wrote:
What do I use for matching on the From: header?
What do you use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 3 at 09:30 AM, quoth Ravi Uday:
Ahhh. Well then, I think you can simply create a macro to unset your
$smtp_pass variable every time you send a message, e.g.:
macro compose y 'send-messageenter-commandunset smtp_passenter'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 4 at 05:57 AM, quoth Kouichiro Iwao:
I have problem sending email with mutt built-in smtp function.
I am using mutt 1.5.19 on freebsd machine and I store emails
in ~/Maildir directory. I set muttrc file like below.
set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, March 2 at 11:54 AM, quoth Ravi Uday:
how to make mutt ask for pwd each time you send email ?
maybe once every 10 mails or based on a timer
Ask for a pwd? Mutt can't even *change* its pwd (without a patch).
Why would you want mutt to do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 3 at 12:04 PM, quoth Magicloud Magiclouds:
Hi,
I use fetchmail/procmail/sendmail and mutt to deal with exchange
mails in office. Well, my mates told me that, they used to use
conversation mode (similiar to thread) to organize
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, March 3 at 01:04 PM, quoth Magicloud Magiclouds:
I think this option only effects how the mails displayed, right?
My problem is that my mails (composed by mutt) could not be organized
as conversation in the receivers' outlook.
Ahh,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, March 2 at 10:51 PM, quoth Ravi Uday:
Yea I meant password.
Ahhh. Well then, I think you can simply create a macro to unset your
$smtp_pass variable every time you send a message, e.g.:
macro compose y 'send-messageenter-commandunset
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, February 27 at 06:08 PM, quoth Carlos Pita:
I don't think this is supported but I'm going to ask it anyway. I
would like to see my replies intercalated in threads.
That's the way *my* email works. :)
I use gmail imap server,
Ew...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, February 26 at 08:07 PM, quoth Carlos Pita:
I'm noticing different encoding behavior for headers displayed at
the index view and those at the pager view for the same email. For
example, at the index view I can see subjects like:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, February 26 at 07:32 PM, quoth Joseph:
firefox -remote openURL\(www.mutt.org,new-tab\)
Error: Failed to send command: 500 command not parseable
Hmmm, so, perhaps openURL requires the http:// in front?
but:
firefox -remote
201 - 300 of 1007 matches
Mail list logo
