Re: dynamic sig based off imap folder

[Todd Zullinger]

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 to use based on what imap
> folder the mail being replied to is in.
> 
> In the .muttrc there's for example a line like this:
> 
> mailboxes =mutt-users =test
> 
> In the manual, the nearest thing I can find to do what
> I'm describing is in "Example 3.8. Using MuttLisp expressions"
> but I'm unsure what expressions to use for an imap folder,
> how to test to see if mutt is in it.

A folder-hook will do this job nicely¹.  It is uner the
heading "Setting Variables Based Upon Mailbox" and described
as:

It is often desirable to change settings based on which
mailbox you are reading. The folder-hook command
provides a method by which you can execute any
configuration command. regexp is a regular expression
specifying in which mailboxes to execute command before
loading. If a mailbox matches multiple folder-hooks,
they are executed in the order given in the .muttrc. 

Here's an example for setting the signature:

folder-hook .   'set signature=~/.sigs/default'
folder-hook =mailbox-a  'set signature=~/.sigs/mailbox-a'

You set the first one as default so that after you change
from mailbox-a you aren't left with the signature you set
for that mailbox.

Often, you may have other variables to set based on the
folder/mailbox and rather than set them all you can use a
folder-hook to source a file which containsd them all, e.g.:

folder-hook .   'source ~/.mutt/profiles/default'
folder-hook =mailbox-a  'source ~/.mutt/profiles/mailbox-a'

¹ http://www.mutt.org/doc/manual/#folder-hook

HTH,

-- 
Todd


signature.asc
Description: PGP signature

Re: Forwarding a false positive classified message

[Todd Zullinger]

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 -- [original subject]"
> 3. open editor with a prefilled message "Hello there, ..."
> 4. save message to my inbox
> 
> I am unsure how to achieve 1-3 with a macro. Is a macro
> the correct way to do that?

I have one which reports missed spam messages.  It looks
roughly like this (edited a bit to remove unrelated parts
and wrap it -- hopefully I haven't broken the syntax in the
process):

macro index ,s "spam-rep...@example.com\
Missed spam\
" "Report missed spam"
macro pager ,s ",s" "Report missed spam"

You would want to replace `Missed spam` with
something like `reporting false positive -- []`.

You would not need `` for non-spam. ;)

I'm sure others here have better macros.  But this works
for me.  Hopefully this gives you some ideas for how to
create something which works for you.

-- 
Todd


signature.asc
Description: PGP signature

Re: Avoiding S/MIME

[Todd Zullinger]

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 available via GPGME).
> 
> How can I prevent this behavior?

You may want to check the crypt_auto* and crypt_reply*
variables to see how they are set.  My first thought would
be disabling crypt_autosmime, e.g.:

set crypt_autosmime=no

-- 
Todd


signature.asc
Description: PGP signature

Re: How do I see the text/html version of an email?

[Todd Zullinger]

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 thought a
>> blank text/plain section was somehow a good idea?

[I know, I know, I'm answering a rhetorical question.]

I suspect one likely group would be the companies who depend
on advertising revenue.  With HTML, they can stuff tracking
(whether direct like hidden pixels or indirect by changing
any URLs in the message to go through their servers.  Those
things aren't very useful in text/plain, so shipping a blank
part just forces many folks to view the text/html.

Of course, sending just text/html would work better -- but
who knows what goes on in the minds of people willing to
perform shady tracking. :)

> I've seen a worse version of this: the text version and the html version are
> completely different.
> 
> On my side, I have this:
> 
> auto_view text/html
> folder-hook . 'unalternative_order *; alternative_order text/plain text/html'
> folder-hook boletines 'unalternative_order *; alternative_order text/html 
> text/plain'
> 
> So normally I look at the plain-text version, except in my folder
> "boletines" (Spanish for "newsletters"), where I default to HTML.
> 
> In those cases where I'm in another folder and I need to look at the HTML
> content, I use this macro:
> 
> macro index,pager ,b "/html" 
> "View first HTML attachment in browser"
> 
> This opens the first available HTML attachmend (typically the message body)
> in my browser of choice (set up via ~/.mailcap).

An alternative (or addition) to the above is a message-hook:

message-hook ~A 'unalternative_order "*"; alternative_order text/enriched 
text/plain text'
message-hook '~C "misbehaving-group@example\.com"' 'unalternative_order "*"; 
alternative_order text/html'

Replace ~C with ~f or other pattern as needed.  You may
need to add something like:

auto_view text/html text/htm message/html message/htm

to the configuration as well, if you want them to open in
the mutt pager rather than in a browser.  I only view html
via plain text, so I set auto_view as-needed.

-- 
Todd


signature.asc
Description: PGP signature

Re: Identifying messages with no To: or CC: headers?

[Todd Zullinger]

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.
> 
> However, when I tried this
> 
>  color index reverse brightblack black "~h ^(delivered|envelope)-to:\ 
> +[0-9a-f]{5,}[.][0-9a-f]{5,}@mydomain.com)$"
> 
> (tried with and without the backslash escaping the space)
> 
> Mutt complains
> 
>  Error in [my muttrc]: '^(delivered': parentheses not balanced
> 
> which looks like the "|" is getting higher precedence than the
> parens.

Quote the pattern, as you would if using ~h in a limit
statement:

  color index reverse brightblack black "~h '^(delivered|envelope)-to: 
+[0-9a-f]{5,}[.][0-9a-f]{5,}@mydomain.com)$'"

There shouldn't be any need to escape the space in the
pattern.

-- 
Todd

Re: macro does not work when mailbox opened read-only

[Todd Zullinger]

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 deleting
> any messages marked for deletion.
> 
> When I delete my custom macro, and revert "q" to its default action,
> then I get this message when exiting from mutt (case 2):
> 
>   Purge 1 deleted message? ([yes]/no):
> 
> When I create custom macro to sync automatically, I get the error on
> read-only mutt, because it cannot be synced.
> 
> So I need "q" that works in both cases.

You may want to look at the $delete option.  It's a
quad-option which defaults to ask-yes.

http://www.mutt.org/doc/manual/#delete

-- 
Todd

Re: remove restriction on line length in mutt compose

[Todd Zullinger]

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 settings.
For vim, the mail.vim ftplugin sets textwidth=72.  You can
print the value of the textwidth from within vim by typing:

:set textwidth

-- 
Todd


signature.asc
Description: PGP signature

Re: Patch [was Re: [Fwd: Re: Impossible to connect to mail server via pops3 using mutt 1.11]

[Todd Zullinger]

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 , which you
>> will find under the clone button on the project details page.
> 
> Yes, I did that as a first operation 2 or 3 days ago, assuming that the patch
> was part of it. To better visualize the repo I have been working on
> setting up gitweb functionality by means of a web server. At the moment,
> I'm still getting 403 forbidden when connecting to localhost, but I
> think I'll get it done.

It may be easier to use a graphical interface like gitk  to
view the repository outside of the command line than setting
up gitweb.  tig, a console repository viewer, is also quite
handy.

Alternately, the 'git instaweb' command can spawn gitweb for
a single repository fairly easily.  It can use a number of
different web servers, lighttpd is one of the simplest --
requiring no manual configuration.

>> If you open a particular commit, the options button has "Email patches" and
>> "Plain diff" views.  So, for example the commit in question is available via 
>> 
>> and 
>> 
>  Ok, thanks. Now it's confirmed that the patch/diff is in a separate
>  repository (not master, which I cloned). I'll get and test it. 

I know Kevin already clarified this in another reply, but
perhaps some additional details will help.

The fix is simply on a different branch.  You can -- with
any git release from the past few years -- checkout an
upstream branch pretty easily.  For this patch on the branch
kevin/stable-oauth-fix, you could use:

$ git checkout kevin/stable-oauth-fix
Branch 'kevin/stable-oauth-fix' set up to track remote
branch 'kevin/stable-oauth-fix' from 'origin'.
Switched to a new branch 'kevin/stable-oauth-fix'

If you don't already have a repo cloned and want to clone a
specific branch, you can do that as well with the --branch
option to 'git clone', e.g.:

$ git clone --branch kevin/stable-oauth-fix \
  https://gitlab.com/muttmua/mutt.git

Hope this helps (and isn't too far off-topic). :)

-- 
Todd


signature.asc
Description: PGP signature

Re: muttrc for different mutt versions

[Todd Zullinger]

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 specific version (2)
> - use a wrapper which invokes mutt with the specific rc file (2)

Mutt also looks for muttrc-$VERSION, so you can avoid the
need for a wrapper.  If you start mutt-1.10.1 and have a
config file at ~/.mutt/muttrc-1.10.1, it will be sourced.

You can use $XDG_CONFIG_HOME/mutt/muttrc-$VERSION or
~/.muttrc-$VERSION as well, of course.

Source: http://mutt.org/doc/manual/#configuration-files

-- 
Todd
~~
Happiness is like peeing on yourself. Everyone can see it, but only
you can feel its warmth



signature.asc
Description: PGP signature

Re: Option to disable S/MIME signature check?

[Todd Zullinger]

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 smime_verify_command="" (along with
> smime_verify_opaque_command and smime_decrypt_command).

Out of curiosity, is it correct that --disable-smime only
applies when building without gpgme?  It looks like with
--enable-gpgme, smime will be available via gpgme?

Thanks,

-- 
Todd
~~
A common mistake people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete
fools.
-- Douglas Adams



signature.asc
Description: PGP signature

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

[Todd Zullinger]

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 'system' is a FreeBSD netbook using mutt+sendmail;
>> 
>> I will Cc me on this mail to see its sent headers;
> 
> The outgoing mails contains a header line:
> 
>   Mail-Followup-To: Matthias Apitz , mutt-users@mutt.org
> 
> Who adds this? mutt by its own? If so, based on what?

Quoting http://mutt.org/doc/manual/#followup-to

3.72. followup_to

Type: boolean
Default: yes

Controls whether or not the “Mail-Followup-To:” header
field is generated when sending mail. When set, Mutt
will generate this field when you are replying to a
known mailing list, specified with the “subscribe” or
“lists” commands.

This field has two purposes. First, preventing you from
receiving duplicate copies of replies to messages which
you send to mailing lists, and second, ensuring that you
do get a reply separately for any messages sent to known
lists to which you are not subscribed.

The header will contain only the list's address for
subscribed lists, and both the list address and your own
email address for unsubscribed lists. Without this
header, a group reply to your message sent to a
subscribed list will be sent to both the list and your
address, resulting in two copies of the same email for
you. 

That's why Kevin suggested setting 'subscribe' for the mutt
list in your config.

The 'honor_followup_to' variable is related, relevant for
mutt users replying to messages with a 'Mail-Follup-To:'
header.

-- 
Todd
~~
The state is the great fictitious entity by which everyone seeks to
live at the expense of everyone else.
-- Fredric Bastiat



signature.asc
Description: PGP signature

Re: Remove Subject prefixing (when answering/forwarding) possible?

[Todd Zullinger]

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 answering/forwarding?
> 
> How do you configure this exactly in .muttrc? Thanks

http://www.mutt.org/doc/manual/#display-munging

subjectrx was added in 1.8.0, it seems.

-- 
Todd
~~
I always keep a supply of stimulant handy in case I see a snake -
which I also keep handy.
-- W. C. Fields



signature.asc
Description: PGP signature

Re: configure: error: could not find sasl lib

[Todd Zullinger]

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 and the leading
From_ line was not escaped Cameron?  It's present in the
original mesage:

> 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:
> 
> From audo...@gmail.com Wed Dec 27 23:09:31 2017
> Date: Wed, 27 Dec 2017 23:09:31 +0100
> From: DGSJ 
> To: audo...@gmail.com
> Subject: prueba mutt
> Message-ID: <20171227215809.GA13385@lucu-hp>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=unknown-8bit
> Content-Disposition: inline
> Content-Transfer-Encoding: 8bit
> User-Agent: Mutt/1.9.2 (2017-12-15)
> Status: RO
> Content-Length: 87
> Lines: 6
> (body of the mail)
> 
> I've installed mutt in several computers, even with the sasl libraries
> also build from source, and this is the first time I have a problem.
> 
> In this case I'm using a Xubuntu OS (4.10.0-42-generic), and I have build
> the libraries installing the Debian packages with apt-get install:
> libgnitls-dev
> libssl-dev
> libsecret-1-dev
> libgsasl7-dev

The debian mutt packages build with Cyrus SASL (from
libsasl2-dev).

I don't known if mutt supports GNU SASL or not.  If GNU SASL
is completely compatible, perhaps you need to pass the
proper path to it with --with-sasl.  Unless you have a
specific need for GNU SASL, I'd just install libsasl2-dev
and build mutt using that SASL implementation.

-- 
Todd
~~
Love is a snowmobile racing across the tundra. Suddenly it flips,
pinning you underneath. At night, the ice weasels come.
-- Matt Groening



signature.asc
Description: PGP signature

Re: Possible to not leave pager if up on first or down on last message?

[Todd Zullinger]

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-pager will not move to the next
>> message when you are at the end of a message and invoke
>> the  function.
> 
> That's for internal page navigation. Pressing  or  is an index
> operation and doesn't affect Scott's issue. (This is the setup I have
> now and Up/Down still close the pager for me.)

Oops, sorry about that.  I also have some key bindings to
remap  and  which I didn't remember.

bindpager   previous-line
bindpager next-line

I knew this sort of thing used to bug me and when I looked
at pager_stop in my muttrc, I thought that was it.  It's
been many years since I set most of these things.  My memory
is obviously not as clear as I'd like to think. ;)

-- 
Todd
~~
Fleas can be taught nearly anything that a Congressman can.
-- Mark Twain



signature.asc
Description: PGP signature

Re: Possible to not leave pager if up on first or down on last message?

[Todd Zullinger]

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 would prefer to
> stay in the pager. Is it possible to configure this?
> 
> My use case is I find it very helpful to be able to focus on one email
> at a time, without knowing how many emails I have. I start mutt with:
> 
> mutt -e "push "

I think you want the pager_stop¹ variable:

3.169. pager_stop

Type: boolean
Default: no

When set, the internal-pager will not move to the next
message when you are at the end of a message and invoke
the  function.

¹ http://www.mutt.org/doc/manual/#pager-stop

-- 
Todd
~~
In my life, I have prayed but one prayer: oh Lord, make my enemies
ridiculous. And God granted it.
-- Voltaire



signature.asc
Description: PGP signature

Re: mutt feeds more to gnupg than it needs, causes invisible/lost

[Todd Zullinger]

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 pgp_auto_decode, then it filters the
 entire message through gnupg, which swallows all the unsigned text.

Indeed.  I've noticed this as well.  A more annoying case is if
someone replies to a clearsigned PGP message and leaves the entire
message intact (as those who top post are prone to doing).  When mutt
displays such a message the only thing it shows is the original, PGP
signed text.  It makes it appear as if the sender had simply resent
the original post without adding anything of their own (the first few
times I saw this, I figured it was user error, as those who top post
are also prone to silly errors like that ;).

I don't have any particular help for you Martin, but I can definitely
confirm what you're seeing.  I unset $pgp_auto_decode to work around
this for the time being.

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Two things are infinite: the universe and human stupidity;
and I'm not sure about the universe.
 -- Albert Einstein (1879-1955)



pgpTWqKsIXbIx.pgp
Description: PGP signature

Re: mutt feeds more to gnupg than it needs, causes invisible/lost

[Todd Zullinger]

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 behaved this way, but it happens somewhat
infrequently, so I could just not remember it.

If you call check-traditional-pgp on this message, is this text lost?
It is for me and I would call it a bug.  It might also be some subtle
difference between our configurations, gpg versions, etc.

I don't know how much I care about it, as I just don't care much
about inline PGP messages.  But it is a bit curious.

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Derek Martin wrote:
 I have pgp_auto_decode set, and additionally I unset it and manually
 executed check-traditional-pgp, and I saw the above text in all cases.
 So unless I misunderstood you, it seems my Mutt behaves differently
 from yours...

Hmmm.  I can reproduce it using mutt -n -F /dev/null.  It also doesn't seem to
matter whether I use the gpgme backend or the classic backend.

 But besides that, check-traditional-pgp is not intended to work with
 MIME messages...

I've seen this problem when there is no PGP-MIME involved.  Or did you mean any
MIME?

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iQFDBAEBCAAtBQJLEI+SJhhodHRwOi8vd3d3LnBvYm94LmNvbS9+dG16L3BncC90
bXouYXNjAAoJEEMlk4u+rwzjtNAIAKAMA3gookXY/N8HY9dgiLhR0+Ts2QvjmbAv
kszePAwBy8KhXTt88MGPEE4Tz0QnUADDTtZBHxhVy29PPE+S9RITPuULgxoNvmcJ
pJSkpGgZivlmm8vs90PBL68YKwH1Lv97XFSQhiAGWHtWBFR4LtB7gAvB+em4oeVB
6hKDo22O2A/5d/oU3L6SpOK/PbyRas4JDbSsV3Kk2lPYMyav+ATH+i9atCIjwi79
S4um0bxLsaTOhuJcjNpgosRpSpTunisYudF84bVmWHpr2NV+TLxeIkL2crai9aYc
XmwnyK9AJljSzoPDlwufqvZRMxVsXs40a2X9EHEZ/uxNJ26XQ3E=
=pxX0
-END PGP SIGNATURE-

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Hard work never killed anybody, but it is illegal in some places.
-- Demotivators (www.despair.com)

Re: couldn't save certificate

[Todd Zullinger]

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 certificates file is /etc/pki/tls/certs/ca-bundle.crt, which, like
on Debian, is provided by the ca-certificates package.

The 'couldn't save certificate' error message could probably be
improved. ;)

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
There, I've gone and soiled myself, are you happy now?!
-- Stewie Griffin



pgp6blqWAHcDQ.pgp
Description: PGP signature

Re: F1 - key-binding trapped

[Todd Zullinger]

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 gnome-terminal-help on my ubuntu 8.10.

 Well - unbind the key in gnome-terminal resp. gnome (no idea how,
 sorry I don't use gnome) or just use a different key for mutt.

In gnome-terminal, use the Edit - Keyboard Shortcuts menu.

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Sometimes I think I understand everything, then I regain
consciousness.



pgpZMXxBv8RVX.pgp
Description: PGP signature

Re: Header weeding for message/rfc822 parts in 1.5.20

[Todd Zullinger]

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
~~
Philosophy:  A route of many roads leading from nowhere to nothing.
-- Ambrose Bierce



pgpUEajOh16yY.pgp
Description: PGP signature

Re: [ANNOUNCE] 1.5.20 released

[Todd Zullinger]

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
~~
There are three ways to get something done: do it yourself, hire
someone, or forbid your kids to do it.
-- Monta Crane



pgpdiss6IYdqq.pgp
Description: PGP signature

Header weeding for message/rfc822 parts in 1.5.20

[Todd Zullinger]

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 dealing with messages sent to mailman lists which
I am an admin/moderator, which isn't a lot.  I'm guessing folks who
get MIME formatted list digests would find the change a bit more
jarring. ;)

¹ http://dev.mutt.org/trac/changeset/536771b4e085

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
I believe in the noble, aristocratic art of doing absolutely nothing.
And someday, I hope to be in a position where I can do even less.



pgp5jHLduULdF.pgp
Description: PGP signature

Re: Header weeding for message/rfc822 parts in 1.5.20

[Todd Zullinger]

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
~~
Until you spread your wings, you'll have no idea how far you can walk.
-- Demotivators (www.despair.com)



pgpFaLTdhuSwl.pgp
Description: PGP signature

Re: Threading with IMAP folders

[Todd Zullinger]

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.  Of course, that
doesn't mean that much of what you wrote might not be applicable to
Matt's situation. :)

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
A little inaccuracy sometimes saves a ton of explanation.
-- H. H. Munro (Saki) (1870-1916)



pgp0D6FpVgZk6.pgp
Description: PGP signature

Re: Gnupg2 vs gnupg

[Todd Zullinger]

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 problem
perhaps twice and haven't had time to find out where the problem was.

I have used gpg-agent for a long time now and it hasn't caused me much
trouble at all with mutt after that last small patch.  (It could just
be that I only trade encrypted messages with mostly well-trained folks
though. ;)

 Does anyone here know what the differences between the two are?

In a nutshell, GnuPG-2 is more modular and has support for S/MIME.
But GnuPG-1.4 isn't going anywhere for a while.

There wre a few threads on the gnupg-users list about this in the last
month or three, though I can't seem to find any of the better messages
from David Shaw or Werner Koch that answered this question in a quick
search of my list archive.

 Why gnupg2 is recommended for desktop use moreso than gnupg1?

Perhaps due to better support for smart cards and such?  But that's
just a guess.  I've stayed with GnuPG-1.4, as I have no need for
S/MIME support.  Hell, I spend most of my time in a terminal, so
better desktop support also doesn't mean much to me. :)

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
The trouble with being punctual is that nobody's there to appreciate it.
-- Franklin P. Jones



pgpF8DIWtS8w2.pgp
Description: PGP signature

Re: clearsign not working

[Todd Zullinger]

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 be set (to remove signing, encrypting, etc.).

i by itself does nothing either.  It merely sets the flag to use
inline (aka traditional) pgp for the message.  You want to use both
s and i such that the PGP menu on the compose screen looks like
this: PGP: Sign (inline)

If you do this, what is the result?  Sending such a message to the
list would probably help.

(That said, hopefully you have a good reason to use inline pgp instead
of the generally superior pgp/mime format. ;)

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
I could never recommend the use of drugs or alcohol to anyone, but
they've always worked for me.
-- Hunter S. Thompson



pgpd0eopsVGEq.pgp
Description: PGP signature

Re: Change unread mark without open the message

[Todd Zullinger]

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 tag-pattern~N\nclear-flagNuntag-pattern~T\n \
   Mark all messages as read

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
A hen is only an egg's way of making another egg.
-- Samuel Butler



pgpyAOlMCks52.pgp
Description: PGP signature

Re: more verbose Enter passphrase: line?

[Todd Zullinger]

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
 adress.
 The problem begins when i want to search emails. I use the
 thorough_search-option to decrypt encrypted messages before
 searching.

Huh, I managed to have missed that option.  Thanks for mentioning it.

 But now, i don't know for which key pair mutt is asking me the
 passphrase for. 
 Is there a possibility to get a more verbose output? Something like
 Enter passphrase for id xyz: ?

If you use gpg-agent you will get this sort of prompt.  To use the
agent with mutt, you need to be sure to export GPG_AGENT_INFO and
GPG_TTY.  You then just add set pgp_use_gpg_agent=yes to your
.muttrc.  See the gpg-agent docs for how to setup the agent to run.

 And actually, is mutt/gpg capable of handling more than one
 passphrase at once?

Using gpg-agent I know this is possible.  It's been ages since I tried
it with mutt's builtin passphrase caching.

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
The ultimate result of shielding men from the effects of folly is to
fill the world with fools.
-- Herbert Spencer



pgpWSPGXhobgY.pgp
Description: PGP signature

Re: Reliable/safe way of removing empty maildirs?

[Todd Zullinger]

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.

I'm sure you meant just the opposite.  It won't remove non-empty dirs.

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
That men do not learn very much from the lessons of history is the
most important of all the lessons of history.
-- Aldous Huxley Collected Essays, 1959



pgp0zq36D0iq5.pgp
Description: PGP signature

Re: EMAIL and / or use_from in batch process

[Todd Zullinger]

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 it:
 % cat bogus_muttrc 
 set envelope_from
 set use_from
 set from=[EMAIL PROTECTED]
 set realname=The Name
 
 earlier, it just had set envelope_from, and I set $EMAIL to the
 address I wanted. This had worked before (with earlier versions of
 1.5.x), and I'm sure that $EMAIL is set, but now, I'm not getting the
 sender or envelope-sender addresses in the email that's being sent out.

This was the same issue that a patch sent to mutt-dev a few days ago
was aimed at: http://marc.info/?l=mutt-devm=119564833700787w=2

It might be worth keeping an eye on that thread.

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
In their enthusiasm for frequent travel through the Doors of
Perception, far too many get hung up on the doorknob.
-- M. Domalgowski



pgpudx1iHYnzX.pgp
Description: PGP signature

Re: unable to use send2-hook / group pattern for automatic

[Todd Zullinger]

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
 gpg key I trust.
 
 I want to use this group feature to switch encryption on and off
 depending on emailaddresses:

FWIW, another way I think you can achieve your goal is to use Nicolas
Rachinsky's crypt-autohook patch[1].  (Many thanks Nicolas!)

[1] http://www.rachinsky.de/nicolas/mutt.shtml

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Wisdom has two parts: (1) having a lot to say and (2) not saying it.



pgpTQA025ecfj.pgp
Description: PGP signature

Re: Spellcheck

[Todd Zullinger]

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 mode.  See :help
spell in vim for details on how to use the spell checker.

 Nevertheless, once you pointed out to me where the real compose
 screen exists, I find that I really do have a workable spell
 checker.  

I tend to prefer this method myself.  It's probably as much from habit
as from anything else.

 N.B. I am a refugee from Windows, so the going has been a bit dicey.
 But I have learned enough about my system (FreeBSD), and the
 programs therein to report to you that the die is cast, and there is
 no turning back.

If you're using vi as an editor and mutt as a mailer, I can imagine
that you'll do well in the *nix world.  Have fun. :)

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
If Stupidity got us into this mess, then why can't it get us out?
-- Will Rogers (1879-1935)



pgpSJfzILTP2W.pgp
Description: PGP signature

Re: GPG keyservers

[Todd Zullinger]

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 versions don't support
searching with a keyid.  I believe this change made it into gnupg
1.4.6, so if you're using something older than that, searching an HKP
keyserver using the keyid with prefixing 0x doesn't usually work.

Try gpg --search-keys 0xED0E1FB7 and see if that works better.  You
can also use gpg --interactive --recv-keys ED0E1FB7.

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Common sense is genius dressed in its working clothes.
-- Ralph Waldo Emerson



pgpUK5sgYYf6u.pgp
Description: PGP signature

Re: GPG keyservers

[Todd Zullinger]

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 unmodified version.
 
 I tried to submit 
 gpg --send-keys 0xED0E1FB7
 gpg --send-keys ED0E1FB7
 
 both went though fine (I think) no complains.
 Except I think it doesn't work. 
 I have removed/updated most keyid's and change expiration to
 unlimited.  but it pulls back expired version.
 pub  1024D/ED0E1FB7  created: 2002-05-09  expires: 2005-02-02

You may have something still on your keyring or on your key which has
the expiration date.  That can cause gpg to still show the key as
expired.  It's worth noting that you cannot remove anything from the
keyservers.  If you have user id's or other parts of your key that you
don't like, you can revoke them, but you can't simply delete them from
your local copy and then re-upload the key.  This is something that
often bites new (and sometimes old) gpg users.

You may want to do some googling and then ask on the gnupg-users list
for more specific gpg help.

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
A statesman is a dead politician. Lord knows, we need more statesmen.
-- Opus



pgpWDt4q7JaOI.pgp
Description: PGP signature

Re: GPG keyservers

[Todd Zullinger]

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 gnupg2-2.0.6.

 You are right, I did some revision and resubmit the key.
 The gpg --interactive --recv-keys ED0E1FB7 is working OK
 the search is not working on this version correctly.
 I'll need to dig deeper into it.

Not even with 0x prefixed when searching by keyid?  I know that works
fine on the 1.x branch, back as far as 1.2.x (the oldest version I had
handy to try it with).  I tried using gpg2 --search ED0E1FB7 and it
failed, while gpg2 --search 0xED0E1FB7 succeeded.  So it seems the
keyserver bug that was fixed in 1.4.6 hasn't been fixed in the gnupg2
branch, at least not in my package (it may be a build problem though).

Anyway, I do recommend asking on gnupg-users if you don't get things
worked out.  There are some helpful folks there, much as there are on
this list.

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Truth is like a well-known whore.  Everybody knows her but it's
embarrassing to meet her in the street.
-- Wolfgang Borchert



pgpc3uyoFPGzJ.pgp
Description: PGP signature

Re: extract pgp/gpg key

[Todd Zullinger]

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 OpenPGP
spec.  The extract-key function works when you have a key block in the
message.  You can attach a key to a message using the attach-key
function from the compose menu (Esck by default).

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Neuroses are red,
Melancholia's blue.
I'm schizophrenic,
What are you?



pgprd7e1wRdbj.pgp
Description: PGP signature

Re: lists and subscribe commands and the To: header

[Todd Zullinger]

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 being from a list?

Pardon me if I'm missing the important bits of this thread (quite
likely)... but there is some support for RFC2369 List-Post headers in
parse.c.  If you use list-reply on a message with a List-Post header
it will do the right thing.

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Politeness, n. The most acceptable hypocrisy.
-- Ambrose Bierce



pgp5eKzolCPzd.pgp
Description: PGP signature

Re: lists and subscribe commands and the To: header

[Todd Zullinger]

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, and h-env-cc is build from the CC headers.

I see.  I should have known I was missing the important part of the
thread. :)

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
If quitters never win, and winners never quit, then who is the fool
who said Quit while you're ahead?



pgpEtNVrOfE5h.pgp
Description: PGP signature

Re: gpg: encrypt with more than one key

[Todd Zullinger]

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 not able to choose more than one gpg
 key in the dialog window with 't' as i'm used to do with addresses
 in my addressbook.
 at the moment, i face this problem only with this mailing list. i'm
 not sure if it's impossible in general to encrypt emails with more
 than one key (for example: one email, two recipients in to:, both
 recipients' keys in the keyring), i have to test that.

Others have covered most of this, but one suggestion I haven't seen is
to use gpg's group feature.  In your gpg.conf you could create a group
for all of the reciepients.  I've not tried this so I don't know if it
has some failing when working with mutt, but it seems likely that it
would work[1].

The syntax in gpg.conf is:

group mynames = paige 0x12345678 joe patti

If you named the group in a way that matched the mailing list, mutt
should automatically pick it when you mail to the group.  If that
doesn't work, you could probably use a pgp-hook.

[1] to my sugar starved brain at this early hour

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Moderation in temper is always a virtue; but moderation in principle
is always a vice.
-- Thomas Paine, Common Sense



pgpyTnNN0dqCB.pgp
Description: PGP signature

Re: Make of docs and other stuff

[Todd Zullinger]

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:-
 
 make[2]: Entering directory `/home/Brian/prog/mutt-1.5.15/doc'
 make makedoc-all
 make[3]: Entering directory `/home/Brian/prog/mutt-1.5.15/doc'
 sed -e 's,@sysconfdir\@,/usr/local/etc,g' -e 's,@bindir\@,/usr/local/bin,g' 
   -e 's,@docdir\@,/usr/local/doc/mutt,g' ./mutt.man mutt.1
 gcc -E -I. -I.. -I/usr/local/include -I.. -DSYSCONFDIR=\/usr/local/etc\ 
   -DBINDIR=\/usr/local/bin\ -DHAVE_CONFIG_H=1 -I../intl -D_MAKEDOC 
   -C ../init.h | ../makedoc -m |  \
   cat ./muttrc.man.head - ./muttrc.man.tail\
muttrc.man
 make -j1 ../makedoc.exe # we do not want to rebuild the documentation in 
   tarball builds
 make[4]: Entering directory `/home/Brian/prog/mutt-1.5.15/doc'
 make[4]: `../makedoc.exe' is up to date.
 make[4]: Leaving directory `/home/Brian/prog/mutt-1.5.15/doc'
 ( date=`head -n 1 ../ChangeLog | LC_ALL=C cut -d ' ' -f 1`  \
 sed -e s/@VERSION\@/`cat ../VERSION` ($date)/ ./manual.xml.head  \
 gcc -E -I. -I.. -I/usr/local/include -I.. 
   -DSYSCONFDIR=\/usr/local/etc\ -DBINDIR=\/usr/local/bin\ 
   -DHAVE_CONFIG_H=1 -I../intl -D_MAKEDOC -C ../init.h | ../makedoc 
   -s  \
 gcc -E -I. -I.. -I/usr/local/include -I.. 
   -DSYSCONFDIR=\/usr/local/etc\ -DBINDIR=\/usr/local/bin\ 
   -DHAVE_CONFIG_H=1 -I../intl -D_MAKEDOC -C ../functions.h | \
   perl ./gen-map-doc ./manual.xml.tail ../OPS* \
   ) manual.xml
 touch stamp-doc-xml
 xsltproc --nonet ./chunk.xsl manual.xml
 I/O error : Attempt to load network entity 
   http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl
 warning: failed to load external entity 
   http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl;
 compilation error: file ./chunk.xsl line 3 element import
 xsl:import : unable to load 
   http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl
 make[3]: [stamp-doc-chunked] Error 5 (ignored)
 touch stamp-doc-chunked
 xsltproc --nonet -o manual.html ./html.xsl manual.xml
 I/O error : Attempt to load network entity 
   http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl
 warning: failed to load external entity 
   http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl;
 compilation error: file ./html.xsl line 3 element import
 xsl:import : unable to load 
   http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl
 make[3]: [manual.html] Error 5 (ignored)
 lynx -dump -nolist -with_backspaces manual.html manual.txt || 
   w3m -dump manual.html manual.txt
 
 It then quit. I have added some newlinetab to make it clearer. So:
 
 1. Why does it have to get this stuff from the internet and why is it
 failing to do so? I have a reliable broadband access.

I ran into this on linux and I believe it's due to not having the
docbook-xsl stylesheets[1] installed.  I added those, as well as
libxslt and the docs built fine.  I have no idea if adding those to
cygwin is a simple task or not.

[1] http://wiki.docbook.org/topic/DocBookXslStylesheets

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
==
The only difference between the saint and the sinner is that every
saint has a past and every sinner has a future.
-- Oscar Wilde



pgpGGgTOUYS69.pgp
Description: PGP signature

Re: GPG and good signature (mis?)behaviour

[Todd Zullinger]

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 01 May 2007 03:50:24 PM CEST) --]
 gpg: Signature made Tue 01 May 2007 03:34:27 PM CEST using DSA key ID 
 gpg: Good signature from xx xxx 
 gpg: WARNING: This key is not certified with a trusted signature!
 gpg:  There is no indication that the signature belongs to the owner.
 Primary key fingerprint:           
 [-- End of PGP output --]

The important part is the gpg warning.  It means that the key used to
sign the message isn't signed (certified) by your key (or the key of
someone else that you've marked as trusted).

You can test this by adding a local signature to a key for which this
happens (gpg --lsign-key keyid).

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
==
It is easier to fight for one's principles than to live up to them.
-- Alfred Adler



pgptbgvFWVXmc.pgp
Description: PGP signature

Re: GPG and good signature (mis?)behaviour

[Todd Zullinger]

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
==
Quick to judge, quick to anger, slow to understand.
Ignorance and prejudice and fear walk hand in hand.



pgpNmAEIlDN1h.pgp
Description: PGP signature

Re: GPG and good signature (mis?)behaviour

[Todd Zullinger]

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 pgp_decrypt_command=gpg --passphrase-fd 0 --no-verbose --batch --output 
 - %f
 set pgp_sign_command=gpg --no-verbose --batch --output - --passphrase-fd 0 
 --armor --detach-sign --textmode %?a?-u %a? %f
 set pgp_clearsign_command=gpg --no-verbose --batch --output - 
 --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f
 set pgp_encrypt_only_command=pgpewrap gpg --batch --quiet --no-verbose 
 --output - --encrypt --textmode --armor --always-trust --encrypt-to 
 0xC9C40C31 -- -r %r -- %f
 set pgp_encrypt_sign_command=pgpewrap gpg --passphrase-fd 0 --batch --quiet 
 --no-verbose --textmode --output - --encrypt --sign %?a?-u %a? --armor 
 --always-trust --encrypt-to 0xC9C40C31 -- -r %r -- %f
 set pgp_import_command=gpg --no-verbose --import -v %f
 set pgp_export_command=gpg --no-verbose --export --armor %r
 set pgp_verify_key_command=gpg --no-verbose --batch --fingerprint 
 --check-sigs %r
 set pgp_list_pubring_command=gpg --no-verbose --batch --with-colons 
 --list-keys %r 
 set pgp_list_secring_command=gpg --no-verbose --batch --with-colons 
 --list-secret-keys %r 
 
 # a regexp: if that matches the mutt output from pgp_verify_command then the 
 message is considered verified
 # I'm not sure this is necessary, since gpg already exit with an useful exit 
 code of 0 in case
 # of success
 set pgp_good_sign=^gpg: Good signature from
 #set pgp_check_exit=no
 
 I'm using mutt 1.5.13. 
 
 Can you explain this behaviour? Is it maybe a mutt bug?
 Thanks in advance for any help.

As Sander pointed out, my previous reply missed the mark a bit...

Looking a little closer (still without the benefit of a morning sugar
solution), I think that your settings could be the problem.  I've been
using the gpg.rc that comes with mutt for a while now (surely before
1.5.13).  You may want to try sourcing that to see it if helps.

The relevant things that I believe are different from your config
above are:

pgp_verify_command=gpg --status-fd=2 --no-verbose --quiet --batch --output - 
--verify %s %f
pgp_good_sign=^\[GNUPG:\] GOODSIG

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
==
Now, now my good man, this is no time for making enemies.
-- Voltaire, on his deathbed in response to a priest asking that
he renounce Satan.



pgplGYSanOgiC.pgp
Description: PGP signature

Re: GPG and good signature (mis?)behaviour

[Todd Zullinger]

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
 results in a S flag), in the bad ones I can't see the s when
 opening them in the index, but it appears when I display the
 corresponding mail in the pager, and the s doesn't become S after
 I verify them even if they are good (according to the gpg output).
 
 I tried to figure out some relevant difference between the good and
 bad folders (I'm using maildir formats), but without success... very
 puzzling, so I have to conclude this is a rather strange bug.

Hmmm.  Do you have folder hooks in play that could cause this?  If you
haven't already, perhaps try with a very stripped down muttrc and see
if it still happens.

 Anyway, apart from the strange s/S inconsistency, the gnupg output
 seems correct (I verified ti with corrupt signatures), so it means I
 don't have to blindly trust stupid flags ;-).

Good to know.  I don't tend to pay much attention to the s/S flag in
the index, so perhaps I've run into this as well without noticing.

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
==
A cynic is a man who, when he smells flowers, looks around for a
coffin.
-- H. L. Mencken



pgpGN83qHLLJZ.pgp
Description: PGP signature

Re: Is merging threads possible?

[Todd Zullinger]

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 machine)

FWIW, mutt-1.5.14 should be included in Fedora 7.  So that might be
one less place you have to update the default install.

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
==
The United States is a nation of laws, badly written and randomly
enforced.
-- Frank Zappa



pgpap3tTd7NUV.pgp
Description: PGP signature

Re: Is merging threads possible?

[Todd Zullinger]

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
==
Many people are secretly interested in life.



pgpp4UaqlJzIr.pgp
Description: PGP signature

Re: Save encrypted-to-self or plain copy of sent message

[Todd Zullinger]

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 glue).

 I can imagine looking at my outbox in a years time and thinking
 Argh, did I really send that unencrypted? or something.

Yeah, I've done just that.

One thing that bugs me a little about using fcc_clear is that I don't
get to keep my signed messages.  I only use fcc_clear so that I can
grep my mail easier and I'd like to keep the signatures intact.  It's
not a big deal or I'd have looked at how I could toggle the setting on
for encrypted mail and off for signed mail.  Someday I'll do that I
tell myself. :)

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
==
I never forget a face, but in your case I'll be glad to make an
exception.
-- Groucho Marx



pgpc9qp1nJxNZ.pgp
Description: PGP signature

Re: Save encrypted-to-self or plain copy of sent message

[Todd Zullinger]

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: no

   When this variable is set, FCCs will be stored unencrypted and
   unsigned, even when the actual message is encrypted and/or signed.
   (PGP only)

 (or alternatively one encrypted with my own public key) for my
 'sent' outbox.

You can do this in your gpg.conf using the encrypt-to option.

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
==
Diplomacy is the art of saying 'Nice doggie!'... till you can find a
rock



pgpvHYCsjfNSP.pgp
Description: PGP signature

Re: reading color quoted replies

[Todd Zullinger]

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 plain text on a per-recipient basis.  If those sending you
such mail are important then it would be worth the effort to explain
to them why they should send you plain text mail.  If they aren't
important, then Patrick's suggestion to file it to /dev/null is best.

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
==
Grant me the senility to forget the people I never liked anyway, the
good fortune to run into the ones I do, and the eyesight to tell the
difference.



pgpAI8yNfqBDb.pgp
Description: PGP signature