CommandBy Mail question about vcards

To list,

I know that RT has a configuration that allows one to include v-cards in
replies. That alone implies that RT has no problem with v-cards coming in
with an email. However, since we installed “CommandByMail” we occasionally
get a set of error messages like below:

Failed command 'version: 2.1’
Error message: Command ‘version’ is unknown

Failed command 'end: vcard’
Error message: Command ‘end’ is unknown

I was wondering if anyone knew of a command or configuration or any setting
in CommandByMail or TakeAction that would resolve this issue?

Has anyone else run into this problem?

I only have a few customers that do this, but because they are in a highly
sensitive area, they always include signitures on their email and I can’t
ask them to stop it just for RT.

Thanks for your consideration on this.

Kenn
LBNL

I know that RT has a configuration that allows one to include v-cards in replies.

It does?

That alone
implies that RT has no problem with v-cards coming in with an email. However, since we
installed “CommandByMail” we occasionally get a set of error messages like below:

Failed command 'version: 2.1’
Error message: Command ‘version’ is unknown

Failed command 'end: vcard’
Error message: Command ‘end’ is unknown

I was wondering if anyone knew of a command or configuration or any setting in CommandByMail
or TakeAction that would resolve this issue?

Has anyone else run into this problem?

I only have a few customers that do this, but because they are in a highly sensitive area,
they always include signitures on their email and I can’t ask them to stop it just for RT.

Might I suggest the $CommandByMailGroup config option that limits use
of the plugin to a single group of power users?

-kevin

Kevin,

Obviously, I could be wrong, but I thought “Set($MessageBoxIncludeSignature,
1);
” was to allow the passing along of the v-card in a reply.

As to your suggestion on using a group filter, I had first thought of that,
but my problem is that these “signiture card users” exist sporadically
throughout several groups that correspond on RT tickets involving Human
Resources and Payroll requests. The HAVE to use RT and they send out too
much email everywhere else using their signiture cards for me to ask them to
turn it off just when corresponding to email to/from RT. It would get too
confusing and inevitably someone would forget and then we get another error
situation. I was hoping it would be a simple patch to examine the email
for a v-card and simply ignore/bypass it just like it does a regular email
with no CBM commands. If not, then we will just have to deal with it. It
just looks bad from the Users perspective (you know how they don’t
understand when you tell them it’s part of the system ;-).

Anyway, at least I know where it’s coming from. Not knowing for me is like
watching a movie (I’m an AVID movie watcher) with no plot (he he).

Thanks for your time and consideration on this.

Kenn
LBNLOn Fri, Aug 20, 2010 at 10:22 AM, Kevin Falcone falcone@bestpractical.comwrote:

On Fri, Aug 20, 2010 at 09:08:47AM -0700, Kenneth Crocker wrote:

I know that RT has a configuration that allows one to include v-cards
in replies.

It does?

That alone
implies that RT has no problem with v-cards coming in with an email.
However, since we
installed “CommandByMail” we occasionally get a set of error messages
like below:

Failed command 'version: 2.1’
Error message: Command ‘version’ is unknown

Failed command 'end: vcard’
Error message: Command ‘end’ is unknown

I was wondering if anyone knew of a command or configuration or any
setting in CommandByMail
or TakeAction that would resolve this issue?

Has anyone else run into this problem?

I only have a few customers that do this, but because they are in a
highly sensitive area,
they always include signitures on their email and I can’t ask them to
stop it just for RT.

Might I suggest the $CommandByMailGroup config option that limits use
of the plugin to a single group of power users?

-kevin

RT Training in Washington DC, USA on Oct 25 & 26 2010
Last one this year – Learn how to get the most out of RT!