Re: [rt-users] Forwarding an e-mail with an HTML alternative

[Martin Drašar]

Dne 7.2.2014 17:52, Kevin Falcone napsal(a):

Thanks for your response. I am not necessarily looking for an easy way
to make RT do my bidding and upgrade is not an option right now. In a
way, I do not really need to use the template at all, incoming messages
are formated just as I want them to be.


On Create Notify Requestors with template Corresopnd

which will relay your mail to the requestors during creation.
Your Scrip is honestly likely to cause all the problems you saw.

Or just set your requestors and then correspond on the ticket with
your content.


Correspond template is not working for me as I would like it to work - 
i.e. in the template I have RT-Attach-Message: Yes, but if I don't 
supply body in the text of the template (because I don't want to insert 
any other text, except the one I have received), no mail is sent.


Can I do something with it?

Another thing is a the RT-Ataach-Message mechanism. If I take a look at 
the sent message from within the RT I see two RT-Attachment headers. 
Does that mean that those two attachments are going to be sent 
separately and not inside multipart/alternative?



4.2 will do a better job of not mangling your mail.  Reading the
outgoing mail transaction though is almost guaranteed to fail.
Just use normal RT correspond actions.


By outgoing mail transaction, do you mean the Correspondence 
transaction? Because I have previously altered the Notify.pm scrip 
(albeit to much lesser extent) to add one special attachment to each 
outgoing e-mail and I had no problems with it at all...


Thanks,
Martin

Re: [rt-users] Forwarding an e-mail with an HTML alternative

[Martin Drašar]

Hmm... so I have just hacked the Template.pm _DowngradeFromHTML() to 
check for multipart/alternative in transaction and supply the text/plain 
part from it, instead of using the HTML::TreeBuilder and 
HTML::FormatText. Seems to work like a charm.


Now I wonder, when it's going to bite me :-)

Martin

Re: [rt-users] GnuPG problems with message decryption

[Martin Drašar]

Dne 22.2.2012 21:48, Ruslan Zakirov napsal(a):

I have this in the log:

[Tue Feb 21 15:34:09 2012] [debug]: Found encrypted inline part 
(/home/RT/RT-4.0.5/sbin/../lib/RT/Crypt/GnuPG.pm:906)
[Tue Feb 21 15:34:09 2012] [debug]: [GNUPG:] ENC_TO 26B34A0AE44C6E92 1 0
[GNUPG:] USERID_HINT 26B34A0AE44C6E92 CSIRT-MU DEVELr...@rt-devel.ics.muni.cz
[GNUPG:] NEED_PASSPHRASE 26B34A0AE44C6E92 023D741AB8EF2A3A 1 0
[GNUPG:] MISSING_PASSPHRASE
[GNUPG:] BAD_PASSPHRASE 26B34A0AE44C6E92
[GNUPG:] ENC_TO 110B534B28C8D875 1 0
[GNUPG:] NO_SECKEY 110B534B28C8D875
[GNUPG:] BEGIN_DECRYPTION
[GNUPG:] DECRYPTION_FAILED
[GNUPG:] END_DECRYPTION (/home/RT/RT-4.0.5/sbin/../lib/RT/Crypt/GnuPG.pm:1417)
[Tue Feb 21 15:34:09 2012] [error]: gpg: cancelled by user
gpg: encrypted with 2048-bit RSA key, ID 28C8D875, created 2010-12-30
   Martin Drasardra...@ics.muni.cz
gpg: encrypted with 2048-bit RSA key, ID E44C6E92, created 2012-02-21
   CSIRT-MU DEVELr...@rt-devel.ics.muni.cz
gpg: public key decryption failed: bad passphrase
gpg: decryption failed: secret key not available 
(/home/RT/RT-4.0.5/sbin/../lib/RT/Crypt/GnuPG.pm:1419)
[Tue Feb 21 15:34:09 2012] [debug]: Found GnuPG protected parts 
(/home/RT/RT-4.0.5/sbin/../lib/RT/Interface/Email/Auth/GnuPG.pm:240)
[Tue Feb 21 15:34:09 2012] [debug]: Error during verify/decrypt operation 
(/home/RT/RT-4.0.5/sbin/../lib/RT/Interface/Email/Auth/GnuPG.pm:244)
[Tue Feb 21 15:34:09 2012] [error]: Had a problem during decrypting and 
verifying (/home/RT/RT-4.0.5/sbin/../lib/RT/Interface/Email/Auth/GnuPG.pm:102)


This is happening with RT-4.0.5 as well as 3.8.7.

Any thoughts?


Have you read the log? It's pretty clear. Message is encrypted for two
recipients. You have required key in the keyring, but you didn't
provide passphrase. You either use passphraseless keys, use gpg-agent
or set passphrase in RT config.



Hi, Ruslan,

I have definitely read the log. Several times...
As I have said, I am using the gpg-agent and in my configuration the 
gpg-agent happily provides a password for RT when signing the message 
(the same operation as decrypting) but fails in this case, i.e. there is 
some problem when retrieving the passphrase for decrypting purposes 
using gpg-agent. It can either be a configuration error or a bug - I 
will probably hunt it down someday no matter what it is, but it would 
help me to hear whether there is someone who actually has it working in 
a setup like mine.


Martin

RT Training Sessions (http://bestpractical.com/services/training.html)
* Boston  March 5  6, 2012