Gregor Zattler wrote:
I configured a group gpg-full which matches all emailaddresses to
which a valid gpg key exists in my keyring. I'm able for instance
to search for emails matching %Cgpg-full in the index and the scroll
bar jumps to the next message which is addressed to somebody who's
William Yardley wrote:
I'm using a command like this to send a bunch of emails out:
% egrep -v ^(#|$) test_email.txt | sed 's/[EMAIL PROTECTED]:digit:]]*//g' |
while read line ; do mutt -F bogus_muttrc -s 'The Subject' ${line}
message_text.txt ; done
Currently, bogus_muttrc has this in
Cameron Simpson wrote:
Yeah, but without even invoking find:
rmdir dir/new dir/tmp dir/cur dir \
|| mkdir -p dir/new dir/tmp dir/cur
Robust, safe, trivial.
Hooray for simplicity. :)
People always seem to forget that rmdir is perfectly safe, in that
it won't remove empty directories.
tannhauser wrote:
i have various email accounts and various gpg key pairs. When i get
an encrypted email, mutt just outputs Enter passphrase: , without
giving any hint for which secret key. As long as i decrypt specific
emails, that behaviour is ok: i know which key pair i use for that
Michael Kjorling wrote:
The easy way that I can think of to do what the OP wants is to tag
the messages (`t'), then use tag-prefix (`;'), clear-flag (`W')
or set-flag (`w'), and then make the desired change.
I've used a macro like this for a while:
macro index ,n
Chris Lemire wrote:
Hello, I'd like to have gpg with --clearsign working and the text to
be in the message, not as an attachment. I tried all of these before
sending an email, i for inline, c for clearsign, and s for sign.
c isn't for clearsign, it's to clear the pgp flags that might
currently
Kyle Wheeler wrote:
I've recently started looking into gpg-agent again, because it seems
the redraw issues that used to plague pinentry calls have been
resolved.
I think there may still be one or two. I found one a few months back
and submitted a patch, but since then I've run into a similar
Kyle Wheeler wrote:
My bet would be that ! was intended as a shortcut to be used when
changing folders (e.g. c!), and its implications as far as hooks go
weren't considered.
FWIW, I use 'folder-hook ! ...' in my mutt config for a few things
and it works well. So it's not generally broken.
Gerard Robin wrote:
Did you make a debian package ?
If yes, can you show your file control ?
Why not just check out the Debian package files from
http://git.debian.org/?p=pkg-mutt/mutt.git;a=summary ?
--
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
I noticed after updating to 1.5.20 that headers were not weeded when
displaying message/rfc822 parts in a message. This appears to be due
to changeset 536771b4e085¹. I'm wondering if there is any particular
work-around for this, or if it's an unintentional side-effect.
I see it mainly when
Brendan Cully wrote:
That was an accident. Would you mind filing a bug at bugs.mutt.org?
Done: http://dev.mutt.org/trac/ticket/3265
Thanks Brendan!
--
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Rocco Rutte wrote:
Thanks, this is fixed now in hg tip -- sorry for the breakage.
Thank you Rocco for the very quick fix and all the other work you've
done. :)
--
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
Michael Tatge wrote:
* On Wed, Jun 24, 2009 11:46AM +0200 Jan-Herbert Damm (jan-h-d...@web.de)
muttered:
this .muttrc entry (in my /etc/Muttrc):
macro generic,pager F1 shell-escape less /[...]/doc/mutt/manual.txt
seems to be trapped by Gnome somehow. F1 (from within mutt) starts
the
bill lam wrote:
Not sure if this is useful to you. I use debian and install its
ca-certificates package, and add the following line inside my
~/.muttrc
set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
I think that may be just what Dale needs. On Fedora, the path to the
ca
martin f krafft wrote:
The actual problem remains though. For some reason, the last message
I sent was inline *and* PGP-mime signed, thus this one is simpler to
exemplify the problem.
There's a bit of text preceding the Hello, up top of this mail,
but if you configured mutt with
I sometimes see TOFU on lists where the sender is replying to a
message that was signed using traditional (inline) PGP. Their message
does not show up once check-traditional-pgp is called. Only the
original text from the quoted PGP signed section is displayed. I
don't think mutt has always
Marc Vaillant wrote:
On Tue, Jan 30, 2007 at 07:31:38PM +0100, Rado S wrote:
[...]
_You_ have several options:
1) educate your eMail partners to quote mutt-friendly (txt-only).
[...]
Are you serious about option 1?
I would be. Even outlook (not sure about outlook express) can be told
to send
mal content wrote:
Currently, when I send a PGP encrypted message to a recipient, it is
encrypted and readable only by them. I'd like to automatically save
a plain copy of the sent message
You can use fcc_clear to achieve this. From the manual:
3.53. fcc_clear
Type: boolean
Default:
mal content wrote:
Ah, nice.
Is there any way to indicate that a message was signed or encrypted
in the cleartext copy?
I don't know of one. I wouldn't be surprised to learn that there is,
as there is very little that mutt can't do (or be taught to do with a
little of the right kinds of
Chris G wrote:
It's really a pity that mutt 'stable' is so old now, it's what gets
delivered on most distributions and means that people trying mutt
won't get to see all the new goodies.
I got 1.4.2.2 on the following:-
Slackware 11 (home machine)
Fedora Core 6 (work desktop
Chris G wrote:
Ah, but when is my work machine likely to get upgraded to Fedora 7?
Some time after I retire I suspect (not that long, I'm 60 now!).
Well, lucky you then. That's a whole lot less to worry about. :)
--
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
Stefano Sabatini wrote:
Hi mutters,
I'm getting this strange behaviour when I try to verify the integrity
of a message with mime type multipart/signed and signed with PGP.
In most cases it works just fine, but in some cases I get something
as:
[-- PGP output follows (current time: Tue
Sander Smeenk wrote:
Sorry, but your key is not 'trusted' in my trustdb, yet the 's' in
front of your message changes to an 'S' after reading it.
Hmmm, you're right.
(I should know better than to post before noon. :)
--
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
Stefano Sabatini wrote:
This is my crypto setting:
# %f: message file
# %s: signature file
# %a: pgp_sign_as value
set pgp_decode_command=gpg %?p? --passphrase-fd 0? --no-verbose --batch
--output - %f
set pgp_verify_command=gpg --no-verbose --batch --output - --verify %s %f
set
Stefano Sabatini wrote:
I discovered this behaviour is dependant on the folder I'm exploring.
There happens to be good folders and bad folders, in the good ones
I can see the s flag right just when I open them in the index and
the verify mechanism works as expected (that is good signatures
Brian Salter-Duke wrote:
I have some comments from the 1.5.15 build. As I found years ago the main
problems are in the make in the doc directory. This is amazingingly
complex, at least to me. It uses tools I have not meet before and I had
to download them from the cygwin site. It failed with:-
tannhauser wrote:
the concrete problem: i'm on a (very small) mailinglist. we all have
the gpg keys of the others. i can not encrypt with more than one
key.
so, how do i send emails to the mailinglist address and encrypt it
with the various recipients' keys?
i was very surprised that i was
Kyle Wheeler wrote:
Now, it's probably fair criticism if you want to say that mutt
should also check List-Post and/or List-ID headers (if they exist),
but for good or ill, it does not currently (file a bug report).
Other than that, though, how do you think mutt *should* identify
messages as
Kyle Wheeler wrote:
Yes, BUT mutt does *not* use those headers to match against the
lists/subscribed lists for the purposes of ~l and ~u pattern
matching. Check out pattern.c, line 1172; all it uses is h-env-to
and h-env-cc. h-env-to is built (in parse.c) from To and
Apparently-To headers,
Joseph wrote:
That is strange, until I when I try to verify my own submission I
get: key ED0E1FB7 not found on keyserver
gpg --search-keys ED0E1FB7
gpg: searching for ED0E1FB7 from hkp server subkeys.pgp.net
gpg: key ED0E1FB7 not found on keyserver
What version of gpg do you have? Older
Joseph wrote:
I'm using gnupg-1.9.21
Huh. That's an old version of gnupg2. It may well have the same bug
in it that the gnupg 1.x branch had. Try updating your gpg package.
and I tried it both with 0x and without.
gpg --interactive --recv-keys ED0E1FB7
worked but it gives me an old
Joseph wrote:
What version are you using?
The one the most stable marked in Gentoo portage:
They have the new one: gnupg-2.0.7 but it has not been marked stable.
I still use the 1.4 branch primarily. I've got gnupg-1.4.7. I do use
gpg-agent from the gnupg2 branch, currently I've got
Joseph wrote:
According to manual ^K (ctrl-shift-K) is for extract-key
when I tried it, I got:
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
Press any key to continue...
The message was pgp signed.
The keys aren't transmitted with each signed message in the
Rem P Roberti wrote:
What I expected to be able to do was to invoke the spell checker
directly from within vi, which is no doubt possible, but which so
far eludes me.
If your vi is vim = 7, then you can use the built-in spellchecker in
vim. To do this, you type :set spell while in normal
Kevin J. McCarthy wrote:
> On Tue, May 15, 2018 at 09:40:38AM +0200, W. Martin Borgert wrote:
>> Is there an option in mutt to do this? Hopefully a run time
>> option, not a compile time option...
>
> The compile-time configuration is the cleanest way to turn it off.
> However, you could try set
Cameron Simpson wrote:
>> Another interesting thing is that although mutt doesn't finally send the
>> mail, msmtp reports it as sent. I mean that in the sent file of msmtp you can
>> find:
>
> The tail of your message from this point seems to be missing.
Perhaps you're reading this from an mbox
Hi Scott,
Scott Kostyshak wrote:
> When I'm in the pager and on the first message, if I accidentally press
> it takes me to the index, with a message of "You are on the first
> message". This makes sense, but I would prefer to stay in the pager.
> Similarly for pressing on the last messsage, I
Ben Boeckel wrote:
> On Wed, Dec 20, 2017 at 14:14:38 -0500, Todd Zullinger wrote:
>> I think you want the pager_stop? variable:
>>
>> 3.169. pager_stop
>>
>> Type: boolean
>> Default: no
>>
>> When set, the internal-page
Claus Assmann wrote:
> On Thu, Sep 06, 2018, Kai Weber wrote:
>
>> How can I have the same muttrc on both machines without running into
>> errors during mutt start?
>
> I split the rc file into
> 1) a common part
> 2) parts specific to the mutt version
> and
> - source the common part (1) in the
Matthias Apitz wrote:
> El día Tuesday, February 27, 2018 a las 10:39:53AM +0100, Ralf Hildebrandt
> escribió:
>> I'm using:
>>
>> # Erase [ext] tags from e-mails
>> subjectrx '\[ext\] *' '%L%R'
>>
>> to remove the tag "optically". Is there any way of removing the
>> Subject: prefix when
Matthias Apitz wrote:
> El día miércoles, abril 25, 2018 a las 08:56:26p. m. +0200, Matthias Apitz
> escribió:
>
>> El día miércoles, abril 25, 2018 a las 02:46:06p. m. -0400, Patrick Shanahan
>> escribió:
>>
>>> then you have someone in your system makeing changes to your posts,
>>
>> the
Hi,
felixs wrote:
> On Thu, Mar 28, 2019 at 03:11:34PM -0700, Kevin J. McCarthy wrote:
>> On Thu, Mar 28, 2019 at 10:20:54PM +0100, felixs wrote:
>>> I tried to access the branch with the patch, but the access is
>>> password-protected.
>>
>> The repo is clonable via
Globe Trotter via Mutt-users wrote:
> ... Fedora 33 (my favorite distribution, which however,
> has not updated mutt for aeons)
As an aside, perhaps you haven't checked in a few weeks?
Fedora has mutt-2.0.5 in both the stable 32 & 33 releases.
But as Remco said, this is most likely your editor
Hi,
Jan Eden wrote:
> my configuration sets a PGP default key:
>
> set pgp_default_key = ...
>
> and outgoing messages are signed accordingly. But every time I reply
> to a message signed using S/MIME, mutt tries to add an S/MIME signature,
> too (which fails, as there is no S/MIME key
Tim Chase wrote:
> On 2022-09-02 19:45, Sam Kuper wrote:
>> Could you not prepend your EXPR with something like this?
>>
>> `^(Delivered|Envelope)-To:\ `
>
> Ah, so the pattern for matching ~h includes the header-name then
> and the regex can match against that? That should work.
>
>
Fourhundred Thecat wrote:
> I am using mutt in 2 modes:
>
> 1) mutt -R -f folder
> 2) mutt-f folder
>
> In case 1), pressing "q" should simply exit. This is read-only mode and
> there are no messages to be deleted.
>
> In case 2), pressing "q" should exit while also automatically
José María Mateos wrote:
> On Sun, Apr 23, 2023 at 02:56:35PM +, Alan Mackenzie wrote:
>> Some considerate organisation has been sending me MIME mails with
>> content in a text/html section and a wholly blank text/plain version.
>> What I see in mutt is the blank text/plain. Who on Earth
Hi,
Kai Weber wrote:
> From time to time I have to report a falsly classified
> message to my mail provider so that they can adjust their
> filters. I am looking for a way to automate that:
>
> 1. Forward selected mail as attachement to x...@foo.com
> 2. Set Subject to "reporting false positive
Hi,
void wrote:
> I have various mailing list emails filtered on the server
> by the mail provider going into various imap folders, based
> on various properties of the email, like List-Id: for example.
>
> What I'd like to have within mutt is for it to dynamically
> decide which signature file
49 matches
Mail list logo
