Hi,
I passed some time trying to make enh-mailgate working with PGP, without
success.
It seems that the version that is in contrib uses an old version of RT.
Typically, the method new RT::CurrentUser() take zero parameters and it
was written as new RT::CurrentUser(RT::SystemUser) in enh-mailgate.
Does anybody have enh-mailgate in daily use? What do you think needs to
be done to make it up-to-date to RT-2.0.2?
Hi,
I passed some time trying to make enh-mailgate working with PGP, without
success.
It seems that the version that is in contrib uses an old version of RT.
Typically, the method new RT::CurrentUser() take zero parameters and it
was written as new RT::CurrentUser(RT::SystemUser) in enh-mailgate.
Actually, if you read the code, you’ll see that RT::CurrentUser->new can
optionally take an argument.
Does anybody have enh-mailgate in daily use? What do you think needs to
be done to make it up-to-date to RT-2.0.2?
Nothing substantive has changed between when enhanced-mailgate was written
and now. It should work fine with 2.0.2.
I have images of Marc in well worn combat fatigues, covered in mud,
sweat and blood, knife in one hand and PSION int he other, being
restrained by several other people, screaming “Let me at it!
Just let me at it!” Eichin standing calmly by with something
automated, milspec, and likely recoilless.
-xiphmont on opensource peer review
Hi,
Has anyone enhanced rt-mailgate working?
I try, I try, but… No success!
What’s the principles?
Are these assumptions correct:
Only PGP signed messages sent to enh-mailgate are allowed to contain
commands
Commands are per example, “RT-status open” on the first line of the
BODY to make the status of the ticket referenced in the subject
([example.com#123]) “open” (the ticket 123 in this example)
How does enh-mailgate knows the PGP keys of clients sending mails? Must
I put public keys somewhere? Or is it not necessary?
Only PGP signed messages sent to enh-mailgate are allowed to contain
commands
For ticket updates, that’s true. For ticket creation, it doesn’t do GPG
ACL checking, since part of the point is to let requestors set ticket
fields
Commands are per example, “RT-status open” on the first line of the
BODY to make the status of the ticket referenced in the subject
([example.com#123]) “open” (the ticket 123 in this example)
It should look like this:
RT-Ticket: 123
RT-Status: open
How does enh-mailgate knows the PGP keys of clients sending mails? Must
I put public keys somewhere? Or is it not necessary?
You need to set up gpg for the user that the mailgate will be running as
with those keys.