/ Luis Mochan wrote on Thu 1.Nov'12 at 14:47:51 -0600 /
I have a related question: after I edit a message (to add X-labels
with an ad-hoc editor), it is marked as new. I would like it to have
the same flags as it had before editing. How can it be done?
Regards,
Luis
On Fri, Nov 02,
Has anyone devised a spam filtering into which an address and subject
line could be entered simply by pressing a key while viewing the mutt
index?
That way, whenever I go down the index pressing the d key to
mark spam items to be deleted, perhaps by pressing some other key I
could mark spam items
/ Russell L. Harris wrote on Fri 2.Nov'12 at 9:21:20 + /
Has anyone devised a spam filtering into which an address and subject
line could be entered simply by pressing a key while viewing the mutt
index?
That way, whenever I go down the index pressing the d key to
mark spam items to
On Tue, Oct 30, 2012 at 08:26:39PM -0700, Kevin J. McCarthy wrote:
Kevin J. McCarthy wrote:
Now, I'm not sure *why* mutt would be doing this. Perhaps someone more
knowledgeable will have suggestions. Do you have any strange hooks or
non-default gpg settings in your muttrc that would turn
On Fri, Nov 02, 2012 at 02:37:01PM -0500, Derek Martin wrote:
Sorry to reply to myself. Looking at the mutt source, the
pgp_strict_enc option seems like a likely culprit for this behavior.
Mutt won't QP encode trailing space emails unless this is set.
Do you by chance have this option
* Jamie Paul Griffin ja...@kode5.net [121102 19:36]:
I have set up macros that bind keys to pass messages to spamassassin
using sa-learn and then puts the message into the spam mailbox. Is
this the type thing you mean? The spam mailbox can later be used to
train spamassassin for future
On Fri, Nov 02, 2012 at 02:42:00PM -0500, Derek Martin wrote:
On Fri, Nov 02, 2012 at 02:37:01PM -0500, Derek Martin wrote:
Sorry to reply to myself. Looking at the mutt source, the
pgp_strict_enc option seems like a likely culprit for this behavior.
Mutt won't QP encode trailing space
Derek Martin wrote:
On Fri, Nov 02, 2012 at 02:37:01PM -0500, Derek Martin wrote:
Sorry to reply to myself. Looking at the mutt source, the
pgp_strict_enc option seems like a likely culprit for this behavior.
Mutt won't QP encode trailing space emails unless this is set.
Do you
Kevin J. McCarthy wrote:
Derek Martin wrote:
And stranger still is that the copy of the message that I receive from
the mailing list ALWAYS VERIFIES CORRECTLY on my end.
Perhaps there is some option or version difference with gpg. Maybe
something in your settings is automatically
