Hi,
when a user responds to a ticket at our site, the message is forwarded
to all interested parties and the user’s name and email is untouched
(i.e. no ‘via RT’, changed mail or anything else).
We would like to enable default signing, but there is a problem with
those mails. As they have an email address the RT does not have the
secret key for, they are not sent.
We in fact only need to enable default signing for messages created via
web interface. Is there some clean way to do it? I know that I can hack
the SignEncryptWidget and hardcode the Sign value there, thus forcing
the signing only in the web interface, but this does not seem like a
long-term solution.
Do you have any idea for clean solution?
Thanks,
Martin
when a user responds to a ticket at our site, the message is forwarded
to all interested parties and the user’s name and email is untouched
(i.e. no ‘via RT’, changed mail or anything else).
This behaviour is strange. Why are you setting From: to individual
email addresses instead of back into RT?
We would like to enable default signing, but there is a problem with
those mails. As they have an email address the RT does not have the
secret key for, they are not sent.
We in fact only need to enable default signing for messages created via
web interface. Is there some clean way to do it? I know that I can hack
the SignEncryptWidget and hardcode the Sign value there, thus forcing
the signing only in the web interface, but this does not seem like a
long-term solution.
Do you have any idea for clean solution?
Use a small bit of javascript in a callback to twiddle the Sign checkbox
on update pages. Clean customization, no need to hack up core components.
when a user responds to a ticket at our site, the message is forwarded
to all interested parties and the user’s name and email is untouched
(i.e. no ‘via RT’, changed mail or anything else).
This behaviour is strange. Why are you setting From: to individual
email addresses instead of back into RT?
Hi Thomas,
at first we used the ‘name via RT our.rt@addr.es’ and then the ‘name
our.rt@addr.es’ pattern, but in both cases our users were unhappy,
because their addressbooks in mail clients started to grow with
duplicate entries for each involved identity. And as we wanted to keep
the name in the header for clarity, using individual addresses seemed
like the only option.
Each message sent from our RT has its address in the reply-to header and
users learned (almost) not to use reply-all but only reply and
reply-to-conference. So far it is working to (almost) everyone’s liking
and the signing and occasional doubling of mails because someone used
reply-all are our only problems.
Do you have any idea for clean solution?
Use a small bit of javascript in a callback to twiddle the Sign checkbox
on update pages. Clean customization, no need to hack up core components.
Hmm, that sounds like the most clean solution. The ‘AfterGnuPG’ callback
is going to be my friend. Thank you for the hint.
Cheers,
Martin