On 2007.10.09 12:18:12 +, Dilip M wrote:
> On 10/9/07, Rem P Roberti <[EMAIL PROTECTED]> wrote:
>
> ...snip...
>
> > getmail version 4.7.6
> > Python version 2.5.1 (r251:54863, Sep 16 2007, 14:19:57)
> > [GCC 3.4.6 [FreeBSD] 20060305]
> >
> > Unhandled exception follows:
> > File "/us
On 2007-10-09, Andreas Leppert <[EMAIL PROTECTED]> wrote:
> On Mon, Oct 08, 2007 at 02:36:30PM -0700, Gary Johnson wrote:
> > Since you didn't elaborate on what you mean by "return" except that
> > it is not the same as "enter", I assume that you mean an ASCII
> > carriage return, 0x0D. That is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Oct 08, 2007 at 04:33:34PM -0700, Gary Johnson wrote:
> > Is there a tool which tells me the characters of keystrokes?
> > xev does not work for key combinations.
>
> Yes, there is such a tool built into mutt. From the index, type
>
>:
Dear list,
It seems impossible to remove the O flag on messages without the use
of Wo, Wn, or NkN (assuming $resolve is set), which is 200% to 300%
of the work I am willing to put into this. Does anyone know of
a better way to approach this?
I came up with
macro index,pager N ":set my_resolve=
Bit of a problem here setting up Procmail. I have a test entry in my
.procmailrc thus:
:0:
* ^Subject: test
testing
When I send a test message to myself with "test" as Subject, Procmail
does indeed filter the mail, creating the "testing" folder and putting
the mail there. But the mail goes dire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 08:38 AM, quoth Rem P Roberti:
>When I send a test message to myself with "test" as Subject, Procmail
>does indeed filter the mail, creating the "testing" folder and putting
>the mail there. But the mail goes directly to the
>What do you mean that mutt "never sees it"---if you open that mailbox,
>is the new message missing? Is it not marked "new"? What's the
>problem?
Is what marked "new"?
>If you're upset that mutt didn't inform you "hey! There's new mail in
>a mailbox you aren't looking at!", keep in mind that mutt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 09:28 AM, quoth Rem P Roberti:
>> What do you mean that mutt "never sees it"---if you open that mailbox,
>> is the new message missing? Is it not marked "new"? What's the
>> problem?
>
> Is what marked "new"?
The new messag
>I suspect you probably are just missing some syntax. For example,
>mutt's mailboxes take full paths, not just names that are relative to
>some other setting. So, for example, if procmail is saving messages to
>$HOME/testing then you need to tell mutt:
> mailboxes $HOME/testing
>Otherwise, i
Hello,
Is it possible to not display the pgp or smime signature at all in the
pager ?
I have set crypt_verify_sig=no in my ~/.muttrc, but obviously this is
not sufficient.
Thanks,
--
Nicolas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 10:23 AM, quoth Rem P Roberti:
> Boy, I'm missing something here. Ok...I did have the syntax wrong,
> and now that I have the path to my mailboxes correctly stated in
> .muttrc Mutt does indeed give me a message at the bott
On 2007-10-09, Nicolas KOWALSKI <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Is it possible to not display the pgp or smime signature at all in the
> pager ?
>
> I have set crypt_verify_sig=no in my ~/.muttrc, but obviously this is
> not sufficient.
I set 'display_filter' to a script that cleans up
On 2007.10.09 12:50:53 +, Kyle Wheeler wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tuesday, October 9 at 10:23 AM, quoth Rem P Roberti:
> > Boy, I'm missing something here. Ok...I did have the syntax wrong,
> > and now that I have the path to my mailboxes correctly state
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 11:08 AM, quoth Rem P Roberti:
> Oh, brother! I didn't realize that you could get to the individual
> folders from within Mutt by c. You want to laugh...I
> responded to your last couple of posts by cut and paste! Things
On Tue, Oct 09, 2007 at 11:06:00AM -0700, Gary Johnson wrote:
> On 2007-10-09, Nicolas KOWALSKI <[EMAIL PROTECTED]> wrote:
> > Is it possible to not display the pgp or smime signature at all in
> > the pager ?
> >
> I set 'display_filter' to a script that cleans up a number of
> message artifact
On 2007-10-09, Nicolas KOWALSKI <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 09, 2007 at 11:06:00AM -0700, Gary Johnson wrote:
> > On 2007-10-09, Nicolas KOWALSKI <[EMAIL PROTECTED]> wrote:
> > > Is it possible to not display the pgp or smime signature at all in
> > > the pager ?
> > >
> > I set 'dis
Back at it (Kyle, are you out there?). I've been trying to set up
individual mailboxes for folks I receive mail from frequently. I
create the mailbox in .muttrc (mailboxes $HOME/Mail/user), and then a recipe
like this in
.procmailrc:
:0:
* ^From: [EMAIL PROTECTED]
user
But the mail isn't gett
On 10/09/07 16:06, Rem P Roberti wrote:
>
> Back at it (Kyle, are you out there?). I've been trying to set up
> individual mailboxes for folks I receive mail from frequently. I
> create the mailbox in .muttrc (mailboxes $HOME/Mail/user), and then a recipe
> like this in
> .procmailrc:
>
> :0:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 05:15 PM, quoth Joseph:
>If you have mbox it should be:
>:0:
>* ^From:[EMAIL PROTECTED]
>$HOME/Mail/user
In case it's not clear, the reason to use .* instead of just a space
is that the way From headers are typically sent is
On 2007.10.09 18:23:23 +, Kyle Wheeler wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tuesday, October 9 at 05:15 PM, quoth Joseph:
> >If you have mbox it should be:
> >:0:
> >* ^From:[EMAIL PROTECTED]
> >$HOME/Mail/user
>
> In case it's not clear, the reason to use .* inste
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Rem P Roberti <[EMAIL PROTECTED]> [10-09-07 19:37]:
> What I don't understand is that since the variable MAILDIR=$HOME/Mail
> exists at the beginning of .procmailrc why is it necessary to state
> the full path to the target mailbox in the recipe?
Do
* Rem P Roberti <[EMAIL PROTECTED]> [2007-10-09 16:37 -0700]:
My thanks again to both of you. Creating my .procmailrc recipe in the
manner suggested by Joseph did the trick. What I don't understand is
that since the variable MAILDIR=$HOME/Mail exists at the beginning of
.procmailrc why is it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 04:37 PM, quoth Rem P Roberti:
> My thanks again to both of you. Creating my .procmailrc recipe in
> the manner suggested by Joseph did the trick. What I don't
> understand is that since the variable MAILDIR=$HOME/Mail exi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 07:05 PM, quoth Breen Mullins:
> MAILDIR by itself isn't special in procmail.
On the contrary, MAILDIR *IS* special. Reread the procmail
documentation. Specifically:
MAILDIR Current directory while procmail is exec
* On Tue, Oct 09, 2007 martin f krafft ([EMAIL PROTECTED]) muttered:
> It seems impossible to remove the O flag on messages without the use
> of Wo, Wn, or NkN (assuming $resolve is set)
> Does anyone know of a better way to approach this?
>
> I came up with
>
> macro index,pager N ":set my_res
* On Tue, Oct 09, 2007 Rem P Roberti ([EMAIL PROTECTED]) muttered:
> Oh, brother! I didn't realize that you could get to the individual
> folders from within Mutt by c.
Actually, the default key binding for is "c"
c is change-folder-readonly.
HTH,
Michael
--
The nice thing about Windows is -
26 matches
Mail list logo
