.me.com:993"
> > set spoolfile = "imaps://my_acco...@imap.mail.me.com/INBOX"
>
> BTW, Kevin's response may have hinted at this a bit, but you can use +
> or = before so that you don't have to repeat the imaps:// part, e.g.,
>
> set folder="imaps:/
On 25-07-2023 10:53, Kevin J. McCarthy wrote:
> I see you solved your problem, but also note the mailboxes command doesn't
> use an assignment syntax. The '=' will be interpreted as a mailbox shortcut
> for $folder. Just use:
>
> mailboxes -label "INBOX&qu
On Mon, Jul 24, 2023 at 10:18:37PM +0200, Mikhail Nidze via Mutt-users wrote:
> The problem was in *folder* and *spoolfile* variables incorrectly set.
> The correct ones are:
>
> set folder = "imaps://imap.mail.me.com:993"
> set spoolfile = "imaps://my_acco..
On Mon, Jul 24, 2023 at 07:22:29PM +0200, Mikhail Nidze via Mutt-users wrote:
My mailboxes are set like this:
mailboxes = -label "INBOX" "imaps://my_acco...@imap.mail.me.com/INBOX"
I see you solved your problem, but also note the mailboxes command
doesn't use a
Update:
The problem was in *folder* and *spoolfile* variables incorrectly set.
The correct ones are:
set folder = "imaps://imap.mail.me.com:993"
set spoolfile = "imaps://my_acco...@imap.mail.me.com/INBOX"
Now INBOX shows message count correctly in sidebar.
Problem solve
Hi all.
My mutt is configured to fetch mail from single IMAP account with
several folders set with *mailboxes ...*. All folders are shown
in sidebar:
sidebar_format = '%B%?F? [%F]?%* %?N?%N/?%S'
The problem is INBOX folder doesn't show message count in sidebar "%S"
c
On 2023-04-03 09:42:35, Kevin J. McCarthy wrote:
> On Mon, Apr 03, 2023 at 12:03:12PM +0800, Sadeep Madurange wrote:
> > Yes, a minimum reproducing muttrc (see attached for the screenshot -
> > the gap between status bar and the word "INBOX" on the left):
> >
>
On Mon, Apr 03, 2023 at 12:03:12PM +0800, Sadeep Madurange wrote:
Yes, a minimum reproducing muttrc (see attached for the screenshot -
the gap between status bar and the word "INBOX" on the left):
set imap_user=x...@asciimx.com
set imap_pass=`pass show email`
set folder=imaps://imap.e
On 2023-04-01 09:53:33, Kevin J. McCarthy wrote:
> On Sat, Apr 01, 2023 at 05:48:41PM +0800, Sadeep Madurange wrote:
> > I just switched to mutt from neomutt. There is a gap of one row between
> > the status row and the first folder (i.e., INBOX) in the sidebar. Can I
> > remo
On Sat Apr01'23 05:48:41PM, Sadeep Madurange wrote:
> From: Sadeep Madurange
> Date: Sat, 1 Apr 2023 17:48:41 +0800
> To: mutt-users@mutt.org
> Subject: How to remove the gap between the status bar and the INBOX
>
> I just switched to mutt from neomutt. There is a gap o
On Sat, Apr 01, 2023 at 05:48:41PM +0800, Sadeep Madurange wrote:
I just switched to mutt from neomutt. There is a gap of one row between
the status row and the first folder (i.e., INBOX) in the sidebar. Can I
remove that?
To make sure I understand, you have $status_on_top set, and there is a
I just switched to mutt from neomutt. There is a gap of one row between
the status row and the first folder (i.e., INBOX) in the sidebar. Can I
remove that?
--
Regards,
Sadeep
PGP: 103BF9E3E750BF7E
signature.asc
Description: PGP signature
ing Mutt it accessed Gmail just fine.
I presume the problem was caused by Mutt blocking its own header
cache. In the debug log the next event after selecting Inbox refers to
header cache:
[2023-02-02 02:17:21] 4> a0005 STATUS "[Gmail]/Drafts" (MESSAGES)
a0006 SELECT "INBOX&
On Wed, Feb 01, 2023 at 07:50:40PM +0200, Jarkko Lavinen wrote:
Using debug I see 'a0006 SELECT "INBOX"' as the last message.
What debug level are you using? Try at least level 3, in this case.
After sending the SELECT command, Mutt tries to read some values, such
as U
I cannot access Gmail with Mutt (2.2.9) any more. After "Selecting
INBOX..." nothing happens. Tried also 1.10.1. The same message and
behaviour.
The problem appeared just few days ago and before this accessing Gmail has
worked for years once authenticated.
I haven't changed m
I cannot access Gmail with Mutt (2.2.9) any more. After "Selecting
INBOX..." nothing happens. Tried also 1.10.1. The same message and
behaviour.
The problem appeared just few days ago and before this accessing Gmail has
worked for years once authenticated.
I haven't changed m
On Sat, Aug 14, 2021 at 09:10:25AM +1000, Cameron Simpson wrote:
> > I created my Hotmail account through mutt-wizard. Previously I
> > created Gmail and GMX accounts successfully. But this time I find no
> > messages in Hotmail Inbox, though I have thousands of emails in
>
On 12Aug2021 12:01, chalao.adda wrote:
>Hello,
>
>I created my Hotmail account through mutt-wizard. Previously I created Gmail
>and GMX accounts successfully. But this time I find no messages in Hotmail
>Inbox, though I have thousands of emails in Hotmail. Here are the step
Hello,
I created my Hotmail account through mutt-wizard. Previously I created Gmail
and GMX accounts successfully. But this time I find no messages in Hotmail
Inbox, though I have thousands of emails in Hotmail. Here are the steps I did.
gpg --full-generate-key
pass init j**@hotmail.com
mw -a
* Julius Hamilton [2021-07-07 22:57]:
> Unfortunately, I have been trying to get going with some simple tools like
> grepmail and mail and I can't find an answer to a simple question I
> have.
I recommend that you re-phrase the simple question.
How I have understood, you wish to see if there are
* Jon LaBadie [2021-07-08 08:37]:
> > Could anyone provide me with some simple steps to download my Gmail inbox
> > to my filesystem as a mailbox, so that I could grepmail through it? I did
> > read that the mailbox could be saved to var/mail or just $HOME. In either
> > c
s)". That sounds local to me.
Could anyone provide me with some simple steps to download my Gmail inbox
to my filesystem as a mailbox, so that I could grepmail through it? I did
read that the mailbox could be saved to var/mail or just $HOME. In either
case I think grepmail can search for
* Julius Hamilton [2021-07-07 22:57]:
> Could anyone provide me with some simple steps to download my Gmail inbox
> to my filesystem as a mailbox, so that I could grepmail through it? I did
> read that the mailbox could be saved to var/mail or just $HOME. In either
> case I think
> I would like to retrieve the contents of my inbox - the emails'
> metadata, sender, subject, date - to stdout, rather than by opening
> an application. Can Mutt dump the inbox page? Does it have any way
> to return to stdout information about the inbox? Or should I use a
>
lso not been able to find how to pass
> my configuration information to mail. The docs seem to assume the information
> is present as environmental variables, and it just shows commands you can call
> to send mail, for example.
>
> Could anyone provide me with some simple steps to d
em to
assume the information is present as environmental variables, and it just
shows commands you can call to send mail, for example.
Could anyone provide me with some simple steps to download my Gmail inbox
to my filesystem as a mailbox, so that I could grepmail through it? I did
read that the mailbox
* Julius Hamilton [2021-07-07 20:27]:
> Thanks.
> There is a lot of good stuff here to look into.
> I think I will try with grepmail first.
> I was wondering what the simplest way to send an email might be - the
> mentioned "mail" unix utility, perhaps?
Mutt is the way.
Use whatever you have ava
ort-term solution.
> >You mentioned there being a print function.
> >Could you provide an example of using that to print the inbox to stdout?
> It
> >would have to be automatic, i.e. not requiring the user to actually open
> >Mutt themselves and type the print command. So
On Wednesday, 07 July at 08:38, Jean Louis wrote:
>
> > The context is that I just would like to send emails and check for
> > responses in a more precise and quick way than opening my inbox. I would
> > like to have commands at my disposal when I am working on something to j
> The context is that I just would like to send emails and check for
> responses in a more precise and quick way than opening my inbox. I would
> like to have commands at my disposal when I am working on something to just
> send an email directly and later check for responses to th
On 06Jul2021 18:19, Julius Hamilton wrote:
>Thanks very much.
>I am now looking into using a Python IMAP library.
Note that imaplib from the Python standard library is only a low level
wrapper for the protocol, not a fulling fledged "remote IMAP mailbox"
tool (which you might expect to trweat i
print function.
Could you provide an example of using that to print the inbox to stdout? It
would have to be automatic, i.e. not requiring the user to actually open
Mutt themselves and type the print command. So that leads me to the
question of if this command can somehow be passed to mutt as a command
inbox to stdout? It
would have to be automatic, i.e. not requiring the user to actually open
Mutt themselves and type the print command. So that leads me to the
question of if this command can somehow be passed to mutt as a command line
option, or if there is some bash automation tool for calling
On 05Jul2021 19:19, Julius Hamilton wrote:
>I would like to retrieve the contents of my inbox - the emails'
>metadata,
>sender, subject, date - to stdout, rather than by opening an application.
>Can Mutt dump the inbox page? Does it have any way to return to stdout
>informa
Hey,
I would like to retrieve the contents of my inbox - the emails' metadata,
sender, subject, date - to stdout, rather than by opening an application.
Can Mutt dump the inbox page? Does it have any way to return to stdout
information about the inbox? Or should I use a different tool for
On Wed, May 08, 2019 at 01:24:29AM -0300, Luciano ES wrote:
I have ~/Mail/inbox as correctly indicated in the line that was
causing me trouble. Still a mystery.
$folder specifies the default location for all your mailboxes. The
first time you enter the browser, this will be where mutt looks
On Tue, 7 May 2019 22:59:51 -0400, Patrick Shanahan wrote:
> > set folder="$HOME/Mail/inbox"
> >
> > When that one line is commented out, the problem disappears.
> you can answer yourself, look at:
> ls -la ~/ |grep -i mail
> ls -la ~/{M,m}ail |grep
* Luciano ES [05-07-19 21:28]:
> I believe the problem has been fixed, though I don't really understand
> why... yet. I'll have to catch up with a lot of reading before I can
> really understand.
>
> I took a new approach and attacked my muttrc file rather than the
On 2019-05-07 22:12, Russell L. Harris wrote:
> On Tue, May 07, 2019 at 12:08:14AM -0300, Luciano ES wrote:
> > The problem is that the Inbox folder is empty. And it shouldn't be.
> > I can inspect that directory say, with a file manager, and it's loaded
> > with
I believe the problem has been fixed, though I don't really understand
why... yet. I'll have to catch up with a lot of reading before I can
really understand.
I took a new approach and attacked my muttrc file rather than the
inbox folder. I deleted about half of all lines in it an
On Tue, May 07, 2019 at 08:00:56PM -0300, Luciano ES wrote:
I don't have any 'mailboxes' command in my .muttrc file. Not at all.
I have this:
set spoolfile="$HOME/Mail/inbox"
I have a few folder-hooks though, and they all point to subdirectories
of $HOME/Mail/inbox.
On 2019-05-07 19:00, Luciano ES wrote:
I pasted the output of ls -AR here:
https://pastebin.com/DihPtit2
Nothing jumps out at me as obviously invalid MH format, but it's clearly
been modified and reused at least a couple times. There's extra stuff
that's not normally present in MH format.
lder" command. If I recall correctly, Mutt assumes "~/Mail" if no
> base is specified.
I don't have any 'mailboxes' command in my .muttrc file. Not at all.
I have this:
set spoolfile="$HOME/Mail/inbox"
I have a few folder-hooks though, and they all point to sub
On Tue, May 07, 2019 at 12:08:14AM -0300, Luciano ES wrote:
The problem is that the Inbox folder is empty. And it shouldn't be.
I can inspect that directory say, with a file manager, and it's loaded
with messages.
Check two things:
(1) The only maildirs or mboxes of which Mutt is
On 2019-05-07 17:11, Luciano ES wrote:
I don't remember how I converted it. It was a very long time ago.
Oh. But the problem just started a day or two ago? Then two questions:
Did something change just before the problem started? If so, what?
And, maybe you could show us the contents of that
On Tue, 7 May 2019 16:28:59 -0400, Kurt Hackenberg wrote:
> On 2019-05-07 15:21, Luciano ES wrote:
>
> > Why does mutt show files rather than browse folders on every first
> > attempt? It doesn't make sense.
>
> Because when you converted your inbox from maildi
On 2019-05-07 15:21, Luciano ES wrote:
Why does mutt show files rather than browse folders on every first
attempt? It doesn't make sense.
Because when you converted your inbox from maildir to MH format, you
didn't do it right. That's my current guess, anyway.
How did
On 2019-05-07, Luciano ES wrote:
> By the way, does mutt support Gmail boxes now? It didn't when I still
> used it. Please note that I am stuck with mutt 1.7.2 which is what
> Debian stable provides.
Yes. Mutt's IMAP support works great with Gmail's IMAP server (and
has for many years).
--
On Tue, 7 May 2019 13:43:22 -0400, Kurt Hackenberg wrote:
> On 2019-05-07 12:13, Luciano ES wrote:
>
> >> Does the Inbox folder contain the standard maildir style
> >> directories: cur, new, tmp ? Unread messages should be inside
> >> 'new', read messa
On 2019-05-07 12:13, Luciano ES wrote:
Does the Inbox folder contain the standard maildir style directories:
cur, new, tmp ? Unread messages should be inside 'new', read messages
inside 'cur'.
Hi. There used to be cur, new, tmp. There shouldn't be because it is
all M
On Mon, 6 May 2019 22:23:39 -0500, Jason wrote:
> On Tue, May 07, 2019 at 12:08:14AM -0300, Luciano ES wrote:
> >
> > Then I tried to use it again, but it didn't quite work anymore.
> >
> > The problem is that the Inbox folder is empty. And it shouldn't be.
On Tue, May 07, 2019 at 12:08:14AM -0300, Luciano ES wrote:
>
> Then I tried to use it again, but it didn't quite work anymore.
>
> The problem is that the Inbox folder is empty. And it shouldn't be.
> I can inspect that directory say, with a file manager, and it'
This is a very old problem.
I used mutt a long time ago. I loved it. Then I stopped using it for a
short while for some reason I can't even remember.
Then I tried to use it again, but it didn't quite work anymore.
The problem is that the Inbox folder is empty. And it shouldn&#x
the Inbox.
Errr ... doesn't Bcc-ing yourself result in saving sent e-mails in the
Inbox? And wasn't the original aim to thread both sides of an exchange
in the one mailbox, for threading?
Bccing yourself delivered the email to yourself which causes it to be
fetches which causes it t
esults
> in mutt anyway for easy persual (the (l)imit keystroke is a grwat boon
> here).
Yes, something beyond mutt's search, and egrep, would be needed on one
mammoth inbox. With archived mail in over a thousand mailboxes, those
simple tools suffice amply, though. (Yeah, probably hav
On 29.03.19 13:37, Max Görner wrote:
> Dear list users,
>
> thank you everyone for the valuable replies. I am a bit relieved to learn that
> others follow similar approaches. I will try to Bcc all e-mails to myself.
> That sounds a bit less hacky than saving sent e-mails in t
mutt such as to save all send
messages to Inbox again. Of course, that would clutter the inbox severely, but
a) I have a hook limiting the view to ~(~N|~F) already
b) the cluttering might be counteracted by Mutt's threading capabilities.
Display filtering of one enormous clutter had
On 28Mar2019 22:05, Gregor Zattler wrote:
I send every email to me via Bcc: the incoming Bcc: copy is
handled by the same procmail scripts as all email and therefore
the email will go in the same folder(s). Admittedly I get
duplicates this way, but I use procmail also as a duplicate
filter an a
Dear list users,
thank you everyone for the valuable replies. I am a bit relieved to learn that
others follow similar approaches. I will try to Bcc all e-mails to myself.
That sounds a bit less hacky than saving sent e-mails in the Inbox.
Thank you for all the replies.
Sincerely
Max Görner
t such as to save all send
> messages to Inbox again. Of course, that would clutter the inbox severely, but
>
> a) I have a hook limiting the view to ~(~N|~F) already
> b) the cluttering might be counteracted by Mutt's threading capabilities.
Display filtering of one enormous clutte
Hi Max,
* Max Görner [2019-03-28; 13:24]:
> I wonder whether one could just configure mutt such as to save all send
> messages to Inbox again. Of course, that would clutter the inbox severely, but
>
> a) I have a hook limiting the view to ~(~N|~F) already
> b) the clut
hether one could just configure mutt such as to save all send
> messages to Inbox again. Of course, that would clutter the inbox severely, but
>
> a) I have a hook limiting the view to ~(~N|~F) already
> b) the cluttering might be counteracted by Mutt's threading capabilities.
>
essage-Id and
In-Reply-To headers. GMail guesses and does heuristics (personally, I
find it far inferior).
> I wonder whether one could just configure mutt such as to save all send
> messages to Inbox again. Of course, that would clutter the inbox severely, but
I do this with:
set
do, I BCC all
outgoing emails to myself so I can have the same consistent inbox view from
everywhere.
Multiple clients in my case means: mutt at home with isync (pull only), webmail
from everywhere else.
Hello,
I am a very pleased Mutt user for several years now. However, I would love to
have a threading similar to GMail, showing send and received messages in the
same thread.
I wonder whether one could just configure mutt such as to save all send
messages to Inbox again. Of course, that would
mail in the thread
and press again it takes me back out to the current inbox index.
I'm pretty much a noob but I'm wondering if it might be possible to
define this as a macro?
Any help would be highly appreciated!
--
Jonas Hedman
XMPP:n...@jabber.at
PGP Key: 0x5c3989
Most importantly, there is a nice procmail recipe in that procmailrc that
creates list inboxes automatically
as soon as you sign up for a mailing list, procmail will create it as a new
inbox for you automatically... pretty cool
:0:
* ^((List-Id|X-(Mailing-)?List):(.*[<]\/[^>]*))
{
On 06.12.13 11:22, Paul E Condon wrote:
> On 20131206_210949, Erik Christiansen wrote:
> > help when you are off in another mailbox, and suddenly decide to fling
> > off a message. To let mutt catch that use case, and put any message to
> > family in the right mailbox, I've settled on:
> >
> > fcc
My question is embedded in the quoted message, below:
On 20131206_210949, Erik Christiansen wrote:
... remove text that's not relevant to my questions
> help when you are off in another mailbox, and suddenly decide to fling
> off a message. To let mutt catch that use case, and put any message to
On Fri, Dec 06, 2013 at 05:02:21AM +0400, Kirill Tkhai wrote:
> Hi,
>
> I want to have a posibility to see inbox and sent messages together
> in one thread. Is this possible without copying content of Sent folder
> to Inbox?
I may be misunderstanding something, but how about just
On 06Dec13 13:57 +0100, Suvayu Ali wrote:
> On Thu, Dec 05, 2013 at 08:21:00PM -0500, Patrick Shanahan wrote:
> > * Kirill Tkhai [12-05-13 20:05]:
> > > I want to have a posibility to see inbox and sent messages together in
> > > one thread. Is this possible with
On Thu, Dec 05, 2013 at 08:21:00PM -0500, Patrick Shanahan wrote:
> * Kirill Tkhai [12-05-13 20:05]:
> > I want to have a posibility to see inbox and sent messages together in
> > one thread. Is this possible without copying content of Sent folder to
> > Inbox?
>
> L
On 06.12.13 05:02, Kirill Tkhai wrote:
> I want to have a posibility to see inbox and sent messages together
> in one thread. Is this possible without copying content of Sent folder
> to Inbox?
There are many ways to skin the message storage cat, all with some
merit. (Except per
* Kirill Tkhai [12-05-13 20:05]:
> I want to have a posibility to see inbox and sent messages together in
> one thread. Is this possible without copying content of Sent folder to
> Inbox?
Leave the "sent" msgs in the inbox
or insteadof "saving" outgoing post, copy
Hi,
I want to have a posibility to see inbox and sent messages together
in one thread. Is this possible without copying content of Sent folder
to Inbox?
Thanks,
Kirill
On 2013-04-19, Paul Hoffman wrote:
> On Fri, Apr 19, 2013 at 07:16:57PM +0300, Kevin Wilson wrote:
>> Hi,
>> I installed mutt of Fedora 18 and configured muttrc
>> to my gmail account; I am able to send messages properly.
>> However, the inbox is almost empty (5 messa
On Fri, Apr 19, 2013 at 07:16:57PM +0300, Kevin Wilson wrote:
> Hi,
> I installed mutt of Fedora 18 and configured muttrc
> to my gmail account; I am able to send messages properly.
> However, the inbox is almost empty (5 messages) and I want to
> fetch previous messages (let'
Hi,
I installed mutt of Fedora 18 and configured muttrc
to my gmail account; I am able to send messages properly.
However, the inbox is almost empty (5 messages) and I want to
fetch previous messages (let's say
1000 or 2000) from my inbox of the gmail account
How can I achieve this ?
rgs
Kevin
* Patrice Levesque [2013-01-30 15:33:11 -0500]:
>
> > My problem is that all Maildir folders are updated automatically when a
> > new email is received, but my Inbox doesn't show updates. To see new
> > email I have to quit mutt and re-open it.
> >
> >
On 2013-01-30 17:54:04 -0300, Leonardo M. Ramé wrote:
> On 2013-01-30 15:33:11 -0500, Patrice Levesque wrote:
> >
> > > My problem is that all Maildir folders are updated automatically when a
> > > new email is received, but my Inbox doesn't show updates. To se
On 2013-01-30 15:33:11 -0500, Patrice Levesque wrote:
>
> > My problem is that all Maildir folders are updated automatically when a
> > new email is received, but my Inbox doesn't show updates. To see new
> > email I have to quit mutt and re-open it.
> >
> >
> My problem is that all Maildir folders are updated automatically when a
> new email is received, but my Inbox doesn't show updates. To see new
> email I have to quit mutt and re-open it.
>
> What I'm doing wrong?.
See this entry from the FAQ, might provid
Hi, I'm using mutt 1.5.21 with sidebar patch from 20120829.
I'm also using Fetchmail and Procmail to store my emails in different
folders. My Inbox is directly read from /var/spool/mail/leonardo, which
is an mbox file, while every other emails are stored in their respective
Maildir fo
[ Paolo Pisati wrote on Mon 8.Oct'12 at 20:57:41 +0200 ]
> the leading dot came from a precooked config file for offlineimap that i
> found around.
> I removed the trailing / and indeed it didn't make any difference.
>
> If you want to see my entire mutt config, is here:
> http://people.canoni
On Mon, Oct 08, 2012 at 02:10:51PM +0100, Jamie Paul Griffin wrote:
> >
> > set mbox_type=Maildir
> > set folder="~/Maildir/"
> > set spoolfile=+inbox
> > set mask="!^\\.[^.]"
> > set record="+.Sent"
> > set postponed="
> > > ~/Mail for it's mailboxes. If you want to use ~/Maildir for your
> > > mailboxes you need to specify $folder to ~/Maildir, which you have done.
> > > But, you want ~/Maildir/inbox to be your spoolfile, so you need to put
> > > this in muttrc
r mailboxes
> > you need to specify $folder to ~/Maildir, which you have done. But, you
> > want ~/Maildir/inbox to be your spoolfile, so you need to put this in muttrc
> >
> > set folder=~/Maildir
> > set spoolfile=+inbox
> > ...
>
> thanks, i
But, you want
> ~/Maildir/inbox to be your spoolfile, so you need to put this in muttrc
>
> set folder=~/Maildir
> set spoolfile=+inbox
> ...
thanks, it worked.
--
bye,
p.
[ Paolo Pisati wrote on Fri 5.Oct'12 at 13:23:25 +0200 ]
> On Fri, Oct 5, 2012 at 1:16 PM, Patrick Shanahan wrote:
> >
> > try: mailboxes +/Maildir/inbox
>
> so what's the point of the variable folder?
>
> set folder="~/Maildir/"
>
> besi
On Fri, Oct 5, 2012 at 1:16 PM, Patrick Shanahan wrote:
>
> try: mailboxes +/Maildir/inbox
so what's the point of the variable folder?
set folder="~/Maildir/"
besides, when i press c? it displays all the mailboxes in ~/Maildir,
so the "root maildir directory" is correct.
* Paolo Pisati [10-05-12 07:11]:
> I can't make mutt to open my ~/Maildir/inbox by default.
...
> mailboxes +inbox
try: mailboxes +/Maildir/inbox
hth :^)
--
(paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711
http://wahoo.no-ip.orgPhoto Album: http
I can't make mutt to open my ~/Maildir/inbox by default.
mutt's status line:
---Mutt: (no mailbox) [Msgs:0
Inc:1]---(threads/date)(all)---
No mailbox is open.
[fla
Hi, currently I store all my responses to ~/Maildir/sent-mail-2012, this
directory is created automatically, because of this configuration:
set record="=sent-mail-`date +%Y`"
I would also like to store my responses in my Inbox, which is set this
as this:
set mbox="+.inbox-`date
Hello mutt users and discussers,
Currently I am successfully seeing everything in my Inbox when I execute
mutt but I don't want to see the entire Inbox. I pretty much have
almost everything the way I want it otherwise though. I also don't want
to see all Important mail regardless of
om those accounts into specific folders, and use folder hooks
> to set variables associated with the respective accounts upon entering
> the folder.
I was reading the above message when it occurred to me that using the
hcache functions of mutt might be suitable to implementing a unified
inbo
tiple
>>>>> accounts delivered to your mailspool using getmail or fetchmail.
>>>>
>>>> except that that downloads the mail to your local machine.
>>>
>>> Not if you run it on your IMAP server.
>>
>> but it still puts all your mail int
your mailspool using getmail or fetchmail.
> > >
> > > except that that downloads the mail to your local machine.
> >
> > Not if you run it on your IMAP server.
>
> but it still puts all your mail into a single mail box, which entirely defeats
> the purpose of a unified
> > So, since nothing is impossible in mutt, how can I get a unified inbox
> > > > for my two accounts?
> > >
> > > I don't think having a specific feature in Mutt is necessary or
> > > desirable to achieve this. You can easily have mail from mult
On Sat, Feb 26, 2011 at 02:53:44PM -0500, Logan Rathbone wrote:
> Personally I prefer to use the right tool for the right job.
> Thunderbird is a much better IMAP client than Mutt, so why not use
> Thunderbird?
How so?
> I disagree; I think Mutt is more of a 'read mail from file' kind of mail
> c
ne
might summarize as "a place for everything, and everything in its
place." Most people I have encountered who use Mutt and enjoy it
specifically do not want a unified inbox, myself certainly included.
I think it's fair to say that Mutt was not designed with this paradigm
in mind...
1 - 100 of 264 matches
Mail list logo
