[bug-anubis] Problem setting up anubis with GPG

[Mike Clark]

I'm trying to setup Anubis to act as a sort of proxy to sign/encrypt
emails coming from a service. The service is currently configured to
send email using our SMTP server. The idea would be to point the
service to Anubis and then point Anubis to the SMTP server. Anubis
would then sign/encrypt messages before sending them on to the SMTP
server.

I setup Anubis and as an initial test, set it up to modify the subject
line. That worked just fine. When I changed it to sign emails, I
started getting an error message in the Anubis debug output.

Here is the Anubis config:

    #
    # The "CONTROL" section.
    # User configuration file.
    #

    ---BEGIN CONTROL---
    bind localhost:2525
    remote-mta SMTP_SERVER_INFO
    ssl-oneway yes
    ---END---

    #
    # The Rule System (The RULE section)
    # User configuration file only. Examples:
    #

    ---BEGIN RULE---

    gpg-passphrase "test1234"

    # Process the (E)SMTP commands.

    if command["mail from"] ".*<address@hidden>?"
     STOP
    fi

    # Process a message header lines.

    if header[From] ".*noreply.*"
      # modify [Subject] "[Anubis Proxy] &" # This action works
      gpg-sign default # This action has an error
    fi

    ---END---

Here is the portion of the debug output related to GPG:

    Protocol: OpenPGP
    Executable: /usr/bin/gpg2
    Version: 2.0.22
    Required Version: 1.4.0
    Protocol: CMS
    Executable: /usr/bin/gpgsm
    Version: 2.0.22
    Required Version: 1.9.6
    Protocol: GPGCONF
    Executable: /usr/bin/gpgconf
    Version: 2.0.22
    Required Version: 2.0.4
    Protocol: Assuan
    Executable: /tmp/gpg-7KgHae/S.gpg-agent
    Version: 1.0
    Required Version: 1.0
    [2319] GPGME: General error.



I'm sure gpg is setup correctly as ```gpg --sign --armor``` from the
command line lets me sign a message (after entering the password).

What have I done wrong to make this not work correctly?

I should mention that I compiled Anubis from source (version 4.2) and
that the results of ```./configure``` showed GPGME support enabled.