Marco Giusti schrieb am 25.06.2010 um 08:50 (+0200):
> i'm using debian testing's package[1] and before debian stable, maybe
> in the upgrade something changed.
There is a slight version change:
http://packages.debian.org/lenny/mutt - stable - mutt (1.5.18-6)
http://packages.debian.org/squeeze
On Thu, Jun 24, 2010 at 09:07:01AM -0700, Chip Camden wrote:
> On Jun 24 16:09, Chris G wrote:
> > After all the recent discussion of detecting new mail etc. it occurs
> > to me that it would be very useful to be able to tell mutt that it
> > should scan all files in a particular directory for new
On Thu, Jun 24, 2010 at 09:00:13AM -0800, rog...@sdf.org wrote:
> On Thu, Jun 24, 2010 at 03:05:14PM +0200, Christian Ebert wrote:
> >I can't reproduce this, neither with $check_mbox_size set or
> >unser. Unless, of course, I copy a message that is flagged as
> >New.
>
> I've seen this sporadicall
On Thu, Jun 24, 2010 at 02:57:05PM +0100, Chris G wrote:
> If one writes a message to an mbox file then the size changes and (if atime is
> enabled) the modification time will be after the access time. So mutt
> *has* to say there's new mail in the mailbox.
Ah, then it is possibly only the immedia
On Fri, Jun 25, 2010 at 10:47:29AM +0100, Chris G wrote:
> I don't really want to know when new mail arrives, what I want is the
> ability to quickly go to all the mailboxes which have new incoming
> mail when I'm running mutt. I don't have any need to respond quickly
> to messages, just a need to
On Fri, Jun 25, 2010 at 08:05:31PM +1000, Erik Christiansen wrote:
>
> [1]
> If mutt knows not to flag the transferred email as new, then it also
> knows enough not chuck up the erroneous "New mail" message. The logic
> used for the message flags is different from that used for confusing
> the use
On Fri, Jun 25, 2010 at 12:10:54PM +0100, Chris G wrote:
> On Fri, Jun 25, 2010 at 08:05:31PM +1000, Erik Christiansen wrote:
> >
> > [1]
> > If mutt knows not to flag the transferred email as new, then it also
> > knows enough not chuck up the erroneous "New mail" message. The logic
> > used for
On Fri, Jun 25, 2010 at 09:08:56AM +0200, Michael Ludwig wrote:
> Marco Giusti schrieb am 25.06.2010 um 08:50 (+0200):
> > i'm using debian testing's package[1] and before debian stable, maybe
> > in the upgrade something changed.
>
> There is a slight version change:
>
> http://packages.debian.o
Erik Christiansen schrieb am 25.06.2010 um 20:48 (+1000):
> While that would be a lot of fun, mutt itself does seem able to be
> cured of its current fibbing behaviour. (Try copying this message to
> this mail folder. Mutt says "New mail in this mailbox." What hokum.)
Confirmed :-)
> Mutt needs
Hi everybody,
since I use screen on a remote server to read mails with mutt,
the question of how to securely store gpg-keys is bothering me.
At the moment I simply don't use gpg on the remote machine.
But since I receive more encrypted mails lately, I am looking for a
solution. Asking google revea
On Fri, Jun 25, 2010 at 10:47:29AM +0100, Chris G wrote:
> On Thu, Jun 24, 2010 at 09:07:01AM -0700, Chip Camden wrote:
> >
> I don't really want to know when new mail arrives, what I want is the
> ability to quickly go to all the mailboxes which have new incoming
> mail when I'm running mutt. I
On Fri, Jun 25, 2010 at 03:23:55PM +0200, Alex Huth wrote:
> On Fri, Jun 25, 2010 at 10:47:29AM +0100, Chris G wrote:
> > On Thu, Jun 24, 2010 at 09:07:01AM -0700, Chip Camden wrote:
> > >
> > I don't really want to know when new mail arrives, what I want is the
> > ability to quickly go to all th
On Fri, Jun 25, 2010 at 02:46:23PM +0200, Michael Ludwig wrote:
> Checking for new mail before a user-triggered write operation, as you
> suggested, would, I think, fix the issue.
Thank you.
After checking 114 fleas which mentioned "New mail", I've added ticket
#3424.
Erik
--
The reasonable
On Fri, Jun 25, 2010 at 03:33:07PM +0100, Chris G wrote:
> On Fri, Jun 25, 2010 at 03:23:55PM +0200, Alex Huth wrote:
> Only if it knows which ones have new mail in them! That's where we
> came in.
>
That´s what i am talking about. I am using sidebar with lot of maildirs
and the following in the
I'm not an expert, but there is a work around I think will work. You
can store your keys on a flash drive... and possibly the entire OS for
that matter. If you do this, you have no problems.
Alternatively, you can encrypt a document and send it as an
attachment. Your fellow international spy ty
On Fri, Jun 25, 2010 at 03:10:34PM +0200, Christoph Kluenter wrote:
> Hi everybody,
>
> since I use screen on a remote server to read mails with mutt,
> the question of how to securely store gpg-keys is bothering me.
If you have junk gpg keys, then put them on a shared remote machine and
type you
How is the what-key function used and should the Mutt wiki include an example
of it's usage?
(From reading, I'm guessing it should be set within either the muttrc or :set
command prompt.)
--
Roger
http://rogerx.freeshell.org/
I'm trying to figure out why bind keys are not working, and finding the reason
being, the default view for my $HOME/.maildir folder on startup isn't defined
as index or pager (or any maps mentioned within the Mutt Wiki map/bind keys
sections).
Here's what my default view looks like:
q:Exit c:Chd
I'm getting multipart/alternative emails from a Yahoo user that have a
text/plain part like the following (modified):
32 Content-Type: text/plain; charset=iso-8859-1
33 Content-Transfer-Encoding: quoted-printable
34
35 George=A0=A0-=A0=A0 Lorem ipsum dolor sit amet, consectiscing elit=
36 F
19 matches
Mail list logo
